I have a number of device groups that I use to control my Kasa devices. Sometimes these devices miss their command for some reason, and therefore don't get turned on/off.
It would be nice of the group device type had a way to resend the command on or off command w/o having to toggle all the devices.
The capability should of course also be extended to the dashboards so you can resend the command from the a dashboard.
The devices themselves do, as well as the group device; in fact, the standard capabilities only have "on" and "off" commands, not "toggle." Can you share where you are seeing this? (Turn off "Show common commands first" on the device detail page if the "On" and "Off" commands get combined into a single switch and you need to see them separately, e.g., because you want to send a specific command; then you'll see both commands listed individually.)
A Dashboard is different, as the standard switch tile assumes the state is correct and effectively only lets you toggle -- though there are workarounds you could do, like creating a virtual button on the hub and adding that button to the dashboard as a tile (or two) instead of (or in addition to) the switch, coupled with an app on the hub that turns the switch on or off in response to the button event.
Of course, you might also want to look into why this is happening or consider some other workaround, like enabling command retry for the problematic devices.
By "toggle" I mean having to cycle all the devices to the other state, then back again, not toggle in group.
I had command retry enabled, but support had me turn it off as I am having a different problem they are trying to resolve.
Curious as to how devices receive and acknowledge commands...I supposed it depends upon the device type and protocol, ie zwave, Matter, webhook, websocket or something custom like the Kasa integration. Are they typically fire and forget? Or is it a send/ack/timeout-resend?
Why? You can send "On" or "Off" directly. Are you saying that doesn't work, even if you issue the specific command (rather than toggling the on/off slider that could be stuck in the "wrong" spot if my above guess was correct)? That would be unusual...
That is typical from the hub's perspective, though the underlying physical layers usually have something built-in to reasonably ensure the message was received, different for each protocol and the details of which I don't know for each -- though whether the device did anything even if the traffic was received may be different. Command Retry adds something at a high layer to make reasonable guesses for commands where a state change is expected.
Do you have a link to this discussion? It's not an all on or off feature; you can enable it for only specific devices. You might know this, but it wasn't apparent from this statement, so I wanted to clarify in case it was only causing problems for some devices.
I guess I'm scratching my head why this is so hard for you to understand.
If I have a group of a dozen Kasa devices and I send an on or off command to it, sometimes one gets missed for some reason.
What I'd like is a way to resend the on or off command again, without having to turn off on or off all the devices to do it.
I'm curious - how is this any different than having command retry turned on for those devices?
I too am interested in seeing the discussion where support asked you to turn command retry off. Could you please link to it?
Solving that situation will permit command retry to be used; which in turn will resolve the issue currently being described.
I understand what you want to do; I don't understand why you claim that it is not possible, since it is. I asked a question, made a guess as to its answer (to try to be helpful without knowing that ahead of time, as it's a likely guess), and provided some steps above to help based on that:
Without an answer, none of the rest is clear (aside from the Dashboard issue I addressed separately). If this doesn't sound like what you're seeing, can you please share more information, including this, so we can learn more? A screenshot (or few) may be helpful.
Thanks!
(The command retry thing is also unusual, and I would be interested to hear more about that, I also asked about above, and it was also not answered. It seems like that would be an easier solution for a recurring issue. But it's certainly possible to send an "on" or "off" command to any device regardless of its state, too, so I'm curious where you're stuck.)
Download the Hubitat app
