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.

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

Are the new EB3A entities supported in Home Assistant? #42

Closed
burpen opened this issue Nov 12, 2022 · 2 comments · Fixed by #45
Closed

Are the new EB3A entities supported in Home Assistant? #42

burpen opened this issue Nov 12, 2022 · 2 comments · Fixed by #45

Comments

@burpen
Copy link
Contributor

burpen commented Nov 12, 2022

I have an EB3A that I've been using since version 0.9.0 and it has the following entities in Home Assistant (edit: also, AC input power, not pictured):

Screenshot_2022-11-12_12-55-31

In the 0.9.2 release, the EB3A config was updated to include additional functionality (eco mode, charging mode, etc.). The problem I have is that even after upgrading to 0.9.2 and beyond (currently running 0.10.0), Home Assistant still only lists the entities shown in the screenshot above. I do see the additional entities if I examine the bluetti topic using MQTT Explorer:

Screenshot_2022-11-12_13-08-54

I assume HA is somehow stuck with a stale autodiscovery manifest, and I'm not sure how to force rediscovery to happen. I have tried stopping bluetti_mqtt, deleting the device in HA, then restarting bluetti_mqtt, to no change. Perhaps this is a Home Assistant problem more than a bluetti_mqtt problem.

On a related note, is the readme's list of supported sensors and switches up to date? I'm not sure if I should take it to mean that anything beyond what's listed there will require some additional development. If that's the case then what I'm seeing may be expected behavior.

@slash5k1
Copy link
Contributor

slash5k1 commented Nov 13, 2022

The home assistant discovery topic is being published by the code in mqtt_client.py under the _send_discovery_message function which covers:

  • ac_input_power
  • dc_input_power
  • ac_output_power
  • dc_output_power
  • total_battery_percent
  • ac_output_on
  • dc_output_on; and
  • led_mode (if the device support led_mode)

Reads like you want the discovery to also include

  • eco_on
  • eco_shutdown
  • charging_mode; and
  • power_lifting_on

You could add these additional items to mqtt_client.py but maybe it would be better to only have the core auto discovery topics in this file and move specific device discovery to their specific device file under core/devices?

@burpen
Copy link
Contributor Author

burpen commented Nov 18, 2022

Reads like you want the discovery to also include ...

Yes, you're spot on about what I was looking for. I haven't had the chance to try out #45, but it looks like it will address everything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants