Dunno man. My integration is registering the entities etc the similar way as the Daikin integration. Maybe that deserves some sort of attribution or not. Otherwise itās not related to o0Zzās Melcloud integration. I didnāt like it and wrote my own. Usually writing something gets you the copyright. Is there something Iām missing here?
Sorryā¦ if you wrote code completly from the strach then OK. But if you use some code from other source then you should mention this in licenseā¦ But itās your callā¦
Ao how is your integration different then Daikin or o0Zz integration?
Iām not sure if following best practices using a reference implementation warrants attribution or not. Iām trying to get this thing into a shape that could be PRd to HA so itās not a high prio thing to sort out from that perspective either.
I used Daikin as a reference on how to do multiple platforms for domain and register things in async way. So itās just similar async_setup, async_setup_entry, async_unload_entry and config_flow approach. Just the parts that do setup against HA. The Daikin integration interacts with Daikin products so thereās nothing else of interest for doing integration with Melcloud.
The integration in my repo tries to be more closely compliant with HA integration guidelines. Config flow, asyncio, external pypi package for melcloud client, unloading, etc. It has also multiple platforms. I didnāt see it productive to try to PR these changes to something existing.
Read the code and see. And please donāt accuse people of copyright breach without evidence. And you donāt have evidence because a brief perusal of the github repos will reveal that there is no similarity between oozzās code and @vilppuvuorinenās.
Iām not accusing anybody nothingā¦ I just mention it that if code came from other source that they should be mentioned, nothing else.
I fully support what he is doing, and Iām thankful that he try to sort out PR etcā¦ So if I somehow offend him than I trully apology - because this was never my intend to doā¦
device_info has the model names from units where the data has been fed in.
Energy sensor. The counter does not necessarily start from zero for some reason and the updates are really sparse. This should be compatible with the utility meter integration.
It looks like my setup has gone silently to read-only mode. I can observe writes going through to MELCloud but they are reset on the next poll. Only writes originating from MELCloud survive the next poll. Is anyone else experiencing this behavior?
In other news, Iāve got the integration otherwise almost PR ready with config flow tests. Iāll try submitting it once I have figured this read-only thing out. Iāll have to verify the the headers and all.
Next Iām thinking of trying to implement vane positions without using swing mode matrix like o0Zz does.
Hello. Thank you for your effort to have this made official. Currently Iām using o0Zzās implementation and it doesnāt go to read only mode.
When this goes PR will it be complicated to replace the community plugin with the official? Iām quite new to HA.
@vilppuvuorinen I tried to install your melcloud integration, but get the following error at startup. Using 0.103.6 of Home Assistant.
Error while setting up platform melcloud
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 148, in _async_setup_platform
task = async_create_setup_task()
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 104, in async_create_setup_task
platform.setup_platform,
AttributeError: module 'custom_components.melcloud.climate' has no attribute 'setup_platform'
Have you configured melcloud in your configuration YAML as climate platform? I have tested this only with config_flow through UI. That has been working like a charm.
Please, try removing platfrom from your config and add the integration via UI. Youāll get a devices, unloading and all that. Your password wonāt be stored in the config entry.
You probably canāt even control it then. I havenāt implemented anything besides the HVAC/heat pump stuff. I could try adding that in based on oOZzās integration later on.