odd changed nothing reconfigured webhook in event node for Node-red and its working now
Thanks everyone
2 Likes
Hi, I'm running into a problem with the HSM node, specifically the one that states "A node that get Hubitat Safetly Monitor state.".
I thought the status would change to correspond with the status in Hubitat, but it just doesn't change status when HSM changes to either arm home, arm away on its own, it's always the status it was in when the node was added as seen in this screenshot.
Am I misunderstanding on how this node should work, is it no supposed to change to the current state, if not how can I check the current status in node-red.
Current node-red version: 1.3.5
Yep can confirm I am getting a similar thing... I have my HSM "armed" and the HSM status is showing up as "disarmed". Re-Arming in HE does nothing.. although events are getting generated they seem to all be "disarm"...
Nothing to see here... all is well, move along, move along...
What is odd to me is, if I query with a http request node and debug, I can see the state change of HSM but not on the hsm node, its as it is not doing the query itself.
Okay I figured out my issue...PEBCAK of course. Lack of understanding about how HSM works. 
The arming bit only works with the Intrusion stuff... on my C-5 Net hub I have no motion sensors so it did not appear only the water sensor. On my C-5 Zigbee hub I do have sensors so as a test, set it up and it worked fine.. intrusion home arm/disarm. doh!!!!
It would be nice to be able to arm water monitor and custom stuff though..
@william2 - how are you connecting to HE - webhook or websocket? Has the HSM ever worked or are you trying to get it to work now?
edit: I am not really using HSM because it doesn't quite fit my use-case.
@erktrek - I have has HSM setup and works fine with my sensors and button. However, this is the first time using the Node-Red integration with Hubitat, been using it with Home Assistant for several years. My setup is with webhook but based on your comment I switched it over to websocket and what do you know, its working although there is a warning in the config node (Not Recommended). I guess for the time being I'll create 2 configs, one for HSM and one for everything else. Thanks for the idea!
1 Like
@william2 Did you manage to see device node status updated with the recommended method (webhook)?
If yes: then be sure to enable the checkbox to Allow control of HSM events to be sent by MakerAPI
If no: then you need to fix the webhook workflow tips to debug here
Or you can keep 2 config nodes 
1 Like
@fblackburn , yes I have them both on and the webhook does connect. Honestly I would like to get rid of the two configs, but for now I guess it will have to do, I even upgraded node-red to the latest version but no change...
Oh I think you need to enable "Include location events to be sent by POST"
2 Likes
Just did this and it made no difference. I also went through the tips for debugging process as well, the only differences I saw was at the end of the webhook, in mine it adds an underline at the end in "webhook_" and no matter what I do to eliminate it Hubitat adds it back...
Edit: disregard the "webhook_" just learned that it mean that I have multiple configs, which in my case I do for now.
I confirm you need this checkbox enabled. Otherwise no HSM event will be sent (I'll update firstpost / readme Doc updated)
If you have two config nodes with only one Maker API instance, then events will sent event to only one config node (because your config nodes will have different endpoints (webhook, webhook_). So be sure to configure only one config node by Maker API instance
1 Like
FYI I read NR v2 upgrade node, updated CI to check node supported version, did some manual tests on things that I thought that could have been broken, checked logs output and, as reported by other users, everything work good 
5 Likes
So I went back to basics and I think I found the problem. If you don't set the "Include location events to be sent by POST?" when you first create the API it won't work if you do it afterwards. I say this because I went back and made a new API making sure everything was on and sure enough the new one worked with everything. Put this one under user error 
3 Likes
Just upgraded to NR2.05. Everything seems to be ok so far 
3 Likes
Yup have been running with no issues except this Aedes error which was present in 1.3 as well.
2 Likes
All good - I'm using mosquitto!
1 Like
I actually run both - Mosquitto for a personal weather station and owntracks on an old RPi3, and Aedes for Node-RED internal stuff like using it in place of Link nodes - for generating and trapping "events" and such..
2 Likes
So, I am not showing devices either in the drop down list.
I looked at the other answers, and it looks as if I am doing everything correctly.
As my Node Red server is on an external VM, do I need to use the cloud address of my server for access?
@rocketwiz @erktrek I see both of you are running NR v2.x. Worth upgrading? I am running v1.0.6 on my NAS and having no issues so curious if it is worth the upgrade. Thanks@
There is nothing I am using right now that demands it but I like to keep current if possible so I can anticipate issues etc.. My clients are still on 1.05+/- and will likely be there a while - 1.xx will be supported until next June according to the release plan.
1 Like
