-
-
Notifications
You must be signed in to change notification settings - Fork 28.7k
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
Mopeka integration is missing all translations in 2023.2.x #87163
Comments
Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) mopeka documentation |
Adding Bluetooth diagnostics, in |
I am Also having the same issue trying to add the Mopeka integration. |
Thanks for reporting. I'll take a look when I add support for the Lippert version of this sensor. |
I've also been having that same issue trying to add the integration the past couple days. Thanks for the effort on this by the way! |
It looks like all the translations are missing in 2023.2.x but present on dev |
Thanks for your work on this. |
Please open a separate issue and provide diagnostics for your bluetooth adapter as well as the mac addresses of the missing Mopeka sensors. They probably have a different model id that we don't yet know about. |
The problem
Bluetooth is not auto-detecting the Mopeka Tank Sensor. When I try to add the integration manually, I get a blank pop up with no buttons or options. I will add a screenshot below.
Thanks
What version of Home Assistant Core has the issue?
core-2023.2.0
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
Mopeka
Link to integration documentation on our website
https://www.home-assistant.io/integrations/mopeka
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
The text was updated successfully, but these errors were encountered: