I’m a new Homey Pro user. So far, I’ve added 9 Leviton Decora Zwave light switches to my Homey Pro using the Leviton app by Koktail Software Development. I’m able to switch lights on and off manually through the Homey app on my iPhone, however, when I write a simple flow to turn them on or off at a specific time, nothing happens. When I add a notification to the flow the notification goes through which suggests the flow is running but for some reason the switch isn’t activating. When I log into the Homey Developer Tools, go the list of Zwave devices, and test the switches the tests are successful (at least it says that the nodes are reachable). However, when I send a simple on/off command from the Developer Tools the switch doesn’t activate and I get the message “timed out after 10,000ms”.
There have been short periods of time when the flows have worked but I haven’t been able to identify for certain what is different when the flows work. For example, one flow worked after I rebooted the Homey Pro, but then they all stopped working again. They worked briefly first thing in the morning and then briefly again after the system had been idle for most of the day.
I’ve removed and then re-added a couple of the switches but that hasn’t seemed to make a difference either.
In the short term, I cans set up routines on Alexa to do what I want to do, but I’d like to understand why it’s not working on Homey and fix it.
(Homey can’t command multiple devices at once, especially when they use the same protocol. Reason: Homey sends all commands at once, causing a signal mess.)
If so, add a slight delay between each device action card.
Or, group them using the < group > app, or Device Capabilities app;
these apps command the grouped devices sequential (as should).
I believe that I have selected the device, but as a newbie I could be mistaken. When I write the card to turn off the light, I first select the device - in this case the master bedroom light - and then I select turn off. The flow will work occasionally - but 90% of the time it does not.
Thanks Johan - you’re correct. In my haste to share a flow, I selected the “Master Bedroom” zone instead of the “Master Bedroom Light”. Sorry for the confusion. Here is what my flows look like more typically - and they don’t work. For some reason, it appears that the request to turn the light on or off is timing out before the light switches.
@Don_Constantine So, the switches don’t respond at all?
Apparently I missed this part of your OP:
If so, we don’t need to test with flows yet.
Don,
Do some of these devices have an awful high number, at the Rx and/or Tx columns (@ Developer z-wave page)?
If so, it’s called a chatty device, which could ruin your z-wave mesh by flooding it with events.
You should be able to decrease the interval of requesting / sending data via device settings.
Here is a screen shot of the z-wave page showing the number of Rx and Tx (I don’t know what is considered to be a high number). I captured the screen just after I had sent a simple off command from the menu on the right hand side and you can see the message I get in the bottom left (timed out after 10,000ms). I looked at the device settings on the developer tools site, on the Homey Pro app, and on the switch manufacturers operation instructions and I don’t see where I can change anything to do with timing of sending or receiving data. Per my initial post, if i write a similar flow in Alexa (Amazon calls them routines), those flows work.
The Living room device as main suspect, and at second place the family room device: these really send/receive a whole bunch more events, compared to the other devices.
As a test: Remove the living room device to see if this makes z-wave network responsive.
What also caught my eye (not a real issue, but it stands out):
There is no mesh network according to the last known route; all devices are communicating directly with Homey.
This shouldn’t be a problem, but Homey’s z-wave signal range is short (depends, sometimes just 4 to 5 meters).
All are z-wave devices that close to Homey?
(Z-wave creates a dynamic mesh itself, it’s not managable)
A mesh could look a bit like this
1-4-6
1-4-9-8
1-7-2
1-7-5
the first line meaning: device 6 uses device 4 as router to reach Homey (1).
.
That timeout error is only from the web page process, expecting a response. Z-wave possibly continues what it tries to do.
To me it’s a bit of a strange error message: it doesn’t actually have to mean something’s not working on Homey itself.
Thank you for all the help! Removing the living room light seems to have solved the problem. I was able to run over 10 different flows without any issues. I then re/added the living room light and the flows continue to work. Hopefully, this fix will be permanent. I’m not exactly sure why it worked but I’ll continue to try to learn about the system to better understand the details of how it works.
As for your other comment, most of the switches are more than 4-5 meters from the hub (it’s a 225 square meter two story house). So I’m not sure why there isn’t more of a mesh network.
