Good afternoon,
I have had everything working fine for about 8 months, but since a few days the template sensors no longer seem to work, they indicate unknown in the developer tools.
When I fill in the template in the template tab, I just see a value.
Seems like template.yaml is no longer being read.
More people suffer from this.
Iâve got this issue toâŚ
If I restart home assistant when the sun is shining, the template sensor is read correctly. But when the dongle gives no output at night, the template sensor is shown as unavailable and does not show up the next day. Then a restart brings it back.
Is there any kind of configuration to restart the template integration ?
Friends, Iâm from Brazil.
I have a problem with the integration, I did all the steps listed, but only the data coming from the inverter appears, what was configured in the template does not appear in the HA, and when I try to apply sensors to the energy tab nothing appears, could you help me?
hi, what do you mean wrong sensor names? i copy paste the lines and got an error: Invalid config for âsensorâ at sensor_solar.yaml, line 1: required key âplatformâ not provided . pls help
Hey, you have no dot in your sensor.yaml? Just for question⌠The yaml starts with minus platform: rest
When you rename your sensor, instead of solplanet PV in my private pv you have to rename the sensors in the template.yaml to. Thatâs what it means
Hello Kevin, thanks for the quick reply.
Now in the dashboard the Solplanet PV status is âokâ but everything is unavalaible
Here is my code : template_solar.yaml
name: âSolplanet PV Produktionâ
unique_id: solplanet_current_production
state: â{{ state_attr(âsensor.solplanet_pv_produktionâ, âpacâ) | float }}â
unit_of_measurement: âWâ
device_class: energy
state_class: measurement
icon: mdi:transmission-tower-export
name: âSolplanet PV Tageswertâ
unique_id: solplanet_daily_production
state: â{{ state_attr(âsensor.solplanet_pv_tageswertâ, âetdâ) | float / 10 }}â
unit_of_measurement: âkWhâ
device_class: energy
state_class: total_increasing
name: âSolplanet PV gesamtâ
unique_id: solplanet_total_production
state: â{{ state_attr(âsensor.solplanet_pv_gesamtâ, âetoâ) | float / 10 }}â
unit_of_measurement: âkWhâ
device_class: energy
state_class: total_increasing
name: âSolplanet PV Temperaturâ
unique_id: solplanet_temperature
state: â{{ state_attr(âsensor.solplanet_pv_temperaturâ, âtmpâ) | float / 10 }}â
unit_of_measurement: â°Câ
device_class: temperature
state_class: measurement
template_solar.yaml :
Any idea what could be the problem? Thanks in advance
That what I mean in my post of names. You named it solplanet PV so your unique IDs have to be renamed to solplanet_pv_ptoduction ins the template.yaml
Then do a restart and everything should work
Thank you ! Works
Can you past you final code here? I get the following error:
Error loading /config/configuration.yaml: mapping values are not allowed here
in â/config/template_solar.yamlâ, line 32, column 13
Hi there
II am considering buying a Solplanet hybrid inverter with battery. but has anyone succeeded in being able to control when batteries charge/discharge in HA, as well as being able to set export to 0
my wish is to use HA to control the inverter in relation to sun hours and the electricity price. a bit like their own AI can
Have someone been able to set parameters in the inverter over the API?
I have an hybrid inverter with battery and was hoping to be able to define when the battery should be charged/discharged depending on eletrical prices etc.
looking in to this i found like for all devices 2 api replies, meter, battery inverter,
should these be added each time ?
if so what would be the best approach?
@derkorte if possible could we do a teams session to get me in the good direction?
totally new in the HA config
I will try to give you some instroduktion, but i havent any battery connected so i have no experience to integrate it in HA
Use file editor in your root folder usually named config folder, cause its the folder where your configuration.yaml is stored.
Add These lines to your configuration.yaml and save it:
sensor: !include sensor.yaml
template: !include template.yaml
Create a new file in your config folder (If its already there edit it) named:
sensor.yaml
and add following:
click save!
back to config folder.
create new file named:
template.yaml
add following:
sensor:
name: âXXXXX_current_productionâ
unique_id: XXXXX_current_production
state: â{{ state_attr(âXXXXXâ, âpacâ) | float }}â
unit_of_measurement: âWâ
device_class: energy
state_class: measurement
name: âXXXXX_daily_productionâ
unique_id: XXXXX_daily_production
state: â{{ state_attr(âXXXXXâ, âetdâ) | float / 10 }}â
unit_of_measurement: âkWhâ
device_class: energy
state_class: total_increasing
name: âXXXXX_total_productionâ
unique_id: XXXXX_total_production
state: â{{ state_attr(âXXXXXâ, âetoâ) | float / 10 }}â
unit_of_measurement: âkWhâ
device_class: energy
state_class: total_increasing
name: âXXXXX_temperatureâ
unique_id: XXXXX_temperature
state: â{{ state_attr(âXXXXXâ, âtmpâ) | float / 10 }}â
unit_of_measurement: â°Câ
device_class: temperature
state_class: measurement
Replace the XXXXX with your name choosed in the sensor.yaml (important!)
then do a restart and you should have new entitys with your choosed name.
My non hybrid Solplanet inverter had Modbus, and I found it way easier and more reliable to use that instead of using the API which could also change. This works great and should be applicable to more inverters that support this.
Itâs not even that complicated because of the great ESPHome community and its support for Home Assistant.
Iâve also wrote down how I did this in a blog post
Step-by-Step Guide to Linking Your (SolPlanet) Solar Inverter to Home Assistant Using ModBus Serial any feedback is welcome of course.
Do I have to get 5v to the esp or does it get the power from the inverter?
Yes you will indeed need to get 5v for it, i would recommend a simple power supply.
I got it from the Solplanet usb stick, which gave me 7V -9V so you will need to step this down. But be careful this may actually damage the inverter
So im fine with this solution, but in my mind itâs not easier for beginners. You have to be fit in soldering and yaml codes. Also you need some stuff like an esp. I will give it a try because I have all the stuff at home. Thanks for the tip.
True, you donât really need to solder, I just chose to. I would recommend to use a simple 5V power supply for the esp. But I totally agree that if someone created a plug and play integration that would be easier for most people, although it might come with some others drawbacks.
I just checked the voltage of the Solplanet stick and itâs pretty inconsistent now at 7V so Iâm not sure I would recommend executing my earlier reply, Iâm going to change that message. (And add a step-down to my current setup 
)
Today Iâve tried a few things but I think there an issue with my translation of gpios for the esp32. Donât you tried to use the original Wi-Fi dongle? Thereâs an esp32 build in. If we solder in the rs485 module, itâs the all in one solution.
Info: For all ones who have added the solplanet inverter to wifi or ethern, i recommend to stay with that.
IF YOU HAVENT ANY DONGLE, then the modbus solution may is something for you. Ive tried out everything, but i see no advantage to the Wifi integration.
May you have some advantage if you have any battery connected⌠but i havent.
heres the modbus file iâve got from solplanet support, got it about 10 mins after my request, gratz for thatâŚ:
