Starting a new thread as this was getting lost in the Hints, Tips & Troubleshooting thread.
Post details of your integration with Home Assistant etc.
I just do max export allowed, and fix an SOC threshold for every hour.
So imaybe 20% per hour @ 5kW. So stop discharging when you hit 20% between 1 and 2, stop when you hit 40% between 12 and 1 etc......
You will finish each night at 20% SOC irrespective of the starting position
Was thinking that alright but wanted to end at 10% bang on 2am (or close to it)
Funny enough the sunsynk flow card displays the time when it hits 10%
But it's not a value I can automate against, I usually set it by hand until it's close to 2am and it has been very accurate but I want to not do it manually ofc
I do 15% per hour. It finishes early (reaches the low threshold) so reverts to discharging normally for the last 15 mins or so of each hour.
So you might end up actually hitting 9% that way, so you could set the threshold for 1 to 2 at 12%
So basically, Trigger time between 1:00 and 2:00 If SOC% > bottom level Then Dump Discharge Else Normal Discharge
Then repeat for all hours from 21:00
Sure throw in the code and I can give it a shot 😀
Anyone else having issues with their myenergi systems (particularly those on S18)?
My devices are showing as unavailable in HA since approx 11:40 and getting a communication error in the myenergi app. The API itself appears to be up though and nothing logged here.
Have logged a ticket and awaiting a response.
App and HA integration seems to be working fine here.
Are you on V5 firmware? How frequently are you polling within HA?
Yeah running V5 on the gen1 hub and eddi. Polling in HA every 10 seconds.
Thanks. Might have to bite the bullet and upgrade to V5.
https://status.myenergi.com/incidents/2pbtvvmv0wy8
New incident posted.
I'd be the same. Every 10 secs on a Gen 1 Hub, with a v5 Eddi and Zappi. No issues as far as I can see
Back as of 14:59.
Thanks graememk, maybe I explained it wrong. What I mean is on the APP I see this but on HA the two consumption sensors neither match the APP total, if that makes sense?
Oh I know what you mean, I had no clue how to help with the integration, but a workaround would be to work from the sensor that is working.
Ok, so I am hopefully a step nearer to getting the inverter data locally rather than from the Solis cloud.
I was trying to figure out how to get the mini pc that HA runs on into the loft next to the inverter so if I have to connect it to the data logger it could be easily done.
Tried a TP link LAN plugin but because the backup socket the solar guys added is not part of the same ring as the other sockets in the house it didn't want to play ball.
I then found an old Sky Wireless device (LAN to wireless) and this seem so have done the trick.
So what would be the simplest way to do this I have started reading various github articles, Solis Modbus and Solarman intergration but am not 100% what is involved.
Also watched the Gordonmarkus video's on YouTube, a lot of which went straight over my head.
This is the data logger that is in the inverter at the moment, I think it is S2-WL-ST so don't think Solarman doable?
Any suggestions/direction would be more than welcome?
Thanks
The S2-WL-ST supports Modbus TCP (port 502) out of the box, but the downside is that no data is uploaded to Solis Cloud while querying locally with Modbus TCP. Is this an issue?
In terms of HA integration, use this or this. The former is using the native Modbus integration, the latter is using a third party integration which has Solis support.
Thanks, will take a look.
looking to do same with SOlis invertor to feed into HA
Hi All,
few days ago i installed Luna 2000 battery and signup to Electric Ireland Night Boost tariff. I managed to fix issue with PV generation after battery install (i was using Shell EM clamp only). But having tariff with 3 diferent prices im not able to create template sensor (i think this what i need to use) to cover all 3 prices/times, does anybody have solution for this?
Did you create the defined time periods and names in automations.yaml? The example below is for a day/night meter (peak and offpeak), I don't see a reason why it can't have three periods.
- id: '1634335289003' alias: ESB Meter Electricty Meter Tariffs description: Day and Night PEAK Tariffs trigger: - platform: time at: 08:11:00 variables: tariff: peak - platform: time at: '23:11:00' variables: tariff: offpeak action: - service: select.select_option target: entity_id: select.hourly_energy data: option: '{{ tariff }}' - service: select.select_option target: entity_id: select.daily_energy data: option: '{{ tariff }}' - service: select.select_option target: entity_id: select.monthly_energy data: option: '{{ tariff }}'
I see, instead of creating new template sensor You have an automation to update entity with prices - this is excelent idea. Im going to check this.
thanks
Then create utility_meter in configuration.yaml:
utility_meter: hourly_energy: source: sensor.shelly_em_esb_meter_channel_1_energy name: ESB Meter Hourly Electrical Energy cycle: hourly tariffs: - peak - offpeak daily_energy: source: sensor.shelly_em_esb_meter_channel_1_energy name: ESB Meter Daily Electrical Energy cycle: daily tariffs: - peak - offpeak
And then a pricing template in the same file:
template: - sensor: - name: "Hourly Cost Total Peak" unique_id: "template_sensor_4" device_class: monetary unit_of_measurement: "€" icon: mdi:currency-eur state: > {{ (states('sensor.hourly_energy_peak') | float * 0.3648 ) | round(2) }} - name: "Hourly Cost Total Off Peak" unique_id: "template_sensor_5" device_class: monetary unit_of_measurement: "€" icon: mdi:currency-eur state: > {{ (states('sensor.hourly_energy_offpeak') | float * 0.105) | round(2) }}
I got it working, thanks
Some of the cards on my energy dashboard.
Some other cards.
Tesla Dash
If I were you'd add templates with "readable names" and use them instead of the "3EM …." when it comes to the dashboard.
Really not too difficult - you basically just clone the values out to another metric and show that one instead.
e.g. add to your configuration.yamlfile
configuration.yaml
sensor: - platform: template sensors: # Can we obfuscate the shelly channels and use the values from a friendly name instead? mains_energy: friendly_name: "Mains Energy" device_class: energy unit_of_measurement: kWh value_template: >- {{ states('sensor.shellyem_channel_1_energy') | float(0) }}
This for me gives me a mains_energy entity with "Mains Energy" as the UI name - which ends up with exactly the same values as the sensor.shelly_em_channel_1_energy (in my case the CT1 clamp is on the Mains).
For me one of the main reasons to do this is that if I ever have to add another shelly to monitor or if I want to use the CT1 clamp to monitor something else - I just do the switch physically, and then update the template here and I haven't lost any of the historical data.
Oh I like the "when is the sun up" one, what's it called?
Horizon Card. It's in HACS.
https://github.com/rejuvenate/lovelace-horizon-card/
Swish! Adding that now :D
