Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modbus entity duplicate even is thay are a different type #112645

Closed
Nicomagno opened this issue Mar 7, 2024 · 2 comments · Fixed by #112701
Closed

Modbus entity duplicate even is thay are a different type #112645

Nicomagno opened this issue Mar 7, 2024 · 2 comments · Fixed by #112701
Assignees

Comments

@Nicomagno
Copy link

Nicomagno commented Mar 7, 2024

The problem

Modbus entities wont load because they are marked as duplicates because they have the same name, but even is the are a different type, for example Climate.quem1 and Switch.quem1.
This used to work.
Also if the same address is used for in the entity Sensor.Temp1 (address:1212) and in the entity Climate.room1 (and the temp address:1212)
This also used to work before.

What version of Home Assistant Core has the issue?

2024.3.0

What was the last working version of Home Assistant Core?

2024.2.5

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Modbus

Link to integration documentation on our website

https://www.home-assistant.io/integrations/modbus/

Diagnostics information

Registrador: homeassistant.components.modbus.validators
Fuente: components/modbus/validators.py:359
integración: Modbus (documentación, problemas)
Ocurrió por primera vez: 15:53:43 (14 ocurrencias)
Último inicio de sesión: 15:53:43

Modbus Horno2/Quemador 3 is duplicate, second entry not loaded!
Modbus Horno2/Quemador 4 is duplicate, second entry not loaded!
Modbus Horno2/Quemador 5 is duplicate, second entry not loaded!
Modbus Horno2/Quemador 6 is duplicate, second entry not loaded!
Modbus Horno2/Enfriador 1 is duplicate, second entry not loaded!

Registrador: homeassistant.components.modbus.validators
Fuente: components/modbus/validators.py:355
integración: Modbus (documentación, problemas)
Ocurrió por primera vez: 15:53:43 (2 ocurrencias)
Último inicio de sesión: 15:53:43

Modbus Horno1/Chimenea Horno Temperatura address Horno11213_holding_0 is duplicate, second entry not loaded!
Modbus Horno1/Aspiracion Horno Temperatura address Horno1433_holding_0 is duplicate, second entry not loaded!

Example YAML snippet

  switches:
   - name: Quemador 1
      address: 4
      command_on: 1
      command_off: 0
      verify:
 climates:
    - name: Quemador 1
      data_type: int16
      scale: 0.1
      offset: 0
      precision: 1
      max_temp: 1000
      min_temp: 730
      temp_step: 1
      target_temp_register: 58
      address: 104
      target_temp_write_registers: true
      temperature_unit: "°C"

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Mar 7, 2024

Hey there @janiversen, mind taking a look at this issue as it has been labeled with an integration (modbus) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of modbus can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign modbus Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


modbus documentation
modbus source
(message by IssueLinks)

@janiversen
Copy link
Member

janiversen commented Mar 7, 2024

Sounds like a bug, let me have a look.

names should be allowed to be duplicate between types, addresses however must be unique to avoid having the same register in multiple entities and often with different values (due to the update frequency).

@github-actions github-actions bot locked and limited conversation to collaborators Apr 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants