Replies: 13 comments 11 replies
-
|
I'm not sure I follow exactly how you are setting the work mode - in your automation, can you click the 3 dots to the right of the action and select 'Edit in Yaml' then paste the yaml code below. For example this is the way I would normally set the work mode using Select, Select, Choose Entity as 'Work Mode' and enter the text in the option 'Feed-in First' (note the 'option' text must be precise) For Feed-in I use this or for Self Use I use this |
Beta Was this translation helpful? Give feedback.
-
|
For Feed In First, the GUI creates this yaml: |
Beta Was this translation helpful? Give feedback.
-
|
Looks like this in the gui editor:
|
Beta Was this translation helpful? Give feedback.
-
|
If you go to Settings, Devices & Services, find the Foxess Modbus integration and click on ‘1 DEVICE’ it will list all the entities along with Controls - if you use the work mode selector there to change to Feed-in First does that work ?, if it does can you check that changing to Self Use also works. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, that works. |
Beta Was this translation helpful? Give feedback.
-
|
Ok try changing your automation to use the select method which is what that drop down box is using - disable your current action, and add another - for the action type ‘Select’ and choose the option ‘Select: Select’ in the list, click ‘Choose Entity’ , type ‘work’ and choose ‘Work Mode’ then in the ‘Option’ box type Feed-in First - make sure you observe the case. You can test the action by selecting the 3 dots on the right and select ‘Run’ - it should change to Feed-in First Assuming that works, repeat for your action that chooses Self Use and test that. |
Beta Was this translation helpful? Give feedback.
-
|
That works. Produces this YAML (as I'm sure you know!): |
Beta Was this translation helpful? Give feedback.
-
|
Ok great, that should keep you going doing it this way 👍 I have a nagging suspicion that this may be using a mis-matched look-up when using the Change Work Mode option - I think the KH uses a different numbering for it’s work modes @canton7 can you confirm?, i’ve always used the ‘Select’ method myself but I thought it worked ok using Change Work Mode option?. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, Fozzie, for your help and clear instructions! Indeed that solves my problem but let me know if there's anything I can do to help get info so the GUI can work for KH inverter users. I feel like maybe it did work previously or maybe only for the Self Use work mode setting. |
Beta Was this translation helpful? Give feedback.
-
|
Can you enable debug logging (Settings - Devices & Services - FoxESS - Modbus - Enable debug logging), try to set it the way you were, then grab the logs? |
Beta Was this translation helpful? Give feedback.
-
|
Hello... Ok, I had it set to change to Feed in First at 22:30 but I see nothing in the log from that time. Here it is though! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. When you set it using an automation, does it change in the Entities list? |
Beta Was this translation helpful? Give feedback.
-
|
The line "Writing registers for tcp://192.168.1.18:502 247: (41000, [1])" shows that it is changing the work mode there |
Beta Was this translation helpful? Give feedback.
-
|
Hey Canton ... I'm not sure I'm a reliable witness right now. I'll test again tomorrow. Maybe it actually is working. What should I be looking for in the logs to see if mode change is working or not? Is it possible the act of deleting the action and re-creating it made it start working again? |
Beta Was this translation helpful? Give feedback.
-
|
OK! I have to apologise for the noise here, now I see it clearly. Both methods successfully change the work mode so there is no problem there. I was trying to have a 5:30am change to feed-in-first so I made an automation to do that. I thought it was not working because the mode was not actually changed even though the automation fired. But what I forgot was that it was going to be immediately changed back to Self Use because my winter time automation switches between self use and force charge depending on if I'm getting an Octopus bonus low rate period (see below, where I should have checked first!) Sorry! I think my only valid issue on this one is that the 'master' version showing in the integration is wrong (shows 1.29 but actually is 1.35). Should I open a new discussion or bug report for that?
|
Beta Was this translation helpful? Give feedback.
-
Mind just sharing a screenshot from the foxess app / foxcloud, showing your different versions? |
Beta Was this translation helpful? Give feedback.
-
|
Fair request!
|
Beta Was this translation helpful? Give feedback.
-
|
Ack for goodness sake, FoxESS keep coming up with new and imaginative ways to encode their version numbers. In this case, I've no idea how they got from 0x129 to "1.35". |
Beta Was this translation helpful? Give feedback.
-
@lamixer No worries, I thought with the firmware change and the addition of 'Peak Shaving' work mode they had changed the work mode to work more like the H3 Pro... - have you tried the Peak Shaving mode?, I know quite a few users wanting this but as usual Fox havent updated any of the manuals to reflect this - they still say the KH has Backup mode 🙄 @canton7 On the upside Fox have just now released a KH update which tales Manager to 1.30, and Master to 1.37 - it might help with the encoding. @williamjeccles Can you let us know what the integration reports your KH Manager / Master version as please |
Beta Was this translation helpful? Give feedback.
-
|
@canton7 I updated to the latest HA version, and look now!
|
Beta Was this translation helpful? Give feedback.
-
|
Ah, are you sure it wasn't just a case of restarting the integration? We only poll the versions when we first connect to an inverter. |
Beta Was this translation helpful? Give feedback.
-
|
No, it probably was restarting the integration. It seems that people who care about knowing when the inverter has changed versions would want to know that with some frequency. Why not do a 4am daily update of the inverter fw versions? |
Beta Was this translation helpful? Give feedback.
-
|
We do re-read it if we disconnect from the inverter, and the assumption was that a firmware update would take long enough that we'd disconnect. Maybe however that's not the case... |
Beta Was this translation helpful? Give feedback.
-
|
It certainly did go offline for a bit while it updated but I'm not sure for how long. |
Beta Was this translation helpful? Give feedback.
-
Hello!
I recently updated my KH10.5 firmware to Master 1.35, Slave 1.01, Manager 1.28 (note also that HA integration shows Master is 1.29, but the others are correct) and this has made me want to use HA to change work modes which I previously didn't use much, but it did work for me.
I have automations set up which are triggering correctly but do not change the work mode if setting to a named work mode.
For example, if I set the action to be "Change Work Mode Option" and choose "Feed In First" from the list, it does not work - does not change to that mode. It does however seem to work if I use "Change Work Mode to First Option" it will change it to "Self Use". For a moment I though Change Work Mode Next was working but this morning it didn't.
On the inverter itself the listed work modes are (1) Self Use, (2) Feed In First, and (3) Peak Shaving.
If this is not a known issue, perhaps please remind me how to test it better / more directly (using the service instead of triggering through an automation?) and how to capture any output you might need to diagnose it.
I'm currently running HA:
Core 2024.7.4
Supervisor 2024.08.0
Operating System 12.4
Frontend 20240710.0
FoxESS - Modbus v1.12.1
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions