-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ST812 added but not functioning #42
Comments
He hello, No one has this problem? Or no one using the ST812? |
Tried to add ST812 to my Homey 5.0. Will only connect as Basic Z-Wave Device. Device Information: |
Hi, Do you have a picture of the device? It shouldn't have Manufacturer ID '309' , this is not Everspring, but Zyxel . So that's why it is not recognized as the ST812. |
Sure
Hope this can be any help
[image: 20210218_111655.jpg][image: 20210218_111632.jpg]
Den tors 18 feb. 2021 11:13ralfvd <[email protected]> skrev:
… Hi,
Do you have a picture of the device? It shouldn't have Manufacturer ID
'309' , this is not Everspring, but Zyxel . So that's why it is not
recognized as the ST812.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#42 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARCHPXG2QUY3HCVS6ONYDQ3S7TR37ANCNFSM4IY2WHTQ>
.
|
Hi, unfortunately the picture is not visible, this is due to GitHub . CAn you send the picture to ralfvd AT gmail.com ? Then we can discuss it per email as well. Thanks! |
This thread is old, but I am having this same issue with my Everspring ST812's in HomeSeer with their new Z-Wave Plus. These worked great in the old version of HomeSeer's plugin. Has it been solved by anyone? Thanks. |
He guys.
i've added two ST812 flood sensors. (both sensors work correct with home assistant). Adding works fine and they are recognised, but don't seem to respond to actual floods. also the batteries always show 100% which they aren't so it seems something is wrong. anyone else had this behavious?
thanks!!
The text was updated successfully, but these errors were encountered: