Hi there,
I bought a Xiaomi Smart Plug 2 Wi-Fi device. This not per default included in the Xiaomi Mi IO binding, but following the instructions in the MI io bindings documentation, I was able to create the JSON database file for the device model cuco.plug.v2eur.
Where can I share the database file for the new device?
@marcel_verpaalen
best to make a github issue for it, and confirm if all channels are working as expected
Will do! Thanks!
Github enhancement
1 Like
Hey, I brought this kind of smart plug and I dont know how to use the json file or where to put it. Can you guys help me with this?
thanks!
@Miko_Mark
I shared the JSON database file here.
According to the documentation under " Advanced: adding local database files to support new devices", you need to drop the file under openhab/misc/miio (on my raspi /etc/openhab/misc/miio). Please then follow the instructions.
Add support for Xiaomi Mijia Thermostatic Kettle 2 Pro (MJJYSH01YM) yunmi.kettle.v19
Coming back to this after quite some time…
I recognized, that after reboot, the devices are all set to UNINITIALIZED. When I disable and then enable the device on the web interface, they do work.
In the log files, I see the following entry:
2024-11-14 22:55:05.649 [INFO ] [internal.handler.MiIoAbstractHandler] - Mi Device model cuco.plug.v2eur identified as: Unknown Mi IO Device (unknown). Does not match thingtype miio:generic. Changing thingtype to miio:unsupported
2024-11-14 22:55:05.696 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key miio:generic:device1 in ManagedThingProvider, because it does not exists.
@marcel_verpaalen Is that a known issue or is there a solution to this?
Ok, checked the logs when I manually disable and then enable the device. The first entry shows up as well
2024-11-14 23:03:39.324 [INFO ] [internal.handler.MiIoAbstractHandler] - Mi Device model Unknown Mi IO Device (unknown) identified as: miio:unsupported, thingtype miio:basic. Does not matches thingtype miio:unsupported. Unexpected, unless manual override.
But the device now goes ONLINE and works. I guess my actual problem is that after reboot, the device is set to UNINITIALIZED…