[mh] Experiences with Misterhouse V6 and Home Assistant

Giles Godart-Brown <[email protected]> Sat, 30 Nov 2024 10:39:42 +0000
Newsgroups gmane.comp.misc.misterhouse.user
Message-ID <[email protected]>
This is a multi-part message in MIME format.
--===============0533817290223832680==
Content-Type: multipart/alternative;
 boundary="------------0qIV0EtaojCkCWfVAjx0wjQw"
Content-Language: en-GB

This is a multi-part message in MIME format.
--------------0qIV0EtaojCkCWfVAjx0wjQw
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

First can I thank everyone involved in getting V6 out, the migration 
went flawlessly.

I have made the following observations/requests following the upgrade 
and starting to use Home Assistant for its UI and integration to devices 
MH hasn't been linked to (yet)

  * I have 73 Tasmota/MQTT devices and have found that, for no apparent
    reason, they don't all get discovered by HA ,so for those I have
    kept them in MH and published their state to HA for its UI.
  * I needed to edit Tasmota_HTTP_Item.pm to add my addition to prevent
    it attempting to contact devices that are offline or unplugged (see
    below), perhaps for a future enhancement?
  * Be aware that when MH starts, Tasmota devices that are controlled by
    HA may well have their state set to UNKNOWN if HA hasn't contacted
    them yet, I have a change trigger  in MH to set these to off pro-tem.
  * I wanted to publish temperature values from MH to HA, thanks to Dave
    for adding support for numbers with a range and an increment.
  * Thanks also to Dave for pointing out that MH objects that have
    set_states will pass these over to an HA select item and that you do
    need a #noloop at the end of your CODE lines in items.mht
  * If you want to publish mode_occupied from MH to HA, you need to
    define it in your items.mht, you cannot rely on
    mh/code/common/mh_control.pl, this probably applies to all objects
    defined there.
  * I'd like to be able to get HA helpers into MH objects, notably a
    button and a toggle. I've not had much time to investigate this, but
    if anyone has a pointer, please let me know.

My next challenge is to get the HA restful API to work so I can add HA 
buttons that run MH subroutines.

Thanks Again

Giles

p.s.
In my implementation, if MH fails to connect to a Tasmota HTTP device, 
it sets a status flag to offline, I have a report that allows me to set 
these to unplugged for devices I know aren't currently connected, e.g. 
the Christmas tree lights or the fans in winter.  This prevents it 
getting stuck when I run a command to say turn off all the lights.

I also use static IP addresses everywhere because MDNS was causing my 
Sky fibre router to reboot about 6 or 7 time a day.
--------------0qIV0EtaojCkCWfVAjx0wjQw
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <font face="Calibri" size="4">First can I thank everyone involved in
      getting V6 out, the migration went flawlessly. <br>
      <br>
      I have made the following observations/requests following the
      upgrade and starting to use Home Assistant for its UI and
      integration to devices MH hasn't been linked to (yet)<br>
    </font>
    <ul>
      <li><font face="Calibri" size="4">I have 73 Tasmota/MQTT devices
          and have found that, for no apparent reason, they don't all
          get discovered by HA ,so for those I have kept them in MH and
          published their state to HA for its UI.</font></li>
      <li><font face="Calibri" size="4">I needed to edit
          Tasmota_HTTP_Item.pm to add my addition to prevent it
          attempting to contact devices that are offline or unplugged
          (see below), perhaps for a future enhancement?</font></li>
      <li><font face="Calibri" size="4">Be aware that when MH starts,
          Tasmota devices that are controlled by HA may well have their
          state set to UNKNOWN if HA hasn't contacted them yet, I have a
          change trigger  in MH to set these to off pro-tem.<br>
        </font></li>
      <li><font face="Calibri" size="4">I wanted to publish temperature
          values from MH to HA, thanks to Dave for adding support for
          numbers with a range and an increment.</font></li>
      <li><font face="Calibri" size="4">Thanks also to Dave for pointing
          out that MH objects that have set_states will pass these over
          to an HA select item and that you do need a #noloop at the end
          of your CODE lines in items.mht<br>
        </font></li>
      <li><font face="Calibri" size="4">If you want to publish
          mode_occupied from MH to HA, you need to define it in your
          items.mht, you cannot rely on mh/code/common/mh_control.pl,
          this probably applies </font><font face="Calibri" size="4">
          to </font><font face="Calibri" size="4">all objects defined
          there.</font></li>
      <li><font face="Calibri" size="4">I'd like to be able to get HA
          helpers into MH objects, notably a button and a toggle. I've
          not had much time to investigate this, but if anyone has a
          pointer, please let me know.<br>
        </font></li>
    </ul>
    <p><font face="Calibri" size="4">My next challenge is to get the HA
        restful API to work so I can add HA buttons that run MH
        subroutines.<br>
      </font></p>
    <p><font face="Calibri" size="4">Thanks Again <br>
      </font></p>
    <p><font face="Calibri" size="4">Giles</font></p>
    <font size="4">p.s.<br>
      In my implementation, if MH fails to connect to a Tasmota HTTP
      device, it sets a status flag to offline, I have a report that
      allows me to set these to unplugged for devices I know aren't
      currently connected, e.g. the Christmas tree lights or the fans in
      winter.  This prevents it getting stuck when I run a command to
      say turn off all the lights.<br>
      <br>
      I also use static IP addresses everywhere because MDNS was causing
      my Sky fibre router to reboot about 6 or 7 time a day.<br>
    </font>
  </body>
</html>

--------------0qIV0EtaojCkCWfVAjx0wjQw--


--===============0533817290223832680==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============0533817290223832680==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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


--===============0533817290223832680==--