Thank you that is awesome i now have the readings 
i did make a few adjustments to correct some values so that they read in KW rather than W but thats way easier when all the code is sat in front of you.
one thing i have noticed if Grid power is 0W the reading shows 65534w which is not a huge concern but would be nice to removed that any ideas?
Yeah I saw that same issue but didn’t get around to looking. Sometimes it’s 0 but then goes to that number, there are two other sensors that also do that.
Some learning that I made for the charging and discharging switches:
I’m normal operation you only need the “saver/auto mode” stitch ON and the “stand by switch” OFF.
You only use the “charge switches” to FORCE the Sofar to charge.
You only use the “discharge switches” to FORCE the Sofar to discharge.
at the moment im just using it as read only no control over the inverter, but once i get my smartmeter fixed and on cheap electric over night ill be moving to charge over night so will be playing with that.
how did you get the slide switchs for the modes? i can only find this
Try using this card yaml for the slider switches:
type: entities
entities:
- entity: switch.sofar_auto_saver_mode
name: Saver / Auto Mode
icon: mdi:battery-sync-outline
- entity: switch.sofar_standby_mode
icon: mdi:power
name: Stand-by
- entity: switch.sofar_charge_mode_2000
name: Chg 2000w
icon: mdi:ev-station
- entity: switch.sofar_charge_mode_2500
name: Chg 2500w
icon: mdi:ev-station
- entity: switch.sofar_charge_mode_3000
name: Chg 3000w
icon: mdi:ev-station
show_header_toggle: false
state_color: true
title: Sofar Inverter Control
Hi,
i try to use this integration with my Sofar HYD-5000ES with wifi logger (S/N: 23XXXXXX). I put on all the parameters and restart HA but all the sensor stay in status “unknown”.
I don’t have any error message in log.
I also try autodiscover mode but without success
If someone have an idea…
Thanks
PS : i have an integration with solarman API which works fine but i would try to get datas directly from the data logger
Well according to the documentation you should have full support:
Supported models:
ME3000SP - Full support
HYD-xx00-ES - Full support
I made some notes to test the API at Solarman website, can you try and see if you get the output directly from the website, then at least you know the values are available for your MQTT server to extract in JSON format:
#How to refresh the Solarman Token Code if sensors stop getting data:
If the SOFAR sensor data stops working try to refresh the token by following these steps:
curl --request POST \
--url 'https://api.solarmanpv.com/account/v1.0/token?appId=20211xxxxxxxxxx&language=en&=' \
--header 'Content-Type: application/json' \
--data '{
"appSecret": "8cb8f0fec435y654ea127eda0c7d9f406e",
"email": "[email protected]",
"password": "9d564hks8679534kghtd6da660b155cf15872fae88fc365a48683cac720cf18"
}'
NOTE: your Sofarman password has to be hashed using SHA256 Password: SHA256 - Online Tools
{
"code": null,
"msg": null,
"success": true,
"requestId": "d94127a5000d00ad",
"access_token": "eyJhbxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"token_type": "bearer",
"refresh_token": "eyJhbxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"expires_in": "5183999",
"scope": null,
"uid": 762072
}
curl --request POST \
--url 'https://api.solarmanpv.com/device/v1.0/currentData?appId=<appId>&language=en&=' \
--header 'Authorization: bearer eyJhbxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' \
--header 'Content-Type: application/json' \
--data '{
"deviceSn": "SE1ESxxxxxxxxx"
}'
NOTE: Paste the ACCESS TOKEN in to the Home Assistant CURL .YAML file: /config/packages/systems/sofar_battery_inverter/solarman_sensors.yaml
{
"code": null,
"msg": null,
"success": true,
"requestId": "51fe94ec1aaf79a2",
"deviceSn": "SE1ESxxxxxxxxxx",
"deviceId": 2150xxxxxx,
"deviceType": "INVERTER",
"deviceState": 1,
"dataList": [{
"key": "SN1",
"value": "SE1ESxxxxxxxxx",
"unit": null,
"name": "SN"
}, {
"key": "SS_CY1",
"value": "9",
"unit": null,
"name": "Production Compliance Country"
}, {
"key": "HWv1",
"value": "V100",
"unit": null,
"name": "Hardware Version"
}, {
"key": "SWmai_v1",
"value": "V280",
"unit": null,
"name": "Software Master Version"
}, {
"key": "DSPv1",
"value": "V280",
"unit": null,
"name": "DSP Version"
}, {
"key": "DSPv2",
"value": "V280",
"unit": null,
"name": "Vice DSP Version"
}, {
"key": "DPi_t1",
"value": "5100",
"unit": "W",
"name": "Total DC Input Power"
}, {
"key": "AV1",
"value": "251.80",
"unit": "V",
"name": "AC Voltage R/U/A"
}, {
"key": "AV2",
"value": "0.00",
"unit": "V",
"name": "AC Voltage S/V/B"
}, {
"key": "AV3",
"value": "0.00",
"unit": "V",
"name": "AC Voltage T/W/C"
}, {
"key": "AC1",
"value": "4.79",
"unit": "A",
"name": "AC Current R/U/A"
}, {
"key": "AC2",
"value": "0.10",
"unit": "A",
"name": "AC Current S/V/B"
}, {
"key": "AC3",
"value": "0.08",
"unit": "A",
"name": "AC Current T/W/C"
}, {
"key": "Et_ge0",
"value": "431",
"unit": "kWh",
"name": "Cumulative Production (Active)"
}, {
"key": "Etdy_ge1",
"value": "8.55",
"unit": "kWh",
"name": "Daily Production (Active)"
}, {
"key": "ST_PG1",
"value": "Purchasing energy",
"unit": null,
"name": "Grid Status"
}, {
"key": "PG_F1",
"value": "49.97",
"unit": "Hz",
"name": "Grid Frequency"
}, {
"key": "PG_Pt1",
"value": "-10.00",
"unit": "W",
"name": "Total Grid Power"
}, {
"key": "t_gc1",
"value": "174",
"unit": "kWh",
"name": "Cumulative Grid Feed-in"
}, {
"key": "Et_pu1",
"value": "9",
"unit": "kWh",
"name": "Cumulative Energy Purchased"
}, {
"key": "t_gc_tdy1",
"value": "0.14",
"unit": "kWh",
"name": "Daily Grid Feed-in"
}, {
"key": "Etdy_pu1",
"value": "1.09",
"unit": "kWh",
"name": "Daily Energy Purchased"
}, {
"key": "PG_V1",
"value": "251.80",
"unit": "V",
"name": "Grid Voltage R/U/A"
}, {
"key": "PG_V2",
"value": "0.00",
"unit": "V",
"name": "Grid Voltage S/V/B"
}, {
"key": "PG_V3",
"value": "0.00",
"unit": "V",
"name": "Grid Voltage T/W/C"
}, {
"key": "PG_C1",
"value": "6.50",
"unit": "A",
"name": "Grid Current R/U/A"
}, {
"key": "PG_C2",
"value": "0.00",
"unit": "A",
"name": "Grid Current S/V/B"
}, {
"key": "PG_C3",
"value": "0.00",
"unit": "A",
"name": "Grid Current T/W/C"
}, {
"key": "BUS_V2",
"value": "396.00",
"unit": "V",
"name": "Busbar Voltage"
}, {
"key": "E_Puse_t1",
"value": "3470.00",
"unit": "W",
"name": "Total Consumption Power"
}, {
"key": "Et_use1",
"value": "249",
"unit": "kWh",
"name": "Cumulative Consumption"
}, {
"key": "Etdy_use1",
"value": "7.26",
"unit": "kWh",
"name": "Daily Consumption"
}, {
"key": "B_ST1",
"value": "Charging",
"unit": null,
"name": "Battery Status"
}, {
"key": "B_V1",
"value": "50.60",
"unit": "V",
"name": "Battery Voltage"
}, {
"key": "B_C1",
"value": "31.29",
"unit": "A",
"name": "Battery Current"
}, {
"key": "B_P1",
"value": "-1650.00",
"unit": "W",
"name": "Battery Power"
}, {
"key": "GE_C1",
"value": "20.41",
"unit": "A",
"name": "Production Current"
}, {
"key": "Pcg_dcg1",
"value": "1590.00",
"unit": "W",
"name": "Charging/Discharging Power"
}, {
"key": "P_INV1",
"value": "1000.00",
"unit": "W",
"name": "Storage Inverter Power"
}, {
"key": "B_left_cap1",
"value": "71",
"unit": "%",
"name": "SoC"
}, {
"key": "t_cd_cg_n1",
"value": "15",
"unit": null,
"name": "Cumulative Charging/Discharging Time"
}, {
"key": "t_cg_n1",
"value": "80",
"unit": "kWh",
"name": "Total Charging Energy"
}, {
"key": "t_dcg_n1",
"value": "72",
"unit": "kWh",
"name": "Total Discharging Energy"
}, {
"key": "Etdy_cg1",
"value": "4.09",
"unit": "kWh",
"name": "Daily Charging Energy"
}, {
"key": "Etdy_dcg1",
"value": "2.26",
"unit": "kWh",
"name": "Daily Discharging Energy"
}, {
"key": "INV_T0",
"value": "39",
"unit": "℃",
"name": "Temperature- Inverter"
}, {
"key": "B_T1",
"value": "22.00",
"unit": "℃",
"name": "Temperature- Battery"
}, {
"key": "T_RDT1",
"value": "33",
"unit": "℃",
"name": "Radiator Temperature"
}, {
"key": "SYSTIM1",
"value": " 22-05-30 09:54:51",
"unit": null,
"name": "System Time"
}, {
"key": "V_eme_o1",
"value": "251.10",
"unit": "V",
"name": "Emergency Output Voltage"
}, {
"key": "P_eme_o1",
"value": "0.00",
"unit": "W",
"name": "Emergency Output Power"
}, {
"key": "Etdy_ge_hou1",
"value": "3.15",
"unit": "h",
"name": "Daily Production Hour"
}, {
"key": "HR_Ege_t1",
"value": "60",
"unit": "h",
"name": "Total Production Hour"
}, {
"key": "CD_TIM1",
"value": "0.03",
"unit": "s",
"name": "Countdown Time"
}, {
"key": "Buck_C1",
"value": "4.67",
"unit": "A",
"name": "Buck Current"
}, {
"key": "LLC_BUS_V1",
"value": "331.70",
"unit": "V",
"name": "LLC Busbar Voltage"
}, {
"key": "C_Dcp1",
"value": "0.01",
"unit": null,
"name": "DC Component-Current"
}, {
"key": "V_Dcp1",
"value": "-69.00",
"unit": null,
"name": "DC Component-Voltage"
}, {
"key": "INV_ST1",
"value": "Grid connected",
"unit": null,
"name": "Inverter status"
}]
}
Thank you,
as i said i already use the integration using Solarman API and it works fine but i would try to get datas directly from the data logger directly with local access
Hi Guys, that 65534 that you’re seeing is the equivalent of - 1 when represented as an unsigned integer - I’m not sure how you would fix it, but I think you can declare the datatype as a signed integer and the issue will be sorted.
Hi Everyone,
Looking to change the amount charged overnight via solar estimates.
I know you can bring in things around python scripts etc, I’m just wondering what’s the easiest method?
I am currently capturing tomorrows solar estimate and have sofar2mqtt up and running.
Thanks for your help.
I use Solcast for my Solar predictions. I have a ‘input_number’ helper set up for the “overnight charge powerwall max charge” and then here are my automation (the Chooses part) that I use to set the different SOC levels required. Obviously I have a power wall but the principle should still be the same. Then using your sofar2mqtt you can turn on charging and turn off once the corresponding Sofar Battery SOC matches the input_number.overnight_charge_powerwall_max_charge
choose:
- conditions:
- condition: numeric_state
entity_id: sensor.solcast_forecast_tomorrow
below: 8
sequence:
- service: input_number.set_value
data:
value: 100
target:
entity_id: input_number.overnight_powerwall_max_charge
- conditions:
- condition: numeric_state
entity_id: sensor.solcast_forecast_tomorrow
above: 8
below: 12
value_template: ""
sequence:
- service: input_number.set_value
data:
value: 80
target:
entity_id: input_number.overnight_powerwall_max_charge
- conditions:
- condition: numeric_state
entity_id: sensor.solcast_forecast_tomorrow
above: 12
below: 14
sequence:
- service: input_number.set_value
data:
value: 70
target:
entity_id: input_number.overnight_powerwall_max_charge
- conditions:
- condition: numeric_state
entity_id: sensor.solcast_forecast_tomorrow
above: 14
below: 18
sequence:
- service: input_number.set_value
data:
value: 60
target:
entity_id: input_number.overnight_powerwall_max_charge
- conditions:
- condition: numeric_state
entity_id: sensor.solcast_forecast_tomorrow
above: 18
sequence:
- service: input_number.set_value
data:
value: 50
target:
entity_id: input_number.overnight_powerwall_max_charge
- conditions:
- condition: numeric_state
entity_id: sensor.solcast_forecast_tomorrow
above: 18
sequence:
- service: input_number.set_value
data:
value: 35
target:
entity_id: input_number.overnight_powerwall_max_charge
Did you check if the token has changed? Follow my post here on how to do that:
Hi Chris, what does passive mode means in this context?
It’s the setting that you must change in the SoFar inverter menu system to allow RS485 controlling of the inverter. See energy storage mode below.
Hi Chris,
is there a reason you choose/prefered the cmcgerty/Sofar2mqqt approach over GitHub - wills106/homeassistant-solax-modbus: SolaX Power Modbus custom_component for Home Assistant (Supports some Ginlong Solis, Growatt, Sofar Solar & Qcells Q.Volt Hyb) ? or are they having very different goals?
if I understand it correctly you can change the settings like charge / discharge of battery from HA. So this way for example you can build logic in HA to trigger when battery should charge?
Hi Joost,
As you know with home assistant, there are always many ways of doing the same thing. I just went the way I did, invested money and time in building the module add setting everything up. It all works for me and I can control charging and discharging of the SoFar and Pylontech batteries in HA…so I’m happy.
Did you find a way to see what the inverter returns locally? I am also trying to catch the Sofar variables locally.
Thanks
I don’t know if anyone can give me a clue here, I am trying to build an estimate for how much power I have avialable based on the load on the system
So something like:
So Inverter Load - (Solar Production + Battery Storage)
The one thing I am struggling to figure out is which metric is the current battery capacity in watts, I see percentage but no watts. Am I missing something.
If anyone has solved for this, please share.
I don’t use Solarman (I opted for Solar Assistant, but in the end the fundamentals are the same), but you are confusing some terminology. Capacity relates to energy (kWh or then kJ). Power is a rate (kW or then kJ/s). Capacity would be like the distance you can cover. Power would then be your speed in this analogy.
If you don’t have energy sensors, you need to integrate the power sensor’s and then sum them, or calculate the net power and integrate that.
Use method left: Integral - Home Assistant.
Otherwise, if what you’re trying to calculate is whether you can switch on the kettle or washing machine now, given your solar potential and battery (all of this in W or kW), then it’s probably more complicated if you want to include the battery. It’s fairly easy just to calculate the difference between your solar forecast and current solar PV power (this is what I do), but your battery will have a max rating (W) and total capacity (kWh), so technically you can hit it as hard as your battery can deliver in combination with your inverter’s rating. Thus, it becomes a question of need over ability.
The reason I only look at the PV, is because that’s the free energy. The battery really is just a big buffer and will either be topped up by solar for free or the grid. Since the grid costs money, I leave it out of the calculation. It’s also much simpler.
You can have a look at all my sensors and stuff. I just recently completed it, but it covers some of the things above.
I can add a screenshot of my dashboard later when I’m at my computer.
Thank Pieter, makes sense and exactly what I needed. Solarman is kak, I don’t know what shenegans they are pulling with the ESP chip in the damn thing, but it’s wifi connectivity is so bad, irrespective of what you do. I have tons of other ESP devices that have no issues. I should probably migrate to Solar Assistant or a Solarman unit with RJ45
