Git Product home page Git Product logo

iobroker.midea's Introduction

Logo

ioBroker.midea

NPM version Downloads Number of Installations (latest) Number of Installations (stable) Dependency Status Known Vulnerabilities

NPM

midea adapter for ioBroker that also Supports Carrier devices

Midea and Carrier Adapter

Changelog

0.0.6

  • (TA2k) initial release

License

MIT License

Copyright (c) 2020 TA2k [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.midea's People

Contributors

apollon77 avatar itprofi avatar jogibear9988 avatar stilicrafter avatar ta2k avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar

Forkers

jogibear9988 apollon77 mideared lighu36 enemy2003 itprofi vlgorskij stilicrafter iobroker-archive michipi85

iobroker.midea's Issues

Account not found

Describe the bug
Can't login with my account.

To Reproduce
Steps to reproduce the behavior:

  1. Login in with your Midea credentials

Expected behavior
Login successfully

Screenshots & Logfiles

Versions:

  • Adapter version: 0.0.7
  • JS-Controller version: 4.0.23
  • Node version: 16.17.1
  • Operating system: Raspberry OS

Additional context

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!

Fehlermeldung midea adapter mit comfee Luftentfeuchter

Describe the bug
Nachdem der Adapter neu gestartet wird kommt die folgenden Meldungen im Log

Expected behavior
Es werden auch keine Variablen angelegt

Screenshots & Logfiles

midea.0 2023-11-12 13:12:27.572 error SyntaxError: Unexpected token F in JSON at position 446 at JSON.parse () at Midea.getDeviceList (/opt/iobroker/node_modules/iobroker.midea/main.js:113:30) at processTicksAndRejections (node:internal/process/task_queues:96:5) at Midea.onReady (/opt/iobroker/node_modules/iobroker.midea/main.js:76:5)
midea.0 2023-11-12 13:12:27.570 error SyntaxError: Unexpected token F in JSON at position 446
midea.0 2023-11-12 13:12:27.555 info function () { [native code] }
midea.0 2023-11-12 13:12:27.553 info [{id=152832116466110, address=192.168.178.91, port=6444, version=3, name=152832116466110, online=True, type=0xa1, subtype=0, flags=0, extra=1, reserved=0, mac=a0681c2bd678, ssid=net_a1_D678, udp_version=4000000, protocol=069fcd, version=3.0.8, sn=000000P0000000Q1A0681C2BD6780000, state=[Dehumidifier]{id=15283211646****, type=0xa1, mode=0, running=False, target_humidity=50, fan_speed=40, tank_full=False current_humidity=45, current_temperature=0 defrosting=False, filter=False, tank_level=0, error_code=0, prompt=False, supports={}}}]
midea.0 2023-11-12 13:12:27.548 info Found 1 devices
midea.0 2023-11-12 13:12:18.333 info Getting devices
midea.0 2023-11-12 13:12:18.331 error *** PY *** Python Error Call to 'connect_to_cloud' failed: > const cloud = await this.midea_beautiful.connect_to_cloud$({ at Midea.login (/opt/iobroker/node_modules/iobroker.midea/main.js:87:21) at Midea.onReady (/opt/iobroker/node_modules/iobroker.midea/main.js:75:18) ... across the bridge ... > cloud.authenticate() at connect_to_cloud (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/init.py:87) > self._get_login_id() at authenticate (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:390) > response = self.api_request( at _get_login_id (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:360) > self.handle_api_error(int(payload[error_code_tag]), payload["msg"]) at api_request (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:302) > handler() at handle_api_error (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:645) > self.authenticate() at session_restart (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:615) > self._get_login_id() at authenticate (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:390) > response = self.api_request( at _get_login_id (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:360) > self.handle_api_error(int(payload[error_code_tag]), payload["msg"]) at api_request (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:302) > handler() at handle_api_error (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:645) > self.authenticate() at session_restart (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:615) > self._get_login_id() at authenticate (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:390) > response = self.api_request( at _get_login_id (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:360) > self.handle_api_error(int(payload[error_code_tag]), payload["msg"]) at api_request (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:302) > handler() at handle_api_error (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:645) > self._retry_check("session-restart", cause=f"{message} ({error})") at session_restart (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:613) > raise CloudRequestError( at _retry_check (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:350) *** JS *** midea_beautiful.exceptions.CloudRequestError: Too many retries while calling session-restart, last error value is illegal. (3004)
midea.0 2023-11-12 13:12:18.330 error Error
midea.0 2023-11-12 13:12:13.111 info starting. Version 0.1.0 (non-npm: TA2k/ioBroker.midea) in /opt/iobroker/node_modules/iobroker.midea, node: v16.20.2, js-controller: 5.0.12
midea.0 2023-11-12 13:12:07.430 info terminating
midea.0 2023-11-12 13:12:06.928 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
midea.0 2023-11-12 13:12:06.925 info terminating

Versions:
CPU: 31,27 %
RAM: 54,3 %
Betriebszeit: 1d21h
Verfügbar: 5.0.12
Installiert: 5.0.12
Ereignisse: ⇥27 / ↦14
Plattform: linux
Betriebssystem: linux
Architektur: arm
CPUs: 4
Geschwindigkeit: 1800 MHz
Modell: unknown
RAM: 3.7 GB
System-Betriebszeit: 1 T. 21:23:31
Node.js: v16.20.2
time: 1699791097719
timeOffset: -60
NPM: 8.19.4
Adapter-Anzahl: 508
Datenträgergröße: 28.9 GB
Freier Festplattenspeicher: 21.9 GB
Aktive Instanzen: 24
Pfad: /opt/iobroker/
Betriebszeit: 1 T. 21:27:57

Additional context
Add any other context about the problem here.

Hallo Leute

Was ist dann mit dem Adapter los da geht ja nichts, könnte sich das mal jemand anschauen ?

Entfeuchter lässt sich nicht mehr steuern, auslesen funktioniert noch

Hallo,

ich habe grade festgestellt das sich mein Luftentfeuchter nicht mehr über Iobroker ein und ausschalten lässt was tadellos Funktionierte.
Hier der Log als Bild, wenn noch was gebraucht wird einfach melden.
Log
log1

Was ich grade noch rausgefunden habe ausschalten lässt er sich noch aber nicht wieder ein

Grüsse

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!

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!

New Dimstal AC not compatible?

Hi,
I Tryed to connect but it seems that Dimstal has changed the WiFi dongle.

The new is not able to connect to any Midea App.
As i know it only works with the " AC Freedom" App.
The AC is this:
Dimstal SMND-QC-12-J-Smart-ECO

Here a pic of the new Dongle:

IMG_3022

i can not get any webinterface.
it seems that only port 80 is open.

has anyone a idea how i can get it in ioBroker at best via local lan.

kind regards
Andy

Midea Geschirrspüler

Hallo zusammen,
habe ein Midea Geschirrspüler SF3.6NW wi, habe den schon in der MSmartLife app angemeldet und läuft auch. Nun wollte ich mit dem Iobroker die Maschine Steuern und Auslesen (Status etc.). Habe den Adapter 0.0.6 Installiert und leider kommt gleich bei der Anmeldung das es den Account nicht gibt. Auf der APP läuft alles ist der Adapter der richtige?

Grüße

Chris

Python lib throws error 

2022-07-08 22:43:10.418  - info: midea.0 (181878) starting. Version 0.1.0 (non-npm: TA2k/ioBroker.midea#fd51f4b710e826e4c3025c70b7eab0d1f771f101) in /opt/iobroker/node_modules/iobroker.midea, node: v18.4.0, js-controller: 4.0.23
2022-07-08 22:43:28.182  - info: midea.0 (181878) Login successful
2022-07-08 22:43:28.187  - info: midea.0 (181878) Getting devices
2022-07-08 22:43:37.833  - info: midea.0 (181878) Found 1 devices
2022-07-08 22:43:40.892  - error: midea.0 (181878) Error
2022-07-08 22:43:40.893  - error: midea.0 (181878) *** PY ***  Python Error  Call to 'appliance_state' failed:
>                     appliance_state = await this.midea_beautiful.appliance_state$({ cloud: this.cloud, appliance_id: id, use_cloud: true });
  at Midea.updateDevices (/opt/iobroker/node_modules/iobroker.midea/main.js:144:39)
  at Midea.onReady (/opt/iobroker/node_modules/iobroker.midea/main.js:78:9)
... across the bridge ...
> appliance.identify(cloud, use_cloud)
  at appliance_state (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/lan.py:1025)
> self.refresh(cloud if use_cloud else None)
  at identify (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/lan.py:810)
> responses = self._status(cmd, cloud)
  at refresh (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/lan.py:381)
> responses = cloud.appliance_transparent_send(self.appliance_id, data)
  at _status (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/lan.py:538)
> response = self.api_request(
  at appliance_transparent_send (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:526)
> self.handle_api_error(int(payload[error_code_tag]), payload["msg"])
  at api_request (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:302)
> handler()
  at handle_api_error (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:645)
> raise CloudError(error, message)
  at cloud_error (/home/iobroker/.local/lib/python3.9/site-packages/midea_beautiful/cloud.py:630)
*** JS *** midea_beautiful.exceptions.CloudError: Midea cloud API error: None (1000)

Adapter funktioniert nicht mit Node 20?

Describe the bug
Seit heute morgen funktioniert der Adapter nicht mehr und schreibt mir das Log voll mit Fehler (siehe Screenshot).
Ich habe den Adapter schon komplett runter geschmissen, neu installiert und auch das Gerät selbst nochmal neu in der Midea App eingepflegt.
Bisher hat nichts geholfen. Würde mich über schnelle Hilfe freuen.

Screenshots & Logfiles
Screenshot 2023-06-18 085840

Versions:

  • Adapter version: 0.0.7
  • JS-Controller version: 4.0.24
  • Node version: v20.2.0
  • Operating system: Debian 12

能支持美的的CCM15路由模块吗

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.

problem in js-controller 3.3.x

iobroker-community-adapters/ioBroker.telegram#227
same problem for midea adapter

midea.0 | 2021-05-05 14:00:10.555 | info | (15936) State value to set for "midea.0.18691697706.status.tempUnit" has to be type "number" but received type "boolean"
midea.0 | 2021-05-05 14:00:10.543 | info | (15936) State value to set for "midea.0.18691697706.control.swingMode" has to be type "boolean" but received type "number"
midea.0 | 2021-05-05 14:00:10.541 | info | (15936) State value to set for "midea.0.18691697706.status.swingMode" has to be type "boolean" but received type "number"
midea.0 | 2021-05-05 14:00:10.540 | info | (15936) State value to set for "midea.0.18691697706.status.offTimer" has to be type "number" but received type "string"

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/TA2k/ioBroker.midea

  • [E154] common.dependencies must contain {"js-controller": ">=2.0.0"} or {"js-controller": ">=3.0.0"}
  • [E605] No actual year found in copyright. Please add "Copyright (c) 2022 TA2k [email protected]" at the end of README.md
  • [E701] No actual year found in LICENSE. Please add "Copyright (c) 2022 TA2k [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

To many Login attempts in last hour

Hi,
Wenn ich die Aktualisierung auf <30 Minuten stelle bekomme ich "to many Login attempts in the last hour" und werde 4h gesperrt.
Auch der Adapter geht dann auf gelb.
Nach 4h geht wieder alles.
Vermutlich wird vor jeder statusabfrage ein login versucht. Die Anzahl summiert sich dann wahrscheinlich bis zut Sperre.

Bad Gateway Rückmeldung

Der Adapter funktionierte (mit seinen Tücken) über ein Jahr ganz gut, allerdings komme ich seit mehreren Tagen nun gar nicht mehr rein. Das Konto funktioniert, die Anmeldedaten hab ich mehrfach gecheckt. Diese Fehlermeldung "Bad Gateway" etc. hatte ich aber noch nicht. Bitte um Hilfe @TA2k

midea.0 2021-07-14 01:46:36.868 error (862639) update Command still failed after relogin
midea.0 2021-07-14 01:46:36.867 error (862639) 502
midea.0 2021-07-14 01:46:36.867 error (862639) "\r\n<title>502 Bad Gateway</title>\r\n<body bgcolor="white">\r\n

502 Bad Gateway

\r\n
openresty\r\n\r\n\r\n"
midea.0 2021-07-14 01:46:36.867 error (862639) Failed to send command
midea.0 2021-07-14 01:46:29.844 error (862639) update Command still failed after relogin
midea.0 2021-07-14 01:46:29.844 error (862639) 502
midea.0 2021-07-14 01:46:29.844 error (862639) "\r\n<title>502 Bad Gateway</title>\r\n<body bgcolor="white">\r\n

502 Bad Gateway

\r\n
openresty\r\n\r\n\r\n"
midea.0 2021-07-14 01:46:29.844 error (862639) Failed to send command
midea.0 2021-07-14 01:46:29.153 info (862639) Try to relogin
midea.0 2021-07-14 01:46:29.153 error (862639) null
midea.0 2021-07-14 01:46:29.153 error (862639) 502
midea.0 2021-07-14 01:46:29.153 error (862639) "\r\n<title>502 Bad Gateway</title>\r\n<body bgcolor="white">\r\n

502 Bad Gateway

\r\n
openresty\r\n\r\n\r\n"
midea.0 2021-07-14 01:46:29.152 error (862639) Failed to send command
midea.0 2021-07-14 01:46:22.128 info (862639) Try to relogin
midea.0 2021-07-14 01:46:22.128 error (862639) null
midea.0 2021-07-14 01:46:22.128 error (862639) 502
midea.0 2021-07-14 01:46:22.128 error (862639) "\r\n<title>502 Bad Gateway</title>\r\n<body bgcolor="white">\r\n

502 Bad Gateway

\r\n
openresty\r\n\r\n\r\n"
midea.0 2021-07-14 01:46:22.128 error (862639) Failed to send command
midea.0 2021-07-14 01:46:21.906 info (862639) Login successful

IObroker install failed from GitHub

Describe the bug
Installation from IObroker failed

To Reproduce
Steps to reproduce the behavior:
IObroker on Raspberry Pi 4b 8GB
Ubuntu 20.04 64Bit
Bildschirmfoto 2021-06-20 um 21 53 33

Expected behavior
Installation succeed

Versions:

Bildschirmfoto 2021-06-21 um 13 23 13

  • Adapter version: 0.0.7
  • JS-Controller version: 12.22.1
  • Node version: : 6.14.12
  • Operating system: Ubuntu 20.04 64bit

Additional context
See screenshot

Midea Adapter wirft Errors aus, funktioniert aber eine zeitlang

Describe the bug
Midea Adapter wirft Errors aus, funktioniert aber eine zeitlang

Screenshots & Logfiles

`

midea.0 2023-09-06 10:24:04.671 error SyntaxError: Unexpected token b in JSON at position 84 at JSON.parse () at Midea.updateDevices (/opt/iobroker/node_modules/iobroker.midea/main.js:159:32) at processTicksAndRejections (node:internal/process/task_queues:95:5)
midea.0 2023-09-06 10:24:04.668 error SyntaxError: Unexpected token b in JSON at position 84
`
Bildschirmfoto 2023-09-06 um 11 21 03

Bis dann einmal täglich der komplette Raspberry mit der ioBroker Instanz mit dieser Meldung einfriert.
Ist dann quasi weder über Terminal noch sonst irgendwie zu erreichen > Stecker ziehen.

midea.0 | 2023-09-06 16:41:46.125 | error | Error: Attempt to access 'appliance_state' failed. Python didn't respond in time (100000ms), look above for any Python errors. If no errors, the API call hung. at /opt/iobroker/node_modules/iobroker.midea/node_modules/pythonia/src/pythonia/Bridge.js:249:13 at waitFor (/opt/iobroker/node_modules/iobroker.midea/node_modules/pythonia/src/pythonia/Bridge.js:124:26) at Bridge.call (/opt/iobroker/node_modules/iobroker.midea/node_modules/pythonia/src/pythonia/Bridge.js:234:18) at Midea.updateDevices (/opt/iobroker/node_modules/iobroker.midea/main.js:144:31)

Versions:

  • Adapter version: 0.1.0
  • JS-Controller version: 4.0.24
  • Node version: 18.17.1
  • Operating system: Raspberry OS Bullseye

Additional context
Über den Midea Adapter lese ich die Luftfeuchte aus.
Über den Alexa Adapter steuere ich den Luftentfeuchter (da der Adapter ja mittlerweile keine Steuerung mehr zulässt).
Es funktioniert alles eine zeitlang (so zirka 24 Stunden), jedoch kommt nahezu stündlich (siehe Screenshot) die idente Fehlermeldung.

Please add you adapter to our repository

We saw your adapter and if it is ready please request that it is added to the repository. With this it becomes available for all users. Please consult https://github.com/ioBroker/ioBroker.repositories#add-a-new-adapter-to-the-latest-repository and the following sections for more details.
If you need help, contact us in the forum https://forum.iobroker.net/ or in the developer chat https://github.com/iobroker-community-adapters/info .

Thank you for your support.

Verbindung wird immer wieder getrennt

Hi,
habe jetzt folgende Konfiguration:

separater Account für iBroker
Intervall auf 61 Min
bewusst KEINE Anmeldung mehr auf dem Android
--> trotzdem wird mir immer die Verbindung getrennt.
image

Danach starte ich den Adapter neu und alles funktioniert wieder bis zum nächsten Mal.
image

MDD-20DEN7-WF dehumidifier many objects are empty

I have a MDD-20DEN7-WF dehumidifier. The Instance are green and i can connect me to the account without problems. But many objects are empty.

grafik
grafik
grafik
grafik

The Branding was COMFEE

Can you integrate them?

Versions:

  • Adapter version: 0.0.7
  • JS-Controller version: 4.0.24
  • Node version: 14.21.1
  • Operating system: Raspberry Pi 4 4GB

Comfee MDDF-16DEN7 WF not fully working

Describe the bug
I have to Comfee MDDF-16DEN7 WF. The adapter shows them both, but the objects are mostly empty. There are no value in path "status" or "control". I'm not sure, if this adapter is completed in any way.

To Reproduce
Steps to reproduce the behavior:
Install adapter, enter net home username & password, wait for 10 minutes (my interval is 5 minutes).

Expected behavior
Some data is shown, but the most status data is missing. Control objects are empty (but I'm not sure, if this is intended).

Screenshots & Logfiles
image

Versions:

  • Adapter version: 0.0.6
  • JS-Controller version: 3.1.6
  • Node version: v10.23.0
  • Operating system: Raspian OS

Plugin is not working anymore with ioBroker v5.0.0

Describe the bug
I tried to install the plugin to the new ioBroker v5.0.0. After installation, the plugin starts crashing with following stacktrace.

iobroker | Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/lib/exitCodes'
iobroker | at Function.Module._resolveFilename (module.js:548:15)
iobroker | at Function.Module._load (module.js:475:25)
iobroker | at Module.require (module.js:597:17)
iobroker | at require (internal/module.js:11:18)
iobroker | at Object. (/opt/iobroker/node_modules/iobroker.midea/node_modules/@iobroker/adapter-core/build/index.js:29:54)
iobroker | at Module._compile (module.js:653:30)
iobroker | at Object.Module._extensions..js (module.js:664:10)
iobroker | at Module.load (module.js:566:32)
iobroker | at tryModuleLoad (module.js:506:12)
iobroker | at Function.Module._load (module.js:498:3)
iobroker |
iobroker | module.js:550
iobroker | throw err;
iobroker | ^
iobroker |
iobroker | Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/lib/exitCodes'
iobroker | at Function.Module._resolveFilename (module.js:548:15)
iobroker | at Function.Module._load (module.js:475:25)
iobroker | at Module.require (module.js:597:17)
iobroker | at require (internal/module.js:11:18)
iobroker | at Object. (/opt/iobroker/node_modules/iobroker.midea/node_modules/@iobroker/adapter-core/build/index.js:29:54)
iobroker | at Module._compile (module.js:653:30)
iobroker | at Object.Module._extensions..js (module.js:664:10)
iobroker | at Module.load (module.js:566:32)
iobroker | at tryModuleLoad (module.js:506:12)
iobroker | at Function.Module._load (module.js:498:3)
iobroker |
iobroker | module.js:550
iobroker | throw err;
iobroker | ^
iobroker |
iobroker | Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/lib/exitCodes'
iobroker | at Function.Module._resolveFilename (module.js:548:15)
iobroker | at Function.Module._load (module.js:475:25)
iobroker | at Module.require (module.js:597:17)
iobroker | at require (internal/module.js:11:18)
iobroker | at Object. (/opt/iobroker/node_modules/iobroker.midea/node_modules/@iobroker/adapter-core/build/index.js:29:54)
iobroker | at Module._compile (module.js:653:30)
iobroker | at Object.Module._extensions..js (module.js:664:10)
iobroker | at Module.load (module.js:566:32)
iobroker | at tryModuleLoad (module.js:506:12)
iobroker | at Function.Module._load (module.js:498:3)
iobroker |
iobroker | module.js:550
iobroker | throw err;
iobroker | ^
iobroker |
iobroker | Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/lib/exitCodes'
iobroker | at Function.Module._resolveFilename (module.js:548:15)
iobroker | at Function.Module._load (module.js:475:25)
iobroker | at Module.require (module.js:597:17)
iobroker | at require (internal/module.js:11:18)
iobroker | at Object. (/opt/iobroker/node_modules/iobroker.midea/node_modules/@iobroker/adapter-core/build/index.js:29:54)
iobroker | at Module._compile (module.js:653:30)
iobroker | at Object.Module._extensions..js (module.js:664:10)
iobroker | at Module.load (module.js:566:32)
iobroker | at tryModuleLoad (module.js:506:12)
iobroker | at Function.Module._load (module.js:498:3)
iobroker |
iobroker | module.js:550
iobroker | throw err;
iobroker | ^
iobroker |
iobroker | Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/lib/exitCodes'
iobroker | at Function.Module._resolveFilename (module.js:548:15)
iobroker | at Function.Module._load (module.js:475:25)
iobroker | at Module.require (module.js:597:17)
iobroker | at require (internal/module.js:11:18)
iobroker | at Object. (/opt/iobroker/node_modules/iobroker.midea/node_modules/@iobroker/adapter-core/build/index.js:29:54)
iobroker | at Module._compile (module.js:653:30)
iobroker | at Object.Module._extensions..js (module.js:664:10)
iobroker | at Module.load (module.js:566:32)
iobroker | at tryModuleLoad (module.js:506:12)
iobroker | at Function.Module._load (module.js:498:3)
iobroker |
iobroker | module.js:550
iobroker | throw err;
iobroker | ^
iobroker |
iobroker | Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/lib/exitCodes'
iobroker | at Function.Module._resolveFilename (module.js:548:15)
iobroker | at Function.Module._load (module.js:475:25)
iobroker | at Module.require (module.js:597:17)
iobroker | at require (internal/module.js:11:18)
iobroker | at Object. (/opt/iobroker/node_modules/iobroker.midea/node_modules/@iobroker/adapter-core/build/index.js:29:54)
iobroker | at Module._compile (module.js:653:30)
iobroker | at Object.Module._extensions..js (module.js:664:10)
iobroker | at Module.load (module.js:566:32)
iobroker | at tryModuleLoad (module.js:506:12)
iobroker | at Function.Module._load (module.js:498:3)
iobroker |
iobroker | module.js:550
iobroker | throw err;
iobroker | ^
iobroker |
iobroker | Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/lib/exitCodes'
iobroker | at Function.Module._resolveFilename (module.js:548:15)
iobroker | at Function.Module._load (module.js:475:25)
iobroker | at Module.require (module.js:597:17)
iobroker | at require (internal/module.js:11:18)
iobroker | at Object. (/opt/iobroker/node_modules/iobroker.midea/node_modules/@iobroker/adapter-core/build/index.js:29:54)
iobroker | at Module._compile (module.js:653:30)
iobroker | at Object.Module._extensions..js (module.js:664:10)
iobroker | at Module.load (module.js:566:32)
iobroker | at tryModuleLoad (module.js:506:12)
iobroker | at Function.Module._load (module.js:498:3)

I installed the plugin against the v4.1.0 and everything seems to work.

To Reproduce
I used docker-compose on a Ubuntu Linux.
version: '2'

services:
iobroker:
restart: always
image: buanet/iobroker:v4.1.0
container_name: iobroker
hostname: iobroker
ports:
- "8081:8081"
volumes:
- iobrokerdata:/opt/iobroker
volumes:
iobrokerdata:

Versions:

  • Adapter version: v0.0.6
  • JS-Controller version:
  • Node version:
  • Operating system:

climate control doesnt work

Hi,
I can log in successfully. The states are then also read, but if I want to send a command, this is not possible.the value will be overwritten immediately. The Extract from the log file:

`

midea.0 2020-05-10 15:36:28.499 error (19389) undefined
midea.0 2020-05-10 15:36:28.498 error (19389) ASYN-Antwort existiert nicht

js-controller 3.0.20
Node.js v12.16.2
System runs in an Synology NAS Docker Container
`

Control of AC not working

Describe the bug
Added new AC to adapter, data points are created, values are ok.
When changing something (Power false -> true) it is not working.

Screenshots & Logfiles
2022-10-14 09:06:53.480 - debug: midea.0 (3198) Command: {"data":[170,30,172,0,0,0,0,0,3,2,64,67,138,20,127,127,0,63,0,0,0,0,0,0,0,0,0,0,0,156]} 2022-10-14 09:06:53.481 - debug: midea.0 (3198) Command + Header: [90,90,1,16,90,0,32,0,1,0,0,0,189,179,57,14,12,5,20,20,29,129,0,0,0,16,0,0,0,4,2,0,0,1,0,0,0,0,0,0,170,30,172,0,0,0,0,0,3,2,64,67,138,20,127,127,0,63,0,0,0,0,0,0,0,0,0,0,0,156,55,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0] 2022-10-14 09:07:03.080 - debug: midea.0 (3198) {"errorCode":"3176","msg":"The asyn reply does not exist ","result":null}

Versions:

  • Adapter version: 0.0.7
  • JS-Controller version: 4.0.23
  • Node version: v16.14.2
  • Operating system: Ubuntu 18.04.6 LTS

Setting the displayed temperature unit

Hello,

first of all: Thank you for your excellent work. I have adopted this project and many of the other existing libraries for my Homebridge plugin (https://github.com/ttimpe/homebridge-midea).

I have gotten a feature request to implement Fahrenheit temperature units and all I need is a setTempUnits method in the SetCommand, however this bit seems to be buried somewhere in the request.

Do you have any idea where it could be?

Probleme mit ein und ausschalten, Verbindung geht verloren bzw. Sitzung ungültig

Gehe wie folgt vor.
Habe per App die Klimaanlage verbunden, die Steuerung funktioniert soweit über die App auch.
Wenn ich jedoch über den iobrokr Kommandos absetze wie "powerState" auf true setzen, schaltet dieser zwar die Klimaanlage ein, jedoch wird der Wert direkt wieder auf "false" gesetzt und die Verbindung geht verloren und ich erhalte sowohl im iobroker log Fehlermeldungen. Die Steuerung ist anschließend über den iobroker nicht mehr möglich.

midea.0	2020-05-14 14:33:08.635	debug	(1012) send successful
midea.0	2020-05-14 14:33:08.634	debug	(1012) {"msg":"OK","result":{"reply":"c0c341f20dbc891296765bde8e1154953a3c8ad4074bfcaff4c6c4ca2f805959b6811d47b9d5a50e9ab14102498d84916a4afb7a785ca23e054686212b290af4b6811d47b9d5a50e9ab14102498d8491e2
midea.0	2020-05-14 14:33:08.434	debug	(1012) Login successful
midea.0	2020-05-14 14:33:08.432	debug	(1012) {"msg":"OK","result":{"originPrivateVersion":"","nickname":"[email protected]","sessionId":"99e75e4c11b84cfe8f392e398c205b6020200514123307568","accessToken":"9c4ab6acbd29d804fb44eab571368d41
midea.0	2020-05-14 14:33:07.527	debug	(1012) {"msg":"OK","result":{"loginId":"f780b30c-83ad-4555-917b-e48da8e51c82"},"errorCode":"0"}
midea.0	2020-05-14 14:33:07.492	info	(1012) Try to relogin
midea.0	2020-05-14 14:33:07.492	error	(1012) Sitzung ungültig
midea.0	2020-05-14 14:33:07.491	error	(1012) Sitzung ungültig
midea.0	2020-05-14 14:33:07.491	error	(1012) 3106
midea.0	2020-05-14 14:33:07.490	error	(1012) Sending failed device returns an error
midea.0	2020-05-14 14:33:07.490	debug	(1012) {"msg":"Sitzung ungültig","errorCode":"3106"}
midea.0	2020-05-14 14:32:33.434	debug	(1012) send successful
midea.0	2020-05-14 14:32:33.432	debug	(1012) {"msg":"OK","result":{"reply":"68dae29f859fb9fe6b99886466095ef869b7e4aea58aa5cc9b075fe141f0208a40cf2cc68d6d3b7a3d2dabd3d5d2f06aa152a8060a334bf34baed0e4cb74940370cf2cc68d6d3b7a3d2dabd3d5d2f06a3c
midea.0	2020-05-14 14:32:33.232	debug	(1012) Login successful
midea.0	2020-05-14 14:32:33.231	debug	(1012) {"msg":"OK","result":{"originPrivateVersion":"","nickname":"[email protected]","sessionId":"c50fa7a5df134424a5e9cc92de9b84af20200514123232367","accessToken":"3f0675d70ea6b2701703a3036741f789
midea.0	2020-05-14 14:32:32.328	debug	(1012) {"msg":"OK","result":{"loginId":"98fd2lba-fblc-4c3b-bdl1-68c1857rca0a"},"errorCode":"0"}
midea.0	2020-05-14 14:32:32.284	info	(1012) Try to relogin
midea.0	2020-05-14 14:32:32.283	error	(1012) Sitzung ungültig
midea.0	2020-05-14 14:32:32.283	error	(1012) Sitzung ungültig
midea.0	2020-05-14 14:32:32.283	error	(1012) 3106
midea.0	2020-05-14 14:32:32.282	error	(1012) Sending failed device returns an error
midea.0	2020-05-14 14:32:32.282	debug	(1012) {"msg":"Sitzung ungültig","errorCode":"3106"}
midea.0	2020-05-14 14:32:16.830	debug	(1012) system.adapter.admin.0: logging true
midea.0	2020-05-14 14:32:14.067	debug	(1012) system.adapter.admin.0: logging false

in der App erhalte ich die Fehlermeldung "Error Unable to verify account, please log in again"

Adapter Version 0.0.3
Node.js v12.16.3
raspberry pi with raspbian buster

Eine Idee woran dies liegt?
HAbe mich auch mal testweise zuvor von der App abgemeldet, gefällt midea wohl auch nicht.

Falls weiter Informationen benötigt werden oder ich irgendwie beim debugging helfen kann, melde dich bitte.

Gruß
jay

Can't connect to air conditioning

Describe the bug
Can´t connect to my Comfee climate
In Iobrooker it allways tells me not connectedt to device or service

Expected behavior
Connect to my Device :-)

Screenshots & Logfiles

image

Versions:

  • Adapter version: <v0.0.7>
  • JS-Controller version: <>
  • Node version: <jv16.17.1>
  • Operating system: <Synology DS220+ with Docker 20.10.3-1308>

Feedback zu der Version 0.1.0 von git

Moin, da meine aktuelle Dimstal über die 0.0.7 zwar auslesbar aber nicht steuerbar war habe ich mal die git-Version gezogen,

Hier ein kurzes Feedback:
Objekte unter control werden nicht mehr aktualisiert.
Im Log:
Found 1 devices

[{id=142936511676950, address=192.168.178.87, port=6444, version=3, name=Living Room, online=True, type=0xac, subtype=acac, flags=0, extra=2, reserved=87, mac=04d6f4587f5e, ssid=net_ac_7F5E, udp_version=0, protocol=150029, version=8.33.21, sn=000000P0000000Q104D6F4587F5E0000, state=[Air conditioner]{id=14293651167****, type=0xac mode=4, running=True, turbo=False, fan_speed=102, turbo_fan=False, purifier=False, dryer=False, target_temperature=21.0, indoor_temperature=24.3, outdoor_temperature=14.4, vertical_swing=False horizontal_swing=False comfort_sleep=False, error_code=0, prompt=False, supports={'eco': 1, 'mode': 1, 'fan_swing': 1, 'electricity': 0, 'strong_fan': 1, 'fan_speed': 1, 'temperature0': 32, 'temperature1': 60, 'temperature2': 32, 'temperature3': 60, 'temperature4': 32, 'temperature5': 60, 'temperature6': 0}}}]

function () { [native code] }

SyntaxError: Unexpected token x in JSON at position 723

SyntaxError: Unexpected token x in JSON at position 723 at JSON.parse (<anonymous>) at Midea.getDeviceList (/opt/iobroker/node_modules/iobroker.midea/main.js:113:30) at processTicksAndRejections (node:internal/process/task_queues:96:5) at Midea.onReady (/opt/iobroker/node_modules/iobroker.midea/main.js:76:5)

Vielleicht hilft das ja bei der weiteren Arbeit, sieht auf jeden Fall interessant aus.

Gruß
Matze

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/TA2k/ioBroker.midea

  • [E605] No actual year found in copyright. Please add "Copyright (c) 2021 TA2k [email protected]" at the end of README.md
  • [E701] No actual year found in LICENSE. Please add "Copyright (c) 2021 TA2k [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

Working

Hi I want to use this with iobroker is it working ?

Power State ein oder ausschalten funktioniert nicht.

Hi,
sobald ich im ioBroker unter Control den Power State auf True setze erscheint im LOG folgendens:

midea.0 | 2020-06-11 19:44:50.841 | info | (8770) Command was not accepted by device. Command wrong or device not reachable 17592186114552 ASYN-Antwort existiert nicht.

Dies haben hier auch schon einige andere User bemängelt. Gibt es da eine lösung?
Alle Geräte sind via WiFI anpingbar durchgehend. 5GHz Wifi bereits deaktiviert.

Alles bereits einmal neugestartet. Klimaanlage Sicherung raus und wieder rein.
Keine Smartphone App ist gestartet.

Es klappt einfach nicht die Innengeräte einzuschalten. Egal bei welchem. Es ist ein Multisplit System von Midea.

Vielen Dank im voraus.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.