Anyone else having MODBUS issues?

[DieterC1984]

Same problem for me now in 2023.9.3.
My charging station is constantly crashing because of this and needed to revert to 2023.9.2 to resolve it.

[Mattie (Mattias)]

Oh noooes…! I guess I’m staying with current version for a while…

[Mattie (Mattias)]

Has anyone tried the 2023.10 release yet? How is it working?

[qian158 (qian)]

Hello, is your Modbus configuration working? I’m learning this to access my Modbus, do you have any information to share, thank you

[Mattie (Mattias)]

there has been breaking changes in the modbus integration so configurations that were previously working have stopped. It was resolved in 2023.9.2 and was reported broken again in 2023.9.3 by some users. The question is if its working as intended in 2023.10?

[Dangerousdave (David Dyde)]

Hi Y’all, I’m having Modbus issues too. I have a number of hardwired (RS485) RTU devices with various timings, and I think sometimes they timings coincide causing a network overload. (a timeout error) It looks like the new revision then spends some time cleaning up buffers which causes it to miss the next modbus poll and the whole thing turns to custard for a while. I cannot run update 9.5, and have had to revert to version 8.5.

[judistakolev]

Hey guys. I have problems with the modbus. I’m noob in it and will be great to have some help. i recive this error:

2024-02-09 20:46:30.444 ERROR (SyncWorker_11) [homeassistant.components.modbus.modbus] Pymodbus: netp: Error: device: 3 address: 30021 → pymodbus returned isError True

And this is my config:

Thanks in advace !!!

[judistakolev]

This is my settings from the convertor

[G8YTZ (Justin)]

I’m having exactly the same problem as others above: I’ve tried various configurations:

modbus:
  - name: USR-NET-IO
    type: tcp
    host: 192.168.30.104
    port: 502
    close_comm_on_error: true
    delay: 1
    timeout: 5
    retry_on_empty: true
    message_wait_milliseconds: 250
    retries: 3
    #delay: 0
    #message_wait_milliseconds: 100
    #timeout: 15
    sensors:
      - name: GB3JV PA Temperature
        slave: 17
        address: 80
        input_type: holding
        unit_of_measurement: °C
        state_class: measurement
        scale: 0.01
        offset: -100
        precision: 0
      - name: GB3JV Return Loss
        slave: 17
        address: 88
        input_type: holding
        unit_of_measurement: dB
        state_class: measurement
        scale: 0.01
        offset: 0
        precision: 0
    switches:
      - name: GB3JV PA
        slave: 17
        address: 3
        write_type: coil
        verify:
      - name: GB3JV Drive
        slave: 17
        address: 2
        write_type: coil
        verify:
    binary_sensors:
      - name: GB3JV PA
        address: 3
        slave: 17
      - name: GB3JV Drive
        address: 2
        slave: 17

Log file looks like this:

Logger: homeassistant.components.modbus.modbus
Source: components/modbus/modbus.py:318
integration: Modbus (documentation, issues)
First occurred: 17:18:27 (62 occurrences)
Last logged: 23:40:20

Pymodbus: USR-NET-IO: Error: device: 17 address: 2 -> Modbus Error: [Input/Output] ERROR: No response received after 3 retries
Pymodbus: USR-NET-IO: Error: device: 17 address: 80 -> Modbus Error: [Input/Output] ERROR: No response received after 3 retries
Pymodbus: USR-NET-IO: Error: device: 17 address: 80 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.30.104:502]

Logger: homeassistant.components.modbus.modbus
Source: components/modbus/modbus.py:318
integration: Modbus (documentation, issues)
First occurred: 17:18:27 (62 occurrences)
Last logged: 23:40:20

Pymodbus: USR-NET-IO: Error: device: 17 address: 2 -> Modbus Error: [Input/Output] ERROR: No response received after 3 retries
Pymodbus: USR-NET-IO: Error: device: 17 address: 80 -> Modbus Error: [Input/Output] ERROR: No response received after 3 retries
Pymodbus: USR-NET-IO: Error: device: 17 address: 80 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.30.104:502]

But I sometimes get this, but it’s a TCP/IP connection, not serial!

Logger: homeassistant.config
Source: config.py:1324
First occurred: 23:35:26 (4 occurrences)
Last logged: 23:42:21

Invalid config for 'modbus' at configuration.yaml, line 43: required key 'baudrate' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 43: required key 'bytesize' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 43: required key 'method' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 43: required key 'parity' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 43: required key 'stopbits' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 44: not a valid value for dictionary value 'modbus->0->type', got 'tcp', please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 45: 'host' is an invalid option for 'modbus', check: modbus->0->host, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 47: 'close_comm_on_error' is an invalid option for 'modbus', check: modbus->0->close_comm_on_error, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 50: 'retry_on_empty' is an invalid option for 'modbus', check: modbus->0->retry_on_empty, please check the docs at https://www.home-assistant.io/integrations/modbus
Invalid config for 'modbus' at configuration.yaml, line 43: required key 'baudrate' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 43: required key 'bytesize' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 43: required key 'method' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 43: required key 'parity' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 43: required key 'stopbits' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 44: not a valid value for dictionary value 'modbus->0->type', got 'tcp', please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 45: 'host' is an invalid option for 'modbus', check: modbus->0->host, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 47: 'close_comm_on_error' is an invalid option for 'modbus', check: modbus->0->close_comm_on_error, please check the docs at https://www.home-assistant.io/integrations/modbus

[Mattie (Mattias)]

Any news for latest version? Still an issue?

[Mattie (Mattias)]

Just updated to 2024.5.2 and everything seems fine after almost 2 hours

[brrt]

I now see this issue on 2024.8.2 … I am lost

[Archades]

Quick question. How are you guys working out the slave addr. I’ve got the Poe 8 port eth relay but wave share going but never figured out the slave I’d. TCP server mode. The software is half Chinese characters sscom. Even with language pack, non unicode. I couldn’t upload the ini file. But it works anyway.

[Mattie (Mattias)]

I’m not using slave address, I configured my two gws as separate devices.

I have another issue tho, my send-commands have stopped working. Anyone having working send commands that can share?

[danclarkau (Dan)]

Upgraded HA to latest version and this appears to be still an issue. Now my MODBUS config area is complaining about not having baudrate etc specified, even though it’s TCP…

Invalid config for ‘modbus’ at configuration.yaml, line 89: required key ‘baudrate’ not provided, please check the docs at Modbus - Home Assistant Invalid config for ‘modbus’ at configuration.yaml, line 89: required key ‘bytesize’ not provided, please check the docs at Modbus - Home Assistant Invalid config for ‘modbus’ at configuration.yaml, line 89: required key ‘method’ not provided, please check the docs at Modbus - Home Assistant Invalid config for ‘modbus’ at configuration.yaml, line 89: required key ‘parity’ not provided, please check the docs at Modbus - Home Assistant Invalid config for ‘modbus’ at configuration.yaml, line 89: required key ‘stopbits’ not provided, please check the docs at Modbus - Home Assistant Invalid config for ‘modbus’ at configuration.yaml, line 90: ‘close_comm_on_error’ is an invalid option for ‘modbus’, check: modbus->0->close_comm_on_error, please check the docs at Modbus - Home Assistant

So frustrating I would have thought it would have been resolved by now in the latest releases.

[danclarkau (Dan)]

Randomly tried commenting out the following and it appears to have resolved the issue. Very strange that it was talking about all those other config options.

#close_comm_on_error: true

[Mattie (Mattias)]

So weird, I still have this issue, the readings are fast and exact byt the writing takes forever at best… Also saw a few others having similair issues a long time ago

Only thing I can see is that it seems to work for a while after a ha reboot

Takes hours to set a Modbus register

Hi again wgumaa! If you’re not using Docker I guess using the Modbus: Write register service is what you need. I tried to use it for my automations but it took several hours before the service actually sent any Modbus packages to the heat pump. I suppose that this might work for you as you’ve installed HA directly on a host. Just using a sensor wont work as it will only update the internal state. You can try this out in the developer tools where you can set the value of a sensor. These settings…

[danclarkau (Dan)]

I reckon comment out all the optional MODBUS lines and just enable one at a time until it works.

[Mattie (Mattias)]

I think my issue was scripts spamming different write registers without delay. I gave it some slack adding 1 minute delay between all actions so the write registers had enough time to register. Working better for now

[Mattie (Mattias)]

I can add to this that I still had issues with my SRNE inverter with a waveshare modbus gateway connected to it. It was slow and a register write could take 10 minutes. This weekend I tried to add other attributes to the config:

Added these lines and after that everything got responsive again
message_wait_milliseconds: 30
timeout: 5

  - type: rtuovertcp
    host: 192.168.1.30
    port: 8888
    name: modbus_tcp
    message_wait_milliseconds: 30
    timeout: 5