grzegorz914 / homebridge-melcloud-control Goto Github PK

Nevermind, I figured it out :-)

Hi!

I succefully added my Ducted AC and I can perfectly control it on the Homebridge's accessories page.

The problem I have is when in the Home App, I can add the Air conditioner as an accessory (sometimes I see the correct info like room temperature or if it's on or off for just a few seconds) and shorty after this, It isn't responding on the Home App. If I remove it from there, to add it again, I have to go to ./homebridge/persist. and remove the files to add it again (If I don't remove the files It's impossible to add it again on the app).

How can I fix it? I don't know what else to do. Do I have to config anything on my router to make it work? Please I need your help.

Thank you so much for this fantastic plugin.

Kind regards

Hi

I'm getting this error when trying to set the temperature (latest plugin installed):
I have tried to uninstall plugin and reinstall after a reboot.

[3/22/2023, 4:29:20 PM] [homebridge-melcloud-control] Air Conditioner Køkken, Set heating threshold temperature error: TypeError: Cannot create property 'HasPendingCommand' on string '/Device/SetAta'

I’ve added my AC unit and it works well, I can control the fan speed under accessory settings homekit, but there is no operation mode “Fan”, only auto, heat and cool.

Any idea why?

Thank you very much

Issue with v0.8.1:

13/03/2023, 15:36:01] [homebridge-melcloud-control] Heat Pump Zuhause, check info, ReferenceError: deviceListHistory24Formatters is not defined, check again in 60s.

Hi all,

I try to add support for Heat Pump and Energy Recovery Ventilation, but I don't have this devices to test, can some one with this devices instal 0.3.0-beta, enable debug mode and get me the log? or just send me the files from /homebridge/melcloud/ folder?

I enabled the mqtt function. When i publish { "Power": true } i can see the that the status on the broker change to { "Power": true }. But a moment later the status go back to { "Power": false }. So i can't switch the device. What can i do? Thank you

When I try to set a threshold ie. from 20c to 22c with Mitsubishi Heater Cooler (model LN-25) it briefly stick in Home app and then slides back to the last setting you touched. In the same time apparently it does stick in Homebridge logs:
Set cooling threshold temperature: 22°C
Set heating threshold temperature: 21°C

Can I do something so it would stick also in the home app?

Firstly, many thanks for the great plugin. I was so annoyed by the need to use MelCloud app.

I believe I am facing a bug with Lock physical controls setting. Here is what's happening:

• If I use separately exposed buttons for Power Lock, Mode Lock or Temp Lock it works as expected. Settings are synchronised with MelCloud and unit successfully. And Remote control follows the settings.
• However if I use HomeKit native Locked/Unlocked toggle (without exposing buttons from the plugin) OR use the button to Lock ALL controls, then at first glance it works well. Unit stops responding on Remote Control (as expected), settings are set to disabled in the MelCloud respectively. But I can't enable it back using HomeKit (regardless of what button I try). From the HomeKit view and from MelCloud view controls seem to be enabled, but remote still can't be used.
  I already started to panic, but luckily disabling and re-enabling controls via MelCloud app fixed it.
  I am able to reproduce this with different remotes and indoor units.

I am not sure whether / how this could be troubleshoot though as MelCloud settings seem to work according to command from the plugin.

Is it something you could investigate?

In the HOOBS logs I am not able to find the homekit setup code. Is there a default one?

• When I install and run the plugin (without creating any button), things work fine and my AC is identified via MelCloud
• Once I create the first button, homebridge will crash with the following error code in the protocol:

[14.7.2022, 10:40:54] [melcloudcontrol] Outdoor: Undefined
[14.7.2022, 10:40:54] [melcloudcontrol] Manufacturer: Mitsubishi
[14.7.2022, 10:40:54] [melcloudcontrol] ----------------------------------
[14.7.2022, 10:40:54] ReferenceError: Cannot access 'buttonState' before initialization
at MELCLOUDCLIENTDEVICE. (/var/lib/homebridge/node_modules/homebridge-melcloud-control/index.js:324:31)
at MELCLOUDCLIENTDEVICE.emit (node:events:527:28)
at MELCLOUDCLIENTDEVICE. (/var/lib/homebridge/node_modules/homebridge-melcloud-control/src/melcloudclientdevice.js:201:22)
at MELCLOUDCLIENTDEVICE.emit (node:events:527:28)
at MELCLOUDCLIENTDEVICE. (/var/lib/homebridge/node_modules/homebridge-melcloud-control/src/melcloudclientdevice.js:150:22)
at MELCLOUDCLIENTDEVICE.emit (node:events:527:28)
at MELCLOUDCLIENTDEVICE. (/var/lib/homebridge/node_modules/homebridge-melcloud-control/src/melcloudclientdevice.js:48:26)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
[14.7.2022, 10:40:54] Got SIGTERM, shutting down Homebridge...
[14.7.2022, 10:40:59] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[14.7.2022, 10:41:04] [HB Supervisor] Restarting Homebridge…

Hi,
I’m not familiar with programming Homebridge, it's new for me.
Here at home we got 5 Heater/Cooler-units connected to MELCloud and would like to use them though HomeKit with Homebridge.
I already followed the steps as given here: https://github.com/grzegorz914/homebridge-melcloud-control but don't know how ti configure the JSON-file in there.

I installed the MELCloud Control Plugin as written:

These are the Heater/Cooler-units that are showing up in the "accessories" tab in homebridge:

This is the code that already exists in the "configure" tab in homebridge (also see for the screenshot if not clear):
{ "bridge": { "name": "Homebridge FA32", "username": "deleted here for privacy reasons", "port": 51305, "pin": "deleted here for privacy reasons", "advertiser": "bonjour-hap" }, "accessories": [], "platforms": [ { "name": "HomeBridge", "port": 8581, "auth": "form", "theme": "auto", "tempUnits": "c", "lang": "nl", "platform": "config" }, { "accounts": [ { "name": "Ruben Melcloud", "user": "deleted here for privacy reasons", "passwd": "deleted here for privacy reasons", "language": "12", "ataDisplayMode": 0, "ataPresets": false, "atwDisplayMode": 0, "atwPresets": false, "ervDisplayMode": 0, "ervPresets": false, "disableLogInfo": false, "disableLogDeviceInfo": false, "enableDebugMode": false, "enableMqtt": false, "mqttAuth": false, "mqttDebug": false } ], "_bridge": { "username": "deleted here for privacy reasons", "port": deleted here for privacy reasons }, "platform": "melcloudcontrol" } ] }

This is the code that already exists in the "MELCloud Control" in the "plugin" tab in homebridge (also see for the screenshots if not clear):
{ "accounts": [ { "name": "Ruben Melcloud", "user": "deleted here for privacy reasons", "passwd": "deleted here for privacy reasons", "language": "12", "ataDisplayMode": 0, "ataPresets": false, "atwDisplayMode": 0, "atwPresets": false, "ervDisplayMode": 0, "ervPresets": false, "disableLogInfo": false, "disableLogDeviceInfo": false, "enableDebugMode": false, "enableMqtt": false, "mqttAuth": false, "mqttDebug": false } ], "_bridge": { "username": "deleted here for privacy reasons", "port": 37449 }, "platform": "melcloudcontrol" }

Where do I put what code so the accessories show up in HomeKit-app?

Thanks in advance!
Ruben

My Mitsubishi air conditioning does not have the swing function, so in that case, and for the HeaterCooler accessory, that property should not be added to the device.

"Device"."SwingFunction": false,

Hello i have 4 air conditioning and the plugin work very well.
There is an air conditioner that I can no longer control with the remote. i tried to enable and disable child mode but it still works only through homekit.

Extra buttons don't work in the last version. I have two air conditionners (linked to Melcloud), and even if the AC work well in homekit, extra buttons don't appears.

First of all, thank you very much for this plugin, it's great to be able to control the air with the Home app. I have several air conditioners working, but one of them I can't add to Home app, it doesn't show up when I click on "I Don't Have a Code or Cannot Scan or More Options." I managed to get it to show up once at first, and it was working for a while but I had to delete the Homebridge and create another one and it seems that Home app thinks it already has it registered although it does NOT appear in the list of connected devices. This unit apears in melcloud plugin and can control it from there, BUT does not show up in Home app. Is it possible to trick Home app by changing the air conditioner identifier? How can I change the serial number or the Homebridge Instance Username of this particular device? Which one should I change? Thanks!

With Version 7 and 8 I have this error

[13/03/2023, 15:05:49] [homebridge-melcloud-control] Heat Pump Zuhause, check info, ReferenceError: devicePresets is not defined, check again in 60s.

Hi

I'm trying to use MQTT with authorization log in, but connection is refused.

Could you please add the field "Client ID" to the MQTT authorization, please.

I'm using Mosquitto as my MQTT broker and it needs the "Client ID" to be abled to log in.

(great plugin - great work - happy with this)

i there, in my hoobs, the accessories appears with an chip image whitout actions.

Hi,
I configured the plugin but I get this error when restarting homebridge
[9/8/2022, 5:31:43 PM] [melcloudcontrol] Heat Pump Ecodan , debug Info: [object Object]
[9/8/2022, 5:31:43 PM] [melcloudcontrol] Heat Pump Ecodan , check info, ReferenceError: ddeviceInfo is not defined, check again in 60s.
[9/8/2022, 5:31:43 PM] TypeError: this.log is not a function
at process.error (/usr/lib/node_modules/homebridge/src/logger.ts:139:10)
at process.emit (node:events:513:28)
at process.emit (/usr/lib/node_modules/homebridge/node_modules/source-map-support/source-map-support.js:516:21)
at emit (node:internal/process/promises:140:20)
at processPromiseRejections (node:internal/process/promises:274:27)
at processTicksAndRejections (node:internal/process/task_queues:97:32)
/usr/lib/node_modules/homebridge/lib/logger.js:90
this.log("error" /* ERROR */, message, ...parameters);
^

TypeError: this.log is not a function
at process.error (/usr/lib/node_modules/homebridge/src/logger.ts:139:10)
at process.emit (node:events:525:35)
at process.emit (/usr/lib/node_modules/homebridge/node_modules/source-map-support/source-map-support.js:516:21)
at process._fatalException (node:internal/process/execution:167:25)

debug log attached

thanks in advance for your help
Paolo

log.zip

Hi, how can i get the choices: Heat, Cool and Fan (add Fann and Remove auto)

        "accounts": [
            {
                "name": "MyFan",
                "language": "12",
                "displayMode": 0,
                "enableDevicePresets": false,
                "disableLogInfo": false,
                "disableLogDeviceInfo": false,
                "enableDebugMode": false,
                "enableMqtt": false,
                "mqttAuth": false,
                "mqttDebug": false
            }

Hi there...

thanks for this amazing project! One thing I was wondering is if it would be possible to "expose" the different Fan speed selection the same way as you expose the different modes for a AC. Basically not have 5 different buttons but just one "selection wheel". Is this possible ?

Using HeaterCooler mode, and with my device with the following features:

• "NumberOfFanSpeeds": 3,
• "HasAutomaticFanSpeed": true,

When I try to set the HK slider to the maximum (AUTO), in the log it says "Air Conditioner Aire Set fan speed mode: 4". Which is invalid, since AUTO = 0 for my AC.

homebridge.log (1).txt

Is this a critical error?

Today, suddenly the MELcloud plugin stopped working. When checking my Homebridge logs, I see this message:

[5/10/2023, 7:28:15 PM] [homebridge-melcloud-control] Account MyAccount, login error, Error: unable to verify the first certificate, reconnect in 65s.

The service works through MELcloud app, any idea why suddenly started to fail? I've been using it for months.

Thanks, BR
Abel

Hi

For unexpected reason the device that works previously on HOOBS stop working.

I just follow normal and basic test.

Restart the bridge
Unistall plugin
Install Again

Nothing this make it works again. On logs i can see that plugin can retrieve the information successfully from MeCloud account

6/19/2023, 4:55:00 melcloudcontrol---- Air Conditioner: Clima Casa ----
6/19/2023, 4:55:00 melcloudcontrolAccount: Casa
6/19/2023, 4:55:00 melcloudcontrolSerial: 2101069086
6/19/2023, 4:55:00 melcloudcontrolFirmware: 19000
6/19/2023, 4:55:00 melcloudcontrolManufacturer: Mitsubishi
6/19/2023, 4:55:00 melcloudcontrol----------------------------------

If i enable the debug also i can see more parameters from the MeCloud

With this situation my the device is not added automatically on the default room via the HOOBS bridge and there is no reason to understand why stop working after more than 1 year and a half :(

Appreciated your answer and thanks for the fantastic work on this addom

I get this in the Homebridge Log:

[homebridge-melcloud-control] This plugin generated a warning from the characteristic 'Target Heater-Cooler State': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.

Is this normal?

Hello, for a few days one of the 4 air conditioners has not been reachable in homebridge. Instead from melcloud it is reachable.

Not sure if the plugin is finished or work in progress, but I just wanted to highlight that after configuring it and restarting homebridge the accessory is no being recognised properly in home app.

When I switch the child bridge mode ON in my homebridge instance, the accessory is not being registered as part of the bridge. I think it remains as an external accessory instead of contained within the process. It would be great to make it compatible with this feature as I have several accessories and this improves performance.

Hi. It would be nice to have the serial number and model. If you can in a future version enable the serial number and model. Thank you very much.

See video attached. Right room temperature is 23.5, but when I change the slider, it changes to 26.5

When I enable MQTT option I get the message error :

MQTT Publish error: TypeError [ERR_INVALID_ARG_TYPE]: The "string" argument must be of type string or an instance of Buffer or ArrayBuffer. Received an instance of Object

I try to change MQTT prefix but what I have done I got same error message.

I use a 2.10 mosquitto server with zigbee2mqtt and Homebridge Zigbee2MQTT plugin.

Hello everyone,

I recently started using homebridge,
I bought a raspberry pi zero W, all to use my air conditioners through homekit, and not through the melcloud app.
installing the plugin it gives me a timeout error, I also noticed that if I try to update hombridge from version 1.5.1 to version 1.6.0 it also gives me a timeout error there, is there anyone who can give me some indications? Thanks so much

These are the params coming in the API:

"ModelSupportsFanSpeed": true,
"HasAutomaticFanSpeed": true,
"NumberOfFanSpeeds": 3,

and the current HK fan speed steps:

• 0: OFF
• 1: Min
• 2: Med
• 3: Max
• 4: — Does not exist in my AA model, should not be there
• 5: — Does not exist in my AA model, should not be there
• 6: Auto

In the log the plugin reports:

• Air Conditioner Aire Room temperature: 26.5°C

But when I see that info in HomeKit it says 27.0°C

Configuration:

            "accounts": [
                {
                    "name": "Aire",
                    "language": "0",
                    "ataDisplayMode": 0,
                    "ataPresets": false,
                    "atwDisplayMode": 0,
                    "atwPresets": false,
                    "ervDisplayMode": 0,
                    "ervPresets": false,
                    "disableLogInfo": false,
                    "disableLogDeviceInfo": false,
                    "enableDebugMode": false,
                    "enableMqtt": false,
                    "mqttDebug": false,
                    "mqttAuth": false
                }
            ]

If I enable MQTT I see in log output:
[homebridge-melcloud-control] MQTT Publish error: TypeError [ERR_INVALID_ARG_TYPE]: The "string" argument must be of type string or an instance of Buffer or ArrayBuffer. Received an instance of Object

My configuration is:

{
            "accounts": [
                {
                    "name": "Name",
                    "user": "[email protected]",
                    "passwd": "password",
                    "language": "4",
                    "displayMode": 0,
                    "disableLogInfo": false,
                    "disableLogDeviceInfo": false,
                    "enableDebugMode": false,
                    "enableMqtt": true,
                    "mqttHost": "192.168.6.19",
                    "mqttPort": 1883,
                    "mqttPrefix": "klima/dg",
                    "mqttAuth": false,
                    "mqttDebug": false
                }
            ],
            "_bridge": {
                "username": "0E:37:BC:83:7A:FA",
                "port": 36374
            },
            "platform": "melcloudcontrol"
}

few weeks after installing and setting up the plugin out of nowhere got the following error:
[homebridge-melcloud-control] Account Alessio, login error, TypeError: Cannot read properties of null (reading 'ContextKey'), reconnect in 65s.
and have no clue about it, tried reinserting the account info and reinstalling but nothing.

hi @grzegorz914, firstly many thanks for your contribution. I have started this week working with homebridge and your plugins are really useful.
I would like to ask you about adding the air conditioner to HomeKit, I can see the accessory in homebridge but not in HomeKit.
I attached config and debug details.
Thanks

Air conditioner debug.pdf
config.pdf

homebridge.log.txt

Version 11.8 was okay.

I am unable to add my two airconditions to HomeKit even they appear properly in Homebridge. I followed the description but the process is timing out in HomeKit with the message “Devise doesn’t respond”. I was running the plug-in from zephyus/ Homebridge-MElcloud2 and there is no need for this manual step in HomeKit to add the devices. As soon the Homebridge is connected to HomeKit my two units appear in HomeKit. Maybe you can contact him how he pulled this off in his plugin.

https://github.com/zephyrus/homebridge-melcloud2

Thanks for your effort

hi, thank you for your work .... when will you implement dehumidifier mode (drying mode)?

I always get this message:

03/04/2023, 12:01:08] [Homebridge UI] Running Command: npm install --save [email protected]
[03/04/2023, 12:02:48] UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "#".
[03/04/2023, 12:03:54] Got SIGTERM, shutting down Homebridge...

Almost always when I want to update the MELCloud plugin. Other plugins can be updated without problems.
Sometimes even without an update.

In homekit model and serial number are not from the unit, but from the wifi interface. AA info should be coming from property Devices.Device."Units": [
{
"SerialNumber": "8XHXXXXX,
"Model": "SEZ-XXXXXX",
"UnitType": 1,
"IsIndoor": true
}

Hi, I just installed this plugin, running as child bridge. The heat pump displays under accessories in the UI, but it just won't show up in the Apple Home app. Any ideas what could be causing this?

When I try to use the plugin, Homebridge enters a restart loop.

Installation details:

• Brand new Raspbian Bullseye installation on Raspberry Pi
• Brand new Homebridge installation
• homebridge-melcloud-control is the only installed plugin

This is the error I see in the logs:
[18/07/2022, 18:41:19] TypeError: Cannot read properties of null (reading 'toString') at melCloudDevice.prepareAccessory (/var/lib/homebridge/node_modules/homebridge-melcloud-control/index.js:461:42) at MELCLOUDCLIENTDEVICE.<anonymous> (/var/lib/homebridge/node_modules/homebridge-melcloud-control/index.js:426:11) at MELCLOUDCLIENTDEVICE.emit (node:events:527:28) at MELCLOUDCLIENTDEVICE.<anonymous> (/var/lib/homebridge/node_modules/homebridge-melcloud-control/src/melcloudclientdevice.js:201:22) at MELCLOUDCLIENTDEVICE.emit (node:events:527:28) at MELCLOUDCLIENTDEVICE.<anonymous> (/var/lib/homebridge/node_modules/homebridge-melcloud-control/src/melcloudclientdevice.js:150:22) at MELCLOUDCLIENTDEVICE.emit (node:events:527:28) at MELCLOUDCLIENTDEVICE.<anonymous> (/var/lib/homebridge/node_modules/homebridge-melcloud-control/src/melcloudclientdevice.js:48:26) at processTicksAndRejections (node:internal/process/task_queues:96:5)

And then:
[18/07/2022, 18:41:19] Got SIGTERM, shutting down Homebridge...

I've tried on another Raspberry Pi and even on a Mac but the behaviour is always the same.
The login to Melcloud is successful because I see the correct details about my devices in the logs.

Hi!
I'm using 2x Mitsubishi Diamond Airco units and 1 outdoor unit.

I noticed when using Siri the mode will sometimes automatically change to auto. How do you guys use this? Because auto mode doesn't seam to work. When changing the temperature in HomeKit it will automatically switch back. This is because melcloud doesn't allow a range (Like cool to '70' degrees and heat to '80' degrees) I think, right?

[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] Unknown Lossnay Schlafzimmer, Unknown system detected.
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] ---- Heat Pump: Ecodan ----
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] Account: [email protected]
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] Model: Undefined
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] Serial: 2225511192
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] Firmware: 37000
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] Hot Water Tank: Yes
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] Zone 2: No
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] Manufacturer: Mitsubishi
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] ----------------------------------
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] Unknown Lossnay Wohnzimmer , Unknown system detected.
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] ---- Air Conditioner: Schlafzimmer Klima ----
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] Account: [email protected]
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] Model: PEAD-SM71JA(L)
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] Serial: 2225512193
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] Firmware: 37000
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] Manufacturer: Mitsubishi
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] ----------------------------------
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] ---- Air Conditioner: Wohnzimmer klima ----
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] Account: [email protected]
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] Model: Undefined
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] Serial: 2225511191
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] Firmware: 37000
[3/23/2023, 10:09:23 PM] [homebridge-melcloud-control] Manufacturer: Mitsubishi

Dear grzegorz914,

thanks for developing this wonderful plugin. I am opening this issue because I obtain the following error when the plug-in try to setup the Air Conditioner model MSZ-SF42VE3.

Check device state error: TypeError: Cannot read properties of null (reading 'toString')

I attach the relevant snippet of the log with debug information. Let me know if you need additional details to address the issue.

melcloud_error.txt.txt

Thanks for your support and best regards,
Marco