This respository contains the required Node-RED flows to scrape the web interface of a STIEBEL ELTRON Internet-Service Gateway (ISG WEB) and forward the data via MQTT to HA (and optionally to an InfluxDB).
For questions and other inquiries, use the issue tracker in this repo.
After I extended my home installation with a photovoltaic converter of SMA and connected the installations (Stiebel Eltron LWZ504e and SMA Sunny Manager), Modbus was not working anymore on the ISG web and I could scrap my old scrapping method (python-stiebe-eltron). The Modbus and EMI “modules” can not run in parallel on the ISG web. The complete history of the marriage between Stiebel Eltron and Home Assistant can be found in this thread, including different solutions: Is there any interest in a Stiebel Eltron climate platform?
At minimum you need the following components:
- STIEBEL ELTRON Internet-Service Gateway ISG WEB
- STIEBEL ELTRON heatpump (compatible). Successfully used devices:
- LWZ504e
- LWZ304
- Tecalor TTC05
- Node-RED, either installed as part of Home Assistant OS as an Add-on, as a separated docker container or as any other possible deployment option.
- MQTT Broker, either installed as part of Home Assistant OS as an Add-on, as a separated docker container or as any other possible deployment option.
- Network connection bewteen all components
The setup can easily be extend with the following components to get very nice history graphs.
- Setup Home Assistant (HA)
- Setup the MQTT Brocker
- Add MQTT integration to HA
- Make sure HA is able to receive MQTT messages
- Setup Node-RED
- Import 2 relevant flows in this repo into Node-RED. The default flows
are
flow_ha-mqtt-discovery.json
andflow_stiebel-servicewelt.json
, the*Tecalor-TTC05.json
flows are for Tecalor TTC05 and compatible devices. - Without InfluxDB: delete the nodes which prepare and send the data to InfluxDB. You don't need them.
- Update the node "Set ISGWeb URL" in flow "Stiebel Servicewelt"
- Update the node "HA MQTT Set device details" with your installation details in flow "HA MQTT Discovery".
- Verify or add the MQTT broker configuration
- Deploy the flows
- Import 2 relevant flows in this repo into Node-RED. The default flows
are
- In HA
- Add the MQTT integration
- In Node-RED
- Trigger the node "Trigger to flush messages to get HA discover new sensors immediately" in flow "HA MQTT Discovery".
- In HA
- Check for new sensors
In HA, if you did setup MQTT, you can go to "Configuration > Integrations > MQTT > CONFIGURE" and start listening to the topic "homeassistant/sensor/#". You should see a bunch of messages, which start with something like "homeassistant/sensor/...".
If you don't see them, go to node-red again. The debug panel will only show something, if an error occurs or if you did enable debug msg nodes. You can do so in the "HA MQTT Discovery" flow. Then redeploy it and you should soon get some messages showing up in the node-red debug log.
- In case you see the messages, but still do not receive anything in HA, it's probably your MQTT broker config in node-red, which is not working.
- In case you don't see any messages, copy the debug node in "HA MQTT Discovery" and attach it anywhere earlier in the flow to find if somewhere the messages are flowing.
The content of this node-red
repository is licensed under MIT, for more details check LICENSE.