@erktrek Thanks but I try those? I attached the flow? I even try to change the payload.value to payload but still no luck? I also had pushed with payload.value?
Essentially you need to have a "/endpoint" prefix to the web hooks so your POST command looks something similar to http://192.168.x.xx:1880/endpoint/hubitat/webhook
In Mrobi's case he also had a password on his NR instance, so he was getting authentication error in his logs. He simply added the "username:pass@ip" format to the url...AND also had to remove special characters from his password.
I personally don't put a pass on my NR instance since it is not exposed to the web and just creates extra headaches with integrations.
it's an old subflow I need to get rid of.. just a switch and some change nodes. A better solution would be a single change node that sets the msg.command with a jsonata expression like this:
payload.value = "on" ? "off" : "on"
I do like to use subflows because it makes editing easier but sometimes you can go too far..
It takes me a lot re-reading to finally understand that I missed to document this feature
You can set the device with msg.deviceId and that's why from version 1.0.0, device is no more mandatory when you save command node
Having the name of the device instead of deviceId would required some tradeoff on performance and/or complexify the node configuration. But you can do similar thing with the request node to fetch all devices and map the name with ID
You want to use the "Switch" node for that. If your using Hubitat device nodes, configure the switch node to evaluate the content of "msg.payload.value".
For a contact sensor, the values are "open" and "closed".