iobroker / iobroker.mihome

Adapter for Xiaomi Mi home smarthome

mihome Gateway

This adapter uses Sentry libraries to automatically report exceptions and code errors to the developers. For more details and for information how to disable the error reporting see Sentry-Plugin Documentation! Sentry reporting is used starting with js-controller 3.0.

Requirements

Android (copied from here )

You first need to enable local network functions by using the Android Mi Home App https://play.google.com/store/apps/details?id=com.xiaomi.smarthome :

• Install the App on a Android device
• Make sure you set your region to: Mainland China under settings -> Locale - at time of writing this seems to be required.
• Mainland China and language can set on English
• Select your Gateway in Mi Home
• Then the 3 dots at the top right of the screen
• Then click on about
• Tap the version (2.27 is the current Android version as of 2 June 2017) number at the bottom of the screen repeatedly
• You should see now 2 extra options listed in English (was Chinese in earlier versions) until you did now enable the developer mode. [ if not try all steps again! ]
• Choose the first new option
• Then tap the first toggle switch to enable LAN functions. Note down the password (29p9i40jeypwck38 in the screenshot). Make sure you hit the OK button (to the right of the cancel button) to save your changes.
• If you change here something, you lose your password!

iOS

You first need to enable local network functions by using the iOS Mi Home App iosApp Mi Install the App on a iOS device:

• Make sure you set your region to: Mainland China under settings -> Locale - required for the moment.
• Mainland China and language can set on English
• Select your Gateway in Mi Home
• Then the 3 dots at the top right of the screen
• Then click on about
• Tap under Tutorial menu(on the blank part) repeatedly
• You should see now 3 extra options listed in Chinese until you did now enable the developer mode. [ if not try all steps again! ]
• Choose the second new option
• Then tap the first toggle switch to enable LAN functions. Note down the password (29p9i40jeypwck38 in the screenshot). Make sure you hit the OK button (to the right of the cancel button) to save your changes.
• If you change here something, you lose your password!

Using acpartner

An adapter of version 1.3.xx or higher allows you to control the air conditioner connected to ioBroker using acpartner.v3 (KTBL11LM), (it will probably work with version v2 too, but the developer had not hardware to test it, if anyone tries, let us know).

The following states have been added to control the air conditioner:

The process of enabling LAN access and receiving GATEWAY KEY can be of some difficulty, the process is described below.

To start using:

• Install the Aqara Home application on your smartphone (https://play.google.com/store/apps/details?id=com.lumiunited.aqarahome),
• register in the Aqara Home application,
• select the "Mainland China" region in the settings,
• add acpartner to the Aqara Home app,
• update the acpartner firmware (click on the air conditioning icon, then the three dots in the upper right corner, then click the lowest point “Software Version”), as a result, Aqara firmware will be installed on acpartner (when using the MiHome application it was from Xiaomi),
• register on the site https://opencloud.aqara.cn/ with the same password and login as in the Aqara Home application (registration confirmation may take some time, I had about 6 hours),
• log in to the console https://opencloud.aqara.cn/console/
• create an application on the tab https://opencloud.aqara.cn/console/app-management with the type "Device access" (I’m not sure about the need for this item (because I did it yet), so you can try to skip it),
• then go to the console https://opencloud.aqara.cn/console and select Gateway LAN on the left, fill in the "Aqara account" and "Password" fields and click the Submit button - you will see your Air Conditioning Controller and the network protocol enable button by clicking to which you allow LAN access and you will see the network key, which is necessary to configure the adapter in ioBroker.
• in the adapter settings, enter the key obtained above.

Usage

You can use small button on temperature sensor to trigger double Press event. Just press twice within 5 seconds. You can set this interval in settings, but do not set it over 10 seconds.

Add device by SID

In case of device does not recognized by its Model name it is possible to try to add device using SID. Currently it is applicable for Aqara 2 channels relay control module which has empty model name due to some problems in Gateway firmware.

In order to add device by SID, open DEVICE SID tab in adapter settings and specify SID and device name from the supported devices list below.

For Aqara relay module it should be specified like this:

Supported devices

• gateway - Xiaomi RGB Gateway
• acpartner.v3 - Aqara AC Partner (KTBL11LM)
• sensor_ht - Xiaomi Temperature/Humidity
• weather.v1 - Xiaomi Temperature/Humidity/Pressure
• switch - Xiaomi Wireless Switch
• sensor_switch.aq2 - Xiaomi Aqara Wireless Switch Sensor
• sensor_switch.aq3 - Xiaomi Aqara Wireless Switch Sensor
• plug - Xiaomi Smart Plug
• 86plug - Xiaomi Smart Wall Plug
• 86sw2 - Xiaomi Wireless Dual Wall Switch
• 86sw1 - Xiaomi Wireless Single Wall Switch
• natgas - Xiaomi Mijia Honeywell Gas Alarm Detector
• smoke - Xiaomi Mijia Honeywell Fire Alarm Detector
• ctrl_ln1 - Xiaomi Aqara 86 Fire Wall Switch One Button
• ctrl_ln1.aq1 - Xiaomi Aqara Wall Switch LN
• ctrl_ln2 - Xiaomi 86 zero fire wall switch double key
• ctrl_ln2.aq1 - Xiaomi Aqara Wall Switch LN double key
• ctrl_neutral2 - Xiaomi Wired Dual Wall Switch
• ctrl_neutral1 - Xiaomi Wired Single Wall Switch
• cube - Xiaomi Cube
• sensor_cube.aqgl01 - Xiaomi Cube
• magnet - Xiaomi Door Sensor
• sensor_magnet.aq2 - Xiaomi Aqara Door Sensor
• curtain - Xiaomi Aqara Smart Curtain
• motion - Xiaomi Motion Sensor
• sensor_motion.aq2 - Xiaomi Aqara Motion Sensor
• sensor_wleak.aq1 - Xiaomi Aqara water sensor
• ctrl_ln2.aq1 - Xiaomi Aqara Wall Switch LN (Double)
• remote.b186acn01 - Xiaomi Aqara Wireless Remote Switch
• remote.b186acn02 - Xiaomi Aqara Wireless Remote Switch
• remote.b286acn01 - Xiaomi Aqara Wireless Remote Switch (Double Rocker)
• remote.b286acn02 - Xiaomi Aqara Wireless Remote Switch (Double Rocker)
• remote.b1acn01 - Xiaomi Aqara Wireless Remote Switch
• vibration - Xiaomi vibration Sensor
• wleak1 - Xiaomi Aqara Water Sensor
• lock_aq1 - Xiaomi Lock
• relay.c2acn01 - Aqara 2 channels relay control module (using SID number)

Changelog

1.4.0 (2022-03-10)

• (drtsb) Added two new aqara devices and some missing icons
• (VLGorskij) fixed the error messages for some states
• (Apollon77) Catch some errors reported by Sentry and users

1.3.7 (2021-01-22)

• (Apollon77) Prevent crash case (Sentry IOBROKER-MIHOME-A)

1.3.6 (2020-09-25)

• (VLGorskij) Added new device QBKG24LM

1.3.5 (2020-09-17)

• (Apollon77) Fix crash cases (Sentry IOBROKER-MIHOME-1..4)

1.3.4 (2020-08-31)

• (Alan) Fixed the crash for non existing attributes

1.3.3 (2020-08-26)

• (bluefox) Sentry is activated

1.3.2 (2020-08-25)

• (VLGorskij) Added ac-partner.v3 support
• (bluefox) Added compact mode

1.3.1 (2020-08-19)

• (Diginix) Fixed calculation for sensor's battery percentage

1.3.0 (2020-01-16)

• (algar42) Ability to add devices with missing model by their SID (e.g. for Aqara two-channel relay)

1.2.9 (2019-11-15)

• (Diginix) Fixed pressure range and values of Aqara weather sensor

1.2.8 (2019-07-18)

• (SchumyHao) Change curtain and gateway light role that making them can be detected by type-detector

1.2.7 (2019-06-25)

• (SchumyHao) Add several devices support for protocol 2.0.x

1.2.6 (2019-03-04)

• (Diginix) Improved calculation for sensor's battery percentage

1.2.5 (2019-01-24)

• (Vanwards) Added long click for Aquara wall switch

1.2.4 (2019-01-15)

• (SchumyHao) Add Chinese support

1.2.3 (2018-10-23)

• (goohnie) New wall switch was added

1.2.0 (2018-10-12)

• (bluefox) refactoring

1.1.2 (2018-10-08)

• (bluefox) New button switch was added

1.1.1 (2018-09-23)

• (bluefox) Fixed the creation of new devices

1.1.0 (2018-09-13)

• (bluefox) New devices added: sensor_switch.aq3, ctrl_ln1.aq1, ctrl_ln2.aq1, sensor_cube.aqgl01, remote.b286acn01, vibration, wleak1, lock_aq1
• (bluefox) Names will be taken from gateway

1.0.7 (2018-06-25)

• (bluefox) The heartbeat timeout and the re-connection interval settings were added

1.0.6 (2018-05-26)

• (bluefox) Added new Aqara cube sensor

1.0.5 (2018-03-05)

• (bluefox) Xiaomi Aqara Wall Switch LN Double was added

1.0.4 (2018-01-21)

• (bluefox) The alarm state was fixed.

1.0.3 (2018-01-21)

• (bluefox) Invalid temperature values will be ignored

1.0.2 (2018-01-14)

• (bluefox) Ignore unknown state of sensors

1.0.0 (2018-01-05)

• (bluefox) Do not overwrite the names
• (bluefox) Ready for Admin3

0.3.3 (2017-11-26)

• (bluefox) Allow multiple mihome gateways

0.2.4 (2017-11-04)

• (bluefox) Add aqara water sensor

0.2.3 (2017-09-22)

• (bluefox) Remove "." from id of the device

0.2.2 (2017-08-01)

• (bluefox) Set after 300ms doublePress to false by Temperature Sensor\nAllow control of Plug

0.2.1 (2017-07-29)

• (bluefox) Implement double click on temperature sensor

0.2.0 (2017-07-18)

• (bluefox) fix battery level

0.1.4 (2017-06-09)

• (bluefox) add cube
• (bluefox) remove voltage by gateway

0.1.1 (2017-06-06)

• (bluefox) Initial commit

License

The MIT License (MIT)

Copyright (c) 2017-2022 bluefox [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.mihome's Issues

Klimaanlagen Controller

Hi,

der Klimaanlagen Controller von Xiaomi wird wohl garnicht unterstützt. Benutze diesen auch als Gateway und schaffe es nicht ihn zu verbinden. Gibt es die möglichkeit das irgendwie hinzubekommen?

please add remote.b186acn01

thx for the new devices.js :-)
now it is mutch easier to add a device.

please add remote.b186acn01 for alle other people.

for me, i made this change:

it´s working :-)

devices.zip

Could not add new sensor: Type "remote.b1acn01" is not valid, use one of Hub::sensorTypes

Hi bluefox!
I have Aqara Smart Wireless Switch (Model:WXKG11LM), but I can not add to device. Here is my log

2018-10-03 18:46:15.038 - warn: mihome.0 Could not add new sensor: Type "remote.b1acn01" is not valid, use one of Hub::sensorTypes

2018-10-03 18:46:22.701 - warn: mihome.0 Could not add new sensor: Type "remote.b1acn01" is not valid, use one of Hub::sensorTypes

Can you please support?

Thanks in advance and best wishes

Xiaomi Aqara Cube Objects doesn't work.

Device is detected and data points are created. But if I use one switch in a blockly trigger it doesn't work and the ioBroker log says:

getState "mihome.0.devices.cube_158d0002******.shake_air" not found (3) states[id]=null

Использование двух экземпляров адаптера

На Raspberry Pi3 работает ioBroker. Подняты два сетевых интерфейса - Lan (192.168.1.45) и WiFi (192.168.1.55)
Установлен адаптер ioBroker.mihome версии 1.2.3 и два экземпляра драйвера - mihome.0 и mihome.1
На эти два экземпляра подключены два шлюза -
на mihome.0(192.168.1.45) висит Xiaomi gateway3 (lumi-gateway-v3) c адресом 192.168.1.71
на mihome.1(192.168.1.55) висит Aqara AC Partner (lumi-acpartner-v1) c адресом 192.168.1.33
Все датчики (движения, температуры, розетки, выключатели) сопряжены с первым шлюзом (на mihome.0)
Если я запускаю оба экземпляра mihome.0 и mihome.1 то получаю в логе ошибку "Error: bind EADDRINUSE 0.0.0.0:9898"
несмотря на то что у в настройках стоят адреса 192.168.1.45 и 192.168.1.55
Затем я останавливаю экземпляр mihome.0 к которому подключены датчики и прочие устройства и стартую экземпляр mihome.1 -
и получаю неожиданный результат - в объектах экземпляра mihome.1 вижу устройства сопряженные с mihome.0
Подскажите, может я что-то не понимаю/делаю не так - на мой взгляд ошибки "Error: bind EADDRINUSE 0.0.0.0:9898" здесь не должно быть,
тогда невозможно использовать два экземпляра адаптера?

false positives on mijia and aqara pir sensors

i have 5 pir sensors, 2 of them have work in my system and 3 - got connected to gateway and bring back into their boxes to wait when they have been needed.
And i have false positives on all of them, sometimes all work well for long time, but sometimes they start triggered for few times a day and even hour!
At MiHome app no any false positives and nothing in mihome log, so i thing sensors work correct

Make adapter ready for Admin v3

For Admin3 some changes are needed: see http://forum.iobroker.net/viewtopic.php?f=24&t=10268

Namen nach Neustart weg

Hallo,

hat man den Geräten in der Lasche "Objekte" von ioBroker Namen vergeben sind diese nach einem Neustart des Adapter leider wieder weg.
Es wäre toll, wenn die Namen erhalten bleiben würden. Bei mehreren gleichen Geräten erleichtert das die Zuordnung.

MfG
B. Müller

Could not add new sensor: Type "vibration" is not valid, use one of Hub::sensorTypes

Sensor couldn´t add to the mihome adapter:

https://www.gearbest.com/smart-home-controls/pp_009661787808.html?wid=1433363

Status vom Vibration Sensor bleibt immer auf "false" stehen

Der Adapter aktualisiert bei Bewegung zwar alle möglichen Werte, aber die Eigenschaft "state" vom Vibration Sensor bleibt leider immer auf "false" stehen.

Fehlalarme wenn Mi Gateway ohne Internet

Hi,

mehrere Nutzer inkl. mir bestätigen folgendes Problem:

Wenn man dem Mi Gateway z.B. via FritzBox den Internetzugang verweigert (und nur dann) funktionieren die Magnetsensoren (sowohl Aqara als auch Original Xiaomi) nicht ganz korrekt.
Es kommt in unregelmäßigen Abständen zu Fehleralarmen aller Magnetsensoren gleichzeitig.
Sprich es werden gleichzeitig alle Sensoren offen gemeldet obwohl dem tatsächlich nicht so ist.
Nach wenigen Minuten bzw. dem Neustart des Adapters sind die Sensoren wieder geschlossen.
Ich, und sich auch der ein oder andere der den Smarthome Geräten keine Verbindung ins Internet erlauben möchte, würden sich freuen wenn hier eine Lösung gefunden werden kann.
Es hat sich durch einen Test eines anderen Forenmitglieds herausgestellt dass die Ursache des Problem der Adapter oder aber ioBroker selbst sein muss.

Ich danke dir im Voraus.

Wireless Switch Double Klick dont work

Hello, when i klick once, the single value, and the double updates to false. And the same happens when i klick double. I have the Single Aqara Wireless Switch.

lumi.gateway.v3 support?

My lumi.gateway.v3 doesn't work, is it supported?

Xiaomi Gateway cannot Setup. Status Yellow

Can not set up Xiaomi Gateway. Status is always yellow. Key is entered correctly. Have already been uninstalled several times instance and reinstalled. Helps nothing. 2 versions of iobroker tried (desktop + iobrocker installed later) and image (lite).

Xiaomi Magic Cube not be integrated

I have a Xiaomi Magic Cube, it can not be integrated in ioBroker. In the MiHome this one works. There is another user with this problem in the ioBroker forum. Are there different Magic Cubes?
How can I contribute to problem solving?

Implement sensor_cube.aqgl01

home-assistant/core#14393 (comment)

Timeout-parameter for lumi.sensor_motion.aq2

Hello,

is it possible to add a timeout-parameter (value=seconds) for the AQARA Motion sensor (lumi.sensor_motion.aq2)?

I want my sensor to recognize motions and turn the lights on in the bathroom for instance. It should immeditaly new motions turn off the lights again if there is no motion anymore, but keep the lights on if new motions have been recognized

I'm experiencing the following issue: By default the sensor recognizes the first motion and remains in motion-status=true for 60 secs exactly. This means that the sensor is not able to recognize new motions within the 60 seconds.

With the mentioned timeout-valueI would like to set the 60 secs to 3 secs for instance. So the sensor would be able to recognize motions every 3 secs after first recognition.

Thank you in advance.

Smart Plug can't change State

The Plug doesn't work. I played with the State of the Plug, but i can't get it work. All other Products works fine except the Smart Plug.
Any idea?

Aqara Wall Switch funktioniert nicht vollständig

Hi,
ich habe Probleme mit den Unterputzschaltern von Aqara (hier das Modell ohne Nullleiter). Es wird im IOBroker nur der Zustand der Relais angezeigt. Ob ein Button gedrückt wurde, wird nicht angezeigt.

Dies ist daher problematisch, da man die Schalter von den Relais entkoppeln kann. Ein Reagieren auf einen Tastendruck ist dann nicht mehr möglich.

Es wäre daher gut, wenn zwei neue Objekte für die Taster angelegt werden könnten, welches das Tastendruck-Event anzeigen (false-true-false).

Gruß
Hiffi

Names will be taken from gateway ?

Hi,
which names? It doesn't work here, every device that the adapter creates have the default Name, not the name I save in the app for the device.
( tested with door-magnet, vibration sensor, Temp.-Sensor)

any ideas?

Alarm scharf/unscharf schalten über iobroker

Hallo
Gibt es eine Möglichkeit den Alarm vom Xiaomi Gateway über iobroker zu schalten ?
Bis jetzt bekomme ich den Alarm aktiviert / deaktiviert über die Mi Home App.
Oder ist das in der API nicht vorgesehen?

mihome v1.1.0

Hi,
ich hab mal n bisserl getestet, mit den verschiedenen Versionen von MiHome unter verschiedenen Umgebungen(npm/node/js-controller), vielleicht hilfts ja bei der Fehlersuche.

Ergebnis:
Version 1.1.0 erzeugt keine neuen Objekte und legt auch keine Datenpunkte/Geräte an. Leider kommen hierzu keinerlei Fehler im Log(auch nicht in iobroker/log unter debug). Vorhandene Objekte werden aktualisiert.
(unter npm6.4.0 und node8.11.4 - js-controller 1.5.2 damit läuft bei mir iobroker sehr stabil)

Mein letzter Bugbericht mit den enorm vielen Debugmeldungen wurde unter npm6.4.1-node8.12-js-controller1.5.1 erzeugt, das ist auch nachvollziehbar, denke, das liegt eher an npm/node/js-contrller Kombination als am MiHome-Adapter, der erzeugt unter 6.4.0/8.11.4/1.5.2 keine solche Meldungen.

Auch das gleiche unter js-controller 1.4.2 mit npm6.4.1 und node10.10.0 - sowohl js-controller 1.5.1/1.5.2 keine Funktion und jede Menge Debugmeldungen.

The heartbeat (Door Sensor, PIR, etc.).

Most recently, my Door Sensor and Motion Sensor sent heartbeat. Door Sensor every 51 minutes sent his fortune true or false. So I realized that the sensor is online and working. I even developed an alert if Door Sensor not responding: https://forum.iobroker.net/viewtopic.php?p=152942#p152942
But now the heartbeat stopped coming. Now I can not distinguish, there are no events, or Door Sensor not work.
I could not understand why it stopped heartbeat. I simultaneously updated Xiaomi MiHome Gateway and updated mihome xiaomi driver iobroker from version 1.0.5 to version 1.0.7.
Earlier the heartbeat Door Sensor was determined only in iobroker (Node-RED), in log xiaomi mihome did not have heartbeat. Consequently, the system Xiaomi able to distinguish The heartbeat from status signals, Good, if iobroker also will be able to distinguish heartbeat from status.
how do i get back heartbeat Door Sensor?

Namen vom Gateway übertragen

Hallo,

ich hab den Adapter in der letzten Version 1.2.3 laufen.
Leider ist die Anzeige der verschiedenen Sensoren und Schalter in iobroker sehr schwierig, da lediglich die IDs und die generelle Gerätebezeichnung angegeben sind.
In der Beschreibung von 1.1.0 hieß es, dass die Namen übertragen werden.
Waren damit die in der App den Geräten zugewiesenen Namen gemeint? Falls ja, wie krieg ich das hin, dass die übertragen werden.
Das Löschen der Objekte und das neustarten und neuinstallieren des Adapters hat lediglich dazu geführt, dass die allgemeine Bezeichnung der Geräte von deutsch nach englisch gewechselt hat.

Add Xiaomi IR Remote

Please Support Xiaomi IR Remote

Feature Request: Sync device names to ioBroker

Currently a user can name each device in the App/Gateway. Inside ioBroker these names never appear but have to be given again.

When adding a number of new devices at once it becomes tricky to know which of the crypitc names/ids inside ioBroker belongs to which actual device.

It would be great if the device names from the Gateway could be synced to ioBroker

device request: Mi Remote IR Blaster

Hi there,
is there the possibility to add the support for Xiaomi Mi Remote device?
https://www.china-gadgets.de/xiaomi-wifi-ir-fernbedienung/
https://de.gearbest.com/smart-home/pp_229556.html

I ordered one from China and can already use it with the Xiaomi Home App for controlling my TV, AVR and AIR Conditioner.

The device is really cheap and you can use it for all kind of IR devices.

Thank you in advice.
Matthias

Einbindung Yeelight bulbs

Hallo allerseits!

Zunächst Hut ab und Danke an euch Fachleute.

Ist aus eurer Sicht auch eine Unterstützung der Yeelight Wifi-Leuchten (E27) machbar?

Als Laie stehe ich vor dem Problem aktuell eine Alexa-Einbindung von Yeelights nur unter Nutzung des Singapur-Servers zu realisieren. Dann bekomme ich aber den Gateway (da Mainland China notwendig) insgesamt nicht installiert.

Wäre klasse wenn ihr die noch aufnehmen könntet!

iobroker mihome Instanz lässt sich nicht starten

Hi @ALL

Ich schaffe es nicht den mihome adapter zum laufen zu bringen.
App und gateway funktionieren.

Jede Hilfe ist willkommen.

Mfg.
Alessandro

-----------------------------LOG--------------------------------------
host.store 2018-03-17 23:16:11.617 info Restart adapter system.adapter.mihome.0 because enabled
host.store 2018-03-17 23:16:11.616 error instance system.adapter.mihome.0 terminated with code 0 (OK)
mihome.0 2018-03-17 23:16:11.603 info terminating
mihome.0 2018-03-17 23:16:11.595 error at Manager.ondecoded (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:332:8)
mihome.0 2018-03-17 23:16:11.595 error at Manager.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
mihome.0 2018-03-17 23:16:11.595 error at Manager. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15)
mihome.0 2018-03-17 23:16:11.595 error at Socket.onpacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:236:12)
mihome.0 2018-03-17 23:16:11.595 error at Socket.onack (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:312:9)
mihome.0 2018-03-17 23:16:11.595 error at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1346:35)
mihome.0 2018-03-17 23:16:11.595 error at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1458:21
mihome.0 2018-03-17 23:16:11.595 error at /opt/iobroker/node_modules/iobroker.mihome/main.js:1057:21
mihome.0 2018-03-17 23:16:11.595 error at startMihome (/opt/iobroker/node_modules/iobroker.mihome/main.js:1106:11)
mihome.0 2018-03-17 23:16:11.595 error at new Hub (/opt/iobroker/node_modules/iobroker.mihome/lib/mihome/Hub.js:31:20)
mihome.0 2018-03-17 23:16:11.595 error TypeError: function from() { [native code] } is not a constructor
mihome.0 2018-03-17 23:16:11.592 error uncaught exception: function from() { [native code] } is not a constructor
mihome.0 2018-03-17 23:16:11.565 info starting. Version 1.0.5 in /opt/iobroker/node_modules/iobroker.mihome, node: v4.2.6
mihome.0 2018-03-17 23:16:11.545 debug statesDB connected
mihome.0 2018-03-17 23:16:11.522 debug objectDB connected
host.store 2018-03-17 23:16:11.169 info instance system.adapter.mihome.0 started with pid 47600

Feature request: Connection state for multiple gateways

Dear Team,

the mihome adapter allows multiple gateways per instance but provides only one connection state info.connection. Would it be possible to add states for each gateway or add a heartbeat (each gateway sends a heartbeat) state for each gateway in device tree? I have more than one gateway connected and the state connected stay true even if one gateway is disconnected.

Heartbeats:

• mihome.0 2018-06-01 20:50:17.202 debug RAW: {"cmd":"heartbeat","model":"gateway","sid":"...b8f","short_id":"0","token":"...","data":{"ip":"x.y.z.16"}}
• mihome.0 2018-06-01 20:50:15.127 debug RAW: {"cmd":"heartbeat","model":"gateway","sid":"...511","short_id":"0","token":"...","data":{"ip":"x.y.z.17"}}

Many Thanks & Best Regards

Could not add new sensor: Type "sensor_switch.aq3" is not valid

good afternoon. I bought the button, but it does not appear in the objects.
Log:
Could not add new sensor: Type "sensor_switch.aq3" is not valid, use one of Hub::sensorTypes
Link:
http://www.dx.com/p/Xiaomi-Aqara-Smart-Wireless-Switch-Key-Built-In-Gyro-Function-ZigBee-WiFi-Works-With-Xiaomi-Smart-Home-Mijia-Mi-Home-APP-White-916499969

Xiaomi Rauchmelder: Kein Alarm auf IOBroker

Hallo @ALL,
hab das Xiaomi Gateway und 2 Smoke Detektoren erfolgreich am Laufen. Die Geräte werden auch in IOBroker erkannt.
Eine Raucherkennung sorgt am Detektor für hörbaren Alarm und am Gateway für Blinken der roten Leuchte. In IOBroker ändert sich aber bei mir kein Status.
Somit ist keine Reaktion in IOBroker wie bspw. Versenden einer Nachricht möglich.

Getestet auf Adapter MIHome1.0.0 und Admin 2.09 sowie Admin 3.011

Could not add new switch ctrl_ln1 - Xiaomi Aqara 86 Fire Wall Switch One Button

Hi bluefox!
I have Aqara switch one button 86, but I can not add to device. Here is my log

mihome.0	2018-07-18 05:47:24.110	warn	Could not add new sensor: Type "ctrl_ln1.aq1" is not valid, use one of Hub::sensorTypes
mihome.0	2018-07-18 05:47:24.075	warn	Could not add new sensor: Type "ctrl_ln1.aq1" is not valid, use one of Hub::sensorTypes

Pls help me to add this switch to device

Не работает настенная розетка Aqara QBCZ11LM

Пытался добавить его в ручную добавив в файле lib/mihome/Hub.js к переменной sensorTypes следующую строку:
ctrl_86plug_aq1:'çtrl_86plug.aq1',
Потом в функции sensorFactory в конструкцию switch добавил переменную
this.sensorTypes.ctrl_86plug_aq1
В итоге получилось так:
case this.sensorTypes.plug: case this.sensorTypes.plug86: case this.sensorTypes.ctrl_86plug_aq1: sensor = new Plug(sid, ip, this); break;
Так же потом в файле main.js к константе names прибавил следующее:
'çtrl_86plug.aq1': 'Xiaomi new Super Plug'
И в этом же файле добавил к конструкции switch в функции createDevice переменную çtrl_86plug.aq1 к розеткам.
Лог который приходит:

В объектах розетка не появляется

neue UnterputzSchalter werden nicht erkannt

Die neuen Unterputzschalter mit "Neutralleiter" werden von dem Adapter leider nicht erkannt, oder nicht an diesen weitergegeben.
In der MiHomeApp lassen Sie sich jedoch einwandfrei ansprechen.

Hier die DebugAusgabe des Adapters. Lediglich der Gateway und der Funk-Aufputzsschalter werden korrekt in den Adapter übernommen.

mihome.0 2018-02-11 15:44:03.788 debug redis pmessage io.mihome.0.devices.* io.mihome.0.devices.86sw2_158d000170ebe7.channel_1 {'val':false,'ack':true,'ts':1518360243784,'q':0,'from':'system.adapter.mihome.0','lc':1518360243784} mihome.0 2018-02-11 15:44:03.783 debug data: 158d000170ebe7(86sw2): {'channel_1':false} mihome.0 2018-02-11 15:44:03.494 debug redis pmessage io.mihome.0.devices.* io.mihome.0.devices.86sw2_158d000170ebe7.channel_1 {'val':true,'ack':true,'ts':1518360243485,'q':0,'from':'system.adapter.mihome.0','lc':1518360243485} mihome.0 2018-02-11 15:44:03.493 debug redis pmessage io.mihome.0.devices.* io.mihome.0.devices.86sw2_158d000170ebe7.channel_1_double {'val':false,'ack':true,'ts':1518360243484,'q':0,'from':'system.adapter.mihome.0','lc':1518359285963} mihome.0 2018-02-11 15:44:03.487 debug RAW: {'cmd':'report','model':'86sw2','sid':'158d000170ebe7','short_id':17339,'data':{'channel_1':'click'}} mihome.0 2018-02-11 15:44:03.486 debug data: 158d000170ebe7(86sw2): {'channel_1_double':false,'channel_1':true} mihome.0 2018-02-11 15:43:59.797 debug RAW: {'cmd':'heartbeat','model':'gateway','sid':'7811dc64dbcd','short_id':'0','token':'RutivcU5r7wRY5NB','data':{'ip':'192.168.178.34'}} mihome.0 2018-02-11 15:43:49.882 debug RAW: {'cmd':'heartbeat','model':'gateway','sid':'7811dc64dbcd','short_id':'0','token':'Des37Qmi6bWAow4O','data':{'ip':'192.168.178.34'}} mihome.0 2018-02-11 15:43:39.845 debug RAW: {'cmd':'heartbeat','model':'gateway','sid':'7811dc64dbcd','short_id':'0','token':'qH5y3eBHyXFkyI2D','data':{'ip':'192.168.178.34'}} mihome.0 2018-02-11 15:43:29.918 debug RAW: {'cmd':'heartbeat','model':'gateway','sid':'7811dc64dbcd','short_id':'0','token':'EUBLpJ8Ghv4T7jn8','data':{'ip':'192.168.178.34'}} mihome.0 2018-02-11 15:43:19.887 debug RAW: {'cmd':'heartbeat','model':'gateway','sid':'7811dc64dbcd','short_id':'0','token':'zC29AVjz2NDqKygj','data':{'ip':'192.168.178.34'}} mihome.0 2018-02-11 15:43:13.939 debug redis pmessage io.mihome.0.devices.* io.mihome.0.devices.86sw2_158d000170ebe7.percent {'val':85.5,'ack':true,'ts':1518360193901,'q':0,'from':'system.adapter.mihome.0','lc':1518359254738} mihome.0 2018-02-11 15:43:13.939 debug redis pmessage io.mihome.0.devices.* io.mihome.0.devices.86sw2_158d000170ebe7.voltage {'val':3.055,'ack':true,'ts':1518360193900,'q':0,'from':'system.adapter.mihome.0','lc':1518359254737} mihome.0 2018-02-11 15:43:13.938 debug redis pmessage io.mihome.0.devices.* io.mihome.0.devices.gateway_7811dc64dbcd.rgb {'val':'#000000','ack':true,'ts':1518360193899,'q':0,'from':'system.adapter.mihome.0','lc':1518359097156} mihome.0 2018-02-11 15:43:13.937 debug redis pmessage io.mihome.0.devices.* io.mihome.0.devices.gateway_7811dc64dbcd.dimmer {'val':0,'ack':true,'ts':1518360193897,'q':0,'from':'system.adapter.mihome.0','lc':1518359097154} mihome.0 2018-02-11 15:43:13.937 debug redis pmessage io.mihome.0.devices.* io.mihome.0.devices.gateway_7811dc64dbcd.on {'val':false,'ack':true,'ts':1518360193895,'q':0,'from':'system.adapter.mihome.0','lc':1518359097152} mihome.0 2018-02-11 15:43:13.936 debug redis pmessage io.mihome.0.devices.* io.mihome.0.devices.gateway_7811dc64dbcd.illumination {'val':1265,'ack':true,'ts':1518360193894,'q':0,'from':'system.adapter.mihome.0','lc':1518360193894} mihome.0 2018-02-11 15:43:13.910 debug RAW: {'cmd':'read_ack','model':'86sw2','sid':'158d000170ebe7','short_id':17339,'data':{'voltage':3055}} mihome.0 2018-02-11 15:43:13.910 debug data: 158d000170ebe7(86sw2): {'voltage':3.055,'percent':85.5} mihome.0 2018-02-11 15:43:13.909 debug device: 158d000170ebe7(86sw2) mihome.0 2018-02-11 15:43:13.909 debug RAW: {'cmd':'read_ack','model':'gateway','sid':'7811dc64dbcd','short_id':0,'data':{'rgb':0,'illumination':1265,'proto_version':'1.0.9'}} mihome.0 2018-02-11 15:43:13.908 debug data: 7811dc64dbcd(gateway): {'illumination':1265,'on':false,'dimmer':0,'rgb':'#000000'} mihome.0 2018-02-11 15:43:13.864 debug RAW: {'cmd':'get_id_list_ack','sid':'7811dc64dbcd','token':'d2FX41x6Q6Fyxl8M','data':['158d0001f247d5','158d000170ebe7']} mihome.0 2018-02-11 15:43:13.466 debug RAW: {'cmd':'iam','port':'9898','sid':'7811dc64dbcd','model':'gateway','ip':'192.168.178.34'} mihome.0 2018-02-11 15:43:13.464 debug device: 7811dc64dbcd(gateway) mihome.0 2018-02-11 15:43:13.286 info starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.mihome, node: v6.12.2 mihome.0 2018-02-11 15:43:09.029 info terminating

Wo kann das Problem dabei liegen und wie kann ich dabei helfen dies zu lösen?

Object rewriting after adapter restarts

I noticed that object's state "native" section recreates ( empties ) after an adapter restarted. It's not good to me because I use this "native" section for storing some settings belonging to object to use in script. Is it possible to change such behavior?

Devices aren't recognized

Hi

I installed 1.0.7 on my ioBroker (ioBroker is up2date), installed teh Gateway using my Android phone, added 2 child devices (Temp and Body Sensor) and both sensors work well, show data in the phone app.

Then I installed the adapter, entered the key under general and also under my gateway's IP address

Adapter seem to work but when I check objects I only see teh gateway but no devices

Attached a screenshot from iobroker and an adapter log which shows that the 2 sensors send data to iobroker

Any idea why I can't see the devices?

Thanks in advance
Daniel
iobroker.log

Arara Cube can not connect with iobroker

Hello, i can't add my aqara cube in iobroker. i connected it in my mihome app on my phone but in iobroker:

mihome.0
2018-09-23 13:37:17.593
debug
RAW: {"cmd":"heartbeat","model":"gateway","sid":"7811dcb25413","short_id":"0","token":"Dzepen07ewMVfSnl","data":{"ip":"192.168.178.25"}}
mihome.0
2018-09-23 13:37:07.452
debug
RAW: {"cmd":"heartbeat","model":"gateway","sid":"7811dcb25413","short_id":"0","token":"zacKaMKzIxPI2KU2","data":{"ip":"192.168.178.25"}}
mihome.0
2018-09-23 13:36:58.606
warn
Could not add new sensor: Type "sensor_cube.aqgl01" is not valid, use one of Hub::sensorTypes
mihome.0
2018-09-23 13:36:58.601
debug
RAW: {"cmd":"read_ack","model":"sensor_motion.aq2","sid":"158d000276d3d1","short_id":19034,"data":{"voltage":3055,"lux":"66"}}
mihome.0
2018-09-23 13:36:58.598
debug
data: 158d000276d3d1(sensor_motion.aq2): {"voltage":3.055,"percent":85.5,"lux":66}
mihome.0
2018-09-23 13:36:58.593
debug
device: 158d000276d3d1(sensor_motion.aq2)
mihome.0
2018-09-23 13:36:58.590
debug
RAW: {"cmd":"read_ack","model":"magnet","sid":"158d00026a2ad8","short_id":58639,"data":{"voltage":3015,"status":"close"}}
mihome.0
2018-09-23 13:36:58.588
debug
data: 158d00026a2ad8(magnet): {"voltage":3.015,"percent":81.5,"state":false}
mihome.0
2018-09-23 13:36:58.587
debug
device: 158d00026a2ad8(magnet)
mihome.0
2018-09-23 13:36:58.585
debug
RAW: {"cmd":"read_ack","model":"magnet","sid":"158d00027b406f","short_id":21644,"data":{"voltage":3045,"status":"close"}}
mihome.0
2018-09-23 13:36:58.583
debug
data: 158d00027b406f(magnet): {"voltage":3.045,"percent":84.5,"state":false}
mihome.0
2018-09-23 13:36:58.582
debug
device: 158d00027b406f(magnet)
mihome.0
2018-09-23 13:36:58.580
debug
RAW: {"cmd":"read_ack","model":"magnet","sid":"158d00027b3d4a","short_id":43924,"data":{"voltage":3025,"status":"close"}}
mihome.0
2018-09-23 13:36:58.578
debug
data: 158d00027b3d4a(magnet): {"voltage":3.025,"percent":82.5,"state":false}
mihome.0
2018-09-23 13:36:58.574
debug
device: 158d00027b3d4a(magnet)
mihome.0
2018-09-23 13:36:58.570
debug
RAW: {"cmd":"read_ack","model":"magnet","sid":"158d00026a2ba6","short_id":12228,"data":{"voltage":3015,"status":"close"}}
mihome.0
2018-09-23 13:36:58.568
debug
data: 158d00026a2ba6(magnet): {"voltage":3.015,"percent":81.5,"state":false}
mihome.0
2018-09-23 13:36:58.567
debug
device: 158d00026a2ba6(magnet)
mihome.0
2018-09-23 13:36:58.565
debug
RAW: {"cmd":"read_ack","model":"magnet","sid":"158d00026a2b28","short_id":36656,"data":{"voltage":2995,"status":"close"}}
mihome.0
2018-09-23 13:36:58.560
debug
data: 158d00026a2b28(magnet): {"voltage":2.995,"percent":79.5,"state":false}
mihome.0
2018-09-23 13:36:58.559
debug
device: 158d00026a2b28(magnet)
mihome.0
2018-09-23 13:36:58.558
debug
RAW: {"cmd":"read_ack","model":"magnet","sid":"158d0001f3852d","short_id":47584,"data":{"voltage":3015,"status":"close"}}
mihome.0
2018-09-23 13:36:58.555
debug
data: 158d0001f3852d(magnet): {"voltage":3.015,"percent":81.5,"state":false}
mihome.0
2018-09-23 13:36:58.554
debug
device: 158d0001f3852d(magnet)
mihome.0
2018-09-23 13:36:58.552
debug
RAW: {"cmd":"read_ack","model":"magnet","sid":"158d0001c2e8d6","short_id":64810,"data":{"voltage":3015,"status":"close"}}
mihome.0
2018-09-23 13:36:58.549
debug
data: 158d0001c2e8d6(magnet): {"voltage":3.015,"percent":81.5,"state":false}
mihome.0
2018-09-23 13:36:58.545
debug
device: 158d0001c2e8d6(magnet)
mihome.0
2018-09-23 13:36:58.543
debug
RAW: {"cmd":"read_ack","model":"magnet","sid":"158d0001bf6226","short_id":26519,"data":{"voltage":3055,"status":"close"}}
mihome.0
2018-09-23 13:36:58.541
debug
data: 158d0001bf6226(magnet): {"voltage":3.055,"percent":85.5,"state":false}
mihome.0
2018-09-23 13:36:58.538
debug
device: 158d0001bf6226(magnet)
mihome.0
2018-09-23 13:36:58.536
debug
RAW: {"cmd":"read_ack","model":"magnet","sid":"158d0001c2e8b6","short_id":29131,"data":{"voltage":3025,"status":"close"}}
mihome.0
2018-09-23 13:36:58.533
debug
data: 158d0001c2e8b6(magnet): {"voltage":3.025,"percent":82.5,"state":false}
mihome.0
2018-09-23 13:36:58.527
debug
device: 158d0001c2e8b6(magnet)
mihome.0
2018-09-23 13:36:58.524
debug
RAW: {"cmd":"read_ack","model":"gateway","sid":"7811dcb25413","short_id":0,"data":{"rgb":0,"illumination":1292,"proto_version":"1.0.9"}}
mihome.0
2018-09-23 13:36:58.514
debug
data: 7811dcb25413(gateway): {"illumination":1292,"on":false,"dimmer":0,"rgb":"#000000"}
mihome.0
2018-09-23 13:36:58.502
debug
RAW: {"cmd":"get_id_list_ack","sid":"7811dcb25413","token":"3NhnsxACkeBVAi6Q","data":["158d0001c2e8b6","158d0001bf6226","158d0001c2e8d6","158d0001f3852d","158d00026a2b28","158d00026a2ba6","158d00027b
mihome.0
2018-09-23 13:36:58.482
debug
RAW: {"cmd":"iam","port":"9898","sid":"7811dcb25413","model":"gateway","ip":"192.168.178.25"}
mihome.0
2018-09-23 13:36:58.460
debug
device: 7811dcb25413(gateway)
mihome.0
2018-09-23 13:36:58.203
info
starting. Version 1.0.5 in /opt/iobroker/node_modules/iobroker.mihome, node: v6.14.4
mihome.0
2018-09-23 13:36:58.021
debug
statesDB connected
mihome.0
2018-09-23 13:36:57.772
debug
objectDB connected

whats up with the cube or with the adapter?

greedings

Adding Xiaomi Thermostat

Hello it is possible to add the Xiaomi Thermostat?
https://de.gearbest.com/robot-vacuum-accessories/pp_1306883.html?wid=1433363

Thank you.

Hallo ist es möglich den Xiaomi Thermostat hinzuzufügen?
Link siehe oben

Ich danke und Gruss

heartbeat timeout generates many log entries

The new heartbeat timeout leads to this log entries the whole day:
Is this ok and as expected?

mihome.0 | 2018-06-27 07:29:24.450 | info | Change connection status on timeout after 20000ms: false
mihome.0 | 2018-06-27 07:28:04.270 | info | Change connection status: true
mihome.0 | 2018-06-27 07:27:34.256 | info | Change connection status on timeout after 20000ms: false
mihome.0 | 2018-06-27 07:18:05.864 | info | Change connection status: true
mihome.0 | 2018-06-27 07:17:35.650 | info | Change connection status on timeout after 20000ms: false

Das wird nicht unterstüzt:

Es wird nicht der Long klick bei den eckigen wireless switchen unterstüzt...

MfG

Hamtaro

Adapter startet nicht

Hallo,

ich habe ein Problem beim Einrichten des Adapters. Ich bekomme den Gateway bzw. den Adapter nicht zum laufen. Der Gateway funktioniert unter der Mi HOME APP und wurde auch so eingestellt wie hier beschrieben. Anbei die Fehlermeldungen aus dem LOG vom iobroker:

host.iobroker	2018-01-16 18:28:33.556	error	instance system.adapter.mihome.0 terminated with code 0 (OK)
mihome.0	2018-01-16 18:28:33.539	info	terminating
mihome.0	2018-01-16 18:28:33.516	error	at Manager.ondecoded (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:332:8)
mihome.0	2018-01-16 18:28:33.516	error	at Manager.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
mihome.0	2018-01-16 18:28:33.516	error	at Manager. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15)
mihome.0	2018-01-16 18:28:33.516	error	at Socket.onpacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:236:12)
mihome.0	2018-01-16 18:28:33.516	error	at Socket.onack (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:312:9)
mihome.0	2018-01-16 18:28:33.516	error	at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1346:35)
mihome.0	2018-01-16 18:28:33.516	error	at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1458:21
mihome.0	2018-01-16 18:28:33.516	error	at /opt/iobroker/node_modules/iobroker.mihome/main.js:1055:21
mihome.0	2018-01-16 18:28:33.516	error	at startMihome (/opt/iobroker/node_modules/iobroker.mihome/main.js:1104:11)
mihome.0	2018-01-16 18:28:33.516	error	at new Hub (/opt/iobroker/node_modules/iobroker.mihome/lib/mihome/Hub.js:31:20)
mihome.0	2018-01-16 18:28:33.516	error	TypeError: function from() { [native code] } is not a constructor
mihome.0	2018-01-16 18:28:33.510	error	uncaught exception: function from() { [native code] } is not a constructor
mihome.0	2018-01-16 18:28:33.498	error	no key defined. Only read is possible
mihome.0	2018-01-16 18:28:33.391	info	starting. Version 1.0.2 in /opt/iobroker/node_modules/iobroker.mihome, node: v4.2.6
host.iobroker	2018-01-16 18:28:32.349	info	instance system.adapter.mihome.0 started with pid 2236

Danke für die Mühe.

Viele Grüße
Michael

Can you add the E27 tunable Lightbulb

Hi, I just paired the lightbulb to my gateway. I can control it in the MiHome App, but it wont show in the IOBroker objects. Can you include this? If you need any information from me, let me know!
Jan

Works the upgraded Version of the Xiaomi Gateway?

Works the upgraded Version of the Xiaomi Gateway?

Thanks Hamtaro

Instances status is constantly changing from green to yellow

Hello, what could it be, this is the adapter status under instance constantly changes from green to yellow. Once he says green and connected to the gateway and then he changes to yellow and says that he is not connected to the gateway. He makes this change every few seconds.

The status remains permanently green when "Connected to Host" and "Life Sign". When "Connected with MiHome" he always changes to red.

Wecker aus App hinzufügen

Hallo,
es wäre cool wenn man mit dem Adapter einen Wecker einstellen kann...mit den Wecktönen der App und wenn man den Wecker dann z.B. über einen Wirelesstaster wieder ausschalten kann.

LG

Hamtaro

Xiaomi switch click or double-click does not work

Hello, I have this Xiaomi Switch (https://de.gearbest.com/smart-light-bulb/pp_257679.html) and would like to embed it in ioBroker. Unfortunately he does not work. Is this switch supported?
This is my code:

on({id: "mihome.0.devices.switch_158d0001bc435e.click"/*Simple click*/, val: true}, function (obj) {
  var value = obj.state.val;
  var oldValue = obj.oldState.val;
  if (getState("mihome.0.devices.switch_158d0001bc435e.click").val == true) {
    setState("mihome.0.devices.gateway_7811dce1d544.on"/*Light*/, true);
    setState("mihome.0.devices.gateway_7811dce1d544.rgb"/*RGB*/, '#002BFF');
    setStateDelayed("mihome.0.devices.gateway_8632dce1d746.on"/*Light*/, false, 3000, false);
  }
})

Can you help me please?

Using two instances of the adapter

On Raspberry Pi3 ioBroker works. Raised two network interfaces - Lan (192.168.1.45) and WiFi (192.168.1.55)
The ioBroker.mihome adapter version 1.2.3 and two driver instances are installed - mihome.0 and mihome.1
Two gateways are connected to these two instances -
Xiaomi gateway3 (lumi-gateway-v3) with the address 192.168.1.71 is hanging on mihome.0 (192.168.1.45)
Aqara AC Partner (lumi-acpartner-v1) with the address 192.168.1.33 hangs on mihome.1 (192.168.1.55)
All sensors (movement, temperature, sockets, switches) are interfaced with the first gateway (on mihome.0)
If I run both instances of mihome.0 and mihome.1, then I get an error in the log "Error: bind EADDRINUSE 0.0.0.0:9898"
in spite of the fact that in settings there are addresses 192.168.1.45 and 192.168.1.55
Then I stop the instance of mihome.0 to which the sensors and other devices are connected and start the instance of mihome.1 -
and I get an unexpected result - in the objects of the mihome.1 instance I see devices associated with mihome.0
Tell me, maybe I don’t understand / do something wrong - in my opinion, the error "Error: bind EADDRINUSE 0.0.0.0:9898" should not be here,
then it is impossible to use two copies of the adapter?

Device request

Is it possible to and the Aqara Smart Motion Sensor device.
Link:
https://de.gearbest.com/smart-home-controls/pp_009661787808.html
Logfile:

mihome.0	2018-08-31 17:30:59.129	debug	RAW: {"cmd":"heartbeat","model":"gateway","sid":"7811dcdeaf46","short_id":"0","token":"8tdJBYnfQdNYNAud","data":{"ip":"192.168.0.185"}}
mihome.0	2018-08-31 17:30:57.253	warn	Could not add new sensor: Type "vibration" is not valid, use one of Hub::sensorTypes
mihome.0	2018-08-31 17:30:57.253	debug	RAW: {"cmd":"read_ack","model":"sensor_switch.aq2","sid":"158d0002130b06","short_id":13795,"data":{"voltage":3105}}
mihome.0	2018-08-31 17:30:57.253	debug	data: 158d0002130b06(switch): {"voltage":3.105,"percent":90.5}
mihome.0	2018-08-31 17:30:57.253	debug	device: 158d0002130b06(switch)
mihome.0	2018-08-31 17:30:57.253	debug	RAW: {"cmd":"read_ack","model":"sensor_motion.aq2","sid":"158d000236a7f2","short_id":7070,"data":{"voltage":3035,"lux":"35"}}
mihome.0	2018-08-31 17:30:57.253	debug	data: 158d000236a7f2(sensor_motion.aq2): {"voltage":3.035,"percent":83.5,"lux":35}
mihome.0	2018-08-31 17:30:57.253	debug	device: 158d000236a7f2(sensor_motion.aq2)
mihome.0	2018-08-31 17:30:57.253	debug	RAW: {"cmd":"read_ack","model":"gateway","sid":"7811dcdeaf46","short_id":0,"data":{"rgb":0,"illumination":1292,"proto_version":"1.1.2"}}
mihome.0	2018-08-31 17:30:57.237	debug	data: 7811dcdeaf46(gateway): {"illumination":1292,"on":false,"dimmer":0,"rgb":"#000000"}
mihome.0	2018-08-31 17:30:57.237	debug	RAW: {"cmd":"get_id_list_ack","sid":"7811dcdeaf46","token":"q1TklyCcjTSzuPe8","data":["158d000236a7f2","158d0002130b06","158d0002a925ef"]}
mihome.0	2018-08-31 17:30:57.237	debug	RAW: {"cmd":"iam","port":"9898","sid":"7811dcdeaf46","model":"gateway","proto_version":"1.1.2","ip":"192.168.0.185"}
mihome.0	2018-08-31 17:30:57.237	info	Change connection status: true
mihome.0	2018-08-31 17:30:57.237	debug	device: 7811dcdeaf46(gateway)
mihome.0	2018-08-31 17:30:57.191	info	Change connection status: false
mihome.0	2018-08-31 17:30:57.175	info	starting. Version 1.0.7 in C:/ioBroker/node_modules/iobroker.mihome, node: v10.5.0
mihome.0	2018-08-31 17:30:57.034	debug	statesDB connected
mihome.0	2018-08-31 17:30:57.019	debug	objectDB connected
host.RITS-PC	2018-08-31 17:30:56.597	info	instance system.adapter.mihome.0 started with pid 13872

Kind regards

device icons

Hi,
thank you for this great adapter! I've a small idea for the future, because the icons of the devices are in Iobroker-Admin/Objects and some Adapters like Material, not clear to see - white icons of a white background... my question, it's possible to make a frame or the background of the Icons or the background of the field in admin in another color?? so the contrast is better?

Second thing, the icons of the "weather" devices are not correct, these are taken from fritz.dect-heating devices..
screenshot here: