search

marq24 / ha-tibber-pulse-local

Local/LAN Tibber Pulse IR/Bridge Integration for Home Assistant. My Tibber invitation Link: https://invite.tibber.com/6o0kqvzf (Code: six, oscar, zero, kilo, quebec, victor, zulu, foxtrot)
Apache License 2.0
94 stars 4 forks source link

Wanted to change the config from hostname to IP, failed #4

Closed ProfDrYoMan closed 11 months ago

ProfDrYoMan commented 11 months ago

Hi,

wanted to change my config from hostname to IP since I saw that the integration is querying the DNS every time.

Failed.

image

If I add the hostname back, I can save the dialog box.

marq24 commented 11 months ago

Und täglich grüßt das Murmeltier :-) Please update to 1.0.7 in BETA Channel let me know, if the issue is solved

ProfDrYoMan commented 11 months ago

Ok, tried 1.0.7 BETA. Could use an IP address.

Something I see now:

Twice: image

One with the entities that are exported by my energy counter and another one with all the other entities from the very first install which are not exported.

What to do?

marq24 commented 11 months ago

ihhhhh... that's quite odd...

Unfortunately I am not able to test here the "IP/HOST-NAME" change - since I can reach my bridge just via it's IP... Which really sucks...

So what is my suggestion?

Restart from the scratch - removing all possible existing integration (entries) and entities

To do so:

  1. Make a Backup :-D

  2. Check one of the still working entities (that provide up2date data) - and note the entity-id (e.g. for the net-frequenzy sensor.lan_tibber_01000e0700ff - here in this example the importnant part is lan_tibber - this is the Display-Name I have have selected during the initial setup phase (lower-case and space replaced by '_') When you delete all the current-existing (Tibber-local) integrations with all the entities, the historic data will not be deleted (at least that is my location here, that the data will not be deleted from the DB) - when then a "new2 integration will be installed, that use the same entity-ids then the previously deleted on, the historic data will be shown.

  3. Once all of your Tibber-local Devices (Geräte) are gone you can add a fresh new one - and here it's important, that you use the DisplayName that you have "recorded" in step 2. To match my given example here I used LAN Tibber which will be 'slugified' by code to lan_tibber - and obviously use the IP of the bridge

  4. Restart HA

I'll keep my fingers crossed

ProfDrYoMan commented 11 months ago

That did work. At least I could manually update all entity names to what I use afterwards and all dashboard and stuff is fine.

But is seems I lost all energy history again. :/ Bummer, but ok.

marq24 commented 11 months ago

But is seems I lost all energy history again. :/ Bummer, but ok.

actually that was not intended/expected at all :-/ Here on my installation I can remove any existing integration - as soon as I reinstall it (and make sure that the entityIDs of the sensors remain the same, then these sensors will continue to show the values of the "old" (already removed) integration... Actually that's how I do all my internal tests of the integrations. Since I need to frequent test the initial installation process, I delete the integration... then reinstall it (based on the new code) and all entities show the "old" data as well...

But looks like that's just a local observation - sorry for leading you in the wrong direction...

ProfDrYoMan commented 11 months ago

No problem. I finally hope that I do not need to touch this again. Relying on you. :) Got my Monthly at my energy provider, good enough form so overview. I already know my consumption pretty well.