Comments (14)
now it worked ;-)
After a high amount of restarts and even shutting down the system I was able to have it running now... for the base topic I just have included "go-eCharger" and with the serial number it resulted in an autodetect ;-)...
Many thanks for your support!
from homeassistant-goecharger-mqtt.
Are you sure you are using this custom component because a unique ID is generated in general here.
from homeassistant-goecharger-mqtt.
Yes - I was directly referred from the home assistant page when clicking in "documentation"...
from homeassistant-goecharger-mqtt.
Interesting. I will have a look! :-)
from homeassistant-goecharger-mqtt.
Many thanks - if you need further information please let me know. In the meantime I try to start the complete setup again... maybe I had some issues in my setup process
from homeassistant-goecharger-mqtt.
Is there something specific I need to include in the field "base topic"? Is there any specific format needed for the serial number?
from homeassistant-goecharger-mqtt.
First of all you should be able to add the component multiple times to talk to different chargers. IMO a missing unique ID
shouldn't have an impact here.
The base_topic
depends on your charger version & firmware. This is the expected pattern to be able to auto-discover your devices: https://github.com/syssi/homeassistant-goecharger-mqtt/blob/main/custom_components/goecharger_mqtt/config_flow.py#L79-L82
from homeassistant-goecharger-mqtt.
ok... to be honest - I do not know what to do with this (sorry!).
I am even not able anymore to add again the first go-e charger which worked before... And I think it was auto detected before. I also know from the MQTT Explorer that both send their values correctly to the Mosquitto broker...
from homeassistant-goecharger-mqtt.
first device is running again after using my backup... but second one is not discovered and I do not really understand what to do or where I could find helpful instructions...
from homeassistant-goecharger-mqtt.
Could you try to subscribe to your mosquitto broker and provide some received messages (including the topics) of both devices? Do you know how to monitor the MQTT traffic manually?
from homeassistant-goecharger-mqtt.
I am able to see all the details send using MQTT Explorer, but I do not know how to monitor it using the Mosquitto broker. Anyway the MQTT is connected to the Mosquitto broker and should therefore show all data
from homeassistant-goecharger-mqtt.
Based on the Mosquitto broker the Base topic seems to be go-eCharger/233782/
Anyway I am not able to get it running using the integration. But when monitoring the MQTT Explorer all information are correctly forwarded to the Mosquitto broker. Both go-e Chargers are identical.... same firmware etc. The other one is running without any issues...
from homeassistant-goecharger-mqtt.
Could you tell me the base topic of the working one? Does it start with a /
or not?
from homeassistant-goecharger-mqtt.
without a /
but I tried to setup the go-e Charger with several combinations for the base topic considering with / and without
Do I need to add anything in configuration.yaml???
from homeassistant-goecharger-mqtt.
Related Issues (20)
- Go-e Integration stopped providing entities although provided via MQTT HOT 27
- PV Surplus Charging - what happens when pGrid gets "unavailable"? HOT 4
- pAkku, pGrid, pPv sensors shown as "unavailable" HOT 2
- Error in Homeassistant since update 2024.01 Deprecation of STATE_CLASS_MEASUREMENT and STATE_CLASS_TOTAL_INCREASING HOT 3
- Entities not populating - what are correct settings? HOT 4
- Is it possible to manually set the load balancing priority in HA? HOT 6
- ValueError with `ocu` HOT 1
- All entities-data unavailable, but visible in MQTT-Explorer HOT 3
- Remove required serial number from topic configuration HOT 2
- No credentials for broker connection HOT 3
- Entity sensor.go_echarger_XXXXXX_wh has state class total_increasing, but its state is not strictly increasing HOT 1
- Working with Gemini flex? HOT 2
- Separate current meter needed? HOT 2
- hashtag in password -connection failed HOT 2
- Updating state for sensor.go_echarger_0XXXXXX_nrg_8 took 0.671 seconds HOT 9
- How to stop/start charging HOT 2
- Warnings in HomeAssistant update 2024.5.4 # 0.23.0 HOT 1
- charger connected but no data in HA HOT 3
- Load balancing
- Services not working in current release (0.24.x) HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from homeassistant-goecharger-mqtt.