I'm trying to add the Homeseer Door/Window sensor to a Hubitat C8pro. I tried mutiple times to get the sensor to work using the LR option. If I add it as a normal zwave it works fine. Most of the failed LR adds resulted in mutiple entries in the zwave details page. I shutdown the hub and waited over a couple of mins before restarting. This time I have mutiple zwave entries and the last entry has a device associated with it. It connected as a "Jasco PRO plugin smart switch". Changed the device type to Device and when I did anything to the sensor nothing was shown. Checked the Smart Start Manager app and it shows the add as a fail.
Here are some of the logs and information.
Is that last node in your table (0x0167) this device? If so, it appears to have been successfully added as an LR device. I would leave the the third-party app out of the picture for the moment since the Z-Wave Details table is the authoritative source, but it pulls the same data, just not in real time, so it should be accurate too (reloading the main page of the app or hitting "Refresh List" may help).
For the two nodes above this, assuming they are non-functional, you should be able to remote them, either from a Remove button that might appear in a few hours or by selecting "Refresh," waiting a few seconds for that to complete, then seeing if "Remove" is there (and maybe trying once more if not; do not go too fast, do more than one operation at a time, or do anything that might test the patience Z-Wave is known for requiring).
Yeah, that's what this driver does: nothing. 
It's the default when no matching driver is found. Have you tried Generic Z-Wave Plus Contact Sensor?
1 Like
Yes I tried the Generic Z-Wave Plus Contact Sensor and it doesn't do anything. No entries after exercising the contact.
Do you see anything in Logs with the debug logging option enabled? That would help tell the difference between a problem with the device (it sent something in your logs above) versus one with just the driver (not parsing the information correctly, though this seems unlikely nowadays...).
With Debug logging on nothing happens when contact is exercised. When I look at the Z-Wave Details the last message is from several hours ago. The Z-Wave logs have these entries:
This suggests that the driver isn't receiving anything from the device (as opposed to it just being a driver problem), which, while maybe not surprising, is good to know for troubleshooting.
These only show commands sent from the hub and are rarely helpful for troubleshooting problems with a device, if anything at all.
In your case: if you haven't tried the easy things first, I'd make sure you're using good batteries (they probably came with something, but maybe try another set just in case). Also, make sure you are on the latest platform release.
I'd also make sure your Z-Wave network is in good shape. Take a look at this doc if you have not, paying particular attention to failed inclusions, not specifically the ones from now (LR is unlikely to be a problem) but also any you have that might be older: How to Troubleshoot Z-Wave | Hubitat Documentation -- but also the rest of the general network tips.
LR is pretty new and has been tricky for some users or devices to get right; some work on the hub is underway to address some changes that can be made on the hub side, though those are unlikely to be complete in the near future. If you don't need LR specifically, it sounds like classic inclusion works and might be the best idea for now. I haven't had any problems myself, aside from needing to try once or twice if the first inclusion attempt failed, so if you do want LR, you might have better luck after addressing any possible issues above. Good luck!
did you ever get this working.. looking at trying one in my mailbox.
No I have not gotten it to work.
FWIW, I just ordered one.
I'm a glutton for punishment.
1 Like
any hope at getting @bobbyD to look at getting this device working in lr mode? it would be a great device due to lr and the regular aaa batteries.. nothing else out there like it..
Did you see this?
ya no thanks 2 cr2032 no more coin cell batteries for me in mailbox if i can help it.
Looks like it did pair and created the device.
Did you grab the logs when it paired?
Did you try and shut down and boot back up?
Having same problem as everyone else? When you activate the sensor nothing is showing activity on the hub?
It.paired but not fully nor correctly
There were no logs generated during pairing. See how zwave info says pending and no stats. And the smartstart app entry says node pending status failed? See attachments
I rebooted. Nothing works no attributes etc. No zwave events or messages
I emailed homeseer support
. Useless they say contact hubitat and are unwilling to debug or test. When i complained.. they said send back for a credit.
1 Like
I meant the solution requiring driver mods.
edit: Also, I know you said there was an issue with using a ZSE18 motion. Is it because the mailbox is metal?
- Not the same issue this device is not comletely finishing pairing.
- No that issue was just poor range for me on that device. Never even got in the mailbox only worked 1/2 way there.
1 Like
bump any update @support at getting this working
1 Like
I see you are in beta. I would wait for some changes in an upcoming build that may help with this (you'll see a notable change in the release notes) and report back after that.
2 Likes
