-
Notifications
You must be signed in to change notification settings - Fork 597
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lumi.ctrl_ln2.aq1 not recognised by mi connect #43
Comments
Sorry, forgot to give you the log entry when I try to register the device with ST: Get Device State TypeError: deviceMap[id].target.state is not a function Error at It just looks like mi_connector hasn't been able to ID the device type successfully and has just allocated it as a generic/unknown device. |
Been playing in the docker image (couldn't find sources), to see if I could find the problem and it looks like two changes are required to get lumi.ctrl_ln2.aq1 devices to work: 1. /usr/src/app/node_modules/miio/lib/devices/gateway/subdevices.js following entry needs to be added to the module.exports: 2. /usr/src/app/miio/miio.js - line 384 Change Maybe fison76 could verify this and add it properly. |
Maybe this 64? is a new model. Thanks much. |
Hi,
I'm having issues connecting a lumi.ctrl_ln2.aq1 to mi connect. Here is what appears to happen:
In the Mi Home app (Hub info page) the device is identified as :{"model":"lumi.ctrl_ln2.aq1","did":"lumi.158d00023b265c","name":"Hall Light"}
When this is pulled into the mi connector application, on the page Add device [ST] it comes up as follows:
Then I attempt to register the device, mi connect throws an error. This doesn't happen for any other devices (I also have a lumi.ctrl_neutral2 which works fine).
Any thoughts?
Thank you
PS: Fantastic tool.
NB: The gateway tokens now appear in the "Hub info" page of the Mi Home app once the wireless communication protocol, so no need to try to strip them out of the DB any more.
The text was updated successfully, but these errors were encountered: