Ronnie1102

Thanks @MartinViljoen

i copied the fix from solarsynkv3 and applied it to my fork (https://github.com/cpether/Home-Assistant---E-Linter-Logger---Sunsynk), so this should be working again if anyone wants it.

Is the service down again? Getting a 500, this was after I had it working yesterday with the gdwaterworth fork

i was getting warnings when using that field that node-RED had deprecated it, that why i changed it to "use". Just hadn't updated the request correctly to use POST. I've committed a fix now.

ok got mine working . Looks like changes on gzip and some header stuff as well
In this


Change the variable headers_with_bearer to ( I changed encoding - removed gzip , referrer and origin )

    var headers_with_bearer = {
        "User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:124.0) Gecko/20100101 Firefox/124.0",
        "Accept": "application/json",
        "Accept-Language": "en-US, en; q=0.5",
        "Accept-Encoding": "deflate",
        "Content-Type": "application/json;charset=UTF-8",
        "Authorization": "Bearer " + global.get("SS.Bearer"),
        "Origin": "https://api.sunsynk.net",
        "Connection": "keep-alive",
        "Referer": "https://api.sunsynk.net/",
        "Sec-Fetch-Dest": "empty",
        "Sec-Fetch-Mode": "cors",
        "Sec-Fetch-Site": "same-site",
        "TE": "trailers"
    }

I may need to make changes on the setting one , but will try work that out later
Will update the git repo when I get some time

It seems Sunsynk is offline.

Must say this has been running flawlessly since your latest updates Gary, great piece of work you have done for all of us!

I've moved away from apex charts in the updated version but you can adjust the card height under breakpoint 1000

Thanks Gambit have not been able to get around getting back to you, this sorted out my issue.

You have to setup an automation to get new data.

alias: Solcast_update description: New API call Solcast trigger: - platform: time_pattern hours: /4 condition: - condition: sun before: sunset after: sunrise action: - service: solcast_solar.update_forecasts data: {} mode: single

Same one as before total_export. Did it that way so you didnt lose history 
 
pre -> filtered -> total_export

Will look at this later. 
 
On teh other topic I will have a look at teh code to force offline the online indicater if teh logger hasnt been updated in the last x minutes
Just busy with work stuff , so may take a few days

Definately looking a lot better after I put the changes in

 

I think it is bad web requests 😕
I have added a request timeout . Changes are in the development branch atm
Existing checks are picking up the aborted request now and not exporting data after it.
 
There also may be a different problem here which is to do with templates and chaining.
I may have to work with the updates so that the flows update directly instead of this (example) :-
  - sensor:
      - name: "Sunsynk PV1 Voltage 109"
        state: >
          {{state_attr('sensor.sunsynk_usable_pv', '1_volt')|float(0)|round(1)}}
 
 

Put a whole lot more error checking in to try stop bad data being exported
Also implemented filter sensors to try stop the 0 data problem on instance reboots/reloads.
Currently changes are in the development branch. Will push to stable branch when I am happy on the results

Actually very straight forward , based on javascript,  I have a far more complicated automation flow
1 problem I see
It only triggers once at 1am. Mine triggers a check every 10 minutes. So if an update doesnt go through it will be rerequested.
 

I know about this. still not sure why.
Looking at a way to import historical information from the sunsynk api into ha
Bit of a "longer term" project for me atm
On paper I have a process mapped out to probably fix the historical data. Still busy looking and experimenting 
Biggest hurdle I have to get past is how to expose the statistics db to the node red docker instance
 

Sweet Just got upgraded and set my intervals to 60s 👍. 
Will try to update the flows tomorrow because I think I messed something up just now so just reverted to my pre update backup.
I did saw one of the lines in the SS_Consolid where it showed my sn_data come back as " 12345678: false" so not sure what I missed but was rushing it so will try again when I have more time tomorrow.
 

Other thing I am busy playing with is monitoring for my Gas Bottles.
I have 2 sets of 2 (48kg) , 1 for downstairs ( Kids/Kitchen ) . 1 for upstairs bathroom & kitchen
Using a smart meter called https://www.eyegas.co.za/, rebranded Sonar Powered Tank Monitoring | MopekaIOT
Homeassisant actually picks up the bluetooth updates which is interesting.
Only problem is getting a usb dongle for bluetooth that is actually supported by Home assistant is a royal pain in the arse.
The Pi 3 and Pi 4 as well as intel nuc bluetooths all work. I have been trying to get one that I can put on the end of a 20m usb cable. But yah
Been through 4 x chinese shops in my area and bought 8 dongles with different branding so far lol
The list of unsupported dongles is longer than the supported.
At the moment I have hidden a pi3 with HA on setup as a remote unit behind a cupboard in my sons room that is near the 1 set of bottles on the opposite side of the wall. My main HA can see the other set of bottles.
 
Graphs are just rough for now. Will make things nice and pretty

 
 
 
 
 

I use for my weather.
Funny enough I turn off my alarm monitoring on my electric fence for rainy weather. Still get notifications on my HA though
Predictions seem to be ok for me
Signed up for this plan . I stay under the 1000 API calls

 

My initial setup false triggered so I need to tweak the conditions a bit but think I might just have had my batt and SOC sensors swapped around. 
I'm not using the weather to check conditions but rather the battery level and the PV level at given times.  Because I run on batteries all the time at night I will always have a high PV draw in the mornings to recharge the batteries so my logic will be something like:
At fixed time (say timeslot 2-4 on my SOC's 09:30, 10:00 & 11:00 )
Check if current batt < SOC level
if so check PV
if below 750w and Priority load is on
Call service turn off
energymode
Not perfect but this is kinda what I manually check and make a judgement call on.
alias: Sunsynk Priority Mode description: Check PV and set Priority Mode [Load/Battery] trigger: - platform: time at: "09:30:00" id: "09:30" - platform: time at: "10:00:00" id: "10:00" - platform: time at: "11:00:00" id: "11:00" condition: [] action: - if: - condition: trigger id: - "09:30" - condition: and conditions: - condition: numeric_state entity_id: sensor.sunsynk_battery_soc_184 below: sensor.battery_cap - condition: numeric_state entity_id: sensor.sunsynk_pv_today below: 750 - condition: state entity_id: input_boolean.sunsynk_energymode state: "on" then: - service: input_boolean.turn_off target: entity_id: - input_boolean.sunsynk_energymode device_id: [] area_id: [] data: {} - if: - condition: trigger id: - "10:00" - condition: and conditions: - condition: numeric_state entity_id: sensor.sunsynk_battery_soc_184 below: sensor.battery_cap - condition: numeric_state entity_id: sensor.sunsynk_pv_today below: 750 - condition: state entity_id: input_boolean.sunsynk_energymode state: "on" then: - service: input_boolean.turn_off target: entity_id: - input_boolean.sunsynk_energymode device_id: [] area_id: [] data: {} - if: - condition: trigger id: - "11:00" - condition: and conditions: - condition: numeric_state entity_id: sensor.sunsynk_battery_soc_184 below: sensor.battery_cap - condition: numeric_state entity_id: sensor.sunsynk_pv_today below: 1000 - condition: state entity_id: input_boolean.sunsynk_energymode state: "on" then: - service: input_boolean.turn_off target: entity_id: - input_boolean.sunsynk_energymode device_id: [] area_id: [] data: {} mode: single A second automation will just reset the boolean again at midnight back to on

My main dashboard for monitoring and smart switch controls with the obligotory RSA loadshedding and weather predictions. 😅

Some inverter stats on seperate pages

Note for anyone else:
To check if Node Red is connected to Home Assistant ( ie long life token or other ) , under global context expand

No Probs
Yea I have no individual charge slots active for myself but can see the benefit of getting those to work as well. 
As long as I can set the priority load/batt and usetimer on/off I can start writing a few automation's that should help automate things on bad weather days so that I don't have to touch a thing myself or micro manage it anymore 🤞

Ahhh thanks will look through and sort that out, all working now by the way appreciate your work!