Is any one having issues with inconsistencies in STATEs between the Node Red server and the Hubitat hub?
I've been having issues where the node red server thinks a certain switch is in the "ON" state but in the HE hub it is actually "OFF" (it is also OFF in reality).
This issue has resulted in some motion lighting flows to not execute properly because in all of my flows I always have it check the current STATE of the switch before deciding to send the command. Hence if the STATE is wrong then the flow wouldnt run correctly.
It sucked, Next time I will go buy a z-wave stick for my computer and get the z-way SW or one of the other Z-wave troubleshooters.
But I live on a single story and the issues were on one side of the house, so I started with excluding 1 switch, doing a repair and seeing if I still had issues. If I still had issues, add switch back and move to the next switch. It was one of the switches that was running slow.
Quick question - does this node work if the hub is password enabled? If I use the direct URL to get to the Zigbee routing tables, it takes me to the login screen and once I do that, it will take me to the routing tables.
I've been able to do it by creating an Automator app (MacOS) using the curl script (originally created by @aaiyar I think). I'm using that to automatically download a Hubitat backup but I was hoping I could do it using Node-red as that would be more platform independent.
It shows the routing, which is not usually human comprehensible, but it also shows the speed.
You can see I have ALL speeds represented... 9.6k, 40k and 100k
What we want is for everything to be 100k, real world is rarely going to be like that.
So you'd want to review each speed and determine 1) makes sense.. battery/Zwave not Plus, etc. and 2) if it's used as a router.
If it doesn't make sense, for example the Row that shows as: 01 -> 07 -> 09 -> 08 9.6kbps is a Hank RGBW Bulb and is ZWave+ -- it should run at 100k. It's not, probably due to distance.. It's Node #8 and so for 2) I can see it is not used as a router... yet. So I can ignore it's low speed for now, but keep my eye out for inserting a router near it as I build out my mesh.