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

charger connected but no data in HA #154

Closed
adieball opened this issue May 24, 2024 · 3 comments
Closed

charger connected but no data in HA #154

adieball opened this issue May 24, 2024 · 3 comments

Comments

@adieball
Copy link

Everything is installed and charger is connected to mqtt - connection is shown in mqtt log

But I don't get any data in the entities.

Only relevant logfile entry in HA log I can find is:

Logger: homeassistant.components.mqtt.number
Quelle: components/mqtt/number.py:195
Integration: MQTT (Dokumentation, Probleme)
Erstmals aufgetreten: 20:38:18 (8 Vorkommnisse)
Zuletzt protokolliert: 20:48:59

Invalid value for number.go_echarger_232684_set_next_trip_energy_limit: 9000 (range 0.0 - 100.0)

@adieball
Copy link
Author

adieball commented May 25, 2024

Correction:
I do get all values in MQTT where it shows as 1 Device with 41 Entities but nothing in the Go-e module (always "no available")

Example from MQTT Debug Information:

{
          "device_class": null,
          "disabled_by": null,
          "disabled": false,
          "entity_category": null,
          "entity_id": "sensor.go_echarger_232684_energy_charged",
          "icon": null,
          "original_device_class": "energy",
          "original_icon": "mdi:flash",
          "state": {
            "entity_id": "sensor.go_echarger_232684_energy_charged",
            "state": "2808.28",
            "attributes": {
              "unit_of_measurement": "Wh",
              "device_class": "energy",
              "icon": "mdi:flash",
              "friendly_name": "go-eCharger_232684 Energy charged"
            },
            "last_changed": "2024-05-25T06:03:27.275854+00:00",
            "last_reported": "2024-05-25T06:03:27.275854+00:00",
            "last_updated": "2024-05-25T06:03:27.275854+00:00"
          },
          "unit_of_measurement": "Wh"
        },{
          "device_class": null,
          "disabled_by": null,
          "disabled": false,
          "entity_category": null,
          "entity_id": "sensor.go_echarger_232684_energy_charged",
          "icon": null,
          "original_device_class": "energy",
          "original_icon": "mdi:flash",
          "state": {
            "entity_id": "sensor.go_echarger_232684_energy_charged",
            "state": "2808.28",
            "attributes": {
              "unit_of_measurement": "Wh",
              "device_class": "energy",
              "icon": "mdi:flash",
              "friendly_name": "go-eCharger_232684 Energy charged"
            },
            "last_changed": "2024-05-25T06:03:27.275854+00:00",
            "last_reported": "2024-05-25T06:03:27.275854+00:00",
            "last_updated": "2024-05-25T06:03:27.275854+00:00"
          },
          "unit_of_measurement": "Wh"
        },

maybe something wrong with the prefix config?
In my go-e app it shows as: "go-eCharger/232684"

Using the mqtt-explorer app I do see the messages from the Charger coming in every second

@syssi
Copy link
Owner

syssi commented May 25, 2024

Please double check the base_topic. I guess it's a prefix thing. Either set the base_topic of the integration to an empty string or change the topic using the app to /go-eCharger/232684.

@adieball
Copy link
Author

@syssi That did the trick, added a / in the go-e app and now I see everyting
thanks a lot!

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

No branches or pull requests

2 participants