Home Assistant
With your MQTT broker set in the box, Home Assistant discovers WeCo Monitor and creates sensor.weco_monitor_soc, sensor.weco_monitor_power, voltage and current, one set of sensors per module such as sensor.weco_monitor_module_1_soc, sensor.weco_monitor_cell_min, sensor.weco_monitor_cell_max, sensor.weco_monitor_soh and binary_sensor.weco_monitor_alarm. No YAML to write.
No MQTT broker? The REST integration can read the local JSON API instead.
MQTT
Once on your broker, readings are open to any client: Telegraf and InfluxDB, Grafana, or a script that writes a monthly health report.
Local JSON API
GET http://moniwatt.local/api.json?key=YOUR_KEY
{ "soc": 74, "power": 2150, "voltage": 53.0,
"modules": [{"soc": 75}, {"soc": 73}], "soh": 99, "alarms": [] }The key is shown in Settings > Access key & Cloud.
Jeedom
A JSON plugin from the Market polls api.json; create info commands for soc, power and soh, and one per module if you want to compare them in a history graph.
Node-RED
An http request node on api.json with parsed JSON, then a function node that finds the module with the lowest charge in msg.payload.modules. Or receive everything through mqtt in.
Domoticz
The MQTT Auto Discovery gateway of Domoticz creates the same devices as Home Assistant; a dzVents script on api.json is the option without a broker.
openHAB
The HTTP binding with JSONPATH, such as $.soc and $.modules[0].soc, or the MQTT binding.
IFTTT, Make and Apilio
With the free Cloud on, IFTTT, Make.com or Apilio can read the private JSON link of your battery and bridge values into SmartLife or Tuya scenes. There is no native Tuya integration.
Ideas for WeCo owners
- Get told when one module keeps ending the day lower than the others.
- Heat water with the surplus once the cluster is full.
- Send yourself a monthly state-of-health report.
- Hold heavy appliances when the battery gets low in the evening.
- Plot each module side by side over the years.