Replies: 1 comment
-
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi together,
thanks first for this great plugin to be able to connectmy Solis inverter RHI-(3-4.6)K-48ES. It was a big step forwards for me to have the data of the inverter just with a small delay of 15 seconds!
But since I'm using this plugin to pull the data, I have the impression, the Pylontech batteries are drained much deeper compared to the past.
I'm using these settings:
That means, in settings I've defined an Backup Mode SOC of 25% and a Battery Minimum SOC of 30% (just for test purpose), but without PV generation, battery drain down to < 10% and than charge over grid.
As you can see, Battery SOC is currently at 26%, BatteryMinimumSOC is set to 30% and battery output energy is 149W.
This can be somehow improved by using "Power Switch" to off. Than battery remain and no discharge happens. I know, by this power switch no DC-AC conversation is active and therefore no energy is pulled from the inverter. I've tried to get this somehow automated by Node-Red flow to use ilumination sensor and time range to switch on , if sun is shining and powerSwitch is set to ff and set PowerSwitch to off, if battery is below a certain limit like 30%. But my NodeRed flow is just reporting API Error.
So maybe somebody do have an idea, what is causing the "uncontrolled" power consumption of my battery and how to improve my NodeRed flow to be able to control the PowerSwitch from outside.
I've tried json code
[ { "id": "22c114fa0cb797be", "type": "api-call-service", "z": "80256283d2de9f87", "name": "PowerSwitch off", "server": "2a08017d41c42a0a", "version": 5, "debugenabled": true, "domain": "input_boolean", "service": "turn_off", "areaId": [], "deviceId": [], "entityId": [ "select.solis_modbus_power_switch" ], "data": "{\"entity_id\":\"select.solis_modbus_power_switch\",\"state\":\"Off\"}", "dataType": "json", "mergeContext": "", "mustacheAltTags": false, "outputProperties": [], "queue": "none", "x": 840, "y": 1440, "wires": [ [ "7d0a7baf4292e3fd" ] ] }, { "id": "2a08017d41c42a0a", "type": "server", "name": "Home Assistant", "version": 5, "addon": false, "rejectUnauthorizedCerts": true, "ha_boolean": "y|yes|true|on|home|open", "connectionDelay": true, "cacheJson": true, "heartbeat": false, "heartbeatInterval": "30", "areaSelector": "friendlyName", "deviceSelector": "friendlyName", "entitySelector": "friendlyName", "statusSeparator": ": ", "statusYear": "hidden", "statusMonth": "short", "statusDay": "numeric", "statusHourCycle": "default", "statusTimeFormat": "h:m", "enableGlobalContextStore": false } ]
or just set_off like
[ { "id": "4ede9966de1ae0f0", "type": "api-call-service", "z": "80256283d2de9f87", "name": "PowerSwitch off", "server": "2a08017d41c42a0a", "version": 5, "debugenabled": true, "domain": "switch", "service": "turn_off", "areaId": [], "deviceId": [], "entityId": [ "select.solis_modbus_power_switch" ], "data": "", "dataType": "jsonata", "mergeContext": "", "mustacheAltTags": false, "outputProperties": [], "queue": "none", "x": 920, "y": 1560, "wires": [ [ "7d0a7baf4292e3fd" ] ] }, { "id": "2a08017d41c42a0a", "type": "server", "name": "Home Assistant", "version": 5, "addon": false, "rejectUnauthorizedCerts": true, "ha_boolean": "y|yes|true|on|home|open", "connectionDelay": true, "cacheJson": true, "heartbeat": false, "heartbeatInterval": "30", "areaSelector": "friendlyName", "deviceSelector": "friendlyName", "entitySelector": "friendlyName", "statusSeparator": ": ", "statusYear": "hidden", "statusMonth": "short", "statusDay": "numeric", "statusHourCycle": "default", "statusTimeFormat": "h:m", "enableGlobalContextStore": false } ]
in HA I can see this instance is expecting On or Off
But how to controll this by NodeRed flow?
Beta Was this translation helpful? Give feedback.
All reactions