Naming sensors: Temperture vs Temperature

[Getiem]

Lot of the temperature sensors are named _temperture

It is now, with attached automations and dashboards, a breaking change, but it would be nice to rename them _temperature.

Any other users for or against?

[remmob]

Yes, I have noticed the typo.
If I change the naming you would have to deinstall the module, all entities are removed.
When installing with different naming the history gets lost.

[Florissilfhout]

So, this is an ongoing issue that will not be resolved? As I just started using your repo (thanks for your work by the way!), I don't have (a lot of) history data that I am desperate to keep.
Would you be able to share an alternative solution?

[remmob]

I’ve created a repair that renames all affected sensors, and it will be included in the next update.
I will release a beta version (1.3.0‑beta3.3) on Wednesday that already contains this fix.

[remmob]

Beta released.

[Getiem]

Nice to see you did a repair on this. Installed, repaired. Had to do some refactoring on automations, dashboard en helpers. So, breaking change to communicate to users.

[remmob]

Breaking change notice already in place, in the release notes.

[remmob]

@Getiem
Ik vroeg mij af of jullie de nieuwe beta 3.4 al geïnstalleerd hadden en wat de ervaringen tot nu toe zijn?

[Getiem]

Bèta 3.4 draait hier nu 4 dagen.

Ik heb geen foutmeldingen op de Amber.
heb in de config de interval weer naar 10 seconden gezet en de notificatie vinkjes alleen aan naar het meldingen systeem van HA.

Reloading/reconnect zie ik niet vanuit de integratie zelf werken. Na uitval netwerk blijven alle waardes op de laatste waarde hangen. De Connect status gaat wel netjes naar Failed. Ik heb mijn automation nu herschreven om dat als trigger te gebruiken.

[remmob]

Gek, dat je dat niet ziet werken.Ik heb het uitvoerig getest en zelf na een uur kwam de amber vanzelf weer online Ik had op mijn module sowieso geen uitval. Test nu met 2x intergratie op de zelfde Amber, dat geeft soms een partial uitval. Ook dat hersteld keurig.

[Florissilfhout]

Ik heb ook de beta 3.4 een paar dagen draaien. Zie nu dat mijn connection status ook naar Failed was gegaan. Nu net de integratie herladen en krijg ik weer nieuwe waardes binnen.

[Florissilfhout]

This error originated from a custom integration.

Logger: custom_components.itho_amber.hub
Source: custom_components/itho_amber/hub.py:370
integration: Itho Daalderop amber (documentation, issues)
First occurred: 03:51:47 (932 occurrences)
Last logged: 10:19:42

No settings data could be read

En waar het denk ik mee begon:

This error originated from a custom integration.

Logger: custom_components.itho_amber.hub
Source: custom_components/itho_amber/hub.py:140
integration: Itho Daalderop amber (documentation, issues)
First occurred: 03:51:22 (1 occurrence)
Last logged: 03:51:22

Unexpected error while reading registers 499-546: [Errno 104] Connection reset by peer
Traceback (most recent call last):
  File "/config/custom_components/itho_amber/hub.py", line 140, in _read_holding_registers
    resp = self._client.read_holding_registers(
        address=address,
        count=count,
        device_id=unit
    )
  File "/usr/local/lib/python3.13/site-packages/pymodbus/client/mixin.py", line 113, in read_holding_registers
    return self.execute(no_response_expected, pdu_reg.ReadHoldingRegistersRequest(address=address, count=count, dev_id=device_id))
           ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/pymodbus/client/base.py", line 202, in execute
    return self.transaction.sync_execute(no_response_expected, request)
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/pymodbus/transaction/transaction.py", line 132, in sync_execute
    response = self.sync_get_response(request.dev_id, request.transaction_id)
  File "/usr/local/lib/python3.13/site-packages/pymodbus/transaction/transaction.py", line 86, in sync_get_response
    if not (data := self.sync_client.recv(None)):
                    ~~~~~~~~~~~~~~~~~~~~~^^^^^^
  File "/usr/local/lib/python3.13/site-packages/pymodbus/client/tcp.py", line 258, in recv
    if (recv_data := self.socket.recv(recv_size)) == b"":
                     ~~~~~~~~~~~~~~~~^^^^^^^^^^^
ConnectionResetError: [Errno 104] Connection reset by peer 

[remmob]

https://github.com/remmob/itho_amber/discussions/categories/beta