0.0.5 docker image version is supported it.
1 Like
Thanks. Can you update your miio version to the latest?
The latest supports zoned cleaning (“app_zoned_clean”)
for roborock vacuums.
Thanks!
Is there a logs on webpage?
Looks like below.
2020-03-31 12:29:34 info Requested to control by ST >> yeelink.light.color1[{“id”:“511111”,“cmd”:“power”,“data”:“on”}]
If there is no logs it’s something wrong settings.
Check your smartapp address
And it must be a local address.
ex) 192.168.1.100:30000
I have no idea.
Did you select a right address on mi connector setting web page?
I just add that model to mi connector.
Re download a 0.0.5 or latest image & Update a smartapp.
Re download a 0.0.5 or latest image & Update a smartapp.
I just add that model to mi connector.
I don’t know if it’s working like lumi.gateway.v3
No logs in mi connector webpage when I try to turn on ceiling light.
But if I open other yeelight , It shows log in webpage
So I think it’s not address problem
But I found docker log when I try to turn on xiaomi ceiling light 1 and 5 ( same error log for both light)
2019-12-12 04:28:54 error: Control >> Error!!! TypeError: Cannot read property ‘target’ of undefined
Error
at router.post (/usr/src/app/routes/control.js:12:54)
at Layer.handle [as handle_request] (/usr/src/app/node_modules/express/lib/router/layer.js:95:5)
at next (/usr/src/app/node_modules/express/lib/router/route.js:137:13)
at isAuthenticated (/usr/src/app/routes/dashboard.js:21:12)
at Layer.handle [as handle_request] (/usr/src/app/node_modules/express/lib/router/layer.js:95:5)
at next (/usr/src/app/node_modules/express/lib/router/route.js:137:13)
at Route.dispatch (/usr/src/app/node_modules/express/lib/router/route.js:112:3)
at Layer.handle [as handle_request] (/usr/src/app/node_modules/express/lib/router/layer.js:95:5)
at /usr/src/app/node_modules/express/lib/router/index.js:281:22
at Function.process_params (/usr/src/app/node_modules/express/lib/router/index.js:335:12)
at next (/usr/src/app/node_modules/express/lib/router/index.js:275:10)
at Function.handle (/usr/src/app/node_modules/express/lib/router/index.js:174:3)
at router (/usr/src/app/node_modules/express/lib/router/index.js:47:12)
at Layer.handle [as handle_request] (/usr/src/app/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/usr/src/app/node_modules/express/lib/router/index.js:317:13)
at /usr/src/app/node_modules/express/lib/router/index.js:284:7
I hope it can help you fix this problem
Thank you
Yes, everything was working fine for months until I updated the docker.
It’s different url from ST to Nas & from Nas to ST.
It looks like a address problem.
When you control a device, nas could’t get a message from st.
Your st hub and nas is same network?
If there is no token part in config.json
paste the content below
“token”: {
“value”: “”,
“enable”: false
}
Then restart a docker container.
I run MI connector on Raspberry PI 3 and It is on same network with ST hub.
Actually , I can control it for months but just cannot use it around October.
But other Yeelight connect with same MI connector and same ST hub have no problem.
So I added that to the config.json and get the same error:
ubuntu@ubuntu-server:/docker/mi-connector$ sudo cat /docker/mi-connector/config.json
"token": {
"value": "xxxxxx",
"enable": false
}
This is also the error I see in the logs:
2020-04-01 05:10:34 [Mi-Connector] info: WebSocket init
2020-04-01 05:10:35 [Mi-Connector] info: Initiallize Ping Processor
2020-04-01 05:10:35 [Mi-Connector] info: ********************************
2020-04-01 05:10:35 [Mi-Connector] info: Mi Connector Version: 0.0.5.1
2020-04-01 05:10:35 [Mi-Connector] info: ********************************
2020-04-01 05:10:35 [Mi-Connector] error: Read Config File Error!!!!! >> SyntaxError: /config/config.json: Unexpected token : in JSON at position 7
It’s empty config.
Just remove a config.json then restart a docker container.
Have a look a dashboard.
If there is a Yeelight on ‘Not Initialized Xiaomi Devices’, it cannot to be connected it.
If it is token is changed or other problem.
Remove a Yeelight on mi home app then re add it again.
Also take a new token from mi home.
I already try many times to remove it and then add it to Mi Home again but still face problem.
On dashboard , it shows initialized successful and If I turn ceiling light by other method I can still see status of it in ST but just cannot control it.
I have no idea.
If i can connect your pc? nas? raspberry? or by teamviewer
I might be find something wrong.
OK. I will add that function on later.
1 Like
Hi, what could be the problem when the Roborock S5 do not automatically add into the smart thing app on the phone?
Server on NAS is up, Vacuum is added, SmartApps and DTH are ok. And the smart app is installed on the phone. I reach the server from this app and from website.
something I have missed?