This error happen when the device ID 2 (ID from domoticz) is not yet in the domoticz database.
It s possible it's a new device added recently, and domoticz need to add it, according the timestamp (22:10:04.XXX), you had all errors in same time, but no more 1s after (time for domoticz to add them) ?
>I have ten of these in use. Two or three of them are always working. The other ones intermittently fail
There is less issues on wired one, and from that I m seing they are using the covering cluster.
You are sending 10 requests every time ?
That 's not the firsts ones to receive the request that work every time ? Or it’s totaly random ?
You have take a look on the mesh, to see if there is not a similar thing on the working one (the same routeur, or only direct connexion) ?
But if you send the request a second time, they can work without problem ?
They have been added ages ago and I have not made any changes to the group. So I am a bit confused about the error.
No, I am sending requests to subsets of the devices. I have three subsets. The first is triggered 5 minutes after sundown. The second set is triggered 10 minutes after sundown. The third subset is triggered somewhere in between. Each subset takes about 30 seconds to complete. The devices refuse to react at random. There is no logic to be found in which device is not reacting.
I am not sure what you mean with looking at the mesh. What should I be looking for?
If I send the command to an individual device that has not responded to the group commands shortly after it refused, it does not react. If I wait a few minutes and activate it from Domoticz, it works most of the time (but not always). I sometimes have to go to deCONZ on my RPi and press the exec button in the Down/Close section of the Windows covering section:
They have been added ages ago and I have not made any changes to the group. So I am a bit confused about the error.
So yes, if it’s an old bug, not normal, can happen on launch, if you use the group in domoticz before the plugin was running, else I don’t think it s normal …
The devices refuse to react at random. There is no logic to be found in which device is not reacting.
If it s random, not usefull to search for an indication on the mesh …
This can be usefull, try to check deconz log with “info” “info_l2” “error” and “error_l2” when making this request.
But your method is good, making a group with some device, and send the request to the group, and I don’t think you can do better, because if you send the request individually, the device don’t work.
For me it s more a problem with the device, but it s strange it work all the time using dieclty the GUI …
If you look at the cluster list for yours devices (the second circle) You have the window covering cluster, but not the on/off or the tuya one ?
The error doesn’t bother me as such. And if it has no relation to the problem with the roller shutter devices then we best leave it at that. Errors occur somtimes
I will test this the coming weekend. A NooB question though: Where do I find the deCONZ log? I see Debug View in the menu. Should I activate the options in the Debug View Dialog to generate a log or is there a log stored somewhere on my Pi?
Correct! I do not have the On/Off cluster or the Tuya cluster. I am not sure if that is significant though.
It happen when you make a command with domoticz (can be a script or a scene)
It s the domoticz unit n°2
If deconz have full started, it have filled a temporary database, so not normal the device can be not present in it.
Where do I find the deCONZ log? I see Debug View in the menu. Should I activate the options in the Debug View Dialog to generate a log or is there a log stored somewhere on my Pi?
No, it’s “easy” with the GUI (depend of devices you have, can be realy talkative), it’s in Debug view, can enable “info” “info_l2” “error” "error_l2’ and if you can “APS”, and can just make a copy/paste of doubtful lines.
I think we will see APS error. But when you make individual request, it s for me, exactly the same one than when you use the deconz GUI, I don’t see reason for one work better than the other.
Correct! I do not have the On/Off cluster or the Tuya cluster. I am not sure if that is significant though.
Yep, some device can use both cluster, or worse the tuya one, your device is more standard than other, it s realy a pity if you have issue on 10 of them.
Thanks for investigating and asking around. I guess I’ll have to learn to live with it or replace the devices with something that is better supported by deCONZ or adheres to the ZigBee standard better than the devices I now have.
If you have suggestions for such (better) devices I am all ears
Lol me too, I have just buy one 10 days ago, still in test.
Wana buy a Legrand one, but 75 Euros, and I have found this one a 20 euros. But it s tuya, you can have random stuff, I cross my fingers to don’t have issues.
I think?
How to setup scenes on phone?
I do not have an laptop in the rooms that i need the scenes, and to take the laptop with me is not my question atm
Is there another way of doing this?
When doing a scene to ON in domoticz, exactly the same lamps does have problems.
The rest works good and going to the color / dim value i did set in the scene in Domoticz…
It don’t work using a phone ? Try to use “desktop view” to have the same display than on a real PC
But groups can be used only if you have a group a device that need EXACTLY the same request.
Else no other solution than using a script to delay requests.
I did try to use that desktop mode on an samsung s21, but unf this didnt work also.
It keeps saying about the screen resolution.
What is the best way to make a “one” button switch to turn on the lights and/or do dim and/or change the color for all devices at once?
i do not want to script this in any way since the colors for some lights are changing several a month
or, if any script is available could you send me a lua based example script to do this directly IN domoticz?
thanks!
i buyed an 10 inch tablet and now i can make scenes, so… I have set all scenes IN deconz…
so far so good, and i can control them in domoticz.
But… why does a group on/off fade dim to the value, and does the scene not?
i have setup in all scenes that i want to fade in all lamps in that scene for 10 seconds, but the fading is not working?
when turning on or off a group the fade is working great, why is this?
thanks
But for that you need the 20 devices need the same command, you can’t set a different color for each.
Okay, now i understand… That’s not what i need.
The reason for a scene is that i use a lot of ynoa gu10 spot lights, and these bulbs does not have the same color, some are way more yellow instead of warm white, and some are more cool white then warm white, that’s why i need to set them single instead of “all”.
if it was that easy as just turning on or off the lamps this problem was not there
Hmm… That is a lot of work then.
Why is this behaviour only with Deconz?
I’m using > ESP Boards, RFLink, RFXCom, Sonoff (Tasmota), Milight (AppLamp) and Z-Wave beside the Zigbee (Deconz) and none of them have this problems…
I can send out 2 times a second to a devices without any interruption, but that is not possible on the deconz so far…
(Ofcourse i do not send out that many requests in any way, but it’s just as an example)
I hope there will be a fix someday with this “loss of target requests”
If the requests are to fast, then i hope that they will add an (adjustable) time (100ms?) buffer in the future
into the coding of Deconz that we can set to made scene/group requests longer instead of doing its request 1 by 1 from a script in Domoticz, as this is not easy as 123.
Btw, before Deconz i used the Hue Gateway and that has always worked without any interruption…
Also when send out 4 scenes in 1 time, it was working perfectly.
The only reason that i changed the hue gateway for deconz is because i want to have more control (and an overview) about the signals between the bulbs/devices.
Thanks for answering, but thats my main problem…
I need scenes instead of groups, with groups we can only turn on or off our devices, but i need color changing per single lamp.
- sorry!)
