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

On 3/29/24 08:22, H Plato wrote:
> My ask is that if there are any code updates out there that folks want to include, to put in a pull request so we can capture them. Also, if anyone can update to master for any testing, that would be great as well.

Can anybody help me with GitHub? One of my pull requests is trying to 
suck in irrelevant changes from another.

So I fixed a minor detail in the MH master branch and submitted a PR 
(call it "PR#1"). Now I have code in a much different and unrelated area 
that I also want to submit ("PR#2). But since PR#1 hasn't been committed 
upstream yet, PR#2 is trying to also include PR#1 as part of the pull 
request. PR#1 affected one file. PR#2 should affect two other files, but 
is trying to include all three. How do I send H Plato a PR#2 that 
doesn't include files from PR#1?

               -Brian M

With the addition of HA_Item, I’ve also updated hollie master with some of my changes. It’s been a long long time since a release, so I think it’s time. I’ll work through the (well documented, thanks Lieven!) process over the next week of so. My ask is that if there are any code updates out there that folks want to include, to put in a pull request so we can capture them. Also, if anyone can update to master for any testing, that would be great as well.

Based on some of the last messages, I like the idea of leveraging MH for logic and ease of automations, but looking to use HomeAssistant for UI and device management in the future. I’m excited to try out Dave’s module and to start redesigning my home automation architecture. Things like my evapotranspiration calculations, I’d leave in MH, but won’t have to update device modules like raZberry, nanoleaf, yeelights, etc… in the future.

howard

I’d be interested in your HA_Item.pm module

From: Dave Neudoerffer <da...@ne...>
Sent: Monday, March 25, 2024 10:34 AM
To: H Plato <hp...@gm...>
Cc: misterhouse list <mis...@li...>
Subject: Re: [mh] MH & HA - Integration? Migration?

I have worked on this quite a bit over the past several months.  I have 3 separate HA/MH installations.  I have been using MH for many years, but my son convinced me to add HA into the mix, for exactly the reasons you state.

As I did a lot of the work on MQTT for MH, I started with an MQTT solution.  However, HA does not publish discovery nor support commands on its entities via MQTT.  So I used the REST API to get a round trip  -- commands and some discovery via the REST API, state change via MQTT.  This was pretty clumsy still.  So I have more recently implemented a fairly simple HA_Item.pm module that uses the HA Websocket API -- the websocket API hooks right into the event bus in HA, so you get everything.  I was giving it some time to settle, and wasn't sure whether anyone else would be interested, but I am happy to share the module.  Or I could put together an MH push, but that would take me a day or two.

Dave

On Mon, Mar 25, 2024 at 9:46 AM H Plato <hp...@gm...<mailto:hp...@gm...>> wrote:
Hello,

  Is anyone using Home Assistant (HA)? I’ve recently picked up a new new devices, and it is impressive the amount of device support available in HA. I’d rather spend my time setting up automations than developing device modules. So I’m thinking about running them in parallel, as my MH instance has lots of logic that I don’t know how to replicate in HA, as well as speech for home events, watering moisture calculations, etc… HA would be a contained VM that would hold the devices and maybe the user interface. I mainly use the floorplan IA7 interface, and I haven’t seen that in HA yet.

  Both MH and HA use MQTT, so that could be a communication option, or using web calls. I also have some older tech that still works fine (weeder and W800), which I’ll have to figure out. My hardware is also old, so I’m seeing this as an opportunity to architect a bit more of a better solution, by virtualizing everything.

  Anyone gone down any of these paths?

________________________________________________________
To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users

I used MH for about 15 years and built a lot of code specific for my needs. My biggest recommendation is to skip putting automations in the yaml files. Use node red, it’s by far the easiest way to migrate. I spent 2 weeks trying to convert using yaml and finally gave up. I installed node red and spent 1 day getting to know it and then spent 1 day converting everything I had custom in MH. HA is great but lacks saving states when restarted, otherwise I find it much superior to MH. The number of devices it supports is amazing!

Good luck!

Sent from my iPad

On Mar 25, 2024, at 9:35 AM, Dave Neudoerffer <da...@ne...> wrote:


I have worked on this quite a bit over the past several months.  I have 3 separate HA/MH installations.  I have been using MH for many years, but my son convinced me to add HA into the mix, for exactly the reasons you state.

As I did a lot of the work on MQTT for MH, I started with an MQTT solution.  However, HA does not publish discovery nor support commands on its entities via MQTT.  So I used the REST API to get a round trip  -- commands and some discovery via the REST API, state change via MQTT.  This was pretty clumsy still.  So I have more recently implemented a fairly simple HA_Item.pm module that uses the HA Websocket API -- the websocket API hooks right into the event bus in HA, so you get everything.  I was giving it some time to settle, and wasn't sure whether anyone else would be interested, but I am happy to share the module.  Or I could put together an MH push, but that would take me a day or two.

Dave

On Mon, Mar 25, 2024 at 9:46 AM H Plato <hp...@gm...<mailto:hp...@gm...>> wrote:
Hello,

  Is anyone using Home Assistant (HA)? I’ve recently picked up a new new devices, and it is impressive the amount of device support available in HA. I’d rather spend my time setting up automations than developing device modules. So I’m thinking about running them in parallel, as my MH instance has lots of logic that I don’t know how to replicate in HA, as well as speech for home events, watering moisture calculations, etc… HA would be a contained VM that would hold the devices and maybe the user interface. I mainly use the floorplan IA7 interface, and I haven’t seen that in HA yet.

  Both MH and HA use MQTT, so that could be a communication option, or using web calls. I also have some older tech that still works fine (weeder and W800), which I’ll have to figure out. My hardware is also old, so I’m seeing this as an opportunity to architect a bit more of a better solution, by virtualizing everything.

  Anyone gone down any of these paths?

________________________________________________________
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

Attached is the HA_Item.pm module.  Documentation is at the top of the file
(such as it is).  Probably drop it in your local code directory for now.
If you want to add items with a .mht file, the included
read_table_snippet.txt can be added to read_table_A.pl or your own read
table file.

I will work on cleanup and more documentation.  I will try to get a pull
request together in the next few days.  In the meantime, if anyone has
fixes or suggestions, please fire my way.

Dave



On Mon, Mar 25, 2024 at 12:16 PM <mis...@si...> wrote:

> I've been playing with HA and MH for a while, too. I have about 6 Z-wave
> switches that replaced Insteon switches, and are attached to HA now. I
> also have about 25 Insteon switches attached to MH. MH and HA update
> each other through MQTT (provided by Mosquitto). I don't think any of my
> customization code cared whether a device was still in MH or got moved
> to HA - it still controls the device by name (e.g. "$Porch_Light"), and
> still runs the same.
>
> I have about 12K lines of code in MH. Someday I may migrate it all over
> to HA, but my initial goal is similar to what others have said: migrate
> all the hardware to HA and keep the existing logic in MH. New logic will
> probably go in HA.
>
>                   -Brian M
>
> On 3/25/24 06:45, H Plato wrote:
> > Hello,
> >
> >    Is anyone using Home Assistant (HA)? I’ve recently picked up a new
> new devices, and it is impressive the amount of device support available in
> HA. I’d rather spend my time setting up automations than developing device
> modules. So I’m thinking about running them in parallel, as my MH instance
> has lots of logic that I don’t know how to replicate in HA, as well as
> speech for home events, watering moisture calculations, etc… HA would be a
> contained VM that would hold the devices and maybe the user interface. I
> mainly use the floorplan IA7 interface, and I haven’t seen that in HA yet.
> >
> >    Both MH and HA use MQTT, so that could be a communication option, or
> using web calls. I also have some older tech that still works fine (weeder
> and W800), which I’ll have to figure out. My hardware is also old, so I’m
> seeing this as an opportunity to architect a bit more of a better solution,
> by virtualizing everything.
> >
> >    Anyone gone down any of these paths?
> >
> > ________________________________________________________
> > 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've been playing with HA and MH for a while, too. I have about 6 Z-wave 
switches that replaced Insteon switches, and are attached to HA now. I 
also have about 25 Insteon switches attached to MH. MH and HA update 
each other through MQTT (provided by Mosquitto). I don't think any of my 
customization code cared whether a device was still in MH or got moved 
to HA - it still controls the device by name (e.g. "$Porch_Light"), and 
still runs the same.

I have about 12K lines of code in MH. Someday I may migrate it all over 
to HA, but my initial goal is similar to what others have said: migrate 
all the hardware to HA and keep the existing logic in MH. New logic will 
probably go in HA.

                  -Brian M

On 3/25/24 06:45, H Plato wrote:
> Hello,
>
>    Is anyone using Home Assistant (HA)? I’ve recently picked up a new new devices, and it is impressive the amount of device support available in HA. I’d rather spend my time setting up automations than developing device modules. So I’m thinking about running them in parallel, as my MH instance has lots of logic that I don’t know how to replicate in HA, as well as speech for home events, watering moisture calculations, etc… HA would be a contained VM that would hold the devices and maybe the user interface. I mainly use the floorplan IA7 interface, and I haven’t seen that in HA yet.
>
>    Both MH and HA use MQTT, so that could be a communication option, or using web calls. I also have some older tech that still works fine (weeder and W800), which I’ll have to figure out. My hardware is also old, so I’m seeing this as an opportunity to architect a bit more of a better solution, by virtualizing everything.
>
>    Anyone gone down any of these paths?
>
> ________________________________________________________
> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>

hi 
i moved to HA last year and never regret it
from my perspective i found no reason to keep both platforms as long as everything was migrated to HA
and yes HA has floorplan possibilities but needed some effort sompersonally did not invest to it
pls feel free to ask me any question for HA maybe you save some time / effort
cheers 
GV




On Monday, March 25, 2024, 3:47 PM, H Plato <hp...@gm...> wrote:

Hello,

  Is anyone using Home Assistant (HA)? I’ve recently picked up a new new devices, and it is impressive the amount of device support available in HA. I’d rather spend my time setting up automations than developing device modules. So I’m thinking about running them in parallel, as my MH instance has lots of logic that I don’t know how to replicate in HA, as well as speech for home events, watering moisture calculations, etc… HA would be a contained VM that would hold the devices and maybe the user interface. I mainly use the floorplan IA7 interface, and I haven’t seen that in HA yet.

  Both MH and HA use MQTT, so that could be a communication option, or using web calls. I also have some older tech that still works fine (weeder and W800), which I’ll have to figure out. My hardware is also old, so I’m seeing this as an opportunity to architect a bit more of a better solution, by virtualizing everything. 

  Anyone gone down any of these paths?

________________________________________________________
To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users

That’s my thinking as well. Get separation with devices and logic, and have MH as the automation engine. I’ve used Node Red before, but as Dave mentioned, I’m also old and the automation and perl rules works really well. MH just doesn’t have the device support and interface optimizations.  

Once everything is separated and virtualized, then other options like migrating logic to another platform could be simplified. Good advice though, I’ll ignore the yaml and look to automate later.


> On Mar 25, 2024, at 9:19 AM, Dave Neudoerffer <da...@ne...> wrote:
> 
> I have tried yaml, nodered and app daemon (python code) for automations in HA. But I am old, and have worked on my perl code in MH for a lot of years. Now all that code still works great even with the devices in HA.  
> 
> My son ended up doing his HA automations using the websocket API from a program he wrote in RUST (after also trying most of the HA automation options). I am just fine doing them in perl, and MH seems like a reasonable place to host them. 
> 
> On Mon, Mar 25, 2024, 11:05 AM Dean Junk <dea...@ms... <mailto:dea...@ms...>> wrote:
> I used MH for about 15 years and built a lot of code specific for my needs. My biggest recommendation is to skip putting automations in the yaml files. Use node red, it’s by far the easiest way to migrate. I spent 2 weeks trying to convert using yaml and finally gave up. I installed node red and spent 1 day getting to know it and then spent 1 day converting everything I had custom in MH. HA is great but lacks saving states when restarted, otherwise I find it much superior to MH. The number of devices it supports is amazing! 
> 
> Good luck!
> 
> Sent from my iPad
> 
>> On Mar 25, 2024, at 9:35 AM, Dave Neudoerffer <da...@ne... <mailto:da...@ne...>> wrote:
>> 
>> 
>> I have worked on this quite a bit over the past several months.  I have 3 separate HA/MH installations.  I have been using MH for many years, but my son convinced me to add HA into the mix, for exactly the reasons you state.  
>> 
>> As I did a lot of the work on MQTT for MH, I started with an MQTT solution.  However, HA does not publish discovery nor support commands on its entities via MQTT.  So I used the REST API to get a round trip  -- commands and some discovery via the REST API, state change via MQTT.  This was pretty clumsy still.  So I have more recently implemented a fairly simple HA_Item.pm module that uses the HA Websocket API -- the websocket API hooks right into the event bus in HA, so you get everything.  I was giving it some time to settle, and wasn't sure whether anyone else would be interested, but I am happy to share the module.  Or I could put together an MH push, but that would take me a day or two.
>> 
>> Dave
>> 
>> On Mon, Mar 25, 2024 at 9:46 AM H Plato <hp...@gm... <mailto:hp...@gm...>> wrote:
>> Hello,
>> 
>>   Is anyone using Home Assistant (HA)? I’ve recently picked up a new new devices, and it is impressive the amount of device support available in HA. I’d rather spend my time setting up automations than developing device modules. So I’m thinking about running them in parallel, as my MH instance has lots of logic that I don’t know how to replicate in HA, as well as speech for home events, watering moisture calculations, etc… HA would be a contained VM that would hold the devices and maybe the user interface. I mainly use the floorplan IA7 interface, and I haven’t seen that in HA yet.
>> 
>>   Both MH and HA use MQTT, so that could be a communication option, or using web calls. I also have some older tech that still works fine (weeder and W800), which I’ll have to figure out. My hardware is also old, so I’m seeing this as an opportunity to architect a bit more of a better solution, by virtualizing everything. 
>> 
>>   Anyone gone down any of these paths?
>> 
>> ________________________________________________________
>> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>> 
>> ________________________________________________________
>> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>> 

Thats great Dave. Thank you.

Insteon is really reliable - the only issue I have is programming keypadlincs. The aldb updates often timeout, so the most reliable and quickest way to update them is to physically remove all the switches and the keypadlinc and connect them to a ‘wiring harness’ type box. A plastic 4 gang box with quick connects. Then I plug that into the same outlet as the PLM, and the aldb can then get updated properly. Take about an hour, but will work.

I think I can do USB passthrough for my serial items, has anyone figured out remote sound? Currently I have an 8 port PCI sound card that I use alsa devices for each room and the ‘aplay’ command to play the festival file. I have an 8 port Raspberry Pi HAT that I was going to use, but don’t know how to send sound remotely. This would remove the PCI card dependancy allowing me to create a proper MH VM.

> On Mar 25, 2024, at 9:12 AM, Dave Neudoerffer <da...@ne...> wrote:
> 
> I do use insteon extensively. I use the mh support for insteon as there have been some reported issues with the ha insteon support. I also tried insteonmqtt for a while but prefer the support in MH, partly because I am familiar with the code, but also it works very well. I publish whatever devices in MH I choose via mqtt. That way HA has full control as well.  Then I can use whichever interface I choose. I also publish most devices to Google so I can control via voice or Google home. 
> 
> My setups are all a mix of devices in MH and HA. For a while, I had some devices that were Google only and used an open source project to send text that got converted to Google voice commands. (Have an MH module for that too). That worked well but, believe it or not, but felt pretty hokey, so I have recently moved those devices into HA (mostly with the HA tuya plugin). 
> 
> I am out doing some errands but will attach the HA module to this thread later today. 
> 
> I will start working on a bit of doc before I submit a push :-)
> 
> Dave
> 
> On Mon, Mar 25, 2024, 10:57 AM H Plato <hp...@gm... <mailto:hp...@gm...>> wrote:
> Thanks Dave. I’m thinking about migrating devices to HA, and then complementing with MH for my light events, speech events, etc… I would be really interested in testing out the module. If you put in a pull request, might be a good time to gather everything in master for a release. Do you use insteon at all? I see there is an insteon module, and would be great to have an updated code base.
> 
> 
> 
>> On Mar 25, 2024, at 8:33 AM, Dave Neudoerffer <da...@ne... <mailto:da...@ne...>> wrote:
>> 
>> I have worked on this quite a bit over the past several months.  I have 3 separate HA/MH installations.  I have been using MH for many years, but my son convinced me to add HA into the mix, for exactly the reasons you state.  
>> 
>> As I did a lot of the work on MQTT for MH, I started with an MQTT solution.  However, HA does not publish discovery nor support commands on its entities via MQTT.  So I used the REST API to get a round trip  -- commands and some discovery via the REST API, state change via MQTT.  This was pretty clumsy still.  So I have more recently implemented a fairly simple HA_Item.pm module that uses the HA Websocket API -- the websocket API hooks right into the event bus in HA, so you get everything.  I was giving it some time to settle, and wasn't sure whether anyone else would be interested, but I am happy to share the module.  Or I could put together an MH push, but that would take me a day or two.
>> 
>> Dave
>> 
>> On Mon, Mar 25, 2024 at 9:46 AM H Plato <hp...@gm... <mailto:hp...@gm...>> wrote:
>> Hello,
>> 
>>   Is anyone using Home Assistant (HA)? I’ve recently picked up a new new devices, and it is impressive the amount of device support available in HA. I’d rather spend my time setting up automations than developing device modules. So I’m thinking about running them in parallel, as my MH instance has lots of logic that I don’t know how to replicate in HA, as well as speech for home events, watering moisture calculations, etc… HA would be a contained VM that would hold the devices and maybe the user interface. I mainly use the floorplan IA7 interface, and I haven’t seen that in HA yet.
>> 
>>   Both MH and HA use MQTT, so that could be a communication option, or using web calls. I also have some older tech that still works fine (weeder and W800), which I’ll have to figure out. My hardware is also old, so I’m seeing this as an opportunity to architect a bit more of a better solution, by virtualizing everything. 
>> 
>>   Anyone gone down any of these paths?
>> 
>> ________________________________________________________
>> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>> 
> 

I have tried yaml, nodered and app daemon (python code) for automations in
HA. But I am old, and have worked on my perl code in MH for a lot of years.
Now all that code still works great even with the devices in HA.

My son ended up doing his HA automations using the websocket API from a
program he wrote in RUST (after also trying most of the HA automation
options). I am just fine doing them in perl, and MH seems like a reasonable
place to host them.

On Mon, Mar 25, 2024, 11:05 AM Dean Junk <dea...@ms...> wrote:

> I used MH for about 15 years and built a lot of code specific for my
> needs. My biggest recommendation is to skip putting automations in the yaml
> files. Use node red, it’s by far the easiest way to migrate. I spent 2
> weeks trying to convert using yaml and finally gave up. I installed node
> red and spent 1 day getting to know it and then spent 1 day converting
> everything I had custom in MH. HA is great but lacks saving states when
> restarted, otherwise I find it much superior to MH. The number of devices
> it supports is amazing!
>
> Good luck!
>
> Sent from my iPad
>
> On Mar 25, 2024, at 9:35 AM, Dave Neudoerffer <da...@ne...>
> wrote:
>
> 
> I have worked on this quite a bit over the past several months.  I have 3
> separate HA/MH installations.  I have been using MH for many years, but my
> son convinced me to add HA into the mix, for exactly the reasons you
> state.
>
> As I did a lot of the work on MQTT for MH, I started with an MQTT
> solution.  However, HA does not publish discovery nor support commands on
> its entities via MQTT.  So I used the REST API to get a round trip  --
> commands and some discovery via the REST API, state change via MQTT.  This
> was pretty clumsy still.  So I have more recently implemented a fairly
> simple HA_Item.pm module that uses the HA Websocket API -- the websocket
> API hooks right into the event bus in HA, so you get everything.  I was
> giving it some time to settle, and wasn't sure whether anyone else would be
> interested, but I am happy to share the module.  Or I could put together an
> MH push, but that would take me a day or two.
>
> Dave
>
> On Mon, Mar 25, 2024 at 9:46 AM H Plato <hp...@gm...> wrote:
>
>> Hello,
>>
>>   Is anyone using Home Assistant (HA)? I’ve recently picked up a new new
>> devices, and it is impressive the amount of device support available in HA.
>> I’d rather spend my time setting up automations than developing device
>> modules. So I’m thinking about running them in parallel, as my MH instance
>> has lots of logic that I don’t know how to replicate in HA, as well as
>> speech for home events, watering moisture calculations, etc… HA would be a
>> contained VM that would hold the devices and maybe the user interface. I
>> mainly use the floorplan IA7 interface, and I haven’t seen that in HA yet.
>>
>>   Both MH and HA use MQTT, so that could be a communication option, or
>> using web calls. I also have some older tech that still works fine (weeder
>> and W800), which I’ll have to figure out. My hardware is also old, so I’m
>> seeing this as an opportunity to architect a bit more of a better solution,
>> by virtualizing everything.
>>
>>   Anyone gone down any of these paths?
>>
>> ________________________________________________________
>> 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 do use insteon extensively. I use the mh support for insteon as there
have been some reported issues with the ha insteon support. I also tried
insteonmqtt for a while but prefer the support in MH, partly because I am
familiar with the code, but also it works very well. I publish whatever
devices in MH I choose via mqtt. That way HA has full control as well.
Then I can use whichever interface I choose. I also publish most devices to
Google so I can control via voice or Google home.

My setups are all a mix of devices in MH and HA. For a while, I had some
devices that were Google only and used an open source project to send text
that got converted to Google voice commands. (Have an MH module for that
too). That worked well but, believe it or not, but felt pretty hokey, so I
have recently moved those devices into HA (mostly with the HA tuya plugin).

I am out doing some errands but will attach the HA module to this thread
later today.

I will start working on a bit of doc before I submit a push :-)

Dave

On Mon, Mar 25, 2024, 10:57 AM H Plato <hp...@gm...> wrote:

> Thanks Dave. I’m thinking about migrating devices to HA, and then
> complementing with MH for my light events, speech events, etc… I would be
> really interested in testing out the module. If you put in a pull request,
> might be a good time to gather everything in master for a release. Do you
> use insteon at all? I see there is an insteon module, and would be great to
> have an updated code base.
>
>
>
> On Mar 25, 2024, at 8:33 AM, Dave Neudoerffer <da...@ne...>
> wrote:
>
> I have worked on this quite a bit over the past several months.  I have 3
> separate HA/MH installations.  I have been using MH for many years, but my
> son convinced me to add HA into the mix, for exactly the reasons you
> state.
>
> As I did a lot of the work on MQTT for MH, I started with an MQTT
> solution.  However, HA does not publish discovery nor support commands on
> its entities via MQTT.  So I used the REST API to get a round trip  --
> commands and some discovery via the REST API, state change via MQTT.  This
> was pretty clumsy still.  So I have more recently implemented a fairly
> simple HA_Item.pm module that uses the HA Websocket API -- the websocket
> API hooks right into the event bus in HA, so you get everything.  I was
> giving it some time to settle, and wasn't sure whether anyone else would be
> interested, but I am happy to share the module.  Or I could put together an
> MH push, but that would take me a day or two.
>
> Dave
>
> On Mon, Mar 25, 2024 at 9:46 AM H Plato <hp...@gm...> wrote:
>
>> Hello,
>>
>>   Is anyone using Home Assistant (HA)? I’ve recently picked up a new new
>> devices, and it is impressive the amount of device support available in HA.
>> I’d rather spend my time setting up automations than developing device
>> modules. So I’m thinking about running them in parallel, as my MH instance
>> has lots of logic that I don’t know how to replicate in HA, as well as
>> speech for home events, watering moisture calculations, etc… HA would be a
>> contained VM that would hold the devices and maybe the user interface. I
>> mainly use the floorplan IA7 interface, and I haven’t seen that in HA yet.
>>
>>   Both MH and HA use MQTT, so that could be a communication option, or
>> using web calls. I also have some older tech that still works fine (weeder
>> and W800), which I’ll have to figure out. My hardware is also old, so I’m
>> seeing this as an opportunity to architect a bit more of a better solution,
>> by virtualizing everything.
>>
>>   Anyone gone down any of these paths?
>>
>> ________________________________________________________
>> To unsubscribe from this list, go to:
>> https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>
>>
>

Thanks Dave. I’m thinking about migrating devices to HA, and then complementing with MH for my light events, speech events, etc… I would be really interested in testing out the module. If you put in a pull request, might be a good time to gather everything in master for a release. Do you use insteon at all? I see there is an insteon module, and would be great to have an updated code base.



> On Mar 25, 2024, at 8:33 AM, Dave Neudoerffer <da...@ne...> wrote:
> 
> I have worked on this quite a bit over the past several months.  I have 3 separate HA/MH installations.  I have been using MH for many years, but my son convinced me to add HA into the mix, for exactly the reasons you state.  
> 
> As I did a lot of the work on MQTT for MH, I started with an MQTT solution.  However, HA does not publish discovery nor support commands on its entities via MQTT.  So I used the REST API to get a round trip  -- commands and some discovery via the REST API, state change via MQTT.  This was pretty clumsy still.  So I have more recently implemented a fairly simple HA_Item.pm module that uses the HA Websocket API -- the websocket API hooks right into the event bus in HA, so you get everything.  I was giving it some time to settle, and wasn't sure whether anyone else would be interested, but I am happy to share the module.  Or I could put together an MH push, but that would take me a day or two.
> 
> Dave
> 
> On Mon, Mar 25, 2024 at 9:46 AM H Plato <hp...@gm... <mailto:hp...@gm...>> wrote:
> Hello,
> 
>   Is anyone using Home Assistant (HA)? I’ve recently picked up a new new devices, and it is impressive the amount of device support available in HA. I’d rather spend my time setting up automations than developing device modules. So I’m thinking about running them in parallel, as my MH instance has lots of logic that I don’t know how to replicate in HA, as well as speech for home events, watering moisture calculations, etc… HA would be a contained VM that would hold the devices and maybe the user interface. I mainly use the floorplan IA7 interface, and I haven’t seen that in HA yet.
> 
>   Both MH and HA use MQTT, so that could be a communication option, or using web calls. I also have some older tech that still works fine (weeder and W800), which I’ll have to figure out. My hardware is also old, so I’m seeing this as an opportunity to architect a bit more of a better solution, by virtualizing everything. 
> 
>   Anyone gone down any of these paths?
> 
> ________________________________________________________
> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
> 

I have worked on this quite a bit over the past several months.  I have 3
separate HA/MH installations.  I have been using MH for many years, but my
son convinced me to add HA into the mix, for exactly the reasons you
state.

As I did a lot of the work on MQTT for MH, I started with an MQTT
solution.  However, HA does not publish discovery nor support commands on
its entities via MQTT.  So I used the REST API to get a round trip  --
commands and some discovery via the REST API, state change via MQTT.  This
was pretty clumsy still.  So I have more recently implemented a fairly
simple HA_Item.pm module that uses the HA Websocket API -- the websocket
API hooks right into the event bus in HA, so you get everything.  I was
giving it some time to settle, and wasn't sure whether anyone else would be
interested, but I am happy to share the module.  Or I could put together an
MH push, but that would take me a day or two.

Dave

On Mon, Mar 25, 2024 at 9:46 AM H Plato <hp...@gm...> wrote:

> Hello,
>
>   Is anyone using Home Assistant (HA)? I’ve recently picked up a new new
> devices, and it is impressive the amount of device support available in HA.
> I’d rather spend my time setting up automations than developing device
> modules. So I’m thinking about running them in parallel, as my MH instance
> has lots of logic that I don’t know how to replicate in HA, as well as
> speech for home events, watering moisture calculations, etc… HA would be a
> contained VM that would hold the devices and maybe the user interface. I
> mainly use the floorplan IA7 interface, and I haven’t seen that in HA yet.
>
>   Both MH and HA use MQTT, so that could be a communication option, or
> using web calls. I also have some older tech that still works fine (weeder
> and W800), which I’ll have to figure out. My hardware is also old, so I’m
> seeing this as an opportunity to architect a bit more of a better solution,
> by virtualizing everything.
>
>   Anyone gone down any of these paths?
>
> ________________________________________________________
> To unsubscribe from this list, go to:
> https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>
>

Hello,

  Is anyone using Home Assistant (HA)? I’ve recently picked up a new new devices, and it is impressive the amount of device support available in HA. I’d rather spend my time setting up automations than developing device modules. So I’m thinking about running them in parallel, as my MH instance has lots of logic that I don’t know how to replicate in HA, as well as speech for home events, watering moisture calculations, etc… HA would be a contained VM that would hold the devices and maybe the user interface. I mainly use the floorplan IA7 interface, and I haven’t seen that in HA yet.

  Both MH and HA use MQTT, so that could be a communication option, or using web calls. I also have some older tech that still works fine (weeder and W800), which I’ll have to figure out. My hardware is also old, so I’m seeing this as an opportunity to architect a bit more of a better solution, by virtualizing everything. 

  Anyone gone down any of these paths?