#Modbus poll interval manual#
With 2021.7 you can set scan_interval: 0, and only have manual scanning (service_call “update_state”). For switch and cover many set the scan_interval to 9999 to avoid polling. We have furthermore added a verify_delay, to allow for e.g. If you configure a switch with verify: and call the turn_on service a read request is sent directly to verify that the switch is turned on. You are mixing some issues as far as I can tell, scan_interval do not have a lot to do with turn on/off a switch. Actually this gave me a problem with my solar inverter, because I do a load monitoring to secure I do not import energy. I am an old SCADA engineer so believe me, I have had quite a number of discussions with the people responsable for core, I strongly believe it is wrong to impose a 5 second limit. Holding Registers which then couldīe read/written by an external HMI/SCADA system. different HA devices and entities are "mapped" on for ex. With Modbus Slave I mean : HA is the Modbus Slave where for ex. I saw some posts on it that somebody was looking into it. (or look into copying the integration as a custom)Īs for Modbus integration functionality : I guess we won't see a modbus slave on HA ? Otherwise I will be leaving modbus then because it's not workable. Maybe you can convince HA owners to allow this again.
Until now it totally worked fine polling each second from HA (running on Proxmox NUC). Maybe I'll have to look then at an (UA) OPC server or MQTT bridge to link Modbus (PLC's.) to HA with faster respons.Ī SCADA/HMI btw. values out of a Solar Converter don't need second updates of their measurements and values.īut when Modbus is used for Switch/Light/Cover/Motion sensors devices,ĥ seconds to wait until a light or switch is turned on (or state read) is simply to long. Why do they limit in then on Modbus Integration. MQTT en other events don't have minimum waiting delays of 5 sec for a state trigger. I wish this was described then first in HA release breaking changes, because then I would not have updated to this latest version and sticked to 2021.5.x.