-
Notifications
You must be signed in to change notification settings - Fork 38
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
Conversion of V2 to V3 Failing #331
Comments
I didn't get any MQTT errors from GivTCP v3 when I upgraded, GivTCP just auto discovered my MQTT. I think you can delete the username and password configured in GivTCP to force it to reconnect. What I did experience though is a load of 'duplicate sensor' errors in the HA core due to the tree structure for the battery sensors changing in v3. Didn't lose any history because the sensor history is held in HA not MQTT, but the mapping of MQTT paths to HA battery entities got broken due to the changed pathnames. In hindsight I could have deleted the entire GivTCP tree structures and it would have recreated everything |
Happy to delete the entire tree from GivTCP down before starting up v3. This might cure the problem of it not finding the V2 sensors to migrate. Not sure about the MQTT username/password. Tried with the default and also tried changing to my own credentials that V2 used, and that failed as well. |
v3 definitely doesn't use the same saved MQTT credentials as v2 (and I have a recollection that if you enter them, it doesn\t work). Update: In the Predbat install instructions for GivTCP v3 I wrote: |
Yes you are right - v3 sets the MQTT addon username/password automatically (which is what I have), but it still cannot connect to the MQTT broker as per original log message. Further advice needed. |
sorry no idea, I haven't seen this issue before. Can only suggest uninstalling GivTCP and Mosquitto completely, restarting HA and the add-on's and repeating the install process to see if that cures it. |
I have uninstalled v2 and v3 of GivTCP, Uninstalled Mosquitto and restarted HA. Reinstalled Mosquitto and GivTCP v3, but on starting I now get bad connection: |
strange when you re-installed mosquitto add-on did you configure the mosquitto integration? https://springfall2008.github.io/batpred/inverter-setup/#givenergy-with-givtcp Anything in the mosquitto log or the HA core log? |
I did, but to be sure I un-installed the Mosquitto add-on, and then deleted the MQTT integration as there was a load of crap still lying there. When I reinstalled Mosquitto it added the MQTT integration back in and I configured as per guide which is basically no configuration needed, i.e. just click OK. |
Here is the Mosquitto Log: |
HA log shows nothing interesting. I still have my MQTTUser in HA which is obviously left over from the last install, but this is just no longer being used. I can still login to MQTT explorer with it to get a client connection to the broker. But obviously its empty as GivTCP cannot connect to it yet. |
I'v managed to sort it myself I think. Looks like it cannot connect to the broker using the built-in MQTT user so i have replaced the pre-populated user/password (opposite to what the instructions say) with my dedicate mqtt user/password and now it seems to connect. Deleting everything and reinstalling has lost all my sensor history which I wanted to avoid, but better to have it working. Just need to reconfigure Predbat as all the sensors have now been renamed (does not default to GIVTCP prefix) and so just need to point it at the new names. |
Stopped v2, started V3 and I get error connecting to the MQTT Broker:
I'm running Mosquitto as my broker from within HA.
Connecting to MQTT explorer connects fine to the broker using my default username/password:
I spot that the serial number for my AIO inverter is reported at 2 levels and imbedded within itself:
This duplicates some entries below (with some differences in values, e.g. battery capacity):
I also got no notification of V2 settings being found and migrated across. I have therefore decided to stop and revert back to V2 whilst this issue is investigated and further instructions on how to install. I would like to keep all my existing sensor history as I have an ongoing SOC issue with GivEnergy and often need to refer back to my data from GIVTCP.
The text was updated successfully, but these errors were encountered: