Replies: 6 comments 1 reply
-
Hi @koehntopp, you are asking for something that is not supported by the device. The api library translates this code into a meaningful description and also introduces extra descriptions for the same code when various conditions are met. For example, the solarbank does not distinguish between charge bypass or charge priority, both have the same status code. Only user changable entity types can be used to reflect user input back to a device and modify something in the device. The integration will use the Api to reflect setting changes back to the solarbank, but the api (and device) must also support this setting change. And for known settings that are really user changeable via Api, there will be a changeable entitiy implemented in the integration once the setting is undestood and supported by the underlying Api library. So actually it is not clear what you want to achieve. The solarbank status is managed only by the device firmware and users can only indirectly influence it via modifications of the usage mode or output presets in the App. Those settings are also supported via Api and the integration. |
Beta Was this translation helpful? Give feedback.
-
I knew I was on the wrong path ;) What I want to do is switch between "only charge" ("Benutzerdefinierter Modus", set to "never discharge") and "discharge according to the data of the smart meter" ("Eigenverbrauch"). Is that possible...? I read the INFO.md a lot of times, there's a screenshot with a "Usage mode" dropdown, but I couldn't figure out the entities to use. Any help appreciated. |
Beta Was this translation helpful? Give feedback.
-
If you want to switch only between the 2 modes, that should be supported by the usage mode entity. This however becomes only available when you use the owner account in the integration. You would have to open a feature request and to use the export system service to provide a snapshot of your Api responses to verify the api responses with shelly device. Then eventually support for shelly can be added when the required info is available in the known request responses. |
Beta Was this translation helpful? Give feedback.
-
(my bad - got it) |
Beta Was this translation helpful? Give feedback.
-
api_devices.json has the Shelly. What exactly do you need, and where do I send it? |
Beta Was this translation helpful? Give feedback.
-
The Shelly as well as User mode switch for Smart meter and Smart Plugs is fully supported with 2.2.0 when logged in as system owner account. |
Beta Was this translation helpful? Give feedback.
-
I need to ask a stupid question - I read about all the fancy schedules, but as I have a Shelly 3EM installed, I really only need to switch between charge_priority and detection modes.
I tried in the developer tools, but the mode did not change (Yes, I used the correct user).
Is that even the right place to do that? How would I switch modes in an automation?
Would be awesome if someone could point me to what I might be doing wrong...
Beta Was this translation helpful? Give feedback.
All reactions