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
Changelog:
For Z-Wave: for now only FIbaro is supported. More devices will follow soon later!
Enjoy!
- Replaced Z-Wave with App-based driver
- Temporarily disabled Infrared as preperation for the Infrared update
- Added support for custom capabilities
- Added support for custom signals
- Added support for apps to get a Homey's Cloud ID
- Apps will be notified when a Flow trigger has been added, changed or removed
- Added software that automatically restarts Homey on a freeze
- Fixed a bug where Homey would freeze
- Fixed a bug where the Microcontroller would crash
- Fixed a bug where a user's DHCP server would not be used
- Interface improvements
- Performance improvements
For Z-Wave: for now only FIbaro is supported. More devices will follow soon later!
Enjoy!
This discussion has been closed.
Comments
Or do I need to check "expirimental updates.."
Really looking forward to this one. Hopefully this will finally solve my Homey's date/time issues.
But after that, adding worked like a charm and the triggers activate!
Then tried to install the Fibaro app manually. As a result got the error 'already installing' and it gave a check-mark in the pop-up 'installed'. Went to the apps section - no Fibaro app installed...
Later on I could install it manually.
BTW: Kaku app crashed.
So much for first impressions - will test further...
Edit: Added the wall plug via the Fibaro app and that does work well - yoohoo!
Z-Wave Findings so far:
when trying to pair any z-wave device it will give me this error in console:
And stays at the please wait while z-wave is getting ready.
After a power cycle this has been fixed, even though the console error stays.
There is no way to know which one is for Z-Wave, or Z-Wave+ for the
- Motion Sensor
- Door/window Sensor
- Smoke Sensor
They both work though.Fibaro Wallplug: (Z-Wave)
Measures the wattage pretty accurately
When included as a light only on/off capability is used, no power (usage) (W and KWh)
When included as a socket i'm missing the power usage (KWh)
Motion Sensor: (Z-Wave)
Does get triggered when seeing motion
No parameters are available as of yet.
EDIT: Seems like homey doesn't send the "Pairing Done" signal, sensor stays in pairing mode.
Smoke Sensor: (Z-Wave+)
No temperature capability.
No parameters are available as of yet.
When the device is out of reach/offline it won't state it anywhere, just keeps the latest information that was there.
@reemster
Range is about 9m with a battery device (motion sensor), and 12m with a wall socket, both normal Z-Wave. (through an open door to the outside, but direct sight)
No possibility to test the range of my smoke sensor (the only Z-Wave+) the connectivity test doesn't want to work.
There seems to be no routing as of yet(?) at least not with the wall socket
There is no way to add custom parameters anymore, will this stay this way? if so, then please add all the options that are available for any device.
And now my date and time are (finally) 100% correct... thank you, Athom!
I think there will be a map kind of thing in the settings menu showing the mesh grid.
But at the moment that has not been implemented yet.
My guess is that it will take a while as well, pretty hard to implement the right way.
did you enable experimental updates?
Because 0.9.1 is just for the experimental channel right now