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 Official
Homey v1.5.X - Experimental
This discussion has been closed.
Comments
Not only Fibaro-Devices, also Philio Motion Sensors (Reported on Git).
At this moment, my zigbee network is stable since weeks.
Why Github, that we all know because that's the issue/feature tracker Athom uses and this is a community forum.
I think it is not complaining but telling what happens.
I did invest around €1000,-- last month in domotica. Then you expect at least the basics will work.
I do agree to use github more. I will from now on
I do also see progression. For me after a month struckeling I do see Z-wave, KaKu, and NFC stable. These where also not stable before. Zigbee is still not. If Zigbee will be stable I'm happy. And I do still believe that Athom will solve this
My solution so far is to reset Homey every night by Candy. After every update I will stop this reset and try again.
This topic is about the 1.5.6RC.X experimental releases wich are labeled experimental for a reason and where everyone has accepted the warning when activating it.
Telling and discussing about problems is good but i see lot's of posts with only complains above and that's why i posted my above message. Complaining about things don't work is one thing but when nobody makes a Github issue Athom will never know about it because this is a community forum wich is not monitored for issues/feature requests.
I am not complaining. I try to give some information, also on Github.
I have resolved ALL of my ZWAVE issues. I will say.. WITHOUT ANY help from Athom Support. All I got back from them is that it must be the app developers fault - @Bram
Anyway.. heres what I did and I hope this helps someone else.
With the new tools page - https://developer.athom.com/tools/zwave
I identified which devices were getting the highest error rates. I then took the highest error-ing device and removed it from my network. I did the reset of the device and then re-added it. I waited 24 hours and moved on the next one. Until I have zero error devices. I had to do 6 devices in total.
I can't say waiting 24 hours between devices makes any difference. But since all of my devices are tied to flows, I didn;t want to have to fix every flow in one go. So this meant fix device/fix flows/wait 24 hours.
I am now back to ZERO delays in my triggers and flows for the last 48 hours
I am still on 1.5.6 rc7. I am not updating until I hear more feedback on the latest versions.
Experimental does not mean: not to use !
Athom should quickly accept customer dissatisfaction. Every update makes Homey unusable. Your comments will surely make us all happier. Thanks for nothing. :-(
That's because too many people use experimental as a stable release and then only start complaining about it or expect that it can be resolved in an instant. Experimental falls out of the normal support and ofcourse Athom will support you but when running experimental you know the risk you are taking when you have only one production Homey at home running experimental, that's what you accepted when activating it (the pop-up you did read and accepted).
I dont think anyone is demanding .. I think its frustration to be told its their fault.
Its when Athom introduce a problem with experimental and then say... 'no, not us.. must be you'.
I for one, would have no problem with Athom turning around and saying.. 'oh, yes, there were unintended consequences to our latest firmware. it wont be fixed until 3 weeks time.'
I did the same, works like a charm
When you want upgrades, don’t get frustrated and act like spoiled kids. Buy a kaku with a receiver and shut up.
Please guys, stop this kind of time wasting, let's find and post real and new items, thanks.
Did not experience any problem with Zigbee (Ikea bulbs) and several Zwave plus devices since last experimental update. So, am I just a lucky user or does the difference in Homey-behaviour has something to do with combination of devices or maybe the local situation?
yes sir, on rc8, but I did this "trick" once the new Zwave diagram was introduced. That was on 1.5.6 rc something.
It gave me insight about the zwave routes between the devices and helped me to solve the faling devices
And how many apps do you have running?
I had to restart Homey every day, now Homey is up and running for 5 days without restarting. I don't know what changed exactly to achive the new behaviour . It looks like Zigbee network is running a self learning curve to improve itsefs?
- Denon AVR
- Samsung Smart TV
- Bosch-Siemens Home Connect
- Google Chromecast
- Spotify
- Wake On Lan
- Pushover
Currently running 15 apps, so I guess 22 at the time.Unfortunately I did not make a screenshot of the Zigbee links when the problem occurred, so I can't check if it somehow changed.
For example 1 light should switch on at 7 and off at 21 and that seems to be working (the flow is working).
But after 21 the light switches on again and there is no flow for it.
When I look at the z-wave messages I see my off message and after a while some enable message (at the time it goes on).
Switching off is no problem using the app but it switches on again after a couple of minutes.
Is this a known problem?
If not I will make a github issue for it, I could not find similar issue at github but maybe it somewhere in an other issue already.
This is what I see in the z-wave log:
It is a fibaro plug