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
In fact only Kaku is reporting in insights. Got 6 greenwave powernode 1 sockets and not one is vissible in insights.
8.39 firmware
Logging of Aeotec sensors is working for me!
@posthok I have this zwave configuration for both my Greenwave Powernode 1 and 6.
Data: 1,1,255
Polling: a value between 200 and 300 (variate between devices to spread the polling load)
Thanx for your settings But still no insight view for z-wave.
I'll wait for the z-wave rewrite maybe that makes a difference.
This is also the case on my fibaro wall plugs. Not sure why athom chose not to include power insights on lights?
So don't expect a quick fix on this....
Also, in the pairing process I was asked what type of connection the socket would have (lightbulb, ventilator, heater). I just OK-d that... can I edit these settings later...?
It was added with a nice icon, the one below in this example is a powernode added as a socket.
However, in a flow the ventilator does not show as an on/off switchable device, but I can only set z-wave parameters:
That is not as it should, I hope....
Do i report this as a bug? How?
You should be able to shift on the right side of this card.
Otherwise re-add the device again, but now as a socket.
Z-wave rewrite is ongoing.
Hopefully with the z-wave overhaul...
Anyone know how to do this?
The powernode (but also the Fibaro 2x 1.5 Relay) are both Z-wave devices using the Multi Channel Command Class.
For another device to switch on a Multi Channel end-point (socket of the powernode), it has to support the Multi Channel Command Class (Association) itself...
Not all devices support this class; Homey does. So it depends on the devices used.
With none of these devces I'm able to add a multi channel node (e.g. socket of the powernode-6).
So either the input validation of the GUI is incorrect, or the COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION is not fully implemented yet to support this function. I created a Github issue for this.