Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Switchmate phantom toggles #115870

Open
Erudition opened this issue Apr 20, 2024 · 4 comments
Open

Switchmate phantom toggles #115870

Erudition opened this issue Apr 20, 2024 · 4 comments
Assignees
@Danielhiversen
Labels
integration: switchmate

Comments

@Erudition
Copy link

The problem

I've had the Switchmate integration working all year, but this month it started toggling on it's own. What's weird is that it doesn't show up in the activity log nor the Core logs, the device still shows the switch is off, after a phantom toggle. I can turn it on and back off in HA to get it to switch back off, but then it will come back on randomly.
Again, this is not from an automation, HA's interface does not know about the change at all.
I disabled the Switchmate app on my phone and it did not stop turning on at seemingly random times.
I unplugged my Home Assistant Green, and... it stopped.

What version of Home Assistant Core has the issue?

core-2024.4.3

What was the last working version of Home Assistant Core?

core-2024.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Switchmate

Link to integration documentation on our website

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

Diagnostics information

Since Switchmate doesn't show up in HA as an integration (yaml only), there's no diagnostic data button.

Example YAML snippet

switch:
  - platform: switchmate
    mac: "FC:74:63:35:1A:XX"
    name: "Switchmate Toggle 1"

Anything in the logs that might be useful for us?

Nope

Additional information

No response
@home-assistant
Copy link

Hey there @Danielhiversen, @qiz-li, mind taking a look at this issue as it has been labeled with an integration (switchmate) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of switchmate can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign switchmate Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)

switchmate documentation
switchmate source
(message by IssueLinks)

@dericosk
Copy link

I have the same issue now, but for me it started after running the update to Operating System 12.3. After updating from 12.2, I started having this issue. I had been running core 2024.4.3 when I updated to 12.3 and still have the issue with core 2024.5.5.

@wynfred
Copy link

wynfred commented Jun 1, 2024

Confirming it's an issue with 12.3. Likely related to the bluez update

@dericosk
Copy link

dericosk commented Jun 1, 2024

I decided to drop back to OS 12.2 and don't have the issue anymore. So will be curious to see if 12.4 has the issue when it comes out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Danielhiversen Danielhiversen

Labels
integration: switchmate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Danielhiversen @Erudition @wynfred @dericosk