X3 can not set use mode after update

[mickemartinsson]

After the update - when changing use mode it changes back after 2-4s. Tried also change via Node-Red - same, the use mode cannot be changed any longer from HA. It used to be very stable - have used Node-Red all winter to buy at the 7 cheapest hours, with a check for lower/higher prices after midnight. It has worked perfectly until the recent update. Now it can not be changed manual (from dropdown) or from Node-Red. Tried to remove the integration and reinstalled it (after updating of the repository) - the same thing.

[wills106]

Have you also lost the ability to change the numbers as well? Such as number.solax_battery_discharge_max_current

Have you recently restarted your Inverter or been disconnected from the Cloud for a while?

If so have you tried pressing the button.solax_unlock_inverter

Other than the unit address yesterday there hasn't been any changes to select.py in quite a while.

[infradom]

I hope the unit address change yesterday did not cause the problem. I did change the select code slightly for this, my system still works correctly ..

[mickemartinsson]

No restart or lost cloud. Tried to press button.solax_unlock_inverter before reinstall and after - no difference.

Can not change times (start/stop) either - the same problem there - they return to the previous value after 2-4s.

[wills106]

I am a bit lost with this fault. I am on 0.4.13 on my X1 Gen3 and I have full control.

Another X3 Gen3 issue #44 but then we have a new X3 Gen3 user that installed yesterday and no reported issues? https://community.home-assistant.io/t/solax-inverter-by-modbus-no-pocket-wifi-now-a-custom-component/140143/433?u=wills106

[stringkillersa]

I noticed the same behavior yesterday. I reverted to 0.4.10, but no change. Found the cause to be runmode=idle. Works again with 0.4.13 when it woke up. (Snowy weather yesterday and very little production, seems it went to idle early...)

[infradom]

Glad to hear that the 0.4.13 change did non cause the problem. This idle mode is indeed . hope we find a solution ...

[mickemartinsson]

Did a test with a change of a value (charger min A) in the cloud app. After that change - everything works again. Looks like an idle problem. Can't seem to wake it from HA, need to be in the cloud app to make it work again.

[ezfrag2021]

I think I am experiencing this problem too but on a new installation of the integration. I have tried deleting the integration from HA and reinstalling but the problem persists.

I have a Solax X3 Hybrid connected to my network via the LAN port on the inverter. The integration connects fine and I can read all sensor value fine but whenever I try to change a setting e.g. SolaX Charger Use Mode from Force Time Use to Self Use Mode I can see the change happen and then instantly change back in the HA Logbook. I have blocked the pocket wifi from accessing the network in case it was this over writing the command but the problem persists.

Do I need to do anything else to enable write commands from HA across the LAN port of the inverter? I found the inverter unlock button and pressed it but nothing happened and I still cannot send commands that stick. I love the integration, by the way, it is far superior to the way of pulling data from the cloud but it would be really nice to be able to push some commands to the inverter. Any help gratefully received!

Edit: suddenly started working. No idea why but I left it for a couple of days and this morning when I pressed the unlock advanced button it changed to a different value and the write functions started to work.

So not sure what happened but it was definitely something to do with the inverter being locked and previous attempts to unlock had failed.

[wills106]

If this happens again it might be worth fully powering down your Inverter and power it back on.

I am guessing the Inverter got itself into some form of a pickle?

[markjsmith]

Hi Will, I’ve noticed something similar to this too, when I try to change the mode manually with the select option I get the following error:

Failed to call service. Select/ select option must contain 1 of identity_id, device_id or area_id.

I've not used selectors before, so I might not have set something properly, but I was thinking it had worked at one point so wondered if it is the same issue?

[wills106]

@markjsmith

Has your Inverter been connected to the cloud previously?

If it hasn’t been connected to the cloud previously or the Inverter has had a full power cycle since it might be in “Locked” mode. Try pressing the “Unlock Inverter” button. It’s full name will be something like button.solax_unlock_inverter depending on how you named it while setting up.

Also if you enable the disabled sensor sensor.solax_lock_state you can check the lock status.

[wills106]

Is anyone still having any of these issues? Or can I close this issue down?

[ezfrag2021]

Sorry I thought I had already given an update in this thread. I left everything for a few days and went on holiday and when I returned it was suddenly working.

I suspect the problem was this the inverter as you suggested and maybe it needed to cycle modes to start working properly again. All ok now. Thanks.

[M0LTE]

@wills106 My X1 hybrid gets stuck in Idle mode and Battery Awaken, Unlock Inverter and Unlock Inverter - Advanced do nothing. The SolaX Cloud app permits me to get the inverter to Run Mode, and then changing inverter settings in HASS seems to work. The next day the HASS integration has no issue changing settings. Would this be the same issue or would you like me to raise a different one?

NB my issues are not new. Interestingly I sometimes see "Setting Success" in the SolaX Cloud app but then if I refresh the page in the app the field will still be set to the old value.

[markjsmith]

That’s the same. It happened last for me after a power cut.

Mark

-- Sent from Canary (https://canarymail.io)

On Sunday, Aug 14, 2022 at 11:16 pm, Tom M0LTE @.*** @.***)> wrote:

@wills106 (https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fwills106&data=05%7C01%7C%7C866efb25d3ff4db96d7b08da7e42a41d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637961121941486499%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=87cOWgplvrh5LXejwHWNEX9X01D29k%2F14sjHsVsRYac%3D&reserved=0) My X1 hybrid gets stuck in Idle mode and Battery Awaken, Unlock Inverter and Unlock Inverter - Advanced do nothing. The SolaX Cloud app permits me to get the inverter to Run Mode, and then changing inverter settings in HASS works. Would this be the same issue or would you like me to raise a different one?

— Reply to this email directly, view it on GitHub (https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fwills106%2Fhomeassistant-solax-modbus%2Fissues%2F48%23issuecomment-1214458892&data=05%7C01%7C%7C866efb25d3ff4db96d7b08da7e42a41d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637961121941486499%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jJSZcSiNCf2N4%2BW9UGv0Ss86a7z8ubvof0bkxv8mVig%3D&reserved=0), or unsubscribe (https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJQNIHBPZOBH3RSFY4SYPOLVZFV35ANCNFSM5SPTJZEQ&data=05%7C01%7C%7C866efb25d3ff4db96d7b08da7e42a41d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637961121941486499%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=FqJyYDk3EmpBgwzRr39x8SpyaH0dA9xjXZz45Raa04s%3D&reserved=0). You are receiving this because you were mentioned.Message ID: @.***>

[wills106]

It's a known issue and I'm not sure what the Cloud does different to wake the Inverter up. It's also very hard for me to trouble shoot as I have enough battery to last over 24hr If I do have two bad solar days I have a 3hr period during the night with cheap electric to charge from the grid.

Are you both trying to change Run Mode so you can charge from the Grid? or are you trying to do something else?

[M0LTE]

That's exactly what I'm trying to do. My cheap energy starts at 00:30 local time and just before then I'd like to make a dynamic decision on what, if any, grid charge to take depending on the morning and full day solar forecast and anticipated local energy needs. I have 18kWh of storage and we utilise around 40kWh per day. On a good day we generate 95% of that from solar, on a bad day we generate 10% of that from solar. My cheap energy is more than 4x cheaper than my peak energy which is why this matters.

Is there anything I can do eg obtain logs to assist?

[wills106]

I'm not sure what Inverter you are using but you mentioned 6S58 here #95 but that isn't a know start of a serial.

If you own aGen2 or Gen3 I would use "Force Time" mode see wiki

Log's wont help in this situation as I am not sure what command to send to actually wake the Inverter up.

[M0LTE]

H4502TH8... (truncating since I don't know if that's sensitive) if that's helps.

[wills106]

You have a Gen4 then (Only needs first 4 digits), so you will need to look at the Gen4 Modes of Operation on the Wiki

[M0LTE]

I'll look to see if that would work or help here. Thanks.

Do you think there is any mileage in having the integration write a setting, then read it back from the inverter, and error (somewhere) or maybe retry if it doesn't stick?

[M0LTE]

@wills106 would you say there is any mileage in pulling the Pocket WiFi dongle out? Would you expect things to work (other than the app) if I did this? I wonder if it is interacting badly with the modbus connection in some way.

[wills106]

I'll look to see if that would work or help here.

If you set the charge times before the Inverter goes to sleep it knows to wake up and start charging at say 00:30

is any mileage in pulling the Pocket WiFi dongle out?

I don't know, I don't have a PocketWiFI or a PocketLan. I connect to the cloud using the built in ethernet. All you can do is try?

[M0LTE]

Right- reason for delaying it is to use the latest possible solar forecast for the next day.

Are you aware of any way to prevent the inverter going to Idle mode? It doesn't provide any benefit...

[wills106]

If you are set to start charging at 00:30 but you don't need to charge have an automation at 00:31 to put the Inverter back into Self Use mode. Or modify the charge window.

I am assuming once the Inverter has woken up to start charging, it will be awake enough to receive normal commands. Once it's wake at 00:30 and you put it back into Self Use mode at 00:31, I don't know how much longer it will stay awake for though.

I don't know if there is anything useful to you in #41

[M0LTE]

Some good ideas, thanks, I'll try some stuff out.

[markjsmith]

Hi Will,

Yes the inverter is cloud enabled and unlocked. Interestingly I can change the state by using an automation which is the main thing, but the selector doesn’t work.

Mark

-- Sent from Canary (https://canarymail.io)

On Monday, Jun 27, 2022 at 5:20 pm, wills106 @.*** @.***)> wrote:

@markjsmith (https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmarkjsmith&data=05%7C01%7C%7C2def59981bb9440ad36d08da5858e3c2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637919436037719084%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=s4S6KoIz4Z%2BI8g83RSM9UvhytaHyeBR%2BCV46Uw16J4U%3D&reserved=0)

Has your Inverter been connected to the cloud previously?

If it hasn’t been connected to the cloud previously or the Inverter has had a full power cycle since it might be in “Locked” mode. Try pressing the “Unlock Inverter” button. It’s full name will be something like button.solax_unlock_inverter depending on how you named it while setting up.

Also if you enable the disabled sensor sensor.solax_lock_state you can check the lock status.

— Reply to this email directly, view it on GitHub (https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fwills106%2Fhomeassistant-solax-modbus%2Fissues%2F48%23issuecomment-1167533857&data=05%7C01%7C%7C2def59981bb9440ad36d08da5858e3c2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637919436037719084%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=tu1DyghWq8Lc%2BqvrMfEYGt4CR1hZeg%2FzXaaZAhkkG3M%3D&reserved=0), or unsubscribe (https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJQNIHBQIVX6BJ3AVXGOWQDVRHIDDANCNFSM5SPTJZEQ&data=05%7C01%7C%7C2def59981bb9440ad36d08da5858e3c2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637919436037719084%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=s5n4xNnSkcpqadUXIlBdGXsCDXGI%2BD7OlJSP6gqGmNk%3D&reserved=0). You are receiving this because you were mentioned.Message ID: @.***>

[emanuelsilvapt]

Hi Any idea why the setting "number.solax_battery_charge_max_current" is taking so long to change the value? This is important because I've automations to set a lower value when I use "Force Time Use" when off-peak starts and change it back to 20A after peak starts. When I change the slide it goes back to 20A; sometimes it changes to the desired value but after 5min or more... Unlocked - Advanced X3 Hybrid with Batteries

Any advice? Thank you very much

[wills106]

Is anyone still having issues changing modes? Especially when the Inverter is a sleep.

There is a comment here on waiting a short while after pressing battery_awaken https://github.com/wills106/homeassistant-solax-modbus/discussions/202#discussioncomment-4223942

I'll give it a couple of days and then close the issue down if no further feedback.

[ezfrag2021]

I didn't realise there was a possible solution. I had never noticed the battery awaken button before. I will try it out the next time the inverter goes to idle.

I am still using the workaround of only changing the use mode a couple of minutes after the inverter wakes up to charge the battery in the night. This was a pain last week when we had a storm blow in and I couldn't set it to back-up mode because it was asleep. Had to create an automation to do it in the middle of the night.