search

britkat1980 / giv_tcp

TCP connection (from inverter) and MQTT implementation
78 stars 37 forks source link

Lost access to battery with 3.0.3? #248

Open mprowe opened 1 day ago

mprowe commented 1 day ago

Following the bummpy transfer from 2.4.9 through 3.0.0 > 3.0.1 > 3.0.2 and now 3.0.3, I now see that I now no longer am able to "see" my battery? Not sure how to pass the information in text-form, so it will have to be screenshot (sorry). image Do I go back to 2.4.9? Or leave it alone until you advise on a solution? Regards, Martin

gcoan commented 1 day ago

I had this happen on v3.0.0. There is a fix @britkat1980 advised on deleting entities from MQTT and I believe it was going to be fixed in v3.0.1 however I have at present reverted back to v2.4.9 as that was working and stable for me.

It might work correctly if you downgrade to 2.4.9 and then upgrade directly to the latest patch to v3, going via the interim releases may be why the fixes introduced in 3.0.1 didn't work for you. That's a suggestion rather than evidence based though !!

mprowe commented 15 hours ago

however I have at present reverted back to v2.4.9 as that was working and stable for me.

Okay. I'm going to do the same. I'm afraid my skills are not up to poking around in the MQTT Server!

britkat1980 commented 12 hours ago

Following the bummpy transfer from 2.4.9 through 3.0.0 > 3.0.1 > 3.0.2 and now 3.0.3, I now see that I now no longer am able to "see" my battery? Not sure how to pass the information in text-form, so it will have to be screenshot (sorry). image Do I go back to 2.4.9? Or leave it alone until you advise on a solution? Regards, Martin

The entity friendly names look odd, can you confirm via the MQTT integration pages that there aren't any other battery devices. You can delete them from that page, to save mucking around with an MQTT broker.