Nyro
@iMicknl @tetienne I updated the whole code in order to detect which command/states are available. After reviewing the 3 differents devices setup I got, it should work, at least on...
@jncanches and @MassimoL06 it could be great if you could test it, this PR should fix your overkiz integration with your respective water heater.
@iMicknl Thanks for your great and deep work on this. I tested running local dev docker container in Visual code. Here is what I did. 1. Checkout on current dev...
> Thanks for your extensive test, @nyroDev! > > > To summarize, in my test case, the local API won't be usable at all beacuse of the "already configured issue"....
> What do you mean by using the cloud API by default? People can choose now? The Config Flow description is clear on what is supported and what's not. Would...
Hi @domenic, do you need more work on this PR in order to merge it?
Hi @domenic, Is there anything elese I can do in order to merge this PR?
@iMicknl Once this PR is merged and published, I'll be able to add new PR on HA. Everything is [ready here](https://github.com/home-assistant/core/compare/dev...nyroDev:home-assistant-core:overkiz/pyoverkiz_update_device_info), I'll just have to update the version number
> I don't see the pro of such property. It will be confusing too have a device url and a base url. From the name, the diff is not obvious....
> I don't see the pro of such property. It will be confusing too have a device url and a base url. From the name, the diff is not obvious....