This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Comments
i submited a new beta 2.0.4 with new zwave mesh driver and moved the smoke detector to the sensor class.
I hope it will now create the trigger cards for the device
Would you -or anyone else- happen to know if I need to re-include the smoke detectors?
The Zwave mesh in settings it still looks the same, and lists the smoke detectors(same as before).
Thanks you for your efforts in resolving this.
Since for other Popp devices the same procedure may apply, I am going to write down the steps I did to resolve this.
1) Remove device from Homey Devices section
2) Press button on device to exclude it
3) I had to reboot since I could not include it again
4) Add Device --> press include button in device
5) the icon change(slightly) in flows so I was very hopeful already, and YES, it can be used to trigger Alarms in the "When" section again.
Awesome work, thanks again.
Edit: een biertje of twee zijn onderweg(Paypal)
And thanks for the effort of course!
Can you have a look into this?
Once you have done this you will see slightly altered icons, and you will be able to use the smoke detectors as trigger cards again.
@mruiter:
Oddly enough Zwave performance of connected devices seems to have improved for me(or I must be imagining things)
Only thing that doesn't seem to work anymore is battery status, how is that on your side?
I guess that's something @mruiter needs to look into.
It does work , if you wake up the device... But most of the time it doesnt work.
Homey doesnt look at the random battery report. Which i also find weird that they cant seem to get it fixed
I just tried to add my z-rain. The app crash directly after adding z-rain.
Just for me?
I`m on beta 2.0.4.
I'v tried both v2.04 and 1.1.7 but it's the same behavior. Homey receive data. What to do?
Have added it without any problems, only problem is that it eats 9v batteries so ive choose to use a 12 v power supply
Indont have it myself hope to hear from him soon so it gets functional in the beta series
I would appreciate that.
connecting/pairing to homey was no problem , but at first it only showed temperature and humidity , but i need it for its wind speed , to retract my screens in case of strong wind
installed the beta app this morning, , now it also shows brightness/helderheid, but still no windmeasure,
@mruiter can i provide anything to help fixing this, or is it not possible to fix the wind measuring?
regards
Eric
The support was made like stated in the document PoPP supplied .
Since the S2 and Flirs bugs in the Homey Zwave core i cant add the keypad myself to test it.
And sinces most documents PoPP supplies with there products are shit it could be its not working as it is in the Beta App.
Seems you are able to join the keypad to homey.
Would it be possible to run the app in the athom-cli in debug and pass me some log files when trying to use the keypad ? Then i can see what goes wrong.
What I can do is that I send the key pad to you so that you can test it yourself.
or you could sideload it from my github.
many thx to the community user that send in the fix
Hope there is another community user with a z-wave rain a development skills that could look into it. And maybee even help with the new Beta SDKv2 version because thats about the only driver in the SDKv2 version in beta that isnt working.
I think one value from z-rain is missing... mm/m2.
Just for me or possible to include this value in the app?