Whatever one is comfortable with is the right solution for them. There is never a right answer as it is a continuum between the two extremes. The corollary is that with complexity comes capability. It is much like those that do not want to use DNS and always use a physical IP address rather than a domain name because complexity is added when needing to depend upon a DNS server to do the translation. Since mcsMQTT has its own MQTT server there is not additional dependency when using MQTT vs. MQTT has advantages related to responsiveness and self-diagnostics so that is the final choice that we made. When MiamiJerry and I were doing the integration we did both approaches. It is also possible to integrate poolController using HTTP rather than MQTT protocol on the network. For other they just want to replace everything when it is not working and don't care what part has broken. For some they want to be able to diagnose what is not working and fix that part. At each layer, there is also a diagnostic capability. The need for poolController software running on Pi is understandable that a layer of complexity has been added. I assume you want to keep the HS component of the complexity otherwise you would not be posting for a solution for HS integration. What are you using as the physical interface between Screenlogic and Pentair? Requirements This plugin was recently rewritten in Typescript to use the latest capabilities of Homebridge 1. I am not knowledgeable with the interfaces available for Pentair hardware. Screen Logic plug-in for Homebridge using the node-screenlogic library.
0 kommentar(er)
