misterhouse-users Mailing List for MisterHouse: Home Automation with Perl

Dave’s HA_Item has been awesome to leverage the Home Assistant device ecosystem and all my misterhouse automation logic. There have been a few enhancements in master so might be good to get a minor release out towards the end of the year.

I’ve been looking at the Home Assistant integrations wanted to fix an integration that doesn’t support one of the older devices that I have. It’s just modifying an existing integration to map a few of the fields. I am having a difficult time figuring out the information flow and learning python at the same time. Wondering if anyone on the list might have done any work on HA integrations and would be open to answering a questions that I have?

It's interesting you say that, I've noticed a lot of things about HA I
don't love and am re-considering OpenHAB.

Same deal with my KeypadLinc's for fan control, I have a bunch of custom
code that turns the right buttons on and off when controlled externally so
the keypad always stays in sync with the state of the fanlinc itself.

When i'm all done I'll probbly add a wiki page for all of it. It does seem
like keeping all the complicated logic and Insteon specific stuff in MH is
the easiest at this point.


On Mon, Aug 11, 2025 at 1:42 PM <mis...@si...> wrote:

> On 8/11/25 10:15, Spencer Ryan wrote:
> > I've finally added more Insteon gear and after giving HA and OpenHAB a
> > run, nothing deals with Insteon as well as Misterhouse.
>
> Several of us are going to HA or OpenHAB for hardware control and MH for
> logic, with MQTT as the link. I'm using OpenHAB (having perceived
> philosophical/attitude differences with HA), but I haven't done much
> with OpenHAB and Insteon yet. Currently it's only managing my Z-wave
> stuff and random other devices it understands (e.g. SleepNumber bed,
> Denon amp).
>
> I'm really liking what I've seen over the last year plus, but migrating
> all my MH-based logic to OpenHab would be a huge project, thus the
> hybrid approach. This division of work is looking very viable, but when
> I look at transferring the Insteon devices over, I'll proceed with
> caution. Thanks for the alert.
>
>
>
>
> ________________________________________________________
> To unsubscribe from this list, go to:
> https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>
>

On 8/11/25 10:15, Spencer Ryan wrote:
> I've finally added more Insteon gear and after giving HA and OpenHAB a 
> run, nothing deals with Insteon as well as Misterhouse.

Several of us are going to HA or OpenHAB for hardware control and MH for 
logic, with MQTT as the link. I'm using OpenHAB (having perceived 
philosophical/attitude differences with HA), but I haven't done much 
with OpenHAB and Insteon yet. Currently it's only managing my Z-wave 
stuff and random other devices it understands (e.g. SleepNumber bed, 
Denon amp).

I'm really liking what I've seen over the last year plus, but migrating 
all my MH-based logic to OpenHab would be a huge project, thus the 
hybrid approach. This division of work is looking very viable, but when 
I look at transferring the Insteon devices over, I'll proceed with 
caution. Thanks for the alert.

We bought a new house a few years ago right as Insteon was collapsing and I
kind of put a pause on what to load the new place with. I had misguided
high hopes for Matter device and still don't have anything that looks as
good as Insteon.

I've finally added more Insteon gear and after giving HA and OpenHAB a run,
nothing deals with Insteon as well as Misterhouse.


So I've started down the rabbit hole of making MH do everything insteon and
HA for modern creature comforts like HomeKit, etc.

HA has it's own quirks with Fans, specifically if you want a
off/low/med/high slider to show up you need to tell it the fan only has 4
states, but then the 0-100 range needs to be mapped to 0-3.

As I keep going down the hole it turns out the MQTT code in MH doesn't
support "FAN" as a type. I intend to build this in, eventually. For now
though I exposed the fan as a dimmable light, and deal with the unfun on
the HA side.

If this helps anyone at this point, I created the fan as a normal light,
with discoverable disabled, and then used MQTT Explorer to add the
autodiscover record by hand. Here's all the magic

{
  "unique_id": "insteon_51D36002",
  "name": "Master Bed Fan",
  "state_topic": "insteon/mbr_fan/state",
  "percentage_state_topic": "insteon/mbr_fan/state",
  "schema": "json",
  "command_topic": "insteon/mbr_fan/level",
  "percentage_command_topic": "insteon/mbr_fan/level",
  "platform": "fan",
  "state_value_template": "{{ value_json.state }}",
  "percentage_value_template": "{% if value_json.brightness == 100 %}3{%
elif value_json.brightness >= 50 and value_json.brightness <= 99 %}2{% elif
value_json.brightness >= 1 and value_json.brightness <= 49 %}1{% elif
value_json.brightness == 0 %}0{% endif %}",
  "command_template": "{ \"state\": \"{{ value }}\"}",
  "percentage_command_template": "{ \"state\":\"{% if value > 0 %}ON{% else
%}OFF{% endif %}\",\"brightness\":{% if value == 3 %}100{% elif value == 2
%}75{% elif value == 1 %}25{% elif value == 0 %}0{% endif %}}",
  "speed_range_max": "3"
}


I'm hoping to genericise most of that into the MH config where you'd be
able to define if you want a fan to act like a 4 speed fan or variable
(0-100%)

What was always a curious annoyance turned into a rabbit hole.

I noticed that on my FanLinc's when I would change the fan speed the
command was sent but the object in MH never got updated with the new
setting. Odd I thought but not a big deal.


Well I tried to write some automation around the fan speed changing and
none of the events would fire. This led me down the rabbit hole to discover
the code that deals with the ACK from a FanLinc was built incorrectly and
thus a Fan (Group 02) ACK would never be processed, which means MH would
never update the state of the object and thus no code that watched for it
to change would ever fire.


I fixed it.

https://github.com/hollie/misterhouse/issues/942

Please see comments in-line.
One other thing on this topic, I run masters and backups on separate 
UPSs in different parts of the house on separate Ethernet switches.  Pis 
use so little power a pretty basic UPS will keep them going for quite a 
while.

Giles

On 26/07/2025 18:31, Brian M wrote:
> TL;DR: Giles described implementing fail-over. Brian describes 
> diskless booting, need for replication, and split-brain issues.
>
> ----
>
> Good to hear from you.
>
> I changed the subject to aid others in finding this topic later, 
> because I think you've got some really good information in your post 
> (below) regarding MH reliability and redundancy. I think you've got a 
> great set-up, and as a result of your post I may head in the same 
> direction. Thank you!
>
> I have two critical RPis doing separate tasks, but really either one 
> could handle both workloads. I could reconfigure them as primary and 
> back-up along the lines of your set-up.
>
>
>         Diskless
>
> Personally, I've always worried about the SD card failing. As a 
> result, I've configured my two RPis to be diskless. They each PXE boot 
> from a central server that runs mdadm-style RAIDed disks. Root, /var, 
> MH's home, and everything else are provided via NFS.
GGB> Yes SD cards are very likely to fail eventually so I have moved 
over to SSDs which have become very cheap now. I mount my Pis in a stack 
with one live USB SSD connected and another cloned disk sat ready to 
connect if the master fails. rpi-clone is great for building these.  I'm 
also experimenting with USB raid arrays like this 
(https://www.maiwo360.com/2Bay/284.html) They seem to work in Raid1 
mirroring,  but I have had one disk fail that slowed the Pi down so much 
it became almost unusable. The good news was that the good disk was OK, 
and I was able to create a new mirror using dd and all is now well 
(there are no docs I can find about how to recover from failures)
>
>
>         Replication
>
> One nuisance issue I see with your set-up is that you need to make 
> sure that MH's home directory is kept in sync between the two systems. 
> A bug fix on one side needs to be applied to the other side, too. 
> Presumably you're doing some automatic Rsync's or something to handle 
> this. In my situation, I have another solution...
>
GGB> My own code is pretty stable now and I've moved a lot of things 
into a MySQL database (temp set points, links between sensors and 
actuators etc,) So I only rsync that on an ad hoc basis after I've made 
and tested changes. The MH data directory is however volatile and I've 
found for my installation an rsync every 2 minutes is sufficient.  Note 
I nfs mount the master SSD to do the sync, then unmount it.
> My MH home lives on a separate NFS share on the central server. 
> Combining my set-up with what you've done, I wouldn't even need to 
> replicate MH configuration and code data between the two RPi's data. 
> The two RPis would still need separate /, /var, etc. to maintain their 
> separate configurations, but either system could mount the MH home 
> share whenever that system became the active system. The newly active 
> system would have the latest, up-to-the-moment, MH data, right down to 
> the log files. This same technique could be applied to my OpenHab 
> system, or any other app I wanted to share.
GGB> My first NAS was quite unreliable so I tried to make the MH 
installation as autonomous as possible. Given my time again with a very 
reliable Synology NAS I would do the same as you.

>
>         Split-brain
>
> The other issue that fail-over set-ups have classically run into is 
> the "split-brain" situation, where some network issue makes the backup 
> think the main system is down when it's not, and now you have two 
> active systems trying to run the world. The DRBD project (ref: 
> https://linbit.com/drbd/) recommends an alternate communication 
> channel (another NIC, maybe some sort of usb-to-usb link, even just a 
> couple of wires between GPIO pins) solely to allow the backup to 
> confirm the main system is really out of service. MQTT's LWT ("last 
> will and testament") function might fill this role, too, if it doesn't 
> live in one of the RPIs.
>
GGB> Good idea. keepalived allows you to write your own code to detect 
if a machine is up or down with a shell script that returns success or 
failure so the options are endless.  I do make extensive use of LWT as well.
> Split-brain is not going to be a day-to-day issue, but will probably 
> happen to everyone with a failover set-up sooner or later. Have you 
> run into this, and how have you handled it?
GGB> Not yet, but no doubt it will bite me one day.
>
>
>         Home Assistant
>
> Re HA: I went with OpenHab because I perceived HA  to have a "My way 
> or the highway" attitude, and their installation models didn't match 
> my use case. OpenHab has a smaller community, to be sure, but I'm 
> pleased. I never used HA, so I don't know the reality of HA and I 
> can't really compare them.
>
>
>         ---
>
> Some day I'll learn to write a short post, but apparently not today. :-/
GGB> :-)
>
> Thanks again for your post. Great stuff there.
>
>                       -Brian M.
>
>
>
> On 7/26/25 03:14, Giles Godart-Brown wrote:
>> Hello Brian
>>
>> Long time.
>>
>> I don't think I can answer your question, but I have now changed the 
>> way I use Misterhouse to increase reliability as follows;
>>
>>   * Complex logic - keep in Misterhouse
>>   * Simple logic (like timers and pirs switching lights) - use
>>     Tasmota's rules wherever possible
>>   * Comms protocol - Mostly MQTT via mosquitto
>>   * UI - Home Assistant
>>   * Interface to difficult devices (like tuya) - Home Assistant
>>   * Voice commands - Alexa - to HA - to MH
>>
>> I've also discovered the pi keepalive daemon 
>> (https://github.com/justinknguyen/Pi-Guide/blob/main/Pi-Guide/keepalived.md) 
>> which allows me to run Misterhouse (and other services) on a pair of 
>> Pis that automatically look after each other and switch if one fails 
>> but keeps a common IP address.
>> For example I was worried about mosquitto being a really important 
>> single point of failure, now I have two pis, the master is on 
>> 192.168.100.23 and the backup on 192.168.100.24 but the common 
>> address 192.168.100.25 is automatically associated with the currently 
>> running server.  All I have to do is set all my devices to look for 
>> 192.168.100.25 and keepalived looks after the routing.
>> I use the same for Wireguard VPN and Misterhouse.
>> Unfortunately Home Assistant is dropping support for native Pi OS 
>> installs, and only concentrating on HA OS which means I cannot use 
>> keepalived. For now I'm thinking I will just have to have a cold 
>> backup machine on standby with a remote power switch so I can power 
>> it up manually if the master fails.
>> Regards
>> Giles
>>
>>
>> On 26/07/2025 08:11, Brian M wrote:
>>> I'm diving into so-called voice commands for the first time, though 
>>> I'm really just using mhsend to send a command from another 
>>> computer. The basics work fine, but in one case I'd like to pass an 
>>> arbitrary file name, and have my code receive that file name. 
>>> Something like "play file <filename>" and have my code be able to 
>>> retrieve whatever was specified for <filename>. Can that be done, 
>>> and if so, what's the syntax to define the voice command with an 
>>> arbitrary string?
>>>
>>>                      -Brian M.
>>>
>>>
>>>
>>> ________________________________________________________
>>> To unsubscribe from this list, go to: 
>>> https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>>
>>
>

TL;DR: Giles described implementing fail-over. Brian describes diskless 
booting, need for replication, and split-brain issues.

----

Good to hear from you.

I changed the subject to aid others in finding this topic later, because 
I think you've got some really good information in your post (below) 
regarding MH reliability and redundancy. I think you've got a great 
set-up, and as a result of your post I may head in the same direction. 
Thank you!

I have two critical RPis doing separate tasks, but really either one 
could handle both workloads. I could reconfigure them as primary and 
back-up along the lines of your set-up.


        Diskless

Personally, I've always worried about the SD card failing. As a result, 
I've configured my two RPis to be diskless. They each PXE boot from a 
central server that runs mdadm-style RAIDed disks. Root, /var, MH's 
home, and everything else are provided via NFS.


        Replication

One nuisance issue I see with your set-up is that you need to make sure 
that MH's home directory is kept in sync between the two systems. A bug 
fix on one side needs to be applied to the other side, too. Presumably 
you're doing some automatic Rsync's or something to handle this. In my 
situation, I have another solution...

My MH home lives on a separate NFS share on the central server. 
Combining my set-up with what you've done, I wouldn't even need to 
replicate MH configuration and code data between the two RPi's data. The 
two RPis would still need separate /, /var, etc. to maintain their 
separate configurations, but either system could mount the MH home share 
whenever that system became the active system. The newly active system 
would have the latest, up-to-the-moment, MH data, right down to the log 
files. This same technique could be applied to my OpenHab system, or any 
other app I wanted to share.


        Split-brain

The other issue that fail-over set-ups have classically run into is the 
"split-brain" situation, where some network issue makes the backup think 
the main system is down when it's not, and now you have two active 
systems trying to run the world. The DRBD project (ref: 
https://linbit.com/drbd/) recommends an alternate communication channel 
(another NIC, maybe some sort of usb-to-usb link, even just a couple of 
wires between GPIO pins) solely to allow the backup to confirm the main 
system is really out of service. MQTT's LWT ("last will and testament") 
function might fill this role, too, if it doesn't live in one of the RPIs.

Split-brain is not going to be a day-to-day issue, but will probably 
happen to everyone with a failover set-up sooner or later. Have you run 
into this, and how have you handled it?


        Home Assistant

Re HA: I went with OpenHab because I perceived HA  to have a "My way or 
the highway" attitude, and their installation models didn't match my use 
case. OpenHab has a smaller community, to be sure, but I'm pleased. I 
never used HA, so I don't know the reality of HA and I can't really 
compare them.


        ---

Some day I'll learn to write a short post, but apparently not today. :-/

Thanks again for your post. Great stuff there.

                       -Brian M.



On 7/26/25 03:14, Giles Godart-Brown wrote:
> Hello Brian
>
> Long time.
>
> I don't think I can answer your question, but I have now changed the 
> way I use Misterhouse to increase reliability as follows;
>
>   * Complex logic - keep in Misterhouse
>   * Simple logic (like timers and pirs switching lights) - use
>     Tasmota's rules wherever possible
>   * Comms protocol - Mostly MQTT via mosquitto
>   * UI - Home Assistant
>   * Interface to difficult devices (like tuya) - Home Assistant
>   * Voice commands - Alexa - to HA - to MH
>
> I've also discovered the pi keepalive daemon 
> (https://github.com/justinknguyen/Pi-Guide/blob/main/Pi-Guide/keepalived.md) 
> which allows me to run Misterhouse (and other services) on a pair of 
> Pis that automatically look after each other and switch if one fails 
> but keeps a common IP address.
> For example I was worried about mosquitto being a really important 
> single point of failure, now I have two pis, the master is on 
> 192.168.100.23 and the backup on 192.168.100.24 but the common address 
> 192.168.100.25 is automatically associated with the currently running 
> server.  All I have to do is set all my devices to look for 
> 192.168.100.25 and keepalived looks after the routing.
> I use the same for Wireguard VPN and Misterhouse.
> Unfortunately Home Assistant is dropping support for native Pi OS 
> installs, and only concentrating on HA OS which means I cannot use 
> keepalived. For now I'm thinking I will just have to have a cold 
> backup machine on standby with a remote power switch so I can power it 
> up manually if the master fails.
> Regards
> Giles
>
>
> On 26/07/2025 08:11, Brian M wrote:
>> I'm diving into so-called voice commands for the first time, though 
>> I'm really just using mhsend to send a command from another computer. 
>> The basics work fine, but in one case I'd like to pass an arbitrary 
>> file name, and have my code receive that file name. Something like 
>> "play file <filename>" and have my code be able to retrieve whatever 
>> was specified for <filename>. Can that be done, and if so, what's the 
>> syntax to define the voice command with an arbitrary string?
>>
>>                      -Brian M.
>>
>>
>>
>> ________________________________________________________
>> To unsubscribe from this list, go to: 
>> https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>
>

Hello Brian

Long time.

I don't think I can answer your question, but I have now changed the way 
I use Misterhouse to increase reliability as follows;

  * Complex logic - keep in Misterhouse
  * Simple logic (like timers and pirs switching lights) - use Tasmota's
    rules wherever possible
  * Comms protocol - Mostly MQTT via mosquitto
  * UI - Home Assistant
  * Interface to difficult devices (like tuya) - Home Assistant
  * Voice commands - Alexa - to HA - to MH

I've also discovered the pi keepalive daemon 
(https://github.com/justinknguyen/Pi-Guide/blob/main/Pi-Guide/keepalived.md) 
which allows me to run Misterhouse (and other services) on a pair of Pis 
that automatically look after each other and switch if one fails but 
keeps a common IP address.
For example I was worried about mosquitto being a really important 
single point of failure, now I have two pis, the master is on 
192.168.100.23 and the backup on 192.168.100.24 but the common address 
192.168.100.25 is automatically associated with the currently running 
server.  All I have to do is set all my devices to look for 
192.168.100.25 and keepalived looks after the routing.
I use the same for Wireguard VPN and Misterhouse.
Unfortunately Home Assistant is dropping support for native Pi OS 
installs, and only concentrating on HA OS which means I cannot use 
keepalived. For now I'm thinking I will just have to have a cold backup 
machine on standby with a remote power switch so I can power it up 
manually if the master fails.
Regards
Giles


On 26/07/2025 08:11, Brian M wrote:
> I'm diving into so-called voice commands for the first time, though 
> I'm really just using mhsend to send a command from another computer. 
> The basics work fine, but in one case I'd like to pass an arbitrary 
> file name, and have my code receive that file name. Something like 
> "play file <filename>" and have my code be able to retrieve whatever 
> was specified for <filename>. Can that be done, and if so, what's the 
> syntax to define the voice command with an arbitrary string?
>
>                      -Brian M.
>
>
>
> ________________________________________________________
> To unsubscribe from this list, go to: 
> https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>

I'm diving into so-called voice commands for the first time, though I'm 
really just using mhsend to send a command from another computer. The 
basics work fine, but in one case I'd like to pass an arbitrary file 
name, and have my code receive that file name. Something like "play file 
<filename>" and have my code be able to retrieve whatever was specified 
for <filename>. Can that be done, and if so, what's the syntax to define 
the voice command with an arbitrary string?

                      -Brian M.

Anyone using an i3 4 button keypad (KP014)?

I've got one on the way and trying to figure out if it's going to work or
if I get to put on my developer hat and write the class for it.

Thanks! That was it.

Since state_now/state_changed are null when there is no change, I just 
check if it is defined.

The following snippet shows what I ended up with:

/if (defined(state_changed $outer_front_lawn_person_status)) {
     print_log "[Frigate Front Lawn Person]: Status changed " . state 
$outer_front_lawn_person_status;
}/



On 4/22/2025 2:40 PM, Dave Neudoerffer wrote:
> I suspect state_now is firing, but your if will return false since 
> state_now returns the state which is 0....
>
> On Tue, Apr 22, 2025, 5:02 PM Brian Rudy via misterhouse-users 
> <mis...@li...> wrote:
>
>     Hi folks,
>
>     I have run into a weird issue with an mqtt_Item which, when
>     changed, returns a raw value of 0 or 1 but only fires state_now
>     and state_changed if the value is 1. However, in the object log I
>     can see that the state is actually changing between 0 and 1.
>
>     Code snippet:
>     /$outer_front_lawn_person_status = new mqtt_Item($mqtt1,
>     "frigate/Front_Lawn/person");/
>     /if (my $state = state_now $outer_front_lawn_person_status) {/
>     /    print_log "[Frigate Front Lawn Person]: Status changed $state";/
>     /}/
>
>
>     With mqtt debug enabled, I see the following in the logs:
>     /04/22/2025 10:55:35  [MQTT D1]: mqtt Rcv'd: R:0
>     T:'frigate/Front_Lawn/person' M:'0'
>     04/22/2025 10:55:35  [MQTT D1]: mqtt_Item nom to MQTT to MH
>     $outer_front_lawn_person_status::set(0, mqtt=HASH(0x5a0323b77138))
>     ...
>     04/22/2025 11:42:12  [MQTT D1]: mqtt Rcv'd: R:0
>     T:'frigate/Front_Lawn/person' M:'1'
>     04/22/2025 11:42:12  [MQTT D1]: mqtt_Item nom to MQTT to MH
>     $outer_front_lawn_person_status::set(1, mqtt=HASH(0x5a0323b77138))
>     04/22/2025 11:42:12  [Frigate Front Lawn Person]: Status changed 1/
>
>
>     In the object logs for /$outer_front_lawn_person_status/ I have:
>     /04/22/2025 11:42:12 1/
>     /04/22/2025 10:55:35 0/
>
>     /
>     /
>
>     Has anyone run into this before, and if so, how did you work
>     around it?
>
>
>     Cheers!
>     -Brian
>     ________________________________________________________
>     To unsubscribe from this list, go to:
>     https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>
>
>
> ________________________________________________________
> To unsubscribe from this list, go to:https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>

I suspect state_now is firing, but your if will return false since
state_now returns the state which is 0....

On Tue, Apr 22, 2025, 5:02 PM Brian Rudy via misterhouse-users <
mis...@li...> wrote:

> Hi folks,
>
> I have run into a weird issue with an mqtt_Item which, when changed,
> returns a raw value of 0 or 1 but only fires state_now and state_changed if
> the value is 1. However, in the object log I can see that the state is
> actually changing between 0 and 1.
> Code snippet:
> *$outer_front_lawn_person_status = new mqtt_Item($mqtt1,
> "frigate/Front_Lawn/person");*
> *if (my $state = state_now $outer_front_lawn_person_status) {*
> *    print_log "[Frigate Front Lawn Person]: Status changed $state";*
> *}*
>
>
> With mqtt debug enabled, I see the following in the logs:
>
>
>
>
>
> *04/22/2025 10:55:35  [MQTT D1]: mqtt Rcv'd: R:0
> T:'frigate/Front_Lawn/person' M:'0' 04/22/2025 10:55:35  [MQTT D1]:
> mqtt_Item nom to MQTT to MH $outer_front_lawn_person_status::set(0,
> mqtt=HASH(0x5a0323b77138)) ... 04/22/2025 11:42:12  [MQTT D1]: mqtt Rcv'd:
> R:0 T:'frigate/Front_Lawn/person' M:'1' 04/22/2025 11:42:12  [MQTT D1]:
> mqtt_Item nom to MQTT to MH $outer_front_lawn_person_status::set(1,
> mqtt=HASH(0x5a0323b77138)) 04/22/2025 11:42:12  [Frigate Front Lawn
> Person]: Status changed 1*
>
>
> In the object logs for *$outer_front_lawn_person_status* I have:
> *04/22/2025 11:42:12 1*
> *04/22/2025 10:55:35 0*
>
>
> Has anyone run into this before, and if so, how did you work around it?
>
>
> Cheers!
> -Brian
> ________________________________________________________
> To unsubscribe from this list, go to:
> https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>
>

Hi folks,

I have run into a weird issue with an mqtt_Item which, when changed, 
returns a raw value of 0 or 1 but only fires state_now and state_changed 
if the value is 1. However, in the object log I can see that the state 
is actually changing between 0 and 1.

Code snippet:
/$outer_front_lawn_person_status = new mqtt_Item($mqtt1, 
"frigate/Front_Lawn/person");/
/if (my $state = state_now $outer_front_lawn_person_status) {/
/    print_log "[Frigate Front Lawn Person]: Status changed $state";/
/}/


With mqtt debug enabled, I see the following in the logs:
/04/22/2025 10:55:35  [MQTT D1]: mqtt Rcv'd: R:0 
T:'frigate/Front_Lawn/person' M:'0'
04/22/2025 10:55:35  [MQTT D1]: mqtt_Item nom to MQTT to MH 
$outer_front_lawn_person_status::set(0, mqtt=HASH(0x5a0323b77138))
...
04/22/2025 11:42:12  [MQTT D1]: mqtt Rcv'd: R:0 
T:'frigate/Front_Lawn/person' M:'1'
04/22/2025 11:42:12  [MQTT D1]: mqtt_Item nom to MQTT to MH 
$outer_front_lawn_person_status::set(1, mqtt=HASH(0x5a0323b77138))
04/22/2025 11:42:12  [Frigate Front Lawn Person]: Status changed 1/


In the object logs for /$outer_front_lawn_person_status/ I have:
/04/22/2025 11:42:12 1/
/04/22/2025 10:55:35 0/

/
/

Has anyone run into this before, and if so, how did you work around it?


Cheers!
-Brian

Paul
I ran out of patience trying to keep Alexa going when Alexa seemed to be continually changing.
I switched over to HA-bridge and found it to be very reliable.
I use the http and mqtt interfaces in HA-bridge to talk to Misterhouse
Regards
Giles

> On 11 Apr 2025, at 00:30, Paul Onley via misterhouse-users <mis...@li...> wrote:
> 
> Has anyone else had all alexa functionality fail? I have deleted all devices and rerun discovery and it found none of my alexabridge items. I have not changed anything in mh in months and this has all been working fine until a couple days ago. I have not updated mh in a couple years so I believe the change is in alexa.
> 
> 
> 
> ________________________________________________________
> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users
> 

Little more information, I see the api call comming into mh from alexa 
but no matter which device I ask for I always get the same ID. Ask for 
living room light and get kitchen, ask for diningroom light and get 
kitchen.

Has anyone else had all alexa functionality fail? I have deleted all 
devices and rerun discovery and it found none of my alexabridge items. I 
have not changed anything in mh in months and this has all been working 
fine until a couple days ago. I have not updated mh in a couple years so 
I believe the change is in alexa.

A few months back I mentioned on the list that I was working on 
enhancements to mqtt_items.pm. I wanted to allow alternate topics if the 
built-in ones didn't meet local needs. Later someone PM'd me for an 
update and I had little progress to report.

I don't remember who asked, or so I can't give them an update. Instead, 
I'll just publish to the list that with the help of 
@da...@ne... and @hplato, I've published those enhancements to 
the master branch. No known changes for existing users of mqtt_items.pm, 
but there are two new optional fields available in MQTT_LOCALITEMS and 
MQTT_REMOTEITEMS. To whoever wrote to me: there you go!

                                -Brian M

Misterhouse can now use a local Large Language Model! Thanks to a recent update to HA_Item from Dave, MH can now send a 'perform action’ request to HA and then parse back the results. Master has been updated.

I found an inexpensive used nVidia 3060TI videocard, installed ollama, and connected it to HA via the HA Ollama integration.

With that backend in place, I can make email reports a bit more ‘friendly’. I send out nightly emails on plant moisture levels, which were technically acurate and boring to read. I’ve now sent that text through the LLM to make it more interesting to read. Really easy with the latest integration:

#noloop=start
my $model = "qwen2_5_7b_instruct_q8_0";
my $prompt = "Please summarize the text that follows these instructions for an email report. The text contains information about soil moisture for plants, and the battery level of the sensors. The output should be concise, friendly and easy to understand, including details on how moist the soil is and only report on battery health if it needs to be replaced with less than 50% remaining. The text also includes a date of the last update, only anything older than a day should be noted. Add a bit of humor and add in a random fun fact that has not been used before. Text is as follows:";
my $output = ""; 
#noloop=stop 

$v_print_soil_timer = new Voice_Cmd("Print [sensor1,all] timer data to the log file");
$v_print_soil_data = new Voice_Cmd("[Print,email] ecowitt sensor data");

if (my $state = said $v_print_soil_data) { 

	my $last_updated;
	my $text = "";

	my $batt1 = state $sensor1_batt ;
	my $batt2 = state $sensor2_batt ;
	my $batt3 = state $sensor3_batt ;
	my $batt4 = state $sensor4_batt ;
	
        $text .= "1 Plant moisture is " . state $sensor1_moist . " %\n";
        $text .= "1 Plant battery is " . $batt1 . " %\n";
	     $last_updated = $main::Time - $sensor1_moist->get_idle_time();
        $text .= "1 Plant Last Updated: " . time_date_stamp(2, $last_updated) . "\n\n";
        $text .= "2 Plant moisture is " . state $sensor2_moist . " %\n";
        $text .= "2 Plant battery is " . $batt2 . " %\n";
	     $last_updated = $main::Time - $sensor2_moist->get_idle_time();
        $text .= "2 Plant Last Updated: " . time_date_stamp(2, $last_updated) . "\n\n";
        $text .= "3 Plant moisture is " . state $sensor3_moist . " %\n";
        $text .= "3 Plant battery is " . $batt3 . " %\n";
	     $last_updated = $main::Time - $sensor3_moist->get_idle_time();
        $text .= "3 Plant Last Updated: " . time_date_stamp(2, $last_updated) . "\n\n";
        $text .= “4 Tree moisture is " . state $sensor4_moist . " %\n";
        $text .= “4 Tree battery is " . $batt4 . " %\n";
	     $last_updated = $main::Time - $sensor4_moist->get_idle_time();
        $text .= "4 Tree Last Updated: " . time_date_stamp(2, $last_updated) . "\n\n";
	    $text .= "\n";

   if (lc $state eq "print") {
	print $text;
   } else {
	if ($use_llm) {
		use_ha_llm($prompt,$text, $model);
	} else {
       		net_mail_send(to => ‘<email>', subject => "Plant Soil Status Report", text => $text);  
	}
   }
}

sub use_ha_llm {
	my ($prompt, $text, $model) = @_;
	$ha_house->ha_perform_action( "conversation.process", {'agent_id'=> "conversation.$model", 'text' => $prompt . " " . $text}, \&use_ha_llm_response_callback, $text );

}
sub use_ha_llm_response_callback {
    my ($success, $response, $text ) = @_;
    my $email_text = $text;
    unless ($success) {
    	&print_log( "[ecowitt.pl]: Error. Callback did not return success, error response=" . $response );
    } else {
        $email_text = $response->{response}->{speech}->{plain}->{speech};
	$email_text =~ s/[^\x00-\x7f]//g; #strip out any funny characters for sending
    }
    net_mail_send(to => ‘<email>', subject => "Plant Soil Status Report", text => $email_text);  
}

Does anyone know of light switches running Tasmota that have an received 
ETL, UL, or CSA certification *after* having had Tasmota installed? For 
light switches that run firmware, I assume that replacing the firmware 
would invalidate any prior safety certification. Any thoughts?

Smart home devices compatible with the Matter standard have garnered 
most of our attention lately, but the compelling features in the latest 
generation of Z-Wave chips convinced the IoT developer Shelly Group to 
build no fewer than 11 new products powered by Z-Wave technology. The 
new collection includes a smart plug, in-wall dimmers, relays, and 
various sensors aimed at DIYers, installers, and commercial builders. 
Citing the ability of Z-Wave 800 (aka Z-Wave Long Range or LR) chips to 
operate IoT devices over extremely long range -- up to 1 mile, line of 
sight -- while running on battery power for up to 10 years, Shelly Group 
CTO Leon Kralj said "Shelly is helping break down smart home 
connectivity barriers, empowering homeowners, security installers, and 
commercial property owners and managers with unmatched range, 
scalability, and energy efficiency to redefine their automation experience."

[...] While most homeowners won't need to worry about the number of IoT 
devices their networks can support, commercial builders will appreciate 
the scalability of Z-Wave 800-powered devices -- namely, you can deploy 
as many as 4,000 nodes on a single mesh network. That's a 20x increase 
over what was possible with previous generations of the chip. And since 
Z-Wave LR is backward compatible with those previous generations, there 
should be no worries about integrating the new devices into existing 
networks. Shelly says all 11 of its new Z-Wave 800-powered IoT devices 
will be available in the first half of 2025.
The new Shelly devices will be available in the U.S. in the first half 
of 2025.

Here's a list of the devices enhanced with the new long-range capabilities:
- Shelly Wave Plug US
- Shelly Wave Door/Window
- Shelly Wave H&T
- Shelly Wave Motion
- Shelly Wave Dimmer
- Shelly Wave Pro Dimmer 1 PM
- Shelly Wave Pro Dimmer 2 PM
- Shelly Wave 1
- Shelly Wave 1 PM
- Shelly Wave 2 PM
- Shelly Wave Shutter


-- 
Rick Steeves
https://www.irelandbybicycle.com

It's all fun and games until someone ends up wearing a cone.


-- 
Rick Steeves
https://www.irelandbybicycle.com

It's all fun and games until someone ends up wearing a cone.

I just got some new Venstar Colortouch thermostats, I have them set up in
HA and I am trying to get them set up in MH with HA_Item.

I have everything working except I get an error when I try to set the temp
set points in MH.

My ha.mht:
HA_ITEM,        thermostat,               climate,
    thermostat,                 ha,         Lower_Thermostat
HA_ITEM,        thermo_status,            climate:hvac_action,
    thermostat,                 ha,         Lower_Thermostat
HA_ITEM,        thermo_mode,              climate:hvac_mode,
    thermostat,                 ha,         Lower_Thermostat
HA_ITEM,        thermo_fan,               climate:fan_mode,
   thermostat,                 ha,         Lower_Thermostat
HA_ITEM,        thermo_setpoint_c,        climate:target_temp_low,
    thermostat,                 ha,         Lower_Thermostat
HA_ITEM,        thermo_setpoint_h,        climate:target_temp_high,
   thermostat,                 ha,         Lower_Thermostat
HA_ITEM,        thermo_preset,            climate:preset_mode,
    thermostat,                 ha,         Lower_Thermostat
HA_ITEM,        thermo_temp,              climate:current_temperature,
    thermostat,                 ha,         Lower_Thermostat
HA_ITEM,        thermo_humidity,          climate:current_humidity,
   thermostat,                 ha,         Lower_Thermostat


When I set the $thermo_setpoint_c in the MH web or I set it with
$thermo_setpoint_c->set($spc); I get the error below:

Use of uninitialized value $action in pattern match (m//) at
/opt/misterhouse/mh/bin/../lib/HA_Item.pm line 1362.
Use of uninitialized value $action in pattern match (m//) at
/opt/misterhouse/mh/bin/../lib/HA_Item.pm line 1366.
12/05/24 01:06:32 PM [HA_Server ERROR]: Received FAILURE on request 29:
$VAR1 = {
          'success' => bless( do{\(my $o = 0)}, 'JSON::PP::Boolean' ),
          'type' => 'result',
          'error' => {
                       'message' => 'expected str for dictionary value @
data[\'service\']. Got None',
                       'code' => 'invalid_format'
                     },
          'id' => 29
        };


-Wayne

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr">Sorry, but this is beyond me, I’ve only just started using HA, haven’t used scenes and , living in the UK we don’t need fans very often :-)</div><div dir="ltr">In my implementation all I needed was the states to match on both ha and mh so I could continue to use mh for the complicated logic I have built over the years, but use HA as an interface to new devices like Tuya and to create a fresh UI.</div><div dir="ltr">I’ll defer to others with more experience</div><div dir="ltr">Sorry I cannot be more helpful</div><div dir="ltr">Giles</div><div dir="ltr"><br><blockquote type="cite">On 5 Dec 2024, at 03:17, Spencer Ryan &lt;sry...@gm...&gt; wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div>Thanks Giles,</div><div><br></div><div>Is there any built in functionality to have status not match the control object like in the code I shared? For example when HA turns a FanLinc on it's really going to trigger a scene so that the KPL tied to the FanLinc also shows correct status, however when reading the status back into HA you don't want to read the scene, but the device itself. <br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Wed, Dec 4, 2024 at 6:05 PM Giles Godart-Brown &lt;<a href="mailto:ggo...@gm...">ggo...@gm...</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>

  
    
  
  <div>
    <font size="4" face="Calibri">The bidirectional bit between
      Misterhouse and Home Assistant via MQTT is included in the latest
      master release. <br>
      Your items.mht looks like this,&nbsp; (substitute your IP addresses and
      HA API key)<br>
      <br>
    </font>#########################################################################################################<br>
    # HA set up<br>
#########################################################################################################<br>
    # HA_SERVER,&nbsp;&nbsp;&nbsp; obj name,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; address,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; keepalive,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    api_key&nbsp; &nbsp;<br>
    HA_SERVER,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ha_house,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 999.999.999.999:8123, 10,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    .............your api key from HA ...................<br>
    <br>
#########################################################################################################<br>
    # MQTT setup<br>
#########################################################################################################<br>
    MQTT_BROKER, mqtt_1, ,&nbsp;&nbsp;&nbsp; 999.999.999.999<br>
    MQTT_DISCOVERY, mqtt_disc_mqtt1,&nbsp;&nbsp;&nbsp; homeassistant, mqtt_1, publish<br>
    <br>
    So if you have any item in&nbsp; Misterhouse you will need an
    MQTT_LOCALITEM, then Misterhouse will sync this bi-directionally
    with HA, <br>
    <br>
    GENERIC,&nbsp;&nbsp;&nbsp; Lounge_comfort_temp,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Lounge|Comfort_temp<br>
    #MQTT_LOCALITEM, &lt;mh-mqtt-object&gt;, &lt;mh-object-to-sync&gt;,
    &lt;mh-mqtt-broker-object&gt;, &lt;ha object type&gt;,&nbsp;
    &lt;node-id&gt;/&lt;mh-object-to-sync&gt;/+, &lt;discoverable&gt;,
    &lt;Friendly Name&gt;<br>
    MQTT_LOCALITEM, Lounge_comfort_mqtt, Lounge_comfort_temp, mqtt_1,
    number,&nbsp;&nbsp;&nbsp; mh/Lounge_comfort_temp/+, 1, Lounge Comfort<br>
    <br>
    If you want to see an HA entity in Misterhouse, you will need an
    HA_ITEM like this<br>
    <br>
    #HA_ITEM,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; object_name,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; domain[:subtype],&nbsp;&nbsp;
    ha_entity,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ha_server,&nbsp; groups, options<br>
    HA_ITEM, Lounge_TV, switch,&nbsp; lounge_tv, ha_house, groups<br>
    <br>
    <br>
    Regards<br>
    Giles<br>
    <br>
    <br>
    <div>On 04/12/2024 21:47, Spencer Ryan
      wrote:<br>
    </div>
    <blockquote type="cite">
      
      <div dir="ltr">Neither. Insteon
        (PLM)--&gt;Misterhouse&lt;--MQTT--&gt;HomeAssistant
        <div><br>
        </div>
        <div><br>
        </div>
        <div><br>
        </div>
        <div>Someone from reddit gave me some code they built to do most
          of this, and I'm about to go down the rabbit hole</div>
        <div><br>
        </div>
        <div>Here is the email from the guy along with the code he
          provided if anyone is curious</div>
        <div><br>
        </div>
        <div><a href="https://pastebin.com/wRfJYWnV" target="_blank">
" rel="nofollow">https://pastebin.com/wRfJYWnV</a><br>
          <br>
          <a href="https://pastebin.com/fumbhVzw" target="_blank">
" rel="nofollow">https://pastebin.com/fumbhVzw</a><br>
          <br>
          <a href="https://pastebin.com/pvYnr37n" target="_blank">
" rel="nofollow">https://pastebin.com/pvYnr37n</a><br>
          <br>
          <a href="https://pastebin.com/378NETi8" target="_blank">
" rel="nofollow">https://pastebin.com/378NETi8</a><br>
          <br>
          <a href="https://pastebin.com/L05ax8vf" target="_blank">" rel="nofollow">https://pastebin.com/L05ax8vf</a></div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Sun, Dec 1, 2024 at 7:43 AM
          Giles Godart-Brown &lt;<a href="mailto:ggo...@gm..." target="_blank">ggo...@gm...</a>&gt;
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div>
            <p><font size="4" face="Calibri">Ryan</font></p>
            <p><font size="4" face="Calibri">How are you doing this?</font></p>
            <p><font size="4" face="Calibri">Device &gt; MQTT &gt;
                Misterhouse <br>
              </font></p>
            <p><font size="4" face="Calibri">OR</font></p>
            <p><font size="4" face="Calibri">Device &gt; MQTT &gt; Home
                Assistant &gt; Misterhouse</font></p>
            <p><font size="4" face="Calibri">If its the former then
                please see <a href="https://github.com/hollie/misterhouse/wiki/Items-mqtt" target="_blank">
" rel="nofollow">https://github.com/hollie/misterhouse/wiki/Items-mqtt</a></font></p>
            <p><font size="4" face="Calibri">Your items.mht will need
                something like</font></p>
            <p><font size="4" face="Calibri">&lt;snip&gt;<br>
#########################################################################################################<br>
                # MQTT setup<br>
#########################################################################################################<br>
                MQTT_BROKER, mqtt_1, ,&nbsp;&nbsp;&nbsp; 192.168.100.64<br>
                MQTT_DISCOVERY, mqtt_disc_mqtt1,&nbsp;&nbsp;&nbsp; homeassistant,
                mqtt_1, publish</font></p>
            <p><font size="4" face="Calibri">#########################################################################################################<br>
                # MQTT devices<br>
#########################################################################################################<br>
              </font><font size="4" face="Calibri">MQTT_DEVICE,
                Workshop_fingerprint, Workshop|tasmota_fingerprint
                ,mqtt_1, tele/Workshop_fingerprint/SENSOR<br>
                CODE,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                $Workshop_fingerprint-&gt;{states_casesensitive} = 1;<br>
                &lt;/snip&gt;</font></p>
            <p><font size="4" face="Calibri">Then every time something
                publishes a message to </font><font size="4" face="Calibri">tele/Workshop_fingerprint/SENSOR your MH
                object </font><font size="4" face="Calibri">Workshop_fingerprint-&gt;{state}
                will be set to the message.&nbsp; <br>
                You may need to decode this as its likely to be JSON</font></p>
            <p><font size="4" face="Calibri">Note you can also use
                wildcards e.g. <br>
                &lt;snip&gt;<br>
                MQTT_DEVICE, MQTT_LWT, , mqtt_1, tele/+/LWT<br>
                &lt;/snip&gt;</font></p>
            <p><font size="4" face="Calibri">If its the latter, then you
                need to use HA_ITEM and MQTT_LOCALITEM</font></p>
            <p><font size="4" face="Calibri">Let me know if this helps<br>
              </font></p>
            <p><font size="4" face="Calibri">Giles<br>
              </font></p>
            <div>On 30/11/2024 18:48, Spencer Ryan wrote:<br>
            </div>
            <blockquote type="cite">
              <div dir="ltr">A timely email from Giles earlier today.
                <div><br>
                </div>
                <div>After my house was almost hit by lightning a few
                  months ago and frying a lot of stuff I finally got
                  around to rebuilding my Raspberry Pi's.&nbsp;</div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div>I'm all Insteon, and I wanted to give HomeAssistant
                  another go after&nbsp;trying it 5+ years ago, spoiler
                  alert, it's Insteon support still is awful.</div>
                <div><br>
                </div>
                <div>I'd like to keep MH doing all of the PLM and scene
                  building work, Someone on reddit gave me some code to
                  interface between the two but I'm looking for some
                  pointers on getting MH set up with MQTT from scratch.
                  I don't see a lot (or any?) real documentation on it.</div>
                <div><br>
                </div>
                <div>Any pointers?</div>
              </div>
              <br>
              <fieldset></fieldset>
              <br>
              <fieldset></fieldset>
              <pre>________________________________________________________
To unsubscribe from this list, go to: <a href="https://lists.sourceforge.net/lists/listinfo/misterhouse-users" target="_blank">" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/misterhouse-users</a>

</pre>
            </blockquote>
          </div>
        </blockquote>
      </div>
    </blockquote>
    <br>
  </div>

</blockquote></div>
</div></blockquote></body></html>

Thanks Giles,

Is there any built in functionality to have status not match the control
object like in the code I shared? For example when HA turns a FanLinc on
it's really going to trigger a scene so that the KPL tied to the FanLinc
also shows correct status, however when reading the status back into HA you
don't want to read the scene, but the device itself.

On Wed, Dec 4, 2024 at 6:05 PM Giles Godart-Brown <ggo...@gm...>
wrote:

> The bidirectional bit between Misterhouse and Home Assistant via MQTT is
> included in the latest master release.
> Your items.mht looks like this,  (substitute your IP addresses and HA API
> key)
>
>
> #########################################################################################################
> # HA set up
>
> #########################################################################################################
> # HA_SERVER,    obj name,       address,        keepalive,      api_key
> HA_SERVER,      ha_house,       999.999.999.999:8123, 10,
> .............your api key from HA ...................
>
>
> #########################################################################################################
> # MQTT setup
>
> #########################################################################################################
> MQTT_BROKER, mqtt_1, ,    999.999.999.999
> MQTT_DISCOVERY, mqtt_disc_mqtt1,    homeassistant, mqtt_1, publish
>
> So if you have any item in  Misterhouse you will need an MQTT_LOCALITEM,
> then Misterhouse will sync this bi-directionally with HA,
>
> GENERIC,    Lounge_comfort_temp,      Lounge|Comfort_temp
> #MQTT_LOCALITEM, <mh-mqtt-object>, <mh-object-to-sync>,
> <mh-mqtt-broker-object>, <ha object type>,
> <node-id>/<mh-object-to-sync>/+, <discoverable>, <Friendly Name>
> MQTT_LOCALITEM, Lounge_comfort_mqtt, Lounge_comfort_temp, mqtt_1,
> number,    mh/Lounge_comfort_temp/+, 1, Lounge Comfort
>
> If you want to see an HA entity in Misterhouse, you will need an HA_ITEM
> like this
>
> #HA_ITEM,       object_name,            domain[:subtype],
> ha_entity,                  ha_server,  groups, options
> HA_ITEM, Lounge_TV, switch,  lounge_tv, ha_house, groups
>
>
> Regards
> Giles
>
>
> On 04/12/2024 21:47, Spencer Ryan wrote:
>
> Neither. Insteon (PLM)-->Misterhouse<--MQTT-->HomeAssistant
>
>
>
> Someone from reddit gave me some code they built to do most of this, and
> I'm about to go down the rabbit hole
>
> Here is the email from the guy along with the code he provided if anyone
> is curious
>
> https://pastebin.com/wRfJYWnV
>
> https://pastebin.com/fumbhVzw
>
> https://pastebin.com/pvYnr37n
>
> https://pastebin.com/378NETi8
>
> https://pastebin.com/L05ax8vf
>
> On Sun, Dec 1, 2024 at 7:43 AM Giles Godart-Brown <ggo...@gm...>
> wrote:
>
>> Ryan
>>
>> How are you doing this?
>>
>> Device > MQTT > Misterhouse
>>
>> OR
>>
>> Device > MQTT > Home Assistant > Misterhouse
>>
>> If its the former then please see
>> https://github.com/hollie/misterhouse/wiki/Items-mqtt
>>
>> Your items.mht will need something like
>>
>> <snip>
>>
>> #########################################################################################################
>> # MQTT setup
>>
>> #########################################################################################################
>> MQTT_BROKER, mqtt_1, ,    192.168.100.64
>> MQTT_DISCOVERY, mqtt_disc_mqtt1,    homeassistant, mqtt_1, publish
>>
>>
>> #########################################################################################################
>> # MQTT devices
>>
>> #########################################################################################################
>> MQTT_DEVICE, Workshop_fingerprint, Workshop|tasmota_fingerprint ,mqtt_1,
>> tele/Workshop_fingerprint/SENSOR
>> CODE,          $Workshop_fingerprint->{states_casesensitive} = 1;
>> </snip>
>>
>> Then every time something publishes a message to tele/Workshop_fingerprint/SENSOR
>> your MH object Workshop_fingerprint->{state} will be set to the
>> message.
>> You may need to decode this as its likely to be JSON
>>
>> Note you can also use wildcards e.g.
>> <snip>
>> MQTT_DEVICE, MQTT_LWT, , mqtt_1, tele/+/LWT
>> </snip>
>>
>> If its the latter, then you need to use HA_ITEM and MQTT_LOCALITEM
>>
>> Let me know if this helps
>>
>> Giles
>> On 30/11/2024 18:48, Spencer Ryan wrote:
>>
>> A timely email from Giles earlier today.
>>
>> After my house was almost hit by lightning a few months ago and frying a
>> lot of stuff I finally got around to rebuilding my Raspberry Pi's.
>>
>>
>> I'm all Insteon, and I wanted to give HomeAssistant another go
>> after trying it 5+ years ago, spoiler alert, it's Insteon support still is
>> awful.
>>
>> I'd like to keep MH doing all of the PLM and scene building work, Someone
>> on reddit gave me some code to interface between the two but I'm looking
>> for some pointers on getting MH set up with MQTT from scratch. I don't see
>> a lot (or any?) real documentation on it.
>>
>> Any pointers?
>>
>>
>> ________________________________________________________
>> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>
>>
>

The bidirectional bit between Misterhouse and Home Assistant via MQTT is 
included in the latest master release.
Your items.mht looks like this,  (substitute your IP addresses and HA 
API key)

#########################################################################################################
# HA set up
#########################################################################################################
# HA_SERVER,    obj name,       address,        keepalive, api_key
HA_SERVER,      ha_house,       999.999.999.999:8123, 10, 
.............your api key from HA ...................

#########################################################################################################
# MQTT setup
#########################################################################################################
MQTT_BROKER, mqtt_1, ,    999.999.999.999
MQTT_DISCOVERY, mqtt_disc_mqtt1,    homeassistant, mqtt_1, publish

So if you have any item in  Misterhouse you will need an MQTT_LOCALITEM, 
then Misterhouse will sync this bi-directionally with HA,

GENERIC,    Lounge_comfort_temp,      Lounge|Comfort_temp
#MQTT_LOCALITEM, <mh-mqtt-object>, <mh-object-to-sync>, 
<mh-mqtt-broker-object>, <ha object type>, 
<node-id>/<mh-object-to-sync>/+, <discoverable>, <Friendly Name>
MQTT_LOCALITEM, Lounge_comfort_mqtt, Lounge_comfort_temp, mqtt_1, 
number,    mh/Lounge_comfort_temp/+, 1, Lounge Comfort

If you want to see an HA entity in Misterhouse, you will need an HA_ITEM 
like this

#HA_ITEM,       object_name,            domain[:subtype], 
ha_entity,                  ha_server,  groups, options
HA_ITEM, Lounge_TV, switch,  lounge_tv, ha_house, groups


Regards
Giles


On 04/12/2024 21:47, Spencer Ryan wrote:
> Neither. Insteon (PLM)-->Misterhouse<--MQTT-->HomeAssistant
>
>
>
> Someone from reddit gave me some code they built to do most of this, 
> and I'm about to go down the rabbit hole
>
> Here is the email from the guy along with the code he provided if 
> anyone is curious
>
> https://pastebin.com/wRfJYWnV
>
> https://pastebin.com/fumbhVzw
>
> https://pastebin.com/pvYnr37n
>
> https://pastebin.com/378NETi8
>
> https://pastebin.com/L05ax8vf
>
> On Sun, Dec 1, 2024 at 7:43 AM Giles Godart-Brown 
> <ggo...@gm...> wrote:
>
>     Ryan
>
>     How are you doing this?
>
>     Device > MQTT > Misterhouse
>
>     OR
>
>     Device > MQTT > Home Assistant > Misterhouse
>
>     If its the former then please see
>     https://github.com/hollie/misterhouse/wiki/Items-mqtt
>
>     Your items.mht will need something like
>
>     <snip>
>     #########################################################################################################
>     # MQTT setup
>     #########################################################################################################
>     MQTT_BROKER, mqtt_1, ,    192.168.100.64
>     MQTT_DISCOVERY, mqtt_disc_mqtt1,    homeassistant, mqtt_1, publish
>
>     #########################################################################################################
>     # MQTT devices
>     #########################################################################################################
>     MQTT_DEVICE, Workshop_fingerprint, Workshop|tasmota_fingerprint
>     ,mqtt_1, tele/Workshop_fingerprint/SENSOR
>     CODE, $Workshop_fingerprint->{states_casesensitive} = 1;
>     </snip>
>
>     Then every time something publishes a message to
>     tele/Workshop_fingerprint/SENSOR your MH object
>     Workshop_fingerprint->{state} will be set to the message.
>     You may need to decode this as its likely to be JSON
>
>     Note you can also use wildcards e.g.
>     <snip>
>     MQTT_DEVICE, MQTT_LWT, , mqtt_1, tele/+/LWT
>     </snip>
>
>     If its the latter, then you need to use HA_ITEM and MQTT_LOCALITEM
>
>     Let me know if this helps
>
>     Giles
>
>     On 30/11/2024 18:48, Spencer Ryan wrote:
>>     A timely email from Giles earlier today.
>>
>>     After my house was almost hit by lightning a few months ago and
>>     frying a lot of stuff I finally got around to rebuilding my
>>     Raspberry Pi's.
>>
>>
>>     I'm all Insteon, and I wanted to give HomeAssistant another go
>>     after trying it 5+ years ago, spoiler alert, it's Insteon support
>>     still is awful.
>>
>>     I'd like to keep MH doing all of the PLM and scene building work,
>>     Someone on reddit gave me some code to interface between the two
>>     but I'm looking for some pointers on getting MH set up with MQTT
>>     from scratch. I don't see a lot (or any?) real documentation on it.
>>
>>     Any pointers?
>>
>>
>>     ________________________________________________________
>>     To unsubscribe from this list, go to:https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>

Neither. Insteon (PLM)-->Misterhouse<--MQTT-->HomeAssistant



Someone from reddit gave me some code they built to do most of this, and
I'm about to go down the rabbit hole

Here is the email from the guy along with the code he provided if anyone is
curious

https://pastebin.com/wRfJYWnV

https://pastebin.com/fumbhVzw

https://pastebin.com/pvYnr37n

https://pastebin.com/378NETi8

https://pastebin.com/L05ax8vf

On Sun, Dec 1, 2024 at 7:43 AM Giles Godart-Brown <ggo...@gm...>
wrote:

> Ryan
>
> How are you doing this?
>
> Device > MQTT > Misterhouse
>
> OR
>
> Device > MQTT > Home Assistant > Misterhouse
>
> If its the former then please see
> https://github.com/hollie/misterhouse/wiki/Items-mqtt
>
> Your items.mht will need something like
>
> <snip>
>
> #########################################################################################################
> # MQTT setup
>
> #########################################################################################################
> MQTT_BROKER, mqtt_1, ,    192.168.100.64
> MQTT_DISCOVERY, mqtt_disc_mqtt1,    homeassistant, mqtt_1, publish
>
>
> #########################################################################################################
> # MQTT devices
>
> #########################################################################################################
> MQTT_DEVICE, Workshop_fingerprint, Workshop|tasmota_fingerprint ,mqtt_1,
> tele/Workshop_fingerprint/SENSOR
> CODE,          $Workshop_fingerprint->{states_casesensitive} = 1;
> </snip>
>
> Then every time something publishes a message to tele/Workshop_fingerprint/SENSOR
> your MH object Workshop_fingerprint->{state} will be set to the message.
> You may need to decode this as its likely to be JSON
>
> Note you can also use wildcards e.g.
> <snip>
> MQTT_DEVICE, MQTT_LWT, , mqtt_1, tele/+/LWT
> </snip>
>
> If its the latter, then you need to use HA_ITEM and MQTT_LOCALITEM
>
> Let me know if this helps
>
> Giles
> On 30/11/2024 18:48, Spencer Ryan wrote:
>
> A timely email from Giles earlier today.
>
> After my house was almost hit by lightning a few months ago and frying a
> lot of stuff I finally got around to rebuilding my Raspberry Pi's.
>
>
> I'm all Insteon, and I wanted to give HomeAssistant another go
> after trying it 5+ years ago, spoiler alert, it's Insteon support still is
> awful.
>
> I'd like to keep MH doing all of the PLM and scene building work, Someone
> on reddit gave me some code to interface between the two but I'm looking
> for some pointers on getting MH set up with MQTT from scratch. I don't see
> a lot (or any?) real documentation on it.
>
> Any pointers?
>
>
> ________________________________________________________
> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>
>