I have a strange issue.. sometimes all my actions are not executed stated in the RM4. I can see that nothing concerning the faulty devices can be found in the log. Is there a way to see in the logs that the HE 7 controller is trying to turn on the devices? Need to isolate if this is a HE 7 controller issue or a device issue. Since this happens randomly to different devices it seems to be a controller issue. Would like to verify this before sending a report to support.
Thanks for the reply, I have tried to delay for 2sek in between every action in the RM4 rule. It did not help.. But great if this is a known issue.. then hopefully it will be solved soon?
I tried groups and simple automation rules without any success.. get the same issue. I found that you can turn on debug logs... But then I will need to learn the Z-Wave protocol..
Do you have the details on this timing issue? I've got some weird stuff going on with simple automation rules not executing against all devices listed, and I'm wondering if it's a related problem.
I don't remember doing this, but maybe I'm not thinking of the right thing. Something vaguely related that isn't going on here is the Zigbee bulb issues that I think Mike stated are being addressed in 2.2.5, but that only affects specific, different commands sent around the same time to the same device (something like an "On" followed by a "Set Color Temperature" or "Set Level," but I forget exactly which or what order)--but definitely not the issue here since it's just a single "On" to each device.
Hopefully logging in the rule (or possibly other apsp that might also use the devices in question) as above can help reveal the problem here.
I think the logs are a little bit confusing. When I turned the rule logs on and triggered the rule, I can see there is a log for turning the "Living room window light right is off"? Waited for some time on the log since I thought some logs could be delayed without any update.
Also I can see that the action for "ON:Kitchen Island Dimmer" is handled but the light is physically not turned on. There is no log for turning the device ON either..
Note: The kitchen dimmers are all "Fibaro Dimmer 2" devices and the rest devices are the "Telldus plugin switches".
I can see that the Dashbords tiles are not always upated, means still off state even though the state is on when checking the device itself? I have refreshed the browser several times using my local IP. But let's discuss this in another topic
Yeah, the point of turning on the logs is to move you further down the troubleshooting path. Now you know that it's not RM that is messing up, it's the device.
It's not at all clear why your "Living room window light night" is turning off immediately after it was turned on by the app. Nor is it clear why "Kitchen Island Dimmer" is MIA.
Ok.. well then ALL my devices are broken.. Since it seems random what device is working or not. Some times its the kitchen light that is not working and then suddenly it is one of the livig room lights. It's not impossible but unlikely I mean it is six different devices and two different vendors. Any tips on how to analyze this further?
Hi, thanks for the suggestion. I'm new to Z-wave but are not all Z-wave PLUS plugin swithes working as repeaters? I mean I have at most about of 3 meters(120 inches) in between the devices.
They are are not all installed in electrical boxes.. but they seem to be bad repeaters . I will get a Z-Wave plus repeater and try if it helps.. Any repeater you can recommend?
Something vaguely related that isn't going on here is the Zigbee bulb issues that I think Mike stated are being addressed in 2.2.5, but that only affects specific, different commands sent around the same time to the same device (something like an "On" followed by a "Set Color Temperature" or "Set Level," but I forget exactly which or what order)--but definitely not the issue here since it's just a single "On" to each device.
