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
0.8.32
This discussion has been closed.
Comments
Apparent update within 0.8.32 is breaking working Z-wave devices (polling and z-wave wakeup)
See also previous post in this topic.
Pre 0.8.32
Post 0.8.32
- Polling of Greenwave powernodes is not working anymore... nothing changed to these devices... only data points during every reboot (several today)
- Fibaro motion sensor still at the same position (~2.5m in clear line of sight to Homey)
- Fibaro motion sensor is providing illumination reports every 1800 seconds...but only temperature and battery during reboots
- The Z-wave wakeup interval does not show in Insights; as pre 0.8.32 it should provide additional data points (outside the 2062 sec) for illumination, temperature and battery; but they are not visible in Insights
- If sensor is past it's wake-up point, it shows as (failed) under settings
- Motion is still working but most likely another z-wave command class
- Restart Z-wave chip / reboot provides a single wakeup... and thus only 1 datapoint after reboot
- Removal and re-adding the motion sensor (2x) does not resolve these issue
For the record the log: 0E146DB463No response from @Athom / @Taco on several posts (forum/slack/github)....
Voice data management is coming in the future.
Z-wave wakeup is apparently working...
I changed (on suggestion of @BasVanDenBosch) parameter 80 (blinking led), saved the settings and did not manually update the motion sensor..
After 2 hours (7200), I again have a blinking light (wake-up succesfull)... but at the same timestamp no data from illumination, temp and battery (whereas pre 0.8.32) this data was provided
I also had this issue with 0.8.30 and it was necessary to full reset including wiping the user settings, as a reset whilst keeping the user settings did not resolve the issue.
As I have added a lot of sensors and flows, it would be preferable if this problem could be solved in another way then a full reset, but unfortunately we do not have telnet or ftp access. Are there any plans to make this available in the future?
Does anyone else have a similar experience as I have not read this anywhere yet.
I have a flow which is in the morning is triggered by the motion sensor. The idea is that the Wall Plug switches on and the radio starts. This was working very well, up until .32. The wall plug is not switched on anymore. I have no idea what the problem is. Reinstall/adding the plug again did not solve the issue.
I did the upgrade to v0.8.32 this Wednesday, and ever since my Homey will freeze at least once a day.
When it happens, also the LED Ring activity (Rainbow effect) is fully frozen.
Does anyone else experience this too?
Tonight i will do a complete reset and check again. If it will happen again then I'll submit the log to Athom for further analysis.
Also running .32 but no issues.
Could be an app or flow? Maybe, if your up to it, document all flows, apps and there settings and every day remove suspicious flows and apps and document when you removed which app and flow.
Have a ping logger pinging your Homey to see when your Homey crashes.
Again, if your up to it
In browser I suddenly got a message from chrome itself which stated "true" and then homey was completely frozen.
Also, haven't had any stability problems on .32 so far, so yeah, I agree with Robin... this may be related to a certain app or flow you have running (infinite loop, maybe?).
even after a reset with a save settings, it did not respond.
then i had to reset homey and wipe all settings
(hating the moment, not the update fact )
Not reachable anymore.
- Homey seems to be a little faster, but crashes on me once every two or three day's. Not sure what causes it, but will try to find a cause next week. (since it's crashed, i think a log is of no use... right?)
- Presence seems to be off, not noticing whether i'm home or not.
- Push notifications seem to be off as well, not getting any response. Maybe because of the beta?
I'm at work right now, so cannot get my homey back to life, usually unplugging it from the power, wait a few seconds and plugging it back in solves the problem for a few days...
Any thoughts?
Tnx!
So, KAKU was working with 0.8.30, but not with firmware 0.8.32
Try re-installing the app?
I re-install the app, but also that is not working.
you will have to have some patience, the 433 mhz chip sometimes just doesn't want to talk to homey, this can be resolved sometimes by restarting homey, sometimes bij power cycling the unit, but sometimes it needs multiple reboots or just to have so time being on to have gone by before a reboot to make the chip work again.
Today i had it as wel (while being busy with some flow adding/changing) i had the same message again, except this time it was shortly after i tried to save a new flow, which caused it to probably corrupt the data.
Because after a power cycle it gave me a red ring.
So i tried to reset it, with keeping data, it kept loading/booting. (for about an hour and a half)
So power cycled again with the end result of a red ring again (corrupt data?)
So now i reset it without keeping the data and i boots up fine, though its a pain in to ass the start all over again.
Luckily because i am trying to squish another bug with the need to full reset also, i am backing up my flows manually in an excel file.
though its still a pain in the ass with 51 flows... to put them back one by one. (it's not the first time as wel)
What i noticed so you can try to avoid to corrupt your data, homey becomes pretty slow with loading and saving your flows.
So stop what you are doing and don't even try to save the flow you are busy with.
And take a look in the settings page what your average loads are.
If you feel it is getting faster again you could try to continue if not just take a reboot (maybe save/send a log for athom to debug afterwards before rebooting), if the error happens you need to reboot anyway.
The reason is probably(?) the garbage collection athom is using, can't think of another thing that could cause this
Maybe that will help?