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
just because you find that is the best route, maybe the z-wave devices find it otherwise.
there can be a lot of interference for example from the one on the attic to the one you find the best route.
A big concrete roof/floor or something metal (or a combination of) in between can cause this big time.
Even something that you can't see or think of that makes the signal way worse.
Extending the mesh network is always a good idea
I find it very very frustrating to have a response from Athom Support to suggest its the app developers fault..
I find it equally frustrating to have the experienced chime in and say we should expect this because its experimental..
Of course we do.. but we like having cutting edge. this is why we are into Home Automation in the first place.
It actually is much more simple. Two days ago all of the people above claim to have had stable systems including me. Today we dont.
It would be less frustrating to have Athom/Experienced Users say - 'Yes, this firmware caused more problems than expected' instead of saying to the user - Did reboot// did you leave it settle// did you ....
That way we are not going around making the problem worse.
Please understand, I know everyone is just trying to help out and be helpful which is what makes this community great. But sometimes, we have be real too
I have been away for the past few days and Homey updated itself to 1.5.6 rc6. So I had no clue of how long it took and glad that happened else, I bet I would have been nervous to update and during the update like many other members above.
Nobody to PTP, nobody to disturb Homey.
Came back today and everything seems to work. Zigbee works, z-wave works.
A bit shy, I have included one of my six Fibaro's motion sensors. All those six sensors have been just sitting with battery removed since the stupid z-wave bug. So far so good, the sensor works perfect. But it has been only a couple of hours and I hope I am not speaking too soon.
Tomorrow I plan to include the second and so on. You will hear if no joy and the bug strikes again. Yes, I know "I am on experimental" hope the new dev tools will help Athom fixing this once it for all and get this Homey promoted here down under as so far it will be a shoot in my own foot to sell this as an HA controller.
Thanks to Athom for this so far good firmware, and for the hard work. Sorry to hear other members have big issues with this new firmware...
All went well although it seemed to take a bit longer than usual (like 30min?).
Everything worked like expected after the update.
what works for me is putting your homey close (same room, max a couple of meters) to the device to be added. New devices can only be added with direct connection to the controller (homey) and not routed (via via other devices).
On inclusion (device being added) the device itselfs draws up a routing map of neighboring devices to communicate with. So it doesn't matter if the controller is not directly reachable anymore as it will try to communicate via the neighbor devices. With the latest update I can finally can see the last working / known route and it helps me with devices which work not all the times as I can see the "wronly" added devices ;-)
ps. I use a powerbank to walk around with the homey until I am finished.
so.. meanwhile.. you've no home controls or automations?
After a PTP and waiting some time it looks like this:
But, after some hours, Homey will loose the connection with the network again.
I have Tradfri bulbs and some Xiaomi Mi ZigBee endpoint devices. The distance between Homey and the closest 5 bulbs is 1 to 4 meters.
I did a search in github issues and could not find a similar zigbee issue. Does that mean I am the only one? And can somebody help me to solve my problem.
Merged above post from a seperated made topic into the 1.5.x experimental generic topic.
I notice stability returning last night to my system
Today suddenly things are responding better and seems 90% back to normal
I guess time allowed for healing of the network
Thanks Bram!
Homey is on it's way to you now. Take good care of him
I thought it was a her?
1.5.6.RC7 just been released to the experimental channel
Hi, any idea what the [Other] Various bugfixes and improvements are? Can't find it on GitHub and I am very happy with rc6, but curious what rc7 brings :-)
Thanks for your quick answer, I noticed that, but does athom clear the staged for the release tag after they released an rc update? With other words, if I look now at everything with the label "staged for release", will it be in the currrent rc?
If not, it is a bit gambling what will be in the update ;-)
I've just received some more Xiaomi devices and added them to Homey, but they were added twice and didn't work as expected. Made a Github issue for it: https://github.com/athombv/homey/issues/2078
Wondering if others see the same.
Added two more Fibaro motion, now 3 included in total. Before even one Fibaro motion used to crash the z-wave.
However, the Fibaro motion sensors work randomly, one hour motion alarm stuck on, the other hour no motion alarm and so on. I still cannot have proper flows based on those sensors.
Hope into a stable version soon.
I only can disable all the updates but can't choose to only get the full working ones.