It isn’t just an issue of patience? How long have you waited? Are there any function for waking up the device and if so, have you tried it? Some devices takes a couple of wake-ups before they are fully synchronized. Mostly a problem with battery devices though, this is mains powered, right?
Did you include it through OH, or by pressing the button on an Aeon zstick? If the latter, it may be having trouble communicating. I imagine the device is down in the basement, with HVAC ducts and water pipes above it. How many other mains powered devices do you have? If you haven’t already, try excluding and reincluding through OH, with the controller set to Network Wide Inclusion. This should help with routing. Another option is to use the development binding, which can perform a heal to help the controller rebuild routes. It’s hard to know what is going on without looking at the logs, so this is pretty much just a guess. It also looks like you are using PaperUI… Habmin is much better for zwave devices.
If I was troubleshooting it, I’d first look at a log of the zwave binding restarting while in debug mode, filtered on the device’s node. I’d probably also watch an exclusion and reinclusion (through OH, not the zstick), while filtering on the next node available, which is where it would show up. But if you haven’t already, try restarting the binding and it may come up.
I see you’ve made some updates to the device db. If they’re important, you’ll need to wait for them to be included in the next binding update.
@romiv This is a rebranded FortrezZ device, right? Should the manufacturer be 84 (hex). It looks like you entered 132 (which happens to be the decimal version of 0x84)?
Edit: Wait, I see you have 84 in the Type field. Can you double check all those values?
Edit2: Please also check for the existence of a node.xml file in the userdata/zwave directory.
Edit3: As a final thought, if you determine that the manufacturer is 84, I wonder if it would make sense to update the database entry for the FortrezZ WV-01
FWIW, I can’t think of a better device to add to a Z-Wave network. I have a water shutoff valve from another manufacturer. Of all the hundreds of dollars I spent of Z-Wave devices, this one really saved my butt when there was a leak in my basement.
There may be a problem with the Type ID. I can not understand what value it should be. There are photos from the manual. The manufacturer is installed automatically. I chose him from the list.
What is ZWIW? I didn’t found it in google =)
@chris Doesn’t this also beg the question whether the FortrezZ WV-01 entry should be updated with this type:id.
Although, I must admit, I’m not sure of the convention for how to handle rebranded devices, as well as whether there are any functional differences between this rebranded device and the other FortrezZ WV-01 devices…
Yes, you are right - it’s the same device and we should add the type/id to the original database entry and delete the new entry.
It’s only rebranded in that there’s a different sticker on the side. As far as the binding knows, it is not rebranded as it has the Fortrez manufacturer ID.
My guess is there is no difference, but if there are, we would need to manage this through firmware versioning. The database fundamentally uses 4 numbers to determine a device type - the manufacturer ID, device type, device ID and firmware version…