search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.56k stars 30.74k forks source link

integration: switcher_kis - turned on triggered by service switch.turn_off - switch turns back on immediately after being turned off #79203

Closed orenbenkiki closed 2 years ago

orenbenkiki commented 2 years ago

The problem

I have a switcher smart plug which I want to control w/ HomeAssistant. When I turn the switch off, either in a script or by clicking on it in the overview card, it turns off for a short time (few seconds), but then it immediately turns back on again. In the logbook I see a message saying it was "turned on triggered by service switch.turn_off".

What version of Home Assistant Core has the issue?

Home Assistant 2022.9.7 Frontend 20220907.2 - latest

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Switcher

Link to integration documentation on our website

https://www.home-assistant.io/integrations/switcher_kis/

Diagnostics information

I have diagnostics turned on but I can't find any diagnostics file on disk. The "device page" for the switcher doesn't show any option for downloading such a file.

Example YAML snippet

No response

Anything in the logs that might be useful for us?

September 28, 2022
Litter-Robot-Switch turned on
12:47:45 PM - 21 seconds ago
Litter-Robot-Switch became unavailable triggered by service switch.turn_off
12:47:41 PM - 25 seconds ago - oren
Litter-Robot-Switch turned on
12:47:00 PM - 1 minute ago

Additional information

This is running in a docker container in a Synology NAS. The container is executed with --net=host. The Synology NAS firewall is disabled.

I have also tried turning the switch off from a script and I get the same results whether I use the service switch.turn_off (either specifying the device or the entity as the target) or whether I use the "device action" called "turn off". However in these cases the logbook says that the switch was turned on by the script (which doesn't contain any turn-on command).

It seems other people have had similar issues but these were closed asking to reproduce the problem on the latest version. I have just downloaded the docker image and HomeAssistant is assuring me it is the very latest version, so...

homeassistant commented 2 years ago

Hey there @tomerfi, @thecode, mind taking a look at this issue as it has been labeled with an integration (switcher_kis) you are listed as a code owner for? Thanks! (message by CodeOwnersMention)

switcher_kis documentation switcher_kis source (message by IssueLinks)

thecode commented 2 years ago

This means HA can't control the switch. This can be 1 of the following:

  1. Firewalling issue, please check https://www.home-assistant.io/integrations/switcher_kis#notes
  2. Device reports wrong IP address, known bug, Switcher is investigating - A reboot of the device should fix it.
  3. Device does not have the minimum required version, however according to Switcher all Plug versions should be supported.

Can you check the app for the device firmware version and add it here? Can you try to update the device firmware version from the app? If there is no firmware update try to reboot the device and check again.

orenbenkiki commented 2 years ago

  1. Firewalling: This is in a container inside Synology, but with --net=host, adn the Synology firewall is completely disabled.

  2. Wrong IP address: The device is automatically detected, but unhelpfully neither the device page nor the card show the IP address, so I can't really tell. There are no errors in the log file or the logbook. Is there any other way to peek at the IP address?

  3. Firmware version: The iPhone app reports firmware version 1.46, whatever that means. There doesn't seem to be any option for updating the firmware in the app.

That said, I unplugged the switch for ~30 seconds and re-plugged it and it works fine for now.

So, the eternal fix: "unplug it to let the dirtry electrons drain, then try again with fresh ones". Sigh.

Thanks!

thecode commented 2 years ago

This means the problem is #2, don't mistake it with updates displayed in HA, the device reports the IP it expects to reply inside the packet, so that it may still show in the device card and even update values from the device, but you will not be able to control it.

This is not affecting only HA, if you enable Local in the Switcher app, you will see that in this case the App switch to cloud mode (will show Online instead of Local) and after reboot of the device it will return to Local. I have reported it to Switcher, including a wireshark capture that shows it and they confirmed they are investigating it.

orenbenkiki commented 2 years ago

Hmmm - does that mean that the problem may/will recur in the future (say, if dhcp assigns a different IP to the switch "just because")?

thecode commented 2 years ago

Hmmm - does that mean that the problem may/will recur in the future (say, if dhcp assigns a different IP to the switch "just because")?

It does not happen on every DHCP assignment change but I would recommend assigning a static IP in the DHCP server/router

orenbenkiki commented 2 years ago

Tricky to do w/o knowing either the IP or the MAC address. I just went and freezed all the 2.4GHz DHCP clients at their current IP addresses, hopefully I got this one as well. Sigh.