Hi @Francesco78, not really sure… but i will add range check for this entity for you. 
Hi @nebbiadigiorno, there is a way for sure. But even so some profiles already does contains some configurable entities for (dis)charge control writing through them is not yet possible because they need to be all written in bulk. You need to use built-in services for writing registers. Some users were already able to solve it so look into GitHub Discussions (optionally Issues) you will find your answers there.
Hi @flyingd73, of course it’s possible! All the necessary configuration entities are already implemented.
Few examples:
Hi David, this integration is working excellently, thank you (once I upgraded the firmware of my ME3000SP). I have a question about Configuration Entities. I’m unclear when it sends the updated configuration to the Inverter. So for example I have multiple Time of Use Rules/Programs and the integration correctly reads the parameters, but to configure a new rule/program, I need to change multiple entities and then send them as one Rule/Program. Also if I want to read the values for entities on Program 1, how do I update using the UI ? Does that make sense, any advice ?
Ah, I think I’ve figured it out. As documented in the MODBUS spec for ME3000SP, I need to change WorkMode from Auto to TOU and this commits the Configuration Changes. I just need to learn a little more about how to sequence my HA Automation actions to set the Program Configuration parameters and then send the Working Mode Change.
1 Like
H @Twin_Decks, you can read more about it here but in short you have to use ACTIONS and write multiple registers in bulk.
1 Like
Hi David, So it was the serial number field in the configuration dialogue. I had it first set to the inverter SN → did work, than after some configuration / installs of the HA system I restarted and the solarman integration was broken → some error msg hinting at a wrong SN applied, then changed it to the Logger SN an it works since then.
1 Like
Hi @lucullus, strange, but since one of the latest versions the serial number is no longer in the configuration anyway.
I’ve been using this integration for a few months now. It’s been 100% reliable.
Today I tried to change grid charge on one of the Time of Use slots and I get an error message:
“Failed to perform the action select/select_option. unsupported operand type(s) for & : ‘list’ and ‘int’”
Version: 25.05.12
Hi @haysdb, thank you for your report, this has already been fixed and is included in the new version.
EDIT: Solved through delete and add device → It is just important to user the exact identical inverter name of course
Getting the following error after upgrade: ValueError: Unique id ‘01jrxng0pqjhysnvbjpbkskpw9_today_battery_life_cycles_sensor’ is already in use by ‘sensor.deye_sun12k_today_battery_life_cycles_2’
→ how do I clear / reset the sensors (and make sure that they use the default naming then, in order to to have to change all my dashboards).
Should I just delete the current device and add it as a new one? @davidrapan
1 Like
Thank you for fixing that so quick.
1 Like
Goodmornig,
after update on reboot i have error:
Registratore: homeassistant.components.sensor
Fonte: helpers/entity_platform.py:824
Integrazione: Sensore (documentazione, problemi)
Prima occorrenza: 16:14:22 (1 occorrenza)
Ultimo accesso: 16:14:22
Platform solarman does not generate unique IDs. ID 01jqw3rxwtpeh6jw9xzccbz8tv_generator_generation_sensor already exists - ignoring sensor.inverter_generator_generation
might be to do with the change in v25.05.20 if you you updated the component to or beyond that version recently as some sensor names changed in that release…
There has never been a sensor with that name (ID). I wonder what happened.
Hi, coming from StephanJoubert integration, first of all i really like to thank you for your work.I have a deye 5k inverter, the logger is a LSW3_15_FFFF_1.0.9E model. On the other integration i got both AC/DC temperature sensor readings. On yours I find only DC readings. The value of ac temps are still readable through solarman website so the stick is able to collect them. Is there a way to add that sensor? Have i messed something with the configuration?
Hi @drdokro, the sensor you are looking for is just called Temperature.
Hello @davidrapan
Thx for your integration, it works flowless for my micro-inverter SUN-M80G4-EU-Q0 firmware MW3_16U_5406_1.62
I wanted to ask you for this particular model, is the communication a pure modbus TCP or based on the “pysolarmanv5” protcol ?
I tried to send direct modbus tcp command but no reply …
Hey, I do get some strange Grid readings → form time to time excessive grid import of 100kW and higher readings from my DeyeSUN-12K -SG04LP3-EU → has anybody an idea where this is stemming from? (the blue spikes in the attached screenshot) Currently I am bypassing the problem by fixing the y-axes in the the plotly graph, however it would be lovely if I could identify the root cause and correct the readings 
Hello, I need help integrating my Solarman smart meter with Home Assistant, but I’m having trouble doing it.
Thank you for your future responses.