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 v1.5.7
We have started the rollout of Homey v1.5.7, which is a bugfix release on top of v1.5.6.
Because this update is distributed in waves, not everyone will get the update at the same time. Existing users running Homey v1.5.6 can bypass the waves by checking for updates manually in Settings > Updates.
Changelog:
Please report any issues you find on our Issue Tracker.
As a sidenote, there is some unclarity about new Homeys being shipped with Homey v1.5.6. Due to a minor hardware change —which is incompatible with older software versions— we chose to produce the new Homeys with the new software.
While Homey v1.5.6 still is in the experimental channel, we regard this update as more stable than the current stable version (v1.5.3). Existing users will receive a stable version of Homey v1.5.7 as soon as the update is cleared by our Quality Assurance team and no new problems arise during testing.
Because this update is distributed in waves, not everyone will get the update at the same time. Existing users running Homey v1.5.6 can bypass the waves by checking for updates manually in Settings > Updates.
Changelog:
- [Core] Fixed a bug that could prevent renaming zones
- [ZigBee] Simultaneous reported attributes are now handled correctly
Please report any issues you find on our Issue Tracker.
As a sidenote, there is some unclarity about new Homeys being shipped with Homey v1.5.6. Due to a minor hardware change —which is incompatible with older software versions— we chose to produce the new Homeys with the new software.
While Homey v1.5.6 still is in the experimental channel, we regard this update as more stable than the current stable version (v1.5.3). Existing users will receive a stable version of Homey v1.5.7 as soon as the update is cleared by our Quality Assurance team and no new problems arise during testing.
This discussion has been closed.
Comments
With 1.5.6. they worked fine.
For me 1.5.7 was no change in 433.(as there is also nothing mentioned in the changelog of 1.5.7 about that)
There are a lot discussions on the forum how to troubleshoot 433/ Kaku.
There are already a lot of Homeys on 1.5.7 so could it be a coincidence with something else changed that blocks your kaku?
Is there any way to "convince" Homey that 1.5.7 is available (despite not being experimental)?
Thanks! Pulling the plug did fix it!
Thanks for your response @bvdbos
When you're on 1.5.7 in experimental, and it goes to stable (without changes) you don't have to do anything in fact.
If you don't want to continue receiving experimental firmwares, just disable the option to receive automatic updates and you're done
I am not really sure if I understand you correctly, but if I disable the option to automatically receive experimental updates, I will still be on 1.5.7 Experimental and not be able to receive stable releases. I still need to reset Homey to be able to re-enter stable channel. Right?
Just did an update to 1.5.8
As a present I did receive spontaneusly an "unknown node""
Is this recognized by somebody?
Any idea how to remove this node?
Beside this I don't see for a couple of days no "z-wave spider" anymore at tools.
I don't complain often (only for the non-functioning voice until now) but this is really bad IMO...
If you just start removing functionalities because you can't get them to work as you expected, what will be left in the end??
Ok, I'll remove my comment from Github then, but my 'disappointment' is still the same