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.
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.