New Homebridge Plug-in via MakerAPI

šŸš§ Developers
908

Ok, do me a favor and follow the following steps for Troubleshooting:

  1. In Hubitat, go open your MakerAPI Instance
  2. Scroll down to find your "URL to send device events to by POST"alt text
  3. Copy the URL and enter the URL in a new browser window
  4. You will see a view like this, showing you the logging output of the plugin, the ability to download the log-file to your computer, enablign, disabling debug mode and see your current configuration alt text
  5. Click the button "Enable Debug Mode"
  6. Change the mode or HSM status the way it causes you issues
  7. Click the "Download Log File" button
  8. Send me the downloaded file. I'll PM you an email address that you can send it to.
1 Like
909

Just sent it over. Thanks

910

Jup,

the mode change events don't event arrive at the plugin. Go back into MakerAPI on Hubitat and make sure that the setting "Include location events to be send by POST?" is enabled

image
image.png1611Ɨ186 17.1 KB

Once enabled, it should work right away

1 Like
911

Oh I didn't have this option checked. Turned it on and now it works!

Thanks!!!

912

@dan.t , is there a more elegant way to reset the :rotating_light: being ā€œtriggeredā€ in the Home app from a custom HSM alert. I clear them in HE, but the only way to get it cleared in the Home app is by restarting Homebridge, or arming and then disarming the system from Home.
BTW Iā€™m using the HubConnect version.

913

I used a virtual momentary switch and rule to reset it. I flip it in home kit and it will clear the triggered notification.

914

Sure thing, update your plugin (just fixed it in both plugins) and you should be good to go

1 Like
915

Much appreciated! Thanks for all of your work on this.

916

Clearing the triggered alerts works perfect. Iā€™ve been having issues with changing modes. I can make the first mode change in the Home app without an issue, but if I try to change the mode back, or to anything else it doesnā€™t work and the mode button goes unresponsive. If I change the mode from dashboard it works as expected and fixes the unresponsive mode buttons in Home. Any idea how I can fix this. I had the same problem with the Makerapi version. This is the only other issue I have had.

917

I just tried that a million times and can't reproduce that. You are using HubConnect, correct? If so, please follow these steps here:

  1. In a new browser window go to http://HOMEBRIDGE-IP:20009/
    20009 is the port the plugin is listening per default. You might have configured a different port in your config.json. If so, please use the port in your config.json
  2. You will see a view like this, showing you the logging output of the plugin, the ability to download the log-file to your computer, enabling, disabling debug mode and see your current configuration alt text
  3. Click the button "Enable Debug Mode"
  4. Do your mode changes flow that cause the issue
  5. Click the "Download Log File" button
  6. Send me the downloaded file. I'll PM you an email address that you can send it to.
1 Like
918

Thanks. I appreciate your help. Iā€™ll do this tonight. This is literally the only problem I have ever had with this app (besides the alerts that are fixed now) and had the same issue with the Makerapi version. Could it be because I have 10 modes?

919

Shouldnā€™t... but hard to say without the logs

920

@dan.t, I just switched over from the MakerAPI plugin to the HubConnect plugin using http. All working well with the exception of HSM - the events are seen by the plugin, but seem to be ignored, I.e. the HSM state changes arenā€™t shown in the Home app.

Hereā€™s a log file snippet:

[11/29/2019, 12:55:13 PM] [Hubitat hhh:0.3.6] New logging client connected
[11/29/2019, 12:55:19 PM] [Hubitat hhh:0.3.6] Debug logging enabled
[11/29/2019, 12:56:04 PM] [Hubitat hhh:0.3.6] Received set HSM State request for state: armAway
[11/29/2019, 12:56:04 PM] [Hubitat hhh:0.3.6] Lets ignore this and use the eventsocket for it...
[11/29/2019, 12:56:07 PM] [Hubitat hhh:0.3.6] send ping
[11/29/2019, 12:56:07 PM] [Hubitat hhh:0.3.6] GET:  { debug: false, path: '/ping', method: 'GET' }
[11/29/2019, 12:56:09 PM] [Hubitat hhh:0.3.6] HE websocket sending keepalive ping
[11/29/2019, 12:56:09 PM] [Hubitat hhh:0.3.6] HE got pong 
[11/29/2019, 12:56:34 PM] [Hubitat hhh:0.3.6] Received set HSM State request for state: disarm
[11/29/2019, 12:56:34 PM] [Hubitat hhh:0.3.6] Lets ignore this and use the eventsocket for it...
921

Do you have hsm set to true in your config file? The ignore statement is normal, but I would still expect a Websocket output.

922

Yes HSM is set to true in the config file.

Also, I originally installed the Hubconnect client using websockets, and noticed the same problem with HSM state changes. I then reconfigured the client to use http. Same result.

923

Can you get me a log file?

  1. In a new browser window go to http://HOMEBRIDGE-IP:20009/
    20009 is the port the plugin is listening per default. You might have configured a different port in your config.json. If so, please use the port in your config.json
  2. You will see a view like this, showing you the logging output of the plugin, the ability to download the log-file to your computer, enabling, disabling debug mode and see your current configuration alt text
  3. Click the button "Enable Debug Mode"
  4. Turn a switch on/off and make an HSM change
  5. Click the "Download Log File" button
  6. Send me the downloaded file. I'll PM you an email address that you can send it to.
924

I see what is going on. It is the ā€˜ in your mode names. I am going to take a look at it. I didnā€™t expect that someone would use an apostrophe in a name....

925

Itā€™s only the wifeā€™s early morning mode. I can take it out; itā€™s not like she looks at it ever. She just wants it to work automagically :wink:

926

I just released a new version for the hubconnect plugin to fix that. The error does not exist on the makerapi version as the interface is different

927

Thank you for that. Iā€™ll give it a shot. BTW. I just noticed the fix for triggered alerts cleared the trigger in Home, but not in HSM.