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.
Closed
Homey v0.9.1
This discussion has been closed.
Comments
Wait for the app to appear in the store, should be ok then.
-zwave plus sensor not working
- rgb controller not working
After full reset still not working
Sound logical, but it should be more logical that the device would be added as a generic typed(movement, security, switching, light, etc,) device so it's functional. In the current way only switching devices are usable. (couldn't/didn't test, so above is based on what I understand from previous posts on this matter).
https://github.com/athombv/homey/issues/742
Whoops.... The only reason why Homey is powered on is because of the sunset function in combination with Hue. Going to check it tonight from the French Campsite else the Vera3 will PTP.
At the moment there are so much differences in working functions/apps, that I will see/check myself hope for the best.
Going to add notification cards to the vacation flows 2 tests in one
OK did some tests and it looks like the current flows didn't run, because..... The Email App failed on flow test.
Did add the mobile card and selected the last mobile device of my device and push notifications came through.
Now its waiting till 21:2? for sunset and see if sunset trigger works.
https://www.dropbox.com/s/u6l6cw4sflit0dy/Screenshot 2016-08-01 19.01.18.png?dl=0
it was working before (without the lux)
Fibaro dimmer is paired, Kaku dimmer, doorbell and motion sensor is working. Now only waiting for associations while I test the stability.
Just test the flow but thats not the correct way i think
did you do a power cycle yet? (pull the power plug and re-insert it again)
Fibaro Rgbw controller is working perfect now even after reboot
After inclusion the device-id for association group 3 is not 1 which gives inclusion errors, but even after changing that to 1, the inclusion errors are gone (by forcing an update) but homey isn't reporting the correct status (alarm/no alarm). Reboot of homey didn't work either..
Does somebody else has the same problem or is it only me ? ;-)
Fibaro app v1.0.4 by the way...
After upgrading to v0.9.1 I notice that, once I include Homey in my other Z-Wave network with HC2 as the main controller, that Homey does no longer do the survey on the Z-Wave network where it is included in (.. to actually adopt all current Z-Wave devices that are available in this network.
It is now standing in idle mode for 12 hours but I don't see any of my "HC2" devices appearing in Homey.
Am I doing something wrong, or?
Best regards,
Mark
But when I added it to Zwave as "'Other", I did react on any input.
Both times using the Fibaro App.
Anybody else experience the same issue ?
the app is from 0.9.2, which will come (probably) this Friday, 0.9.2 will fix some bugs with the z-wave driver.
the app seems to be working and i could pair my powernode6