I bought 3 of these to use with Hubitat and Home Assistant. They work flawlessly on HA but with Hubitat there's only one way communication. When you first include the keypad it works fine for that first disarm but after that the keypad won't communicate with Hubitat. Hubitat can send packets to the keypad but not the other way around. If you soft reset the keypad a few times or send commands to the keypad it might work for a little bit but then it goes back to not working. I seen a few other people in closed post report this same issue. Maybe It's a new firmware thing. Here's the info I've gathered. No it's not ghost nodes or anything like that, been doing this for a while now and my Zwave mesh is strong. They are paired S2 control access. It's like the keypad is waiting for the hub to send something. S2 hubitat Zwave I kind of expected this stuff since its a keypad and not a contact sensor or something simple. Ring outdoor contact sensors work fine with s2. Oh well at least they work normal with HA. Glad I came across some app that brings HA devices to Hubitat. Here I was thinking I'll need to share my Hubitat zwavw devices with HA. I thought Zwave was going to be a nightmare with HA but nope. Oh same problem with both the built in driver and Community driver just different errors.
Did you include the keypad with S2?
lol you surely didn't read
So just to be clear. It does include and you get information in the logging, but you are getting java errors?
The screen shot i am seeing is cut off on both sides can you show the whole errors
Oh I read that it gave you a warning for not being encrypted, my question was did you do it intentionally knowing that many Ring devices only have full functionaity if included with S2.
I included them every way you can lol, smartstart manual s2 non s2.
those are are the entire errors they keypad just goes poof no more communication it's really funky. If you send the configure command you get those errors.
When I look at the images you included in your original post it is clearly cut off on the left side in both images. The second one is cut off on the right side as well. I understand those lines are the errors, but we they are cut off on both sides so only part of the error is showing.
The top error message looks like it failed when you clicked the configure button. not sure what the issue is with the second one.
Can you confirm what drivers you are running. and what versions if possible?
I have a keypad, but it looks like a older version of the firmware. The value it looks like the logging is showing is the same as what is shown on my device as well.
That is @bptworld community driver. Perhaps he can help shed some light on what is going on with it.
Yep, that's my understanding - they repeat anything just fine, encryption/decryption is only done at the endpoints (s2 device and hub).
As far as firmware goes, is it somehow paired to both the Hubitat hub and a ring alarm hub? I'm not sure how it would get firmware updates without being connected to a ring alarm hub.
To the point of one-way comms... As you mentioned there have been several threads where others reported the same basic issue, though I haven't heard many reports of it coming back once paired and working successfully - the exception being that mine did, once, after a power surge/outage. Are you running on battery, or keeping it connected to mains power?
No ring alarm, I just bought them the other day. They shipped with this firmware.
I"ve tried both
Or the drivers just need to be updated. It isn't a compatibility thing perse, but a driver thing.
Hello, I am experiencing similar issues, were you able to fix it? Thanks
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
