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.
Comments
Please Athom, give this some attention. I fell partly responsible as I rated the Homey 4 stars in mij PCM review, anticipating that - 2 months down the line - this would be solved.
Adding new functionality to Homey is nice, making the current work is simply a must!
I have to disagree with you. Greenwave has worked for me without any issues, albeit in a setup with an Aeotec z-wave stick controlled by Domoticz. Also, after a Homey re-boot - not touching Greenwave - the unconnected powernodes will always auto-connect again.
So, it is my conclusion that it is not Greenwave hardware related, but the combination of Homey with the Athom Greenwave App.
PS
I too have Candy re-boot Homey every night, in an etempt to keep Greenwave operational.
It looks to me that the Greenwave app is the issue in combination with Homey current versions.
The powernodes 1 don't have this problems, it's the powernodes 6 which have the green flashing lights. Ah, but rebooting every night makes a big difference, that's a good advice for people who suffer from the greenwave issues... Still: the powernode 6 devices pretend they're so good I'd think it would be a real best-seller but they're not made anymore?
Actions taken:
- (re-) confirmed that the right parameters are stored on the motion sensors (by modifying the LED color)
- Updated my flows to prevent the erratic data reports from my motion sensors to send repetitive ON (or OFF) commands; added AND card to only send a switch on command if the lamp itself is switched off
- Luminance values were already averaged (2 data points) to smoothen fluctuation; I consider to even extend it to 3 data points.
Today Homey / Greenwave has been running again stable without stalling / breaking up and is responding directly without delays. I will disable my nightly Homey reboot to see if the stability will hold tomorrow.
On suggestion of @caseda I will re-pair my motion sensors tomorrow evening, to see if the parsers that were still part of the Z-wave driver at the moment that I added the motion sensors (back in September) are causing the erratic data reports.
Lesson learned: DON'T trust Insights (graphs) while troubleshooting, but download the actual loggings to see the data. Insights shows multiple data points with same value and with some seconds in between as 1 point (only).
Suggestion to other users:
Since I re-paired my Greenwave powernodes with SW v0.9.3, my powernodes are running quite stable (no green lights flashing, on any of my 3 PN-6's and 2 PN-1's)
Re-pairing them with current Homey SW and GW app (1.0.6) will even automatically add the right parameters (polling and alive) to avoid stalling the Z-wave network. So it might be an option to exclude/remove the powernodes from Homey and re-add them (after a reboot)
As mentioned in my post above, I would recommend to re-pair them with current SW and app version.
Unfortunately I have to say that both the 1 and 6 port Greenwave have flashing led issues in my setup....
- With the flow adaptation, Homey is running stable again for serveral days - Re-paired my Fibaro motion sensors (with in between reboots and update to v1.0.1)
Still my motion sensors show some "erratic" data reports, which cannot be explained by the settings used; see the Github issue that I created for more data / background...
I would appreciate if someone with a similar setup (combination of Fibaro Motion sensors and Greenwave Powernodes, without any other Z-wave devices with routing capability), could contribute their Insights data (downloaded) and devices settings to this issue...
I don't have Fibaro sensors, but Aetoec's (4 of them). Can that be of any use?
- Removed all Fibaro devices
- Removed all Greenwave Powernode 1 devices
- Removed all Sensitive devices
- Removed the apps from Homey
- Factory reset Z-wave
- Reboot Homey
- After restart, pulled the Homey plug for 10 minutes
- Installed only the Fibaro app (as most my devices are Fibaro)
- Installed 2x wall plugs (checked working fine)
- Installed 1x Fibaro Motion Sensor (Z-Wave Plus), checked working fine
- Installed 2x Fibaro Dimmer 2 (checked working fine)
Wanted to install another Fibaro Dimmer 2 and get the message "wait for zwave to become ready". This message stays up for minutes. Still wanted to add 3 more Fibaro devices but stopped as I also noticed that Homey membory increased from 80Mb to 140Mb and all earlier zwave devices have become unresponsive. Looks like zwave freezes again. So stopped the effort.
It looks to me there is a massive issue on Homey with zwave, not specificly related to Greenwave nodes as I experience it also with Fibaro as explained above.
I am 65% dependend on zwave as most my devices use this. Homey is completly unreliable on this protocol for me so I have the same situation as before the complete rewrite.
Can someone confirm that also a complete z-wave reset does not solve your issues experiencing with an unstable zwave?
Looks there is more work to do for @Athom ;, shame this happend just before the official stable release that I am not experiencing as stable at all.
@Annemarie FYI
What I noticed is once a device is included the zwave seems very stable, the proces of including is the real fight - there is def some room for improvement (feedback of status) from the controller / leasoned learned. My next steps will be to introduce a couple of dimmers and switches we will see if Homey is capable to deal with it - but again in my experience it is the inclusion proces and feedback to user that need improvement.
So 20 devices is no problem at all for Homey.
Tell me how I can get the log(file) and I will happily forward it to you!
The sensor should trigger the switch to turn on the light. Last wednesday I already added the sensor to homey and created a dummy flow to test the responsiveness. In general this was pretty good. Movement was picked up and Homey responded. This weekend I installed the switch and adjusted the flow. In the meanwhile Homey also updated to 1.0.1 (was 0.10.9).
From the Homey app I can switch on the light, responsiveness is reasonable. But Homey doesn't seam to react to the motion sensor. I can see the different values (movement, temperature,..), but it looks like they aren't 'realtime'. For example: when I walk by the sensor I am detected but Homey doesn't update the status.
The sensor gives feedback when it detects movement, a led lights up. So the sensor is working. The sensor is also in range of Homey. But it look likes Homey doesn't process the signal. Or it processes it with a big delay.
Any tips? Will there be a update for z-wave? Is it a bug? It looks like I am not the only one with problems.
Try to remove and add the HW and see
Hi,
The behavior that is described above is very similar to what I'm facing the last days. I have mainly zwave devices from Fibaro ( approx 15 x Dimmer 2, 2 z-wave PIR, 3 z-wave plus PIR).
I also removed all devices and performed a factory reset of the z-wave network due to unexpected performance issues. Unfortunately z-wave is still not functioning as it should....sometimes it's working....sometimes it is very slow and sometimes it is not working at all.
This is pretty annoying so hopefully Athom can fix this ASAP.
Thanks
I
- Did you change any settings / parameters on these devices (in particular the motion sensor)?
- Is the responsiveness the same directly after a reboot or deteriorating over time?
- When you have the device card open (seeing the motion sensor state), does it change when walking buy?
- Can you share the flows that you are using to switch on the Fibaro switch?