This is one of the best add-on…
It’s working really fast, when I click it change from OFF to ON it takes about 30 seconds. So if somebody has long time to affect the change maybe you have problem with your HA network speed etc…
I have 3 Wi-Fi adapters and all is working fine…
Does anybody know if this add-on will be sometime officially supported? From my side it should be - it is working withouth any error…
A question for the developer [o0Zz]
I use this great custom_component and was wondering why this isn’t available from Homeassistants site: https://www.home-assistant.io/components/
It works flawlessly, and it should be easy available to everyone.
Are there some rules as to why this is ?
Does anybody has set up automation for HA and MelCloud?
I have problem that on my automation I got error:
2018-12-13 08:40:19 WARNING (MainThread) [homeassistant.core] Unable to find service custom_components/melcloud_kuhinja_111111
But if I set something via GUI everything represent / works fine. So all commands are received and applied, but via automation I got error…
My configuration:
customize.yaml:
climate.melcloud_kuhinja_111111: friendly_name: Mitsubishi (Kuhinja) icon: mdi:fan
automation.yaml:
- id: '1500' alias: KUHINJA - prižgi KLIMA (05:21) trigger: platform: time at: '05:21:00' condition: condition: and conditions: - condition: time weekday: - mon - tue - wed - thu - fri - condition: numeric_state entity_id: sensor.kuhinjat below: '24' - condition: numeric_state entity_id: sensor.dnevnat below: '22' action: - service: climate.melcloud_kuhinja_111111 data: temperature: 28 fan_mode: Speed 5 (Max) operation_mode: Heat swing_mode: Swing
Is this way correct? Why I get error that custom_component is not found? But everything else regarding controling melcloud is working with no problem…
I must say that I have 3 MelCloud units… every with the other name offcourse…
Some stuf from logs:
This is normal data when all is OK…
2018-12-13 08:39:54 INFO (MainThread) [custom_components.climate.melcloud] Device info lease timeout, refreshing…
2018-12-13 08:40:02 INFO (MainThread) [custom_components.climate.melcloud] Device info lease timeout, refreshing…
2018-12-13 08:40:11 INFO (MainThread) [custom_components.climate.melcloud] Device info lease timeout, refreshing…
This is the info when I change setting via MelCloud, I change “Kuhinja” device, but there is no data which is “Kuhinja”…
2018-12-13 08:34:17 INFO (SyncWorker_11) [custom_components.climate.melcloud] Device configuration successfully applied
There is only data that it’s applied successfully…
I would also like to participate if somehow I can help regarding making this add-on officially supported…
Perhaps it has not been submitted via a pull request?
Maybe it does not comply with HA’s coding rules?
The developer submitted a pull request but the component did not get approved. The developer said he did not have time to fix the missing requirements.
Here is correct solution for automation:
# Prižgi KLIMA - KUHINJA: PON,TOR,SRE,ČET,PET; -20; 05:21 - id: '1500' alias: KUHINJA - prižgi KLIMA (05:21) trigger: platform: time at: '05:21:00' condition: condition: and conditions: - condition: time weekday: - mon - tue - wed - thu - fri - condition: numeric_state entity_id: sensor.kuhinjat below: '24' - condition: numeric_state entity_id: sensor.dnevnat below: '22' action: - service: climate.set_temperature entity_id: climate.melcloud_kuhinja_111111 data: temperature: 28 - service: climate.set_fan_mode entity_id: climate.melcloud_kuhinja_111111 data: fan_mode: 'Speed 5 (Max)' - service: climate.set_operation_mode entity_id: climate.melcloud_kuhinja_111111 data: operation_mode: Heat - service: climate.set_swing_mode entity_id: climate.melcloud_kuhinja_111111 data: swing_mode: Swing # Ugasni KLIMA - KUHINJA: PON,TOR,SRE,ČET,PET; 06:26 - id: '1501' alias: KUHINJA - ugasni KLIMA (06:26) trigger: platform: time at: '06:26:00' condition: - condition: time weekday: - mon - tue - wed - thu - fri action: - service: climate.set_operation_mode entity_id: climate.melcloud_kuhinja_111111 data: operation_mode: Off
I hope that this help to somebody who want set automation…
You can find all available parameters here (marked with red color):
So maybe we must found somebody who is willing to fix missing / broken stuff…
Is there such a problem using it as a custom component?
For the future use, yes…
If somehow came some “breaking” change this could stopped working…
Also currently it’s not user friendly for set up (copying files) etc… My personal experience was that one time HA web interface completly stopped working becase I copy the component files + set other climate stuff - HA hang out - only samba and ssh worked - so that I could solve problem - but not everybody is so skillful in this matters…
My latest configuration (automation) for MelCloud (Mitsubishi) with enabled notify push message.
First is for enable climate, and second is to turn off climate.
# Prižgi KLIMA - KABINET: Če je temperaturni senzor več kot 25 stopinj
- id: '1502'
alias: KABINET - prižgi KLIMA (več kot 25)
trigger:
platform: numeric_state
entity_id: sensor.kabinet_t
above: '25'
for:
hours: 0
minutes: 15
seconds: 0
condition:
- condition: numeric_state
entity_id: sensor.zunaj_t
above: '4'
action:
- service: climate.set_temperature
entity_id: climate.melcloud_kabinet_XXXXXX
data:
temperature: '19'
- service: climate.set_fan_mode
entity_id: climate.melcloud_kabinet_XXXXXX
data:
fan_mode: 'Speed Auto'
- service: climate.set_operation_mode
entity_id: climate.melcloud_kabinet_XXXXXX
data:
operation_mode: 'Cool'
- service: climate.set_swing_mode
entity_id: climate.melcloud_kabinet_XXXXXX
data:
swing_mode: 'Swing'
- service: notify.simon
data:
message: "KABINET - vklop klime (hlajenje)."
title: "KLIMA VKLOP"
# Ugasni KLIMA - KABINET: Če je temperaturni senzor manj kot 20 stopinj
- id: '1503'
alias: KABINET - ugasni KLIMA (manj kot 20)
trigger:
platform: numeric_state
entity_id: sensor.kabinet_t
below: '20'
for:
hours: 0
minutes: 30
seconds: 0
condition:
- condition: state
entity_id: climate.melcloud_kabinet_XXXXXX
state: 'Cool'
action:
- service: climate.set_temperature
entity_id: climate.melcloud_kabinet_XXXXXX
data:
temperature: '19'
- service: climate.set_fan_mode
entity_id: climate.melcloud_kabinet_XXXXXX
data:
fan_mode: 'Speed Auto'
- service: climate.set_operation_mode
entity_id: climate.melcloud_kabinet_XXXXXX
data:
operation_mode: 'Off'
- service: climate.set_swing_mode
entity_id: climate.melcloud_kabinet_XXXXXX
data:
swing_mode: 'Swing'
- service: notify.simon
data:
message: "KABINET - izklop klime (hlajenje)."
title: "KLIMA IZKLOP"I think they just shutdown the whole melcloud api system. Can anyone else confirm that their is still working?
No, it still works.
I have no problem.
Working with no problem… daily use in automation…
Edit: ok is working for 0.88. For custom componets change folder and file from.
custom_components/climate/melcloud.py
to
custom_components/melcloud/climate.py
Thanks a million, this could have costed me hours.
Just a quick solution if anybody runs into the same issue as I did (see above #71). Melcloud component was working fine until I added a (Melcloud compatible) Ecodan unit, a hot water / heater unit. It works great in the Melcloud app but it renders the HA component useless because it can only recognize A/C devices. Once you register the Ecodan into your account, the HA component returns an error and stops running. I’m guessing it would be simple (and very useful) to add this device to the code, but my programming knowledge is very limited. Until someone can lend a hand with this, there’s a simple solution: create a new Melcloud account and invite yourself as guest from the original account to control all your devices except for the water/heater unit. Then log into that account from the HA component.
If someone want to take a look at what info the Ecodan returns through the API, PM me.
Not working again after upgrade to 0.89. trying to find out why.
Thanks for the headsup, then I’ll wait with my upgrade.