Saw this new binding and started switching things back from mqtt (just by changing item links).
But then I got to the Long Range (LR) devices and receive the following error in the thing:
UNINITIALIZED
HANDLER_CONFIGURATION_PENDING
{id=The value must not be greater than 255.}
This seems like a safety limit to support legacy mesh nodes, hoping LR can be supported one day or if anyone knows how to change the upper limit of the node id as LR starts its numbering range at 256.
Have to look into it, but was not aware LR starts its node id’s from 256. If that is all it takes I can come up with a fix. I’m not able to access my computer the next two weeks. After that I will fix it
I believe its for compatibility of legacy zwave mesh networks running concurrently; it threw me for a loop after I figured out how to use the smart start feature as I expected a node06 and instead received a node256 (which is the only way LR will activate).
Its no rush, getting majority of my devices back with ease has been a win (I have a weird issue with mqtt things and saving them turns some things off when saving, annoying when I hit save by mistake and turn off lights on the spouse).
Hi all,
Was there a fix to this? I am getting the same issue on my Zwave-Js LR device.
Thanks!
I am not aware of any fix yet, I am patiently waiting and hoping it appears in a patch note or the Dec major release.
Opened a ticket on the github.. looks like they are going to take a peak at the code.
Im getting ready to move all my zwave to the zwave js..
Please try this:
