![]() If I can make Option 2 run on it's own an the same HA NUC (proxmox) then it's also an option. Think I'll check option 3, if it's fast, then i'll stick to that. Option 4 is very unlikely, although I did that path already for the SAJ Solar integration. Option 3 is doable in NodeRED and can integrate easy with HA. Option 2 works great, but then I have to make some sort of startup script somewhere or a Addon (docker ?) copy official Modbus addon to a custom integration and change code. NodeRED's Modbus flows to read holding registers and map to HA variables.Ĥ. Would be nice to have this as an HA integration or Docker with a config interface.ģ. ![]() ![]() Modbus4MQTT : not tested (looks like there is a docker also)Ģ. If this minimal scan rate of 5 sec stays, I'm leaving the official HA Modbus Integration path.ġ. This is completely unusable as kauha describes if you want to read modbus as a button trigger to switch lights. ![]() I'm still a professional SCADA/PLC engineer, and with that experience I can't imagine why they would limit to minimal 5 sec. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |