Hi,
I had to reconfigure my devices, means no communication was possible and I reset my Yeelight bolor bulb (4pcs) and Xiaomi robot.
Mi Home (installed on mobile devie) was used to connect them again - control is possible.
Now I used tool “MiToolkit 1.4” to read new tokes from mobile device - but they are the same.
Before I have used MiServer “China Mainland” and tried to change to “Germay”.
Only vac cleaner was found, but when reading tokes, all have be shown and they are same as for China mainland server.
In additon no yeelight.has been found.
Those tokens did not work - any idea how to fix problem with old tokes / find new token ?
Thanks for your reply
Markus
Hi Marcel thank you for the really astonishing work with this binding, I can confirm that yeelight color bulb 2 is working with model string “yeelink.light.color2”.
I had some trouble at the begging, but was my bad, I pasted the wrong token and manually set the device model string that was blank and nothing was working than I read the post and your tip about checking “show properties”.
This drove me back to the right way, thank you again.
One last thing is there a way to extract the token from Yeelight app? The point is that Yeelight color bulb 2 seem to work only with MiHome china server and there is no straight way with this setting to use the light with Alexa
I might be mistaken, but I think that is not going to help you much,
The discovery in OH will discover the token as well (similar as this tool does). However, most devices don’t provide their tokens anymore. (they do provide it after a reset, but the token gets changed once you update the wifi settings, hence useless.)
Nowadays, one easy way to get the token is by using the hacked mihome app, which will have the token in the screen. Alternatively downgrade to old version and get the miio2.db from a backup to extract the token…
The easiest way to obtain tokens is to browse through log files of the Mi Home
app version 5.4.49 for Android. It seems that version was released with debug
messages turned on by mistake. An APK file with the old version can be easily
found using one of the popular web search engines. After downgrading use a file
browser to navigate to directory SmartHome/logs/plug_DeviceManager, then
open the most recent file and search for the token. When finished, use Google
Play to get the most recent version back.
I found this really easy way to extract tokens from Yeelight app, you need to be rooted.
Use root explorer and look for miot.xml, open the file with a text editor and in the device list you can find the tokens.
Hi I’m facing this problem both of my yeelight bulb are rebooting time by time, at least every 4 hours, uninstalled the binding and the problem is gone… Any tip?
Thanks in advance
Pls update the binding to the latest (snapshot) version. This is an unfortunate bug in the 2.4 version. (some devices don’t like message ID 0 and reboot)
Is there a wiki where I can see what commands I can send the Yeelight devices? I’m having difficulty creating rules to bind to my wireless switches / motion sensors
Hi, for a while ive been using the MI IO binding with a yeelight color bulb. i get this strange behaviour where, while its on, it randomly after a while, sets itself to red and 100 brightness. i have no idea what is causing this. it happens maybe every hour or so. is this maybe the same issue MrCupola had before?
I have troubles extracting the token from the Yeelight app. I’ve tried:
extracting SQLight db from com.yeelight.cherry, but the device.db->device does not have token column
using miio npm lib - the token changes after the Yeelight app gets paired with the bulb, so no use
Do you have any alternative ways? I have successfully extracted the Roborock token out of Mi Home app, but this Yeelight token is a myster for me! I have yeelink.light.color1
Solution: the token of the yeelight App is stored in this file (root required):
com.yeelight.cherry/shared_prefs/miot.xml. You can just open this file with a editor or notepad, its not a database like miio2.db.
In BasicUI, the Colormode channel of the yeelight gives a warning:
[WARN ] [ui.internal.items.ItemUIRegistryImpl] - Exception while formatting value '2' of item LivingroomR_colorMode with format '%.0f': f != java.lang.String
its defined as a String, while it outputs numbers.
could this also be a reason for the errors im experiencing with resetting of colormode?
Hi, for a while ive been using the MI IO binding with a yeelight color bulb. i get this strange behaviour where, while its on, it randomly after a while, sets itself to red and 100 brightness. i have no idea what is causing this. it happens maybe every hour or so. is this maybe the same issue MrCupola had before?