Replies: 2 comments 5 replies
-
Quite a few ways to do this, from what you have described probably the easiest way to implement this is with this integration https://github.com/custom-components/remote_homeassistant You could also use REST API, but it would take a lot more work. |
Beta Was this translation helpful? Give feedback.
-
You can use mbusd instead of node-red there -- it exposes your modbus HAT as a ModbusTCP server (so it will look the same as any of the TCP to modbus adapters). If you want node-red to be able to connect to it as well, just configure it to talk ModbusTCP (so mbusd is serving both node-red and HA). Someone else set that up here: #235 (comment) |
Beta Was this translation helpful? Give feedback.
-
Hoping for a little guidance here!
I have a Raspberry Pi 4 including the Modbus HAT, with Node-Red and MQTT installed on. This is a dedicated device and is used for various things and works quite happily. I have a dashboard which visualises modbus data from my H1 inverter really well, but it is very basic!
I am just in the process of starting to setup Home Assistant and I've come across the Fox ESS integration and it looks fantastic so I'd like to take advantage of it, I have a separate PI with HA installed on and this is where I am getting stuck.... how do I get the modbus data from one PI to another.
Ideally what I'd like to do and think can be done (I just can't figure it out) is to use Node-Red to emulate the inverterand make the Modbus messages available in their original state so that the integration can consume them. I have tried various ways using the Modbus nodes but I have not figured it out.
Any help and ideally a worked example would be amazing and very much appreciated.
Thanks
Rob
Beta Was this translation helpful? Give feedback.
All reactions