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

well, I've got a collection of 1-wire sensors about the house, as well 
as using 1-wire to turn on and off the relays for my speaker system, 
using the Eric Vickery 4 channel relay Board 3.1 from hobby-boards.com

Except that the board is no longer responding. And hobby-boards.com is 
also no longer (and looking through wayback, been gone a long time)

So anyone out there a) familiar with the board and b) know what a 
suitable replacement might be? It's probably been 20 years since I last 
tinkered with it.

Rick

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

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

Hi all,

Amazon decided to end-of-life the old Smart Home Skill v2 APIs in favor 
of the v3 APIs on November first of this year, so my original direct 
integration needed a bit of a refresh.

For anyone still using this, my latest forwarder Lambda and handler for 
Misterhouse can be found in my Github repo here: 
https://github.com/rudybrian/IoT-Playground

Cheers!

-Brian


On 2/3/2017 11:48 AM, Brian Rudy wrote:
> Hi Craig,
>
> I'm glad you got things up and working!
>
> The only change I had to make to http_server.pl was committed to the 
> master branch as of 7635334 
> <https://github.com/hollie/misterhouse/commit/9517046899291a6f84517d643aa08234ac4a0b8f>. 
> I discovered this when developing/testing alexa.pl using Postman, but 
> am not sure this is an issue that would manifest itself when using the 
> Lambda API proxies as I haven't dumped the headers that they are 
> sending.Before making the change, http_server.pl was stripping the 
> POST body (the JSON in this case) because it wasn't looking at the 
> correct header to get the Content-Length.
>
> What did you end up changing to get it working for you?
>
>
> On 1/31/17 18:58, Craig wrote:
>> Brian,
>>
>> Nice job putting this together. It was challenging to get it all 
>> working. I setup nginx on a raspberry pi for the reverse proxy. I 
>> can't imagine how hard it must have been to figure it out from 
>> scratch. I have followed all the steps and finally got it to work. I 
>> do have a question though.
>>
>> I kept getting errors when trying to post the discovery request. The 
>> error was due to http_server.pl <http://http_server.pl> not passing 
>> the JSON data to alexa.pl <http://alexa.pl>. I tweaked it to pass it 
>> on if the request was for bin/alexa.pl <http://alexa.pl>. Did you 
>> have to make any changes to http_server.pl <http://http_server.pl>? I 
>> would be interested what you did. Is this something that should be 
>> added to the release version of mh?
>>
>> Thanks for your work. With an echo and 3 dots, I finally have decent 
>> voice control of mh.
>>
>> -Craig
>>
>>
>> On Wed, Jan 4, 2017 at 4:28 PM, Brian Rudy <br...@pr...> wrote:
>>
>>     Hi folks,
>>
>>     Here are the full set of steps required to deploy the current
>>     working revision of the Alexa Smart Home API version of the MH
>>     integration that I have been working on. This ultimately belongs
>>     in the Wiki after development is finished. The setup is fairly
>>     involved and should only be undertaken if you have sufficient
>>     comfort in each of the functional areas. The Testing and
>>     Troubleshooting sections are incomplete, but there should be
>>     enough here to get you started.
>>
>>      1. Configuring your reverse proxy
>>           * See here:
>>             https://github.com/hollie/misterhouse/wiki/ReverseProxy
>>             <https://github.com/hollie/misterhouse/wiki/ReverseProxy>
>>      2. Adding basic authentication to your reverse proxy
>>          1. Create a password file and add a user (see
>>             https://httpd.apache.org/docs/current/programs/htpasswd.html
>>             <https://httpd.apache.org/docs/current/programs/htpasswd.html>)
>>          2. For example: htpasswd /etc/httpd/.htpasswd-users jsmith
>>          3. You will need to define the following in your config
>>              1. AuthType Basic
>>              2. AuthName "Authentication Required"
>>              3. AuthUserFile    "/etc/httpd/.htpasswd-users"
>>      3. After completing the previous two steps, you should have an
>>         Apache configuration like the following from Apache 2.2:
>>           * # Reverse proxy for Misterhouse
>>             ProxyRequests    off
>>             ProxyHTMLEnable    On
>>             ProxyPass /mh/ http://my.misterhouse.ip:8080/
>>             <http://my.misterhouse.ip:8080/>
>>             ProxyHTMLURLMap http://my.misterhouse.ip:8080
>>             <http://my.misterhouse.ip:8080> /mh
>>
>>             <Location /mh/>
>>                  AuthType Basic
>>                  AuthName "Authentication Required"
>>                  AuthUserFile    "/etc/httpd/.htpasswd-users"
>>                  Require valid-user
>>                  ProxyPassReverse    /
>>                  ProxyHTMLEnable    On
>>                  SetOutputFilter    proxy-html
>>                  ProxyHTMLURLMap    /    /mh/
>>                  ProxyHTMLURLMap /mh    /mh
>>                  RequestHeader unset    Accept-Encoding
>>              </Location>
>>      4. DDNS
>>           * If you do not have a static public IP address, you will
>>             need to use DDNS so that you can use a hostname to reach
>>             your reverse proxy. Configuration and setup of DDNS is
>>             beyond the scope of this document.
>>      5. Obtaining an SSL certificate
>>           * You will need to obtain an SSL certificate for your
>>             reverse proxy
>>           * There are many places that will happily sell you an SSL
>>             certificate, or you can use a free certificate from Let's
>>             Encrypt (https://letsencrypt.org <https://letsencrypt.org>)
>>           * Self-signed certificates may work as well, but are
>>             untested and are not recommended.
>>      6. Setting up HTTPS support on your reverse proxy
>>           * Once you have your SSL certificate, you will need to
>>             install it on your reverse proxy.
>>           * An example configuration for Apache 2.2 is shown below:
>>               o SSLCertificateFile
>>                 /etc/pki/tls/certs/my.misterhousehost.com.crt
>>                 SSLCertificateKeyFile
>>                 /etc/pki/tls/private/my.misterhousehost.com.key
>>                 SSLCertificateChainFile
>>                 /etc/pki/tls/certs/my.misterhousehost.com-chain.pem
>>      7. Firewall
>>           * Your firewall will need to forward TCP port 443 to your
>>             reverse proxy to allow the HTTPS requests through.
>>      8. Setting up Login with Amazon
>>          1. Smart Home Skills require an OAuth 2.0 provider. To
>>             simplify the integration, I recommend the use of the
>>             Login with Amazon service available in the Amazon
>>             Developer portal:
>>             https://developer.amazon.com/login-with-amazon
>>             <https://developer.amazon.com/login-with-amazon>
>>          2. Create a new security profile per the instructions here:
>>             https://stackoverflow.com/questions/37512303/whats-an-easy-way-to-setup-oauth-for-an-amazon-alexa-connected-home-skill
>>             <https://stackoverflow.com/questions/37512303/whats-an-easy-way-to-setup-oauth-for-an-amazon-alexa-connected-home-skill>
>>              1. You will need to copy the Client ID and Client Secret
>>                 values from your security profile into the Skill
>>                 Adapter settings in step 9.
>>              2. You will also need top copy the Redirect URLs
>>                 (usually there are two) from step 9 into the Web
>>                 Settings of your security profile once your Skill
>>                 Adapter is created.
>>      9. Creating the Alexa Skill
>>          1. Log in to the Amazon developer console here:
>>             https://developer.amazon.com <https://developer.amazon.com>
>>          2. Select ALEXA, and then click Get Started > under the
>>             Alexa Skills Kit
>>          3. Click Add a New Skill
>>          4. In Skill Information
>>              1. Select a Skill Type of Smart Home Skill API
>>              2. Select a name (this is arbitrary, but cannot overlap
>>                 with existing skill names)
>>              3. Click Next
>>          5. In Configuration
>>              1. Set the Authorization URL to
>>                 https://www.amazon.com/ap/oa
>>                 <https://www.amazon.com/ap/oa>
>>              2. Change the Client Id to the Client Id created in Step 8
>>              3. Create a new Scope of "profile:user_id"
>>              4. Set the Access Token URI to
>>                 https://api.amazon.com/auth/o2/token
>>                 <https://api.amazon.com/auth/o2/token>
>>              5. Set the Client Secret to the Client Secret created in
>>                 Step 8
>>              6. Copy each of the Redirect URLs to the Web Settings of
>>                 your Login With Amazon security profile from step 8
>>              7. Enter a Privacy Policy URL (this is arbitrary, but is
>>                 required for account linking)
>>              8. Click Save
>>              9. Your skill is not yet complete, as you need to enter
>>                 the Endpoint ARN you will create in step 10.
>>             10. Check the North America region and enter the ARN you
>>                 created in step 10, then click Next
>>             11. The Configuration section should now have a green
>>                 checkmark
>>             12. In Test, click Show this skill in the Alexa App
>>     10. Setting up AWS Lambda Skill Adapter Function
>>          1. Log into the AWS console: https://console.aws.amazon.com
>>             <https://console.aws.amazon.com>
>>          2. Familiarize yourself with the steps required to create a
>>             Smart Home skill as show here:
>>             https://developer.amazon.com/blogs/post/Tx34M7F8Z8U7U8B/Creating-Your-First-Alexa-Smart-Home-Skill
>>             <https://developer.amazon.com/blogs/post/Tx34M7F8Z8U7U8B/Creating-Your-First-Alexa-Smart-Home-Skill>
>>
>>              1. Note: This is only for reference, as we will be
>>                 creating a skill adapter in JavaScript with Node.js
>>          3. To create the MisterHouse forwarder function, in Lambda
>>             select Create new Function.
>>              1. Change your Region to US East (N.Virginia). This is
>>                 the only region that currently supports the Alexa
>>                 Smart Home API.
>>              2. Search for "home". This should return two blueprints.
>>                 Select the "alexa-smart-home-skill-adapter"
>>              3. Enter the Application Id from your skill created in
>>                 step 9, and select Create Trigger
>>              4. In the Configure Function screen
>>                  1. Name your function (this is arbitrary), and
>>                     update the description as you see fit
>>                  2. Replace the Lambda function code with the code
>>                     from here:
>>                     https://raw.githubusercontent.com/rudybrian/IoT-Playground/master/AWS-Lambda/MisterHouse-alexa-smart-home-skill-api-forwarder.js
>>                     <https://raw.githubusercontent.com/rudybrian/IoT-Playground/master/AWS-Lambda/MisterHouse-alexa-smart-home-skill-api-forwarder.js>
>>                  3. Edit the REMOTE_CLOUD_HOSTNAME and auth
>>                     parameters per your hostname and credentials
>>                       * For example:
>>                           o var REMOTE_CLOUD_HOSTNAME =
>>                             'my.misterhousehost.com
>>                             <http://my.misterhousehost.com>';
>>                           o auth: 'jsmith:jsmithspassword',
>>                  4. Create a new custom role
>>                      1. Select IAM Role of lambda_basic_execution
>>                      2. and a Policy Name of "Create a new Role Policy"
>>                      3. Click Allow
>>                  5. Once the custom role is created
>>                      1. Select Role: "Choose and existing role"
>>                      2. Select Existing role: "lambda_basic_execution"
>>                  6. In Advanced settings
>>                      1. Change the Memory (MB) from 512 to 128.
>>                  7. Click Next
>>              5. Click Create function
>>              6. Copy the ARN (in the upper right-hand corner of the
>>                 screen) to the Endpoint in your Skill from step 9.
>>     11. Grab a copy of the latest web/bin/alexa.pl <http://alexa.pl>
>>         from my GitHub repo here:
>>         https://raw.githubusercontent.com/rudybrian/misterhouse/add_alexa_smart_home_support/web/bin/alexa.pl
>>         <https://raw.githubusercontent.com/rudybrian/misterhouse/add_alexa_smart_home_support/web/bin/alexa.pl>
>>         and install on your MH instance.
>>          1. Edit the $list_name variable to point to the group or
>>             type of items you wish to expose to Alexa.
>>     12. Testing
>>          1. Testing web/bin/alexa.pl <http://alexa.pl>
>>              1. You can use Postman to test interaction with MisterHouse.
>>                  1. Select POST, and enter the URL on your local
>>                     network to alexa.pl <http://alexa.pl>
>>                      1. For example:
>>                         http://my.misterhouse.ip:8080/bin/alexa.pl
>>                         <http://my.misterhouse.ip:8080/bin/alexa.pl>
>>                      2. In Body
>>                          1. Select raw and JSON (application/json)
>>                          2. in the POST body enter a Discovery
>>                             request such as the following
>>                               * {
>>                                     "header": {
>>                                         "messageId":
>>                                 "6d6d6e14-8aee-473e-8c24-0d31ff9c17a2",
>>                                         "name":
>>                                 "DiscoverAppliancesRequest",
>>                                         "namespace":
>>                                 "Alexa.ConnectedHome.Discovery",
>>                                         "payloadVersion": "2"
>>                                     },
>>                                     "payload": {
>>                                         "accessToken": "blah"
>>                                     }
>>                                 }
>>                               * Click Send, and you should see a JSON
>>                                 response with an array of your
>>                                 discoveredAppliances in the payload
>>          2. Testing HTTPS
>>          3. Testing the MH reverse proxy
>>          4. Testing the Lambda skill adapter
>>              1. Log into the AWS console, and select the Lambda
>>                 function you created in step 10.
>>              2. Under the Actions drop-down, select "Configure test
>>                 event"
>>              3. In "Input test event"
>>                  1. Select Sample event template of "Alexa Smart Home
>>                     - Control"
>>                  2. In the text box, enter the same JSON you used to
>>                     test web/bin/alexa.pl <http://alexa.pl>
>>                  3. Click Save and test
>>                  4. In the response you should see the same JSON
>>                     response you saw when testing web/bin/alexa.pl
>>                     <http://alexa.pl>
>>          5. Testing from http://alexa.amazon.com/
>>             <http://alexa.amazon.com/>
>>              1. Click on Skills, then click Your Skills
>>              2. You should see the Skill you created in step 9, with
>>                 "Account linking required" next to it
>>              3. Click on your skill
>>              4. Log in with your Amazon credentials
>>                  1. After login your skill should be activated
>>              5. Go to the Smart Home section
>>              6. Click on Discover Devices (you can also ask Alexa to
>>                 discover devices)
>>                  1. You should now see the list of devices as shown
>>                     when testing the Lambda Skill adapter
>>                  2. You can now ask "Alexa turn on {friendlyName}"
>>     13. Troubleshooting
>>
>>
>>     Have fun!
>>
>>     -Brian
>>
>>
>>
>>     On 1/3/17 17:27, Brian Rudy wrote:
>>>
>>>     Hi folks,
>>>
>>>     Thanks to Wayne's hard work and the flexibility of OSS, we now
>>>     have two choices for directly integrating our Amazon Echos (and
>>>     select 3rd party devices with AVS API implementations
>>>     <https://developer.amazon.com/alexa-voice-service>) with
>>>     MisterHouse!
>>>
>>>     Since there are two separate implementations, I thought I would
>>>     provide a high-level overview of them both.
>>>
>>>     Each implementation has it's strengths and weaknesses, and you
>>>     can choose which works best for you. Both implementations
>>>     currently use the same Alexa Smart Home intent schema, which
>>>     constrains voice interaction to control devices by 'actions' of
>>>     the type on/off, percent, temperature and increase/decrease.
>>>     Voice responses are limited to "Ok" or, on error, a specific
>>>     error response. Both implementations require Internet
>>>     connectivity. Discovered devices are visible in the Smart Home
>>>     section of the Alexa app on your iOS/Android devices as well as
>>>     http://alexa.amazon.com#smart-home
>>>     <http://alexa.amazon.com#smart-home>, and can be added to groups
>>>     which allow control of multiple devices in the group with a
>>>     single intent (utterance).
>>>
>>>     Wayne's implementation emulates a Phillips Hue bridge, which
>>>     uses SSDP for device discovery over the local network (between
>>>     an Echo and MisterHouse). Since MisterHouse is emulating a Hue
>>>     bridge, other IoT devices that support interacting with Hue
>>>     lights (Google Home, Logitech Harmony, etc) should also work.
>>>     The network flow for control commands is as follows: "voice
>>>     input"->Echo (local network)->Amazon AVS (cloud)->Echo (local
>>>     network)->MisterHouse (local network)->Controlled devices
>>>     (device-specific). With this implementation you don't need to
>>>     open up your home network to inbound external access. Wayne,
>>>     please feel free to correct or fill in anything I have stated
>>>     incorrectly or might have missed :)
>>>
>>>     The implementation that I have been working on interacts
>>>     directly with Amazon's official Alexa Smart Home API and
>>>     discovers the MH-defined devices (objects) that support state
>>>     changes of the same state 'actions' supported by the Amazon
>>>     Smart Home API. This implementation works by using an AWS Lambda
>>>     hosted service that forwards all the Alexa Smart Home API
>>>     requests directly from Amazon's Voice Services through to
>>>     MisterHouse unaltered. web/bin/alexa.pl <http://alexa.pl> acts
>>>     upon these requests and responds back to the Lambda hosted
>>>     service, which in turn forwards that response back to the Smart
>>>     Home API. It requires that the Lambda hosted service is able to
>>>     reach MisterHouse via an authenticated HTTPS request. Since MH
>>>     doesn't natively support HTTPS, you will need to have an HTTPS
>>>     reverse proxy
>>>     <https://github.com/hollie/misterhouse/wiki/ReverseProxy> with
>>>     (basic) authentication at the edge of your network to handle the
>>>     requests and forward them to MH. The network flow for control
>>>     commands is as follows: "voice input"->Echo (local
>>>     network)->Amazon AVS (cloud)->AWS Lambda (cloud)->HTTPS reverse
>>>     proxy (local network)->MisterHouse (local network)->Controlled
>>>     devices (device-specific)
>>>
>>>     Cheers!
>>>     -Brian
>>>
>>>     On 12/31/16 00:25, Brian Rudy wrote:
>>>>
>>>>     Thanks to the extra time permitted by the holidays I finally
>>>>     have both the discovery and control functionality working to a
>>>>     minimal degree. The simple HTTPS forwarder AWS Lambda code (in
>>>>     JavaScript for Node.js) I am using can be found here:
>>>>     https://github.com/rudybrian/IoT-Playground/blob/master/AWS-Lambda/MisterHouse-alexa-smart-home-skill-api-forwarder.js
>>>>     <https://github.com/rudybrian/IoT-Playground/blob/master/AWS-Lambda/MisterHouse-alexa-smart-home-skill-api-forwarder.js>
>>>>
>>>>     To pair down the list of eligible devices during discovery, the
>>>>     given group (I used "Lights" for testing) object members are
>>>>     inspected for those that have possible states of "on" (for
>>>>     on/off) and 80% (for those that support percentage). These
>>>>     "actions" are provided back to the Alexa Smart Home API in the
>>>>     DiscoverAppliancesResponse. Currently I only have the turnOn
>>>>     and turnOff actions working, with the rest of the actions
>>>>     stubbed out. If you want to have a look, I have the MH code in
>>>>     my add_alexa_smart_home_support branch here:
>>>>     https://github.com/rudybrian/misterhouse/tree/add_alexa_smart_home_support
>>>>     <https://github.com/rudybrian/misterhouse/tree/add_alexa_smart_home_support>
>>>>
>>>>     To use this as-is, you will need a reverse proxy setup with
>>>>     authentication to handle the inbound HTTPS requests from AWS
>>>>     and forward them on to MH.
>>>>
>>>>     A great deal still needs to be added, but it is working, and
>>>>     seems to do so fairly well.
>>>>
>>>>
>>>>     Cheers!
>>>>     -Brian
>>>>
>>>>     On 12/26/16 16:30, Brian Rudy wrote:
>>>>>
>>>>>     Thanks Wayne,
>>>>>
>>>>>     Most aspects that power the Echo (including NLP/NLU via AVS)
>>>>>     are hosted at Amazon, so there is a certain amount of cloud
>>>>>     connectivity that is unavoidable with the Echo and kin. I too
>>>>>     would prefer hosting everything within my own private network,
>>>>>     but thus far the main thrust of commercial IoT solutions are
>>>>>     cloud-based, and it looks like that ship has sailed.
>>>>>
>>>>>     What I am looking to do would have a minimal forwarding layer
>>>>>     in AWS Lambda (currently the only supported endpoint for the
>>>>>     Smart Home skill type) and perform the rest of the logic
>>>>>     natively in Perl with MH. I was able to stub out some simple
>>>>>     simple Discovery and Control functions earlier today using the
>>>>>     Login with Amazon OAuth provider to provide account pairing
>>>>>     and a hacked up version of the Smart Home skill adapter sample
>>>>>     (which needed updating to support the current
>>>>>     Alexa.ConnectedHome message format in place of the Alexa
>>>>>     Lighting API that has now been deprecated)
>>>>>
>>>>>     I haven't figured out how to handle selective device discovery
>>>>>     either, but my current thoughts are to do this by filtering
>>>>>     out devices that are not capable of the the supported list of
>>>>>     Smart Home API 'actions' (setTargetTemperature,
>>>>>     incrementTargetTemperature, decrementTargetTemperature,
>>>>>     setPercentage, incrementPercentage, decrementPercentage,
>>>>>     turnOff, turnOn)
>>>>>
>>>>>     I'll keep fiddling with this as time permits, but am happy to
>>>>>     test anything you would like another set of eyes on.
>>>>>
>>>>>
>>>>>     Happy holidays!
>>>>>     -Brian
>>>>>
>>>>>
>>>>>     On 12/23/16 06:20, Wayne Gatlin wrote:
>>>>>>     My problem with the skills is that they have to be hosted at
>>>>>>     Amazon which means adding latency for internet traversal and
>>>>>>     being dependent on my internet connectivity for my home
>>>>>>     functions to work. I am not a fan on cloud hosting for my HA
>>>>>>     stuff.
>>>>>>
>>>>>>     I have been working on a perl implementation of the hue api
>>>>>>     emulation that is integrated into Misterhouse which means you
>>>>>>     will be able to select the objects in MH that you want to
>>>>>>     present to alexa for discovery. I haven't decided on the best
>>>>>>     way to do this yet.
>>>>>>
>>>>>>     I think the limitation is 25 devices per tcp port (emulated
>>>>>>     hue bridge), so I plan to just add more ports (configurable
>>>>>>     in mh) and look at the port the request comes in on and
>>>>>>     respond with that set of devices.
>>>>>>
>>>>>>
>>>>>>     I'll upload to git once I have something ready to start testing.
>>>>>>
>>>>>>
>>>>>>     On Thu, Dec 22, 2016 at 7:34 PM, Brian Rudy
>>>>>>     <br...@pr...> wrote:
>>>>>>
>>>>>>         Thanks Wayne,
>>>>>>
>>>>>>         I just picked up a few of the 2nd generation Echo dots to
>>>>>>         cover the house during Amazon's black Friday sale and
>>>>>>         have only just stated playing with them using the native
>>>>>>         ecobee integration and IFTTT. I have done a small amount
>>>>>>         of research into the ASK and developing Alexa skills with
>>>>>>         the skills SDK using nodejs/Lambda, but haven't been able
>>>>>>         to put much time into it yet.
>>>>>>
>>>>>>         I too have no desire to run a Java app alongside
>>>>>>         MisterHouse and now that formal Alexa Smart Home Skill
>>>>>>         API specs have been released, I think we can do better
>>>>>>         natively than what is possible using the Hue API with an
>>>>>>         external bridge. The mechanics of how to communicate will
>>>>>>         differ a bit (must use an OAuth 2.0 provider and have
>>>>>>         open access from Amazon to communicate via HTTPS with
>>>>>>         MH), but this opens up considerably more possibilities. A
>>>>>>         few major ones that come to mind are true device
>>>>>>         discovery (not needing to hard-code MH URLs) and
>>>>>>         increasing the device limit (up to 300) inherent in the
>>>>>>         Hue API (up to 75 in batches of 25).
>>>>>>
>>>>>>         I have limited time to play with MH stuff these days, but
>>>>>>         hope to spend a few hours over the holidays tinkering
>>>>>>         with this.
>>>>>>
>>>>>>
>>>>>>         Cheers!
>>>>>>
>>>>>>         -Brian
>>>>>>
>>>>>>
>>>>>>
>>>>>>         On 12/9/16 22:50, Wayne Gatlin wrote:
>>>>>>>         I know this is an old thread, but I am getting an echo
>>>>>>>         and I have started working on the native perl code to
>>>>>>>         integrate the echo with Misterhouse via upnp emulating a
>>>>>>>         hue bridge like the amazon-echo-bridge does. This will
>>>>>>>         eliminate having to run the external java
>>>>>>>         amazon-echo-bridge which seems to be CPU intensive and
>>>>>>>         cumbersome.
>>>>>>>
>>>>>>>         I don't have the echo yet, so in order to move on I need
>>>>>>>         a quick network capture of the echo discovering the
>>>>>>>         bridge and sending a few commands to a light or 2 using
>>>>>>>         the amazon-echo-bridge.
>>>>>>>
>>>>>>>         I have also been reading that google home will work with
>>>>>>>         the amazon-echo-bridge, it just has to be set to port
>>>>>>>         80. Could some one test that? If it does work, send me a
>>>>>>>         capture of that as well? This would be a direct local
>>>>>>>         option which is much better than the cloud methods.
>>>>>>>
>>>>>>>         I also have to figure out a good way to select which
>>>>>>>         objects or voice commands are presented to the echo
>>>>>>>         because from what I see only 25 devices per bridge is
>>>>>>>         supported and from what I can tell its only on or off
>>>>>>>         commands. It looks like I can get around that by using
>>>>>>>         multiple virtual bridges, but some MH systems will
>>>>>>>         likely have hundreds of objects/voice commands so a
>>>>>>>         method of selecting/mapping will be needed.
>>>>>>>
>>>>>>>         _Wayne
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>         On Sun, Aug 9, 2015 at 9:42 AM, Craig
>>>>>>>         <ar...@gm...> wrote:
>>>>>>>
>>>>>>>             I finally got this running under windows on my mh
>>>>>>>             server (had to use Chrome with the
>>>>>>>             --disable-web-security flag to add devices). Very
>>>>>>>             cool, but does require you to add each command as a
>>>>>>>             device. Does anybody know how hard it would be to
>>>>>>>             set up a bridge where you could pass any mh voice
>>>>>>>             command? I would love to see the bridge
>>>>>>>             functionality in a mh module.
>>>>>>>
>>>>>>>             On Fri, Jul 3, 2015 at 8:01 AM, Timothy Spaulding
>>>>>>>             <spa...@ic...> wrote:
>>>>>>>
>>>>>>>                 I can claim success now.
>>>>>>>
>>>>>>>                 My problem was with using Internet Explorer on
>>>>>>>                 the web page to configure the devices.
>>>>>>>
>>>>>>>                 -----Original Message-----
>>>>>>>                 From: Timothy Spaulding
>>>>>>>                 [mailto:spa...@ic...]
>>>>>>>                 Sent: Thursday, July 2, 2015 6:43 PM
>>>>>>>                 To: The main list for the MisterHouse home
>>>>>>>                 automation program
>>>>>>>                 Subject: Re: [mh] MisterHouse and Echo integration
>>>>>>>
>>>>>>>                 Tom,
>>>>>>>
>>>>>>>                 Thanks for posting this and your steps.
>>>>>>>
>>>>>>>                 I am trying it out, but I am getting stuck at
>>>>>>>                 the point of adding devices.
>>>>>>>
>>>>>>>                 I have added my bridge;
>>>>>>>                 htttp://autopi:8080/api/devices Added a name:
>>>>>>>                 Upstairs Landing Lights (have also tried with
>>>>>>>                 just a single word for the name) Added the
>>>>>>>                 on/off URLs;
>>>>>>>                 http://house/set?$Upstairs_Landing_Lights?on
>>>>>>>                 <http://house/set?$Upstairs_Landing_Lights?on>
>>>>>>>                 (that URL works all by itself as well).
>>>>>>>
>>>>>>>                 When I click on add, I don't get anything. No
>>>>>>>                 device is added.
>>>>>>>
>>>>>>>                 -----Original Message-----
>>>>>>>                 From: Tom [mailto:tom...@gm...]
>>>>>>>                 Sent: Monday, June 29, 2015 4:55 PM
>>>>>>>                 To: The main list for the MisterHouse home
>>>>>>>                 automation program
>>>>>>>                 Subject: [mh] MisterHouse and Echo integration
>>>>>>>
>>>>>>>                 I've also added this info to the wiki...
>>>>>>>                 https://github.com/hollie/misterhouse/wiki/Echo-integration-using-amazon-echo-ha-bridge
>>>>>>>                 <https://github.com/hollie/misterhouse/wiki/Echo-integration-using-amazon-echo-ha-bridge>
>>>>>>>                 ---------------------------------------------
>>>>>>>
>>>>>>>                 I found the following bridge which allows the
>>>>>>>                 echo to control pretty much any device.
>>>>>>>
>>>>>>>                 It works with the on off commands..
>>>>>>>
>>>>>>>                 ie:
>>>>>>>                 Alexa turn on my kitchen lights
>>>>>>>                 Alexa turn off my kitchen lights
>>>>>>>
>>>>>>>                 She simply responds with "OK" and since it's
>>>>>>>                 handled locally, it is fast.  In most cases, my
>>>>>>>                 lights are on/off before she finishes saying OK
>>>>>>>
>>>>>>>
>>>>>>>                 You need to include the URL for the on/off
>>>>>>>                 commands.. the URL could be a Perl script to
>>>>>>>                 kick off more than a simple lights on/off command
>>>>>>>
>>>>>>>
>>>>>>>                 https://github.com/armzilla/amazon-echo-ha-bridge
>>>>>>>                 <https://github.com/armzilla/amazon-echo-ha-bridge>
>>>>>>>
>>>>>>>                 the requires Java 8
>>>>>>>
>>>>>>>                 here's a description from the github page:
>>>>>>>
>>>>>>>                 -----------
>>>>>>>                 emulates philips hue api to other home
>>>>>>>                 automation gateways. The Amazon echo now
>>>>>>>                 supports wemo and philip hue... great news if
>>>>>>>                 you own any of those devices! My house is pretty
>>>>>>>                 heavily invested in the z-wave using the Vera as
>>>>>>>                 the gateway and thought it would be nice bridge
>>>>>>>                 the Amazon Echo to it.
>>>>>>>
>>>>>>>                 Register a device, bind to some sort of on/off
>>>>>>>                 (vera style) url
>>>>>>>                 -----------
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>                 Here are the steps I used to install the bridge
>>>>>>>                 on my Synology
>>>>>>>
>>>>>>>                 ------------------------------------------------------------------------
>>>>>>>
>>>>>>>                 Amazon Echo HA Bridge install on Synology  (it
>>>>>>>                 can be run on pretty much anything.. include Pi's)
>>>>>>>
>>>>>>>                 mkdir
>>>>>>>                 /volume1/@appstore/Amazon_Echo_HA_Bridge/
>>>>>>>
>>>>>>>                 cd
>>>>>>>                 /volume1/@appstore/Amazon_Echo_HA_Bridge/
>>>>>>>
>>>>>>>                 curl
>>>>>>>                 https://github.com/armzilla/amazon-echo-ha-bridge/releases/download/v0.1.3/amazon-echo-bridge-0.1.3.jar
>>>>>>>                 <https://github.com/armzilla/amazon-echo-ha-bridge/releases/download/v0.1.3/amazon-echo-bridge-0.1.3.jar>
>>>>>>>
>>>>>>>                 vi listen.sh
>>>>>>>                 hohup java -jar amazon-echo-bridge-0.1.3.jar
>>>>>>>                 --upnp.config.address=<synology IP> >>
>>>>>>>                 /volume1/@appstore/Amazon_Echo_HA_Bridge/log/amazon_bridge.log
>>>>>>>                 &
>>>>>>>
>>>>>>>                 (to specify port, add --server.port=yyyy ie: 
>>>>>>>                  java -jar
>>>>>>>                 amazon-echo-bridge-0.1.3.jar
>>>>>>>                 --upnp.config.address=<synology IP>
>>>>>>>                 --server.port=yyyy)
>>>>>>>
>>>>>>>                 chmod +x listen.sh
>>>>>>>
>>>>>>>                 sh listen.sh
>>>>>>>
>>>>>>>                 logs are in
>>>>>>>                 /volume1/@appstore/Amazon_Echo_HA_Bridge/log/amazon_bridge.log
>>>>>>>
>>>>>>>
>>>>>>>                 add/remove devices:
>>>>>>>                 http://<synology IP>:8080/configurator.html
>>>>>>>
>>>>>>>                 -----------
>>>>>>>                 Bridge server:  update the address with your
>>>>>>>                 server IP.. i.e.:
>>>>>>>                 http://<synology IP>:8080/api/devices
>>>>>>>
>>>>>>>
>>>>>>>                 Add a new device
>>>>>>>
>>>>>>>                 Name:  ie: Kitchen
>>>>>>>
>>>>>>>                 On URL: http://<Misterhouse
>>>>>>>                 IP>/ia5/set?$kitchen_light=on
>>>>>>>                 Off URL: http://<Misterhouse
>>>>>>>                 IP>/ia5/set?$kitchen_light=off
>>>>>>>
>>>>>>>
>>>>>>>                 ---------
>>>>>>>
>>>>>>>                 go to echo settings
>>>>>>>                 http://echo.amazon.com/#settings/connected-home
>>>>>>>                 <http://echo.amazon.com/#settings/connected-home>
>>>>>>>                 and have her Discover Devices
>>>>>>>
>>>>>>>                 or simply say
>>>>>>>
>>>>>>>                 "Alexa discover devices"
>>>>>>>
>>>>>>>                 ---------------------------------------------------------------------------------------
>>>>>>>
>>>>>>>                 Now you should be able to control your devices
>>>>>>>                 as follows:
>>>>>>>
>>>>>>>                 Alexa turn on/off <name>
>>>>>>>
>>>>>>>                 Alexa turn on my kitchen light
>>>>>>>
>>>>>>>                 ------------------------------------------------------------------------------
>>>>>>>                 Don't Limit Your Business. Reach for the Cloud.
>>>>>>>                 GigeNET's Cloud Solutions provide you with the
>>>>>>>                 tools and support that you need to offload your
>>>>>>>                 IT needs and focus on growing your business.
>>>>>>>                 Configured For All Businesses. Start Your Cloud
>>>>>>>                 Today.
>>>>>>>                 https://www.gigenetcloud.com/
>>>>>>>                 ________________________________________________________
>>>>>>>                 To unsubscribe from this list, go to:
>>>>>>>                 https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>>>>>>                 <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>>>>>>>
>>>>>>>
>>>>>>>                 ------------------------------------------------------------------------------
>>>>>>>                 Don't Limit Your Business. Reach for the Cloud.
>>>>>>>                 GigeNET's Cloud Solutions provide you with the
>>>>>>>                 tools and support that you need to offload your
>>>>>>>                 IT needs and focus on growing your business.
>>>>>>>                 Configured For All Businesses. Start Your Cloud
>>>>>>>                 Today.
>>>>>>>                 https://www.gigenetcloud.com/
>>>>>>>                 ________________________________________________________
>>>>>>>                 To unsubscribe from this list, go to:
>>>>>>>                 https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>>>>>>                 <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>>>>>>>
>>>>>>>
>>>>>>>                 ------------------------------------------------------------------------------
>>>>>>>                 Don't Limit Your Business. Reach for the Cloud.
>>>>>>>                 GigeNET's Cloud Solutions provide you with the
>>>>>>>                 tools and support that
>>>>>>>                 you need to offload your IT needs and focus on
>>>>>>>                 growing your business.
>>>>>>>                 Configured For All Businesses. Start Your Cloud
>>>>>>>                 Today.
>>>>>>>                 https://www.gigenetcloud.com/
>>>>>>>                 ________________________________________________________
>>>>>>>                 To unsubscribe from this list, go to:
>>>>>>>                 https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>>>>>>                 <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>             -- 
>>>>>>>             -Craig
>>>>>>>
>>>>>>>             ------------------------------------------------------------------------------
>>>>>>>
>>>>>>>             ________________________________________________________
>>>>>>>             To unsubscribe from this list, go to:
>>>>>>>             https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>>>>>>             <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>         ------------------------------------------------------------------------------
>>>>>>>         Developer Access Program for Intel Xeon Phi Processors
>>>>>>>         Access to Intel Xeon Phi processor-based developer platforms.
>>>>>>>         With one year of Intel Parallel Studio XE.
>>>>>>>         Training and support from Colfax.
>>>>>>>         Order your platform today.http://sdm.link/xeonphi
>>>>>>>
>>>>>>>         ________________________________________________________
>>>>>>>         To unsubscribe from this list, go to:https://lists.sourceforge.net/lists/listinfo/misterhouse-users <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>>>>>>>
>>>>>>         ------------------------------------------------------------------------------
>>>>>>         Developer Access Program for Intel Xeon Phi Processors
>>>>>>         Access to Intel Xeon Phi processor-based developer
>>>>>>         platforms. With one year of Intel Parallel Studio XE.
>>>>>>         Training and support from Colfax. Order your platform
>>>>>>         today.http://sdm.link/intel
>>>>>>         ________________________________________________________
>>>>>>         To unsubscribe from this list, go to:
>>>>>>         https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>>>>>         <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>>>>>>
>>>>>>
>>>>>>     On Thu, Dec 22, 2016 at 7:34 PM, Brian Rudy
>>>>>>     <br...@pr...> wrote:
>>>>>>
>>>>>>         Thanks Wayne,
>>>>>>
>>>>>>         I just picked up a few of the 2nd generation Echo dots to
>>>>>>         cover the house during Amazon's black Friday sale and
>>>>>>         have only just stated playing with them using the native
>>>>>>         ecobee integration and IFTTT. I have done a small amount
>>>>>>         of research into the ASK and developing Alexa skills with
>>>>>>         the skills SDK using nodejs/Lambda, but haven't been able
>>>>>>         to put much time into it yet.
>>>>>>
>>>>>>         I too have no desire to run a Java app alongside
>>>>>>         MisterHouse and now that formal Alexa Smart Home Skill
>>>>>>         API specs have been released, I think we can do better
>>>>>>         natively than what is possible using the Hue API with an
>>>>>>         external bridge. The mechanics of how to communicate will
>>>>>>         differ a bit (must use an OAuth 2.0 provider and have
>>>>>>         open access from Amazon to communicate via HTTPS with
>>>>>>         MH), but this opens up considerably more possibilities. A
>>>>>>         few major ones that come to mind are true device
>>>>>>         discovery (not needing to hard-code MH URLs) and
>>>>>>         increasing the device limit (up to 300) inherent in the
>>>>>>         Hue API (up to 75 in batches of 25).
>>>>>>
>>>>>>         I have limited time to play with MH stuff these days, but
>>>>>>         hope to spend a few hours over the holidays tinkering
>>>>>>         with this.
>>>>>>
>>>>>>         Cheers!
>>>>>>
>>>>>>         -Brian
>>>>>>
>>>>>>         On 12/9/16 22:50, Wayne Gatlin wrote:
>>>>>>>         I know this is an old thread, but I am getting an echo
>>>>>>>         and I have started working on the native perl code to
>>>>>>>         integrate the echo with Misterhouse via upnp emulating a
>>>>>>>         hue bridge like the amazon-echo-bridge does. This will
>>>>>>>         eliminate having to run the external java
>>>>>>>         amazon-echo-bridge which seems to be CPU intensive and
>>>>>>>         cumbersome.
>>>>>>>         I don't have the echo yet, so in order to move on I need
>>>>>>>         a quick network capture of the echo discovering the
>>>>>>>         bridge and sending a few commands to a light or 2 using
>>>>>>>         the amazon-echo-bridge.
>>>>>>>         I have also been reading that google home will work with
>>>>>>>         the amazon-echo-bridge, it just has to be set to port
>>>>>>>         80. Could some one test that? If it does work, send me a
>>>>>>>         capture of that as well? This would be a direct local
>>>>>>>         option which is much better than the cloud methods.
>>>>>>>         I also have to figure out a good way to select which
>>>>>>>         objects or voice commands are presented to the echo
>>>>>>>         because from what I see only 25 devices per bridge is
>>>>>>>         supported and from what I can tell its only on or off
>>>>>>>         commands. It looks like I can get around that by using
>>>>>>>         multiple virtual bridges, but some MH systems will
>>>>>>>         likely have hundreds of objects/voice commands so a
>>>>>>>         method of selecting/mapping will be needed.
>>>>>>>         _Wayne
>>>>>>>         On Sun, Aug 9, 2015 at 9:42 AM, Craig
>>>>>>>         <ar...@gm...> wrote:
>>>>>>>
>>>>>>>             I finally got this running under windows on my mh
>>>>>>>             server (had to use Chrome with the
>>>>>>>             --disable-web-security flag to add devices). Very
>>>>>>>             cool, but does require you to add each command as a
>>>>>>>             device. Does anybody know how hard it would be to
>>>>>>>             set up a bridge where you could pass any mh voice
>>>>>>>             command? I would love to see the bridge
>>>>>>>             functionality in a mh module.
>>>>>>>             On Fri, Jul 3, 2015 at 8:01 AM, Timothy Spaulding
>>>>>>>             <spa...@ic...> wrote:
>>>>>>>
>>>>>>>                 I can claim success now. My problem was with
>>>>>>>                 using Internet Explorer on the web page to
>>>>>>>                 configure the devices. -----Original
>>>>>>>                 Message----- From: Timothy Spaulding
>>>>>>>                 [mailto:spa...@ic...] Sent: Thursday,
>>>>>>>                 July 2, 2015 6:43 PM To: The main list for the
>>>>>>>                 MisterHouse home automation program
>>>>>>>                 Subject: Re: [mh] MisterHouse and Echo
>>>>>>>                 integration Tom, Thanks for posting this and
>>>>>>>                 your steps. I am trying it out, but I am getting
>>>>>>>                 stuck at the point of adding devices. I have
>>>>>>>                 added my bridge; htttp://autopi:8080/api/devices
>>>>>>>                 Added a name: Upstairs Landing Lights (have also
>>>>>>>                 tried with just a single word for the name)
>>>>>>>                 Added the on/off URLs;
>>>>>>>                 http://house/set?$Upstairs_Landing_Lights?on
>>>>>>>                 <http://house/set?$Upstairs_Landing_Lights?on>
>>>>>>>                 (that URL works all by itself as well). When I
>>>>>>>                 click on add, I don't get anything. No device is
>>>>>>>                 added. -----Original Message----- From: Tom
>>>>>>>                 [mailto:tom...@gm...] Sent: Monday, June
>>>>>>>                 29, 2015 4:55 PM To: The main list for the
>>>>>>>                 MisterHouse home automation program Subject:
>>>>>>>                 [mh] MisterHouse and Echo integration I've also
>>>>>>>                 added this info to the wiki...
>>>>>>>                 https://github.com/hollie/misterhouse/wiki/Echo-integration-using-amazon-echo-ha-bridge
>>>>>>>                 <https://github.com/hollie/misterhouse/wiki/Echo-integration-using-amazon-echo-ha-bridge>
>>>>>>>                 --------------------------------------------- I
>>>>>>>                 found the following bridge which allows the echo
>>>>>>>                 to control pretty much any device. It works with
>>>>>>>                 the on off commands.. ie: Alexa turn on my
>>>>>>>                 kitchen lights Alexa turn off my kitchen lights
>>>>>>>                 She simply responds with "OK" and since it's
>>>>>>>                 handled locally, it is fast.  In most cases, my
>>>>>>>                 lights are on/off before she finishes saying OK
>>>>>>>                 You need to include the URL for the on/off
>>>>>>>                 commands.. the URL could be a Perl script to
>>>>>>>                 kick off more than a simple lights on/off
>>>>>>>                 command
>>>>>>>                 https://github.com/armzilla/amazon-echo-ha-bridge
>>>>>>>                 <https://github.com/armzilla/amazon-echo-ha-bridge>
>>>>>>>                 the requires Java 8 here's a description from
>>>>>>>                 the github page: ----------- emulates philips
>>>>>>>                 hue api to other home automation gateways. The
>>>>>>>                 Amazon echo now supports wemo and philip hue...
>>>>>>>                 great news if you own any of those devices! My
>>>>>>>                 house is pretty heavily invested in the z-wave
>>>>>>>                 using the Vera as the gateway and thought it
>>>>>>>                 would be nice bridge the Amazon Echo to it.
>>>>>>>                 Register a device, bind to some sort of on/off
>>>>>>>                 (vera style) url ----------- Here are the steps
>>>>>>>                 I used to install the bridge on my Synology
>>>>>>>                 ------------------------------------------------------------------------
>>>>>>>                 Amazon Echo HA Bridge install on Synology  (it
>>>>>>>                 can be run on pretty much anything.. include
>>>>>>>                 Pi's) mkdir
>>>>>>>                 /volume1/@appstore/Amazon_Echo_HA_Bridge/ cd
>>>>>>>                 /volume1/@appstore/Amazon_Echo_HA_Bridge/ curl
>>>>>>>                 https://github.com/armzilla/amazon-echo-ha-bridge/releases/download/v0.1.3/amazon-echo-bridge-0.1.3.jar
>>>>>>>                 <https://github.com/armzilla/amazon-echo-ha-bridge/releases/download/v0.1.3/amazon-echo-bridge-0.1.3.jar>
>>>>>>>                 vi listen.sh hohup java -jar
>>>>>>>                 amazon-echo-bridge-0.1.3.jar
>>>>>>>                 --upnp.config.address=<synology IP> >>
>>>>>>>                 /volume1/@appstore/Amazon_Echo_HA_Bridge/log/amazon_bridge.log
>>>>>>>                 & (to specify port, add --server.port=yyyy ie: 
>>>>>>>                  java -jar amazon-echo-bridge-0.1.3.jar
>>>>>>>                 --upnp.config.address=<synology IP>
>>>>>>>                 --server.port=yyyy) chmod +x listen.sh sh
>>>>>>>                 listen.sh logs are in
>>>>>>>                 /volume1/@appstore/Amazon_Echo_HA_Bridge/log/amazon_bridge.log
>>>>>>>                 add/remove devices: http://<synology
>>>>>>>                 IP>:8080/configurator.html ----------- Bridge
>>>>>>>                 server:   update the address with your server
>>>>>>>                 IP.. i.e.: http://<synology IP>:8080/api/devices
>>>>>>>                 Add a new device Name:  ie: Kitchen On URL:
>>>>>>>                 http://<Misterhouse
>>>>>>>                 IP>/ia5/set?$kitchen_light=on Off URL:
>>>>>>>                 http://<Misterhouse
>>>>>>>                 IP>/ia5/set?$kitchen_light=off --------- go to
>>>>>>>                 echo settings
>>>>>>>                 http://echo.amazon.com/#settings/connected-home
>>>>>>>                 <http://echo.amazon.com/#settings/connected-home>
>>>>>>>                 and have her Discover Devices or simply say
>>>>>>>                 "Alexa discover devices"
>>>>>>>                 ---------------------------------------------------------------------------------------
>>>>>>>                 Now you should be able to control your devices
>>>>>>>                 as follows: Alexa turn on/off <name> Alexa turn
>>>>>>>                 on my kitchen light
>>>>>>>                 ------------------------------------------------------------------------------
>>>>>>>                 Don't Limit Your Business. Reach for the Cloud.
>>>>>>>                 GigeNET's Cloud Solutions provide you with the
>>>>>>>                 tools and support that you need to offload your
>>>>>>>                 IT needs and focus on growing your business.
>>>>>>>                 Configured For All Businesses. Start Your Cloud
>>>>>>>                 Today. https://www.gigenetcloud.com/
>>>>>>>                 ________________________________________________________
>>>>>>>                 To unsubscribe from this list, go to:
>>>>>>>                 https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>>>>>>                 <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>>>>>>>                 ------------------------------------------------------------------------------
>>>>>>>                 Don't Limit Your Business. Reach for the Cloud.
>>>>>>>                 GigeNET's Cloud Solutions provide you with the
>>>>>>>                 tools and support that you need to offload your
>>>>>>>                 IT needs and focus on growing your business.
>>>>>>>                 Configured For All Businesses. Start Your Cloud
>>>>>>>                 Today. https://www.gigenetcloud.com/
>>>>>>>                 ________________________________________________________
>>>>>>>                 To unsubscribe from this list, go to:
>>>>>>>                 https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>>>>>>                 <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>>>>>>>                 ------------------------------------------------------------------------------
>>>>>>>                 Don't Limit Your Business. Reach for the Cloud.
>>>>>>>                 GigeNET's Cloud Solutions provide you with the
>>>>>>>                 tools and support that you need to offload your
>>>>>>>                 IT needs and focus on growing your business.
>>>>>>>                 Configured For All Businesses. Start Your Cloud
>>>>>>>                 Today. https://www.gigenetcloud.com/
>>>>>>>                 ________________________________________________________
>>>>>>>                 To unsubscribe from this list, go to:
>>>>>>>                 https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>>>>>>                 <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>>>>>>>
>>>>>>>
>>>>>>>             -- 
>>>>>>>             -Craig
>>>>>>>             ------------------------------------------------------------------------------
>>>>>>>             ________________________________________________________
>>>>>>>             To unsubscribe from this list, go to:
>>>>>>>             https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>>>>>>             <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>>>>>>>
>>>>>>>
>>>>>>>         ------------------------------------------------------------------------------
>>>>>>>         Developer Access Program for Intel Xeon Phi Processors
>>>>>>>         Access to Intel Xeon Phi processor-based developer platforms.
>>>>>>>         With one year of Intel Parallel Studio XE.
>>>>>>>         Training and support from Colfax.
>>>>>>>         Order your platform today.http://sdm.link/xeonphi
>>>>>>>
>>>>>>>         ________________________________________________________
>>>>>>>         To unsubscribe from this list, go to:https://lists.sourceforge.net/lists/listinfo/misterhouse-users <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>>>>>>>
>>>>>>         ------------------------------------------------------------------------------
>>>>>>         Developer Access Program for Intel Xeon Phi Processors
>>>>>>         Access to Intel Xeon Phi processor-based developer
>>>>>>         platforms. With one year of Intel Parallel Studio XE.
>>>>>>         Training and support from Colfax. Order your platform
>>>>>>         today.http://sdm.link/intel
>>>>>>         ________________________________________________________
>>>>>>         To unsubscribe from this list, go to:
>>>>>>         https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>>>>>         <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>>>>>>
>>>>>>
>>>>>>     ------------------------------------------------------------------------------
>>>>>>     Developer Access Program for Intel Xeon Phi Processors
>>>>>>     Access to Intel Xeon Phi processor-based developer platforms.
>>>>>>     With one year of Intel Parallel Studio XE.
>>>>>>     Training and support from Colfax.
>>>>>>     Order your platform today.http://sdm.link/intel
>>>>>>
>>>>>>     ________________________________________________________
>>>>>>     To unsubscribe from this list, go to:https://lists.sourceforge.net/lists/listinfo/misterhouse-users <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>>>>>>
>>>>>     ------------------------------------------------------------------------------
>>>>>     Check out the vibrant tech community on one of the world's most
>>>>>     engaging tech sites, SlashDot.org!http://sdm.link/slashdot <http://sdm.link/slashdot>
>>>>>
>>>>>     ________________________________________________________
>>>>>     To unsubscribe from this list, go to:https://lists.sourceforge.net/lists/listinfo/misterhouse-users <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>>>>>
>>>>     ------------------------------------------------------------------------------
>>>>     Check out the vibrant tech community on one of the world's most
>>>>     engaging tech sites, SlashDot.org!http://sdm.link/slashdot <http://sdm.link/slashdot>
>>>>
>>>>     ________________________________________________________
>>>>     To unsubscribe from this list, go to:https://lists.sourceforge.net/lists/listinfo/misterhouse-users <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>>>>
>>>     ------------------------------------------------------------------------------
>>>     Check out the vibrant tech community on one of the world's most
>>>     engaging tech sites, SlashDot.org!http://sdm.link/slashdot <http://sdm.link/slashdot>
>>>
>>>     ________________________________________________________
>>>     To unsubscribe from this list, go to:https://lists.sourceforge.net/lists/listinfo/misterhouse-users <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>>>
>>     ------------------------------------------------------------------------------
>>     Check out the vibrant tech community on one of the world's most
>>     engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>>     ________________________________________________________ To
>>     unsubscribe from this list, go to:
>>     https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>     <https://lists.sourceforge.net/lists/listinfo/misterhouse-users> 
>>
>> -- 
>> -Craig
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org!http://sdm.link/slashdot
>>
>> ________________________________________________________
>> To unsubscribe from this list, go to:https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org!http://sdm.link/slashdot
>
> ________________________________________________________
> To unsubscribe from this list, go to:https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>

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">https://pastebin.com/wRfJYWnV</a><br>
          <br>
          <a href="https://pastebin.com/fumbhVzw" target="_blank">https://pastebin.com/fumbhVzw</a><br>
          <br>
          <a href="https://pastebin.com/pvYnr37n" target="_blank">https://pastebin.com/pvYnr37n</a><br>
          <br>
          <a href="https://pastebin.com/378NETi8" target="_blank">https://pastebin.com/378NETi8</a><br>
          <br>
          <a href="https://pastebin.com/L05ax8vf" target="_blank">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">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">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
>>
>>
>