black-thunder / iobroker.melcloud

Integrates Mitsubishi Electric devices via MELCloud into ioBroker

Icon made by Freepik from www.flaticon.com

ioBroker.melcloud

melcloud adapter for ioBroker

This adapter integrates Mitsubishi Electric devices via MELCloud (https://www.melcloud.com/) into ioBroker.

Documentation:

• English description
• Deutsche Beschreibung

Discussion:

• ioBroker Forum

Changelog

1.4.1 (2024-05-24)

• (Black-Thunder) Added new option to ignore SSL errors

1.4.0 (2024-02-29)

• (Black-Thunder) Added new option to completely disable polling

1.3.7 (2024-02-09)

• (Black-Thunder) Login procedure was refactored to reduce number of calls to the MELCloud servers
• (Black-Thunder) Minimum polling interval was raised to 5 minutes
• (Black-Thunder) Default polling interval was raised to 10 minutes

1.3.6 (2023-11-03)

• (Black-Thunder) Minimum Node.js Version was raised to 16
• (Black-Thunder) Dependencies were updated

1.3.5 (2023-08-01)

• (Black-Thunder) Memory leak was fixed

1.3.4 (2023-05-11)

• (Black-Thunder) Certificate issues were fixed (e.g. "Error: unable to verify the first certificate")

1.3.3 (2023-04-14)

• (Black-Thunder) Handling of error data from cloud was improved
• (Black-Thunder) Admin UI has been updated
• (Black-Thunder) ATW devices: New state "heatPumpFrequency" added
• (Black-Thunder) ATW devices: New state "operationState" added
• (Black-Thunder) ATW devices: Commands "operationModeZone1" and "operationModeZone2" fixed

1.3.1 (2023-03-24)

• (Black-Thunder) fixed "undefined is not a valid state value" log messages
• (Black-Thunder) fixed crash after connection is lost (e.g. due to missing internet connection)
• (Black-Thunder) updated admin UI and translations
• (Black-Thunder) fixed a lot of adapter checker issues and warnings

1.3.0 (2023-03-17)

• (Black-Thunder) added online status to each device (visible in admin object tree)
• (Black-Thunder) added error status to each device (visible in admin object tree)
• (Black-Thunder) added error code and messages to device info
• (Black-Thunder) added new command "timerToggle" to enable/disable device timers

1.2.1 (2022-12-06)

• (Black-Thunder) added consumption reports for air to water devices

1.2.0 (2022-09-20)

• (Black-Thunder) Added support for air to water devices (e.g., heat pumps)
• (Black-Thunder) Added new device-independent channel "reports" fur cumulative reports across all devices (see documentation for new structure)
• (Black-Thunder) Restructured device-specific channel "reports" and added new sub-channel "lastReportData" (see documentation for new structure)
• (Black-Thunder) Fix: always trigger on "getPowerConsumptionReport" ignoring the state value
• (Black-Thunder) Fixed js-controller warnings

1.1.6 (2022-02-06)

• (Black-Thunder) fixed warnings

1.1.5 (2022-02-06)

• (Black-Thunder) replaced deprecated package "request" with "axios"
• (Black-Thunder) fix warnings for js-controller v4
• (Black-Thunder) updated dependencies

1.1.4 (2021-05-16)

• (Black-Thunder) implemented separate queue for sending device commands to improve robustness when sending multiple commands
• (Black-Thunder) only update "control" state values with ack=true when it was requested by user before

1.1.3 (2021-05-12)

• (Black-Thunder) IMPORTANT: The adapter now requires js-controller 3.1 at least
• (Black-Thunder) ignore unchanged state values to decrease network traffic
• (Black-Thunder) only update state values if they are really changed
• (Black-Thunder) extend existing objects to ensure compatibility with js-controller >= v3.2
• (Black-Thunder) only allow values with 0.5 steps for "targetTemp"

1.1.2 (2021-04-30)

• (Black-Thunder) added compatibility with js-controller >= v3.2
• (Black-Thunder) updated dependencies

1.1.1 (2021-01-10)

Attention: With this version you must reenter your password in the adapter settings and save again! Otherwise, login will fail.

• (Black-Thunder) fix: correctly use auto decryption handling for password
• (Black-Thunder) polling interval in adapter settings is now limited to values greater than 0

1.1.0 (2021-01-08)

• (Black-Thunder) new functionality: retrieve power consumption reports
• (Black-Thunder) adapter connection state now correctly set accordingly to the cloud connection
• (Black-Thunder) added release-script and Dependabot, updated dependencies

1.0.6 28.06.2020

• (Black-Thunder) implemented queue mechanism for sending requests to cloud
• (Black-Thunder) disabled adapter autostart after installation

1.0.5 21.06.2020

• (Black-Thunder) added more checks when processing HTTP response
• (Black-Thunder) corrected typo in subscribeStates()
• (Black-Thunder) moved subscribeStates() after init and first successful connection

1.0.4 05.06.2020

• (Black-Thunder) added new value for 'vaneHorizontalDirection': 50/50 (1 vane left, 1 vane right - only for models with 2 independent horizontal vanes)

1.0.3 03.06.2020

• (Black-Thunder) renamed pre-defined values for 'vaneHorizontalDirection' and 'vaneVerticalDirection'
• (Black-Thunder) refactored polling logic: if connection is lost, a maximum of 3 retries are made; if still not successful, the next retry will be made after 1 hour

1.0.2 01.06.2020

• (Black-Thunder) correctly classify 'pollingInterval' as number
• (Black-Thunder) corrected max values for states 'vaneHorizontalDirection' and 'vaneVerticalDirection'
• (Black-Thunder) check 'vaneHorizontalDirection' and 'vaneVerticalDirection' for valid values

1.0.1 29.05.2020

• (Black-Thunder) fixed bug in device control when two or more devices are present

1.0.0 (first public stable release) 28.05.2020

• (Black-Thunder) re-added "melcloud.X.info" node as it breaks display of connection state otherwise
• (Black-Thunder) some refactoring

0.0.3-alpha4 27.05.2020

• (Black-Thunder) technical improvements for setting 'power'

0.0.3-alpha3 27.05.2020

• (Black-Thunder) parent for each device is now a channel
• (Black-Thunder) "melcloud.X.info" node removed, state "connection" now directly assigned to "melcloud.X"

0.0.3-alpha2 26.05.2020

• (Black-Thunder) optimized performance/reduced DB transactions
• (Black-Thunder) dynamically adjust min/max limits for 'targetTemp' and 'setFanSpeed'
• (Black-Thunder) added more documentation

0.0.3 26.05.2020

• (Black-Thunder) added indicator if device is reachable
• (Black-Thunder) corrected role of "targetTemp", "power" and "deviceName"
• (Black-Thunder) added new states "macAddress" and "actualFanSpeed" (indicates fan speed when running in auto mode)
• (Black-Thunder) added translations

0.0.2-alpha9 25.05.2020

• (Black-Thunder) fixed crash when devices are assigned to different floors/areas

0.0.2-alpha8 25.05.2020

• (Black-Thunder) fixed "Swing" of vanes

0.0.2-alpha7 25.05.2020

• (Black-Thunder) fix "power" state

0.0.2-alpha6 25.05.2020

• (Black-Thunder) create object folders as channels so that enums can be assigned
• (Black-Thunder) predefined states for fan speed, vane horizontal/vertical, "Swing" added
• (Black-Thunder) changing operation mode doesn't power on device anymore
• (Black-Thunder) min/max for setTemperature added

0.0.2-alpha5 25.05.2020

• (Black-Thunder) added more error logging

0.0.2-alpha4 25.05.2020

• (Black-Thunder) operation modes "Dry" and "Vent" added, removed confusing mode "Off" (device state is now only controlled by "power")
• (Black-Thunder) control of fan speed, horizontal and vertical vane direction added
• (Black-Thunder) reduced amount of logging entries

0.0.2-alpha3 24.05.2020

• (Black-Thunder) fixed 'request' dependency

0.0.2-alpha2 24.05.2020

• (Black-Thunder) fixed check of adapter settings
• (Black-Thunder) added more logging

0.0.2 24.05.2020

• (Black-Thunder) first implementation of device control (all states under "device.XXX.control")
• (Black-Thunder) added more device options
• (Black-Thunder) extended and optimized logging (e.g., when logging into MelCloud)
• (Black-Thunder) implemented polling of cloud data

0.0.1-alpha4 11.05.2020

• (Black-Thunder) fixed password encryption

0.0.1-alpha3 11.05.2020

• (Black-Thunder) refactored code
• (Black-Thunder) prepared device control

0.0.1-alpha2 11.05.2020

• (Black-Thunder) password stored encrypted
• (Black-Thunder) fixed username check
• (Black-Thunder) implemented adapter connection state based on cloud connection
• (Black-Thunder) handled connection failures to cloud better
• (Black-Thunder) optimized logging

0.0.1

• (Black-Thunder) initial release

License

MIT License

Copyright (c) 2024 Black-Thunder [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

iobroker.melcloud's Issues

Anzeigefehler der Adapter-Einstellung 'Language'

Ist

Wird die Sprache in den Instanzeinstellungen hinterlegt und gespeichert, so wird beim nächsten Aufruf der Einstellungen trotzdem immer der erste Eintrag in der Liste (EN) angezeigt. Gespeichert wurde aber der korrekte Wert, ist ein rein kosmetisches Problem. Wird das dropdown-Menü ausgeklappt, so ist dort auch der korrekte Wert selektiert.

Soll

Anzeige des gespeicherten Werts und nicht des ersten in der Liste.

Erkennung, wenn Geräte von extern (z.B. Fernbedienung) geschaltet wurden

Feature-Wunsch

"Was noch interessant wäre - sofern möglich - kann man irgendwie abgleichen ob die KA von der Fernbedienung manuell gestartet wurde oder über ein Script ? Wäre cool wenn die KA merken würde wenn sie über ihre FB eingeschaltet wurde und nicht mitbekäme wenn sie per Broker gestartet wurde bzw. Wenn es da einen Unterschied gäbe. Dann könnte man einem Script sagen das es nicht laufen soll wenn die KA mit Absicht gestartet wurde. Das würde verhindern das ein Script die Anlage abschaltet obwohl man die gerne am laufen hätte. Ich habe das jetzt über einen etwas unzuverlässigen Umweg realisiert …"

Evtl. Lösungsansatz

Überwachen des states 'power' auf Änderung, nachdem Daten mit MELCloud synchronisiert wurden --> 'power' wurde extern geändert. Timing-Probleme beachten!

Adapter rewrites "Changed From" data to value "melcloud.0"

Hi,
It's strange the adapters behavior. Adapter rewrites "Changed From" data to value "melcloud.0" at once. See Objects->States view. Example: You change the state "Power" from Admin console. You see "Changed from": "admin.0/admin". The adapter changes it to "melcloud.0" in ~1 sec. Looks like Its ack confirmation.
It's impossible to understand and make interpretation in scripts who makes the changes (User or Script or Adapter).

Thank you

Aktuellen Status auslesen

Hallo zusammen,
In der MelCloud App ist der jeweilige Status der einzelnen Kreisläufe ersichtlich.

So sehe ich zB Unzulässig/StandBy/Heitzbetrieb und ein entsprechendes Icon.

Wird dieser Status bereits abgefragt und ich sehe ihn nur nicht?

Falls er nicht abgefragt wird währe es super, wenn Ihr den mit einbaut.

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/Black-Thunder/ioBroker.melcloud

• [E605] No actual year found in copyright. Please add "Copyright (c) 2021 black-thunder [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2021 black-thunder [email protected]" at the start of LICENSE

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Compatibility check and testing for Node.js 14 and 16

Dear Adapter developer,

Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.

Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16

Please add both versions to the adapter testing which is executed on commits.

If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!

On questions please talk to us at ioBroker/ioBroker.js-controller#1138

Please close the issue after you checked it.

Thank you very much for your support!

Melcloud instance recovery after lost connection

Hi @Black-Thunder
It`s for notice.
Melcloud adapter could not reconnect to MELCloud service after internet channel interruption.
It needed a manual restart.
Find the log attached.

Melcloud: 1.1.4
Controller: 3.3.15
Admin: 5.1.25

Thank you
Best Regards,
Vadim
RecoveryConnectionIssue_log.txt

Memory Leak: RAM consumption increases over time

Describe the bug
I observed problems with RAM availability on my ioBroker VM instance and investigate the consumption of all adapters using Telegraf and Grafana.
One of the main problematic adapters is MelCloud:

Within 2 days, the consumption went up from 2% (of 5 GByte RAM) to 10%.
At the beginning of the graph, I rebootet my VM to have a clean start, therefore you see the drop.

In my setup, I poll the information for 2 A/C devices from the Melcloud.

To Reproduce
Steps to reproduce the behavior:
Start the adapter and wait. Observe the RAM consumption

Expected behavior
Stable memory consumption

Screenshots & Logfiles
see above

Versions:

• Adapter version: 1.34
• JS-Controller version: 4.0.24
• Node version: v18.17.0
• Operating system: Debian VM

Let me know if any further information is required. I'm willing to support the debugging if this helps

View in widget 8 freezes after changing mode in melcloud

Hi!

First of all -> thanks for that really good work!
I'm facing a problem with your melcloud adapter. When changing mode in melcloud adapter, my view in widget 8 freezes in my vis. It's not just if i push a button in my vis for changing the mode - also if i change the mode external with the melcloud app, the widget freezes and it's not just at one endpoint. All endpoint acting like this. Everythin i can do, if my widget 8 freezes -> refresh the whole vis.
I'm wondering that i'm the first one who facing that problem.

Please help with that problem.

Thank you so much

Adapter lässt sich nicht installieren

Ich versuche den Adapter in der Version 1.2.0 (von GitHub) im iOBroker zu installieren. Hatte vorher die Version 1.1.6 drauf. Diese habe ich gelöscht (auch den Ordner in den Objekten), da ich erst dachte, das es an der bestehenden Installation liegt.

Bei Befehl ausführen bleibt ewig der Status:
`$ iobroker url Black-Thunder/ioBroker.melcloud --host iobroker --debug

install Black-Thunder/ioBroker.melcloud

NPM version: 6.14.17

Installing Black-Thunder/ioBroker.melcloud... (System call)`

Wenn ich wieder versuche die 1.1.6 Version die direkt im iOBroker zur Verfügung steht zu installieren, dann geht das ohne Probleme.

Ich habe es sowohl über GitHub als auch direkt über die Adresse versucht. Immer das gleiche.
Was kann das Problem sein?

Abrufen der Verbrauchswerte aus den Berichten

Feature-Wunsch

Aus Forum
"Is it possible to get power consumption statistic from MELCloud from Reports?"

Evtl. Lösungsansatz

Mitschneiden des Netzwerk-Traffics, wenn in der App die Berichte abgerufen werden

Error 429 - We have detected excessive traffic from your account, your access to the service has been limited for a few hours.

Hello,

adapter worked till yesterday fine for me. Now I lost the connection over a day and then I'm blocked by the Melcloud because of too many tries to log in. With that the adapter doesn't work any more.

Any help ?

Bernhard

Befehl zum Starten der Warmwasseraufbereitung

Das wäre ein Super Feature, dass man leider derzeit nicht über die MelCloude machen kann.

Super wäre es, über einen Befehl die Anlage aufzufordern, jetzt die Warmwasseraufbereitung zu starten.
Somit könnte man eine Art SG Ready Funktion nachstellen.

ZB es ist genug Solarenergie verfügbar. Über SetTankWaterTemperatur könnte man diese auf ZB 55 einstellen und über den Befehl die Anlage dazu bringen, JETZT auf diese Temperatur aufzuheizen.

Danke euch

enable/disable timer

is it possible to add enable/disable timer in controls?

Cumulative reports

Thanks for the adapter.

It would be great if you could add a function to collect the power reports for all devices (and maybe all kind of modes) in one datapoint.

This would make it easier to cumulate the total consumption for an entire house instead of using scripts with multiple calls to get the reports.

v1.3.6 ständiger wechsel true/false

Hab ein Split Klimagerät von Mitsubishi.
Seit der letzten Verson habe ich das Problem das der IOB Datenpunkt "melcloud.0.devices.52888497.control.power" ab und zu zwischen
true und false im 30 Sekunden Rhythmus wechselt.
Hat das schonmal jemand beobachtet ?

Hier als Diagramm dargestellt, gelb ist dieser Datenpunkt als Ein/Aus dargestellt, grün die Leistung vom Gerät.

Error: unable to verify the first certificate

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '...'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.

Versions:

• Adapter version:
• JS-Controller version:
• Node version:
• Operating system:

Additional context
Add any other context about the problem here.

Der Adapter startet nicht mehr bleibt auf rot.
Habe ihn dann auf die neuste Version upgedatet, aber auch kein Erfolg.
Habe auch mal das Passwort gelöscht und neu eingegeben. Im Internet und über App kann ich mich noch in der Melcloud anmelden....
Lief über Monate ohne Problem.

Log:

melcloud.0	2023-05-10 18:12:38.787	error	Error: unable to verify the first certificate
melcloud.0	2023-05-10 18:12:38.787	error	There was a problem sending login to: https://app.melcloud.com/Mitsubishi.Wifi.Client/Login/ClientLogin
melcloud.0	2023-05-10 18:12:38.578	info	Connecting initially to MELCloud and retrieving data...
melcloud.0	2023-05-10 18:12:38.357	info	starting. Version 1.3.3 in /opt/iobroker/node_modules/iobroker.melcloud, node: v14.20.1, js-controller: 4.0.23
melcloud.0	2023-05-10 18:12:33.425	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
melcloud.0	2023-05-10 18:12:33.422	info	terminating
melcloud.0	2023-05-10 18:12:33.420	info	onUnload(): Cleaned everything up...
melcloud.0	2023-05-10 18:12:33.415	info	Got terminate signal TERMINATE_YOURSELF
melcloud.0	2023-05-10 18:12:14.548	error	Error: MELCloud password empty! Check settings.
melcloud.0	2023-05-10 18:12:14.438	info	starting. Version 1.3.3 in /opt/iobroker/node_modules/iobroker.melcloud, node: v14.20.1, js-controller: 4.0.23
melcloud.0	2023-05-10 18:12:09.523	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
melcloud.0	2023-05-10 18:12:09.520	info	terminating
melcloud.0	2023-05-10 18:12:09.519	info	onUnload(): Cleaned everything up...
melcloud.0	2023-05-10 18:12:09.516	info	Got terminate signal TERMINATE_YOURSELF

Update stable version in repo from 1.1.4 to 1.1.6

Think about update stable version to 1.1.6

Version: stable=1.1.4 (286 days old) => latest=1.1.6 (19 days old)
Installs: stable=278 (69.15%), latest=44 (10.95%), total=402
Click to edit

Temperatur Einstellung wird zurückgesetzt

Installiert ist die Github Version v1.2.0
Ich hab das Problem das die Zieltemperatur der Split-Klimaanlage (Datenpunkt targetTemp) nach einer Minute immer auf 19°C zurückgesetzt wird. Dabei ist es egal ob ich über die Infrarot Fernbedienung, über Node-Red oder über ioBroker "Objekte" selbst die Temperatur ändere. Auch ist es egal ob mit ack oder ohne.Erst hab ich gedacht das targetTemp durch roomTemp überschrieben wird aber das scheint nicht so zu sein. Es wird immer durch 19°C ersetzt.
Im debug Log sind keine Fehler.
Irgend eine Idee ?

Nachtrag: Der einzige Wert der die 19°C enthält ist der Punkt DefaultCoolingSetTemperature im Log.

Log warn nach versuchtem Update auf 1.1.5

Hallo
Ich habe soeben versucht auf 1.1.5 das Update zu machen;
Im Log sehe ich keine Meldung bezüglich dass das Update nicht durchgeführt worden ist - bei den Instanzen steht jedoch auch nach dem Update noch die 1.1.4 - und bei den Adapter-Updates erscheint es auch immer noch. (keine Ahnung ob das ein Bug im heute geupdateten Controler ist..)

Was aber im Log stand ist der Warn nach dem Update:
" warn | This object will not be created in future versions. Please report this to the developer. "
" warn | Object devices.14778845.reports.getPowerConsumptionReport is invalid: obj.common.min is only allowed on obj.common.type "number" or "mixed", received "boolean" "

Controler: 4.0.4
Node.js: v14.19.0

Gruss
Matt

Separate Left and Right VaneVerticalDirection?

I see that you've added a vaneHorizontalDirection value for separate control of the left and right vanes a few versions back, but I don't see a similar option for the vertical vanes (one up and one down). Do you know if this is something that is supported in MelCloud, and if so, exactly how it works? The use case is as follows:

I have a Kaiteki 6600 mounted in between two floors, in the stairway, and use the two separate vertical vanes to direct air both up and down. When the temperature on the main floor is above 21 degrees I would like the hot airstream to be split between the two floors (left vane up, right vane down), but when the temperature on the main floor drops below 21 degrees I would like the hot airstream to only be pushed into the main floor (both vanes up) to heat it up as quickly as possible.

Nur für Klimageräte oder auch für andere MelCloud Geräte

Hallo Zusammen,

ich habe eine Wärempumpe (Heizung) und kann auch über die MelCloud darauf zugreifen.
Nun Habe ich mal den Adapter installiert. Adapter ist grün und es werden mir auch viele Objekte angezeigt aber der größte Teil ist Null oder 0

Kann ich irgendetwas tun, unterstützen ?

Viele Grüße
Thomas

Object nextCommunication has "Invalid date" after updating javascript or admin adapter

Describe the bug
The Object "nextCommunication" has "Invalid date" after updating javascript or admin

To Reproduce
Steps to reproduce the behavior:

1. Open object "melcloud.0.devices.X.info.nextCommunication"
2. Check state

Expected behavior
date should be displayed correct like object "melcloud.0.devices.X.info.lastCommunication"

Screenshots & Logfiles

Versions:

• Adapter version: 1.1.4
• JS-Controller version: 3.3.12
• Node version: v12.19.0
• Operating system: raspbian

Additional context
Add any other context about the problem here.

Compatibility check to js-controller 4.0

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

If something is not correct this is logged as 'warning' or 'info' log.

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn or info log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1749

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

Update stable version in repo from 1.1.6 to 1.2.1

Think about update stable version to 1.2.1

Version: stable=1.1.6 (318 days old) => latest=1.2.1 (15 days old)
Installs: stable=462 (71.74%), latest=60 (9.32%), total=644
Click to edit

Update stable version in repo from 1.2.1 to 1.3.1

Think about update stable version to 1.3.1

Version: stable=1.2.1 (123 days old) => latest=1.3.1 (15 days old)
Installs: stable=435 (63.13%), latest=52 (7.55%), total=689
Click to edit

Compatibility check to js-controller 3.3 and Admin5 React UI

Dear Adapter developer,

with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.

If something is not correct this is logged as 'warning' or 'info' log.

Please take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1301

Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.

More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui

Please close the issue after you checked it.

Thank you very much for your support!

Update stable version in repo from 1.2.1 to 1.3.3

Think about update stable version to 1.3.3

Version: stable=1.2.1 (144 days old) => latest=1.3.3 (15 days old)
Installs: stable=451 (64.71%), latest=52 (7.46%), total=697
Click to edit

problem sending login to: https://app.melcloud.com/Mitsubishi.Wifi.Client/Login/ClientLogin

After installing the adapter ( v 1.3.4) and entering log-in data, the logfile shows:

AxiosError: Request failed with status code 500

There was a problem sending login to: https://app.melcloud.com/Mitsubishi.Wifi.Client/Login/ClientLogin

The device is registered with MELCloud and can be controlled via app and web.

deviceOnline false - Steuerung funktioniert aber

Hallo!

Bis vor einigen Tagen lief alles prima. Jetzt werden mir meine Geräte jedoch als offline (deviceOnline=false) angezeigt. LastCommunication ist jedoch aktuell und eine Steuerung klappt auch.
In der Melcloud-App scheint es jedoch eine Änderung gegeben zu haben: Dort wird in der Fußzeile nun nicht mehr der Zeitpunkt der letzten (oder kommenden) Kommunikation angezeigt.

Adapterversion ist 1.1.6

UPDATE: Sehe gerade, da kann der Adapter nichts für. Ihm wird vom Webservice in der Tat "Offline": "true" zurückgegeben ... scheint wohl ein Problem beim Anbieter zu sein.

Info. The WIFI module can't connect to the MelCloud server. (It's not the Adapter issue)

If anybody has a MelCloud communication problem:

1. That is not the adapter problem.

"It's a global issue. The WIFI module can't connect to the server. So it just fails.

The server returns 503 Service Unavailable: Back-end server is at capacity

So don't waste your time resetting the wifi and like that. Just waste of time.

I also got this response after contacting the technical support

As you may have noticed, we are currently facing a communication problem regarding our WiFi interfaces. I would like to assure you that our technical team is fully committed to resolving this issue.

We implement all necessary resources to ensure that these inconveniences are resolved as quickly as possible. Our goal is to ensure the reliability and performance of our services, and rest assured that we are working diligently to restore the situation to normal."

"Workaround:
If you manage your own DNS server, you can get online again, setting the host "production.receiver.melcloud.com" to resolve to the IPaddress: 52.215.226.151"

From:
www.reddit.com

Update stable version in repo from 1.0.6 to 1.1.1

Think about update stable version to 1.1.1

Version: stable=1.0.6 (211 days old) => latest=1.1.1 (15 days old)
Installs: stable=282 (89.24%), latest=27 (8.54%), total=316
Click to edit

Update stable version in repo from 1.1.4 to 1.1.6

Think about update stable version to 1.1.6

Version: stable=1.1.4 (282 days old) => latest=1.1.6 (15 days old)
Installs: stable=282 (70.15%), latest=40 (9.95%), total=402
Click to edit

Request failed with status code 429

Unfortunately I still have the problem that the connection to MelCloud cannot be established.
I paused the adapter for 3 days now and started it again this evening.
Unfortunately, the familiar error message came immediately
So the adapter couldn't connect to the cloud at all.
I can access the cloud without any problems via https://app.melcloud.com/

What could be the reason?

Allow same day reports

It seems that the vendor interface allows getting intra-day reports. Please consider allowing start- and endDate to be the same.