Just got back from the tip and I find lots and lots of questions here. Itās turning into the āfirst night live on predbatā thread which I still havenāt looked at recently. 140+ unread messages over there so Iām fearing the mountain to read ā¦
SteveCook Should HA time be set as GMT +1? to reflect BST?
No, just leave it set to GMT+0 (London). Thatās what mine is and it handles BST fine.
Daveb01 Oh no, I did the same thing, created a MQTT user and pasted that in, also used this ID for GivTCP. There are loads of errors in the logs now.
I think if youād have just removed the user name and password from the givtcp config then it should have auto populated it again. But anyway, a good test of the backup and recovery system š
Daveb01 One more question when installing Predbat it says, can you confirm I need AppDaemon please?
Install Predbat, either
Predbat is a program written in Python. It needs āsomethingā inside Home Assistant to run the Python program in. Originally Trefor used AppDaemon, then he made a custom version of AppDaemon called AppDaemon-predbat, and now he has a dedicated Predbat add-on. The Predbat add-on is the recommended way of running Predbat and at some point the AppDaemon option will cease to be supported.
So if you are using the Predbat add-on to run Predbat within, then no, you donāt need AppDaemon for Predbat. AppDaemon is a general purpose Python runtime environment so you might find some other program you want to run within AppDaemon (I have Octoblock installed), but not needed for Predbat any more.
Rbor Moving up to v3 is not clean! It may be better for a new set up entirely without v2 baggage to get in the way.
Other than my misconfiguration issue with the inverter prefixes which was entirely my own fault as I wanted inverter 1 to be prefixed G and inverter 2 to be prefixed H, rather than the other way round as GivTCP had defaulted to, I found the upgrade process completely painless.
I would argue strongly against starting with a whole new load of sensors as (a) it loses sensor history if you have something with a new name, and (b) it would peopleās dashboards and Predbat config would need to be changed for the new sensor names.
Rbor I have no idea how to get MQTT Explorer to look at my MQTT broker
A quick summary of how to use MQTT Explorer.
You will find that in HA you canāt delete any of the givtcp_ entities from the normal devices & services /entities view as they are created by MQTT. You have to delete them from MQTT first.
First stop GivTCP
Then in addonās, MQTT Explorer, start MQTT Explorer
Thereās no configuration needed
Click Open Web UI
Youāll get a login box like this:

Enter a valid HA username and password. Can use the one you created previously for GivTCP connecting to MQTT or probably (not tested) put you own HA username and password in.
Click save to save the credentials, then connect
You will see a tree of MQTT topics. GivEnergy is whatās come direct off the inverter (useful to see the raw inverter data), homeassistant is the sensors that GivTCP is writing to HA
Open the homeassistant tree and find and select the sensor you want to remove (step 1):

make sure you have selected the right sensor, do not select something too high up in the tree
Then click the delete icon on the right, step 2
Youāll get an āare you sureā or something similar and confirm this.
You should be able to do this for all the battery sensors you want to remove, and once done in MQTT Explorer you can then delete the sensors from Devices & Services / Entities
Donāt go in to Developer tools / Statistics and click āfixā to remove the sensors from there as that will remove all your historical data for these sensors. Assuming you want to retain it.
Once done, can shutdown MQTT explorer, maybe restart HA to be sure, and restart GivTCP and it should create all the MQTT sensors afresh.
Daveb01 [11:43:22] INFO: SSL is not enabled
2024-09-19 11:43:24: Warning: Mosquitto should not be run as root/administrator.
No idea, which log do you see this in? I donāt but my Mosquitto has been running since the last full HA reboot so if its early in the log it may have wrapped off the screen