search

britkat1980 / giv_tcp

TCP connection (from inverter) and MQTT implementation
73 stars 34 forks source link

GivTCP Entities 'Unavailable' #31

Closed AndyBowden closed 1 year ago

AndyBowden commented 1 year ago

Since updating to HA Core 2023.5.3 earlier today, all GiVTCP entities are displayed as 'unavailable'. I have updated to GiVTCP 2.1.13. I've tried restarts and checked my GivTCP config setting which seem correct. Reverting to back up from yesterday didn't help. The GiVTCP log includes text below. Any ideas / suggestions? Thanks

2023-05-15 12:59:39,460 - startup - [ERROR] - MQTT Broker process died. Restarting... 2023-05-15 12:59:39,461 - startup - [CRITICAL] - Starting Mosquitto on port 1883 1684151979: mosquitto version 2.0.11 starting 1684151979: Config loaded from /app/GivTCP_1/mqtt.conf. 1684151979: Opening ipv4 listen socket on port 1883. 1684151979: Error: Address in use

stace2023 commented 1 year ago

This is likely because of the latest GIVTCP update adding a 2nd entity for each item. But is the second one that's "added" that has the data if you only have 1 inverter, this needs to be inverted so it's picking up the right entity.

Fingers crossed this gets picked up on soon :) PLEASE :-)

RaptorG commented 1 year ago

@stace2023 spot on, version 2.1.13 is adding an extra entity and suffixed with _2. This broke all the automation tied down to existing GivTCP entities. Luckily, I could revert to snapshot.

777deano commented 1 year ago

Came across this after I had the same issue. I found a backup which is for version 2.1.11, reverted to this version and now all working.

CaptSB commented 1 year ago

I am stuck with the two sets of entities now and the old ones don’t work. This has really stuffed things up and it looks like it will take ages to get it back to where I had it.

I have restored HA and GivTCP to where they were a few days ago but it is still stuck with the _2 entities.

Any suggestions please???

On Mon, 15 May 2023 at 19:14, 777deano @.***> wrote:

Came across this after I had the same issue. I found a backup which is for version 2.1.11, reverted to this version and now all working.

— Reply to this email directly, view it on GitHub https://github.com/britkat1980/giv_tcp/issues/31#issuecomment-1548334729, or unsubscribe https://github.com/notifications/unsubscribe-auth/A64N7OWSDGOUWVAU4T442ZTXGJXALANCNFSM6AAAAAAYCD3X5U . You are receiving this because you are subscribed to this thread.Message ID: @.***>

-- Sent from Gmail Mobile

777deano commented 1 year ago

I am stuck with the two sets of entities now and the old ones don’t work. This has really stuffed things up and it looks like it will take ages to get it back to where I had it. I have restored HA and GivTCP to where they were a few days ago but it is still stuck with the _2 entities. Any suggestions please??? On Mon, 15 May 2023 at 19:14, 777deano @.> wrote: Came across this after I had the same issue. I found a backup which is for version 2.1.11, reverted to this version and now all working. — Reply to this email directly, view it on GitHub <#31 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A64N7OWSDGOUWVAU4T442ZTXGJXALANCNFSM6AAAAAAYCD3X5U . You are receiving this because you are subscribed to this thread.Message ID: @.> -- Sent from Gmail Mobile

I only restored the Givtcp to a previous version and left HA on the same version.

Can't really offer anything more than that as new to HA and giv_tcp

CaptSB commented 1 year ago

I have fudged it all to work again but can’t see any data from earlier than today but at least my automations should work and data logging is back up and running. I only started with HA in April so still a novice but this is my first real hiccup so a bit upset that my hard work has been broken.

On Mon, 15 May 2023 at 20:11, 777deano @.***> wrote:

I am stuck with the two sets of entities now and the old ones don’t work. This has really stuffed things up and it looks like it will take ages to get it back to where I had it. I have restored HA and GivTCP to where they were a few days ago but it is still stuck with the _2 entities. Any suggestions please??? On Mon, 15 May 2023 at 19:14, 777deano @.> wrote: Came across this after I had the same issue. I found a backup which is for version 2.1.11, reverted to this version and now all working. — Reply to this email directly, view it on GitHub <#31 (comment) https://github.com/britkat1980/giv_tcp/issues/31#issuecomment-1548334729>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A64N7OWSDGOUWVAU4T442ZTXGJXALANCNFSM6AAAAAAYCD3X5U https://github.com/notifications/unsubscribe-auth/A64N7OWSDGOUWVAU4T442ZTXGJXALANCNFSM6AAAAAAYCD3X5U . You are receiving this because you are subscribed to this thread.Message ID: @.> -- Sent from Gmail Mobile

I only restored the Givtcp to a previous version and left HA on the same version.

Can't really offer anything more than that as new to HA and giv_tcp

— Reply to this email directly, view it on GitHub https://github.com/britkat1980/giv_tcp/issues/31#issuecomment-1548419944, or unsubscribe https://github.com/notifications/unsubscribe-auth/A64N7OR4E37PA34MUKT4YUDXGJ5VNANCNFSM6AAAAAAYCD3X5U . You are receiving this because you commented.Message ID: @.***>

-- Sent from Gmail Mobile

AndyBowden commented 1 year ago

I went all the way back to a back up of GivTCP 2.1.7 which returned config settings to a single inverter, but I'm still getting the 'port 1883 .. address in use' warning. I've not been able to determine what, if anything, other than GivTCP might be using port 1883. I'm wondering if a clean re-install of 2.1.7 might do the trick.

RaptorG commented 1 year ago

What kind of HA installation you have? DOCKER or OS? How is GivTCP running Docker or as an addon? If you are running MQTT broker as well as GivTCP’s own broker you may be getting a conflict. Try stopping all other add-ons and then start GivTCP.

I don’t have spare time to tinker around this week but coming weekend I will try to update to 2.1.13 and cleanup old entities and reconfigure dashboards and all the automation. Unless devs can fix it some other way. This update seems very intrusive.

stace2023 commented 1 year ago

@britkat1980 any news please?

AndyBowden commented 1 year ago

I think I have fixed things or at least I am in the process of doing so. As is so often the case, there were multiple causes. The MQTT address in use issue seems to be down to the fact that I was connected remotely via a Cloudflared tunnel when I was at home and had thought I was connected locally. I had multiple instances of GivTCP entities as others had reported. I uninstalled GiVTCP, deleted all GivTCP entities and re-installed 2.1.13. I still have to update my dashboards and automations which will take quite a while. I'll report progress. I run GivTCP as an add-on and MQTT 6.2.1

britkat1980 commented 1 year ago

This scenario comes as a result of restructuring the entity_id and friendly names. This is now fixed, so if it changes your entity_id you may need to then update your automations and dashboards, but it will be a one time thing.

CaptSB commented 1 year ago

Hi, will the fix link the historical data from the old entities to the new? The _2 entities lost the link to the historical data.

Thanks

Richard

On Tue, 16 May 2023 at 14:40, britkat1980 @.***> wrote:

This scenario comes as a result of restructuring the entity_id and friendly names. This is now fixed, so if it changes your entity_id you may need to then update your automations and dashboards, but it will be a one time thing.

— Reply to this email directly, view it on GitHub https://github.com/britkat1980/giv_tcp/issues/31#issuecomment-1549696670, or unsubscribe https://github.com/notifications/unsubscribe-auth/A64N7OXVVLP4CAN4Q5YI73TXGN7VNANCNFSM6AAAAAAYCD3X5U . You are receiving this because you commented.Message ID: @.***>

-- Sent from Gmail Mobile

mprowe commented 1 year ago

_"This scenario comes as a result of restructuring the entityid and friendly names." Okay, understood. Thank you.

"This is now fixed, " How does my system get "fixed"? What do I need to do? Why the coma? Is the fix dependant on the subsequent clause: _"...so if it changes your entityid..."

Regards, Martin

britkat1980 commented 1 year ago

The new entityid naming convention is: _. So if that’s what your current entity ids are then you may get the _2 entities. To return to the original and keep the link to historical data, then you need to:

1) In GivTCP settings, change the HADevicePrefix to 'GivTCP' for ALL inverters - IMPORTANT STEP IF YOU HAVE MULTIPLE INVERTERS! 2) Install MQTT Explorer 3) STOP GivTCP 4) Log in to MQTT Explorer, using same login details as GivTCP uses 5) Delete ALL MQTT entries that refer to GivTCP (some are hidden in different hierarchies) 6) Go to settings/Devices & Services - select the entites under Mosquitto Broker and DELETE all entities that are associated with GivTCP 7) Restart GivTCP

ashleycbaker commented 1 year ago

@britkat1980 thanks 👍

I followed the instructions and have managed to get everything pretty much back to how it was, history seems to be there too

AndyBowden commented 1 year ago

I've just got everything working again after problems arose early on Monday. 2 lessons learnt:

1 Only adopt an update if it solves a problem one is experiencing or it gives one new functionality of value. 2 Document one's automations so that if they need change, one can remember how they are supposed to function.

mprowe commented 1 year ago

Hi, For the more timid users, can someone suggest a less dramatic route to getting back on-track with GivTCP? Rather than the "delete ALL..." approach advocated by britkat1980 in his post on 16th May, is it possible to just delete ONE item at a time. Will that allow me to confirm that I am doing things correctly once or twice, before moving on the the ALL stage. Regards, M.

Adrian57 commented 1 year ago

How do I update GivTCP WITHOUT creating all these _2 entities?

777deano commented 1 year ago

See britkat1980 post above ​​ -- Sent with Tutanota, enjoy secure & ad-free emails.

19 May 2023, 22:23 by @.***:

How do I update GivTCP WITHOUT creating all these _2 entities?

— Reply to this email directly, > view it on GitHub https://github.com/britkat1980/giv_tcp/issues/31#issuecomment-1555267723> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/A74A57KE5ZE5EHMSVXFGVFTXG7QF7ANCNFSM6AAAAAAYCD3X5U> . You are receiving this because you commented.> Message ID: > <britkat1980/giv_tcp/issues/31/1555267723> @> github> .> com>

Adrian57 commented 1 year ago

See britkat1980 post above ​​ -- Sent with Tutanota, enjoy secure & ad-free emails. 19 May 2023, 22:23 by @.***: … How do I update GivTCP WITHOUT creating all these _2 entities? — Reply to this email directly, > view it on GitHub <#31 (comment)>> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/A74A57KE5ZE5EHMSVXFGVFTXG7QF7ANCNFSM6AAAAAAYCD3X5U> . You are receiving this because you commented.> Message ID: > <britkat1980/giv_tcp/issues/31/1555267723> @> github> .> com>

I may misunderstand but I think britkat1980's reply above is to fix the problem after it has happened. What I am trying to do is update GivTCP without it adding the _2 entities at all. I updated the other day and was hit with the _2s, so I restored. Now I want to update without getting the _2s. Anyone know how, or do I have to update and then fix (as above)? I'd rather not. Or will it be fixed next release?

mcmillanb commented 1 year ago

I was only using Mosquitto broker for GivTCP which made it easier to fix:

  1. Stop GivTCP in Add-ons
  2. Uninstall Mosquitto broker in Add-ons
  3. Settings, Devices & Services
  4. Click the three dots on Mosquitto broker, then Delete
  5. Reinstall Mosquitto broker in Add-ons and start it
  6. Settings, Devices & Services, configure Mosquitto broker
  7. Add-ons, restart GivTCP

After a minute or so all of the entities were recreated with the correct names and my dashboards all started working

ispookie666 commented 1 year ago

I was only using Mosquitto broker for GivTCP which made it easier to fix:

  1. Stop GivTCP in Add-ons
  2. Uninstall Mosquitto broker in Add-ons
  3. Settings, Devices & Services
  4. Click the three dots on Mosquitto broker, then Delete
  5. Reinstall Mosquitto broker in Add-ons and start it
  6. Settings, Devices & Services, configure Mosquitto broker
  7. Add-ons, restart GivTCP

After a minute or so all of the entities were recreated with the correct names and my dashboards all started working

Probably the easiest workaround I have seen!!!

britkat1980 commented 1 year ago

Closing Issue. This was a breaking change.