Modbus

I recently installed a Daikin ducted heatpump, along with a Daikin ERV that sits in line with the heatpump. Instead of going with a connected smart controller (none of which supported the ERV anyway) I got a modbus controller for the system that Daikin seems to market more towards commercial installs. The benefit is that I now have full local control of the system via Home Assistant but it also works in tandem with the standard wall controller (incase Home Assistant is down, or something)

Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23.

I've got Daikin heat pumps with the wifi module, but NOT using the wifi. There's a small plug on the side of the module that allows it to be connected via modbus (industrial automation control communications bus). A rs485 adapter plugged into homeassistant and some wires later and they are all controllable fully local and hardwired!

Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23.

Same problem with SDM72D-M and SDM120M on PROTOSS PE-11 via modbus over tcp. From both masters I only get 6W (is wrong) and nothing from Slave.

Excerpt saved from GitHub on 2026-10-23.

Same problem with SDM72D-M and SDM120M on PROTOSS PE-11 via modbus over tcp. From both masters I only get 6W (is wrong) and nothing from Slave.

Excerpt saved from GitHub on 2026-10-23.

The problem Flexit integration has stopped working after upgrading from core 2024.2.5 ### What version of Home Assistant Core has the issue? 2024.3.0 - 2024.5.1 ### 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 Flexit ### Link to integration documentation on our website https://www.home-assistant.io/integrations/flexit ### Diagnostics information modbus_hub contain no entities, causing instability, entry not loaded ### Example YAML snippet [code] ### Anything in the logs …

Excerpt saved from GitHub on 2026-10-23.

The problem I've had a Modbus TCP integration with my INIM intrusion panel for two years without any issues, working flawlessly up until version 2025.1.4. However, since upgrading to 2025.2, I've encountered numerous problems. It appears that some registers, primarily coils, are being missed, and I'm unable to read or write to them reliably. I want to emphasize that I haven't made any changes whatsoever to either my integration YAML file or the INIM intrusion panel configuration. Due to this bug, I'm no longer able to arm/disarm certain zones. This issue occurs randomly with specific …

Excerpt saved from GitHub on 2026-10-23.

Description: This module is for using modbus registers as a thermostat. It allows for changing the target temperature, and monitoring the current temperature. A pull request has been submitted for home-assistant.github.io as well. Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#4593 ## Example entry for `configuration.yaml` (if applicable): ```yaml climate: - platform: modbus name: Watlow F4T # Modbus TCP slave: 1 # Control Loop 1 Setpoint target_temp_register: 2782 # Universal Input 1 Module 1 current_temp_re

Excerpt saved from GitHub on 2026-10-23.

5. I’m really happy with the my sungrow setup. Local modbus monitoring and control. 6. I have several Shelly relays and as part of my renovations that are currently underway I am installing Shelly pro relays and dimmers, using standard Clipsal 240v wall switches and smarts from HA. I haven’t implemented No3 yet but I am thinking of a zigbee option. Somfy hubs seem to be changing accessibility and zigbee is pretty straightforward. Seems a number of local blinds places sell zigbee options.

Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23.

I have same kind of problems. I have TCP Modbus to Epever UPower (UP3000-HM5042) and it have been working fine up to 2025.1.4 version, but not with any 2025.2.x versions. I can read values but I have one critical switch and it doesn't work. If I upgrade to 2025.2.x I cant get values for "Grid Voltage" but switch doesn't work anymore. When try to use switch I get error [code] I have tried to change switch config and I either get this error or it doesn't work, My Modbus conf ``` #EPEver UPower-Hi + USB CH343 + mbusd modbus: - name: epever type: tcp host: 172.16.101.34 port: 502 timeout: 10 …

Excerpt saved from GitHub on 2026-10-23.

Proposed change Add support for Sungrow solar inverters with encrypted TCP modbus communication. To enable support use "type: sungrow" under modbus integration. ## Type of change - [ ] Dependency upgrade - [ ] Bugfix (non-breaking change which fixes an issue) - [ ] New integration (thank you!) - [X] New feature (which adds functionality to an existing integration) - [ ] Breaking change (fix/feature causing existing functionality to break) - [ ] Code quality improvements to existing code or addition of tests ## Example entry for `configuration.yaml`: ```yaml # Example configuration.yaml …

Excerpt saved from GitHub on 2026-10-23.