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.

Sign up for GitHub

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

Jump to bottom

Warning: modbus communication open on startup #127570

Open
RALFISBORN opened this issue Oct 4, 2024 · 4 comments · May be fixed by #128980
Open

Warning: modbus communication open on startup #127570

RALFISBORN opened this issue Oct 4, 2024 · 4 comments · May be fixed by #128980
Labels
integration: modbus

Comments

@RALFISBORN
Copy link

RALFISBORN commented Oct 4, 2024 •
edited
Loading

The problem

Hello,
Since updating to Core 2024.10.0, I get the following warning message every time I start:

Logger: homeassistant.components.modbus.modbus
Source: components/modbus/modbus.py:344
Integration: Modbus

image

Nothing has been changed on the system apart from the core update.

What version of Home Assistant Core has the issue?

2024.10.0

What was the last working version of Home Assistant Core?

2024.9.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

modbus

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

# Modbus Energiezähler UV
- name: modbus_energycounter_uv
  type: tcp
  host: 192.168.10.34
  port: 502
  timeout: 10
  sensors:
    - name: 30013_Wirkleistung_L1
      unit_of_measurement: W
      address: 12 #Modbus Register 30013
      input_type: input
      data_type: float32
      slave: 1
      scan_interval: 5
    - name: 30015_Wirkleistung_L2
      unit_of_measurement: W
      address: 14 #Modbus Register 30015
      input_type: input
      data_type: float32
      slave: 1
      scan_interval: 5
    - name: 30017_Wirkleistung_L3
      unit_of_measurement: W
      address: 16 #Modbus Register 30017
      input_type: input
      data_type: float32
      slave: 1
      scan_interval: 5
    - name: 30053_Summe_Netz-Erzeugung
      unit_of_measurement: W
      address: 52 #Modbus Register 30053
      input_type: input
      data_type: float32
      slave: 1
      scan_interval: 5
    - name: 31281_Leistung_Import
      unit_of_measurement: W
      address: 1280 #Modbus Register 31281
      input_type: input
      data_type: float32
      slave: 1
      scan_interval: 5
    - name: 31283_Leistung_Export
      unit_of_measurement: W
      address: 1282 #Modbus Register 31282
      input_type: input
      data_type: float32
      slave: 1
      scan_interval: 5

Anything in the logs that might be useful for us?

No response

Additional information

No response
@home-assistant
Copy link

home-assistant bot commented Oct 4, 2024

modbus documentation
modbus source

@wimjanse
Copy link

wimjanse commented Oct 4, 2024

Same issue. This is a warning only, but all modbus data works fine.

@netmikey
Copy link

netmikey commented Oct 6, 2024

Might be a resurrection of #57946 that got fixed 3 years ago in #57953

@dana-se
Copy link

dana-se commented Oct 20, 2024

Same issue in 2024.10.3, but modbus data works fine.

@crug80 crug80 linked a pull request Oct 22, 2024 that will close this issue
Open
19 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
integration: modbus
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Adjust logging level in ModBus crug80/core
5 participants
@netmikey @joostlek @dana-se @wimjanse @RALFISBORN