-
-
Notifications
You must be signed in to change notification settings - Fork 31.3k
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.
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
SwitchBot Meter Pro (CO2 Monitor) Support #128502
Comments
Hey there @Danielhiversen, @RenierM26, @murtas, @Eloston, @dsypniewski, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) switchbot documentation |
Would be great if the switchbot meter pro can be added to home assistant :-) |
should be fixed in #128991 |
had the same issue before 2024.11 and also after the update. I think i just ignored them reboot the system (not just HA) and removed the ignore again. It was something like this. |
@Mar1usW3 This is strange, although restarting the HA didn't fix anything, I unplugged and re-plugged the raspberry pi and one of the devices are now detected correctly! |
The other one is still getting detected as a light strip, even after restarting and unplugging many times. Is there a way to update it to a meter device manually after adding it to HA? |
I'd recommend raising an issue at the library pySwitchBot. The name comes from the discovery info |
The problem
The SwitchBot Meter Pro (CO2 Monitor) is not recognized in Homeassistant via bluetooth
What version of Home Assistant Core has the issue?
core-2024.10.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
SwitchBot Bluetooth
Link to integration documentation on our website
https://www.home-assistant.io/integrations/switchbot/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: