Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Setup * start sensor search * press both buttons until LEDs start to blink Button events * left button: 1002 * right button: 2002 * both buttons: 3002 Issues #249 #165
- Loading branch information
Showing
1 changed file
with
37 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!!!
I've built the latest greatest following the readme instructions (even using 2.04.85 packages).
Once done, I restarted. The version shown in the settings is 2.04.84, is it normal?
I think I can make the aqara switch join the network (it seems to blink properly) but unfortunately nothing show up in the interface.
Am I doing something wrong?
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To build the latest commits replace:
git checkout -b mybranch V2_04_84
with
git checkout -b mybranch master
otherwise you'll get only commits up to 2.04.84.
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok thanks, indeed I think I've built the plugin to 2.04.85 now (shows up in the interface). I checked the de_web_plugin.cpp file and I had the latest file.
But unfortunately the switch still doesn't appear in the interface when I add it.
I feel stupid to ask, but the "sensor search" is started from the "devices" menu, right?
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The switch currently only shows up in the REST API not in the app interface. It will be added to show up in devices/switches (Phoscon app).
Yes currently there is no wizard available for the switch so it must be added via
devices > sensors > Add new sensor > Other
. On success there should be a messageSensor ready
.From there custom rules must be created via REST API. It will take some time until this is supported via Phoscon app since, unlike other switches the Xiaomi switch doesn't control a group to which lights can be added, therefore integration takes more time here.
Later on we want to add an editor which allows to specify actions for any button of any switch. This will make configuring switches a lot easier than the current group based limited approach.
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@manup thanks.
I must be missing something still that you think is obvious ;) But I'm very basic... I see no sensors submenu anywhere in the webinteface (which I guess is the Phoscon app as you call it).
So I guess there is another "menu" I should be able to access (from the command line?). Or maybe I need to update the web interface to a higher version.
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry my bad, thought you refer to the new beta Phoscon app.
In the "old" webapp you need to open the network via
Menu > Settings > Open Network
; then add the switch as described above. But it will be only visible in the REST API not the webapp itself.e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No problem @manup ;) I requested an invite on the new beta app.
In the mean time, I'm following the REST API doc :)
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello :-), I've got a single button version of the Aqara switch here and it doesn't seem to be detected.
If tried to make some sense of the changes made to the code above and it seems like the only difference would be the number of buttons and the ModelID.
If you'd like I could probably send more information about the switch.
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please provide the model id as reported in basic cluster.
I think it should be enough to add the model id on various places.
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm guessing that the model_id would then be: 0x7816?
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The other two hex numbered devices are Aqara door sensors.
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, it is the field Model.
Here:
lumi.sensor_86sw2
If it is not visible you may need to rejoin the switch.
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The model field is empty. I did install the beta 2.04.85, with te master version of the
deconz-rest-plugin
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it visible in the basic cluster view?
(click on second circle of the switch node)
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is saying only this; which looks nothing like lumi.sensor_86sw2
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nearly there :) now open the "Cluster info" panel from menu and click on the "Basic" cluster
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can see it in the rest api :) now I can create my first rule, yay!
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The model id is also empty there, but I also tried the reset factory button and I think it is decoupled now or something.
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oke I've tried to fetch the information from a bulb
and it worked. trying the switch again
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Jeeej found it :-D, I had to add it again.
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
excellent :) I'll add it
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:-D, Wow thank you
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@manup sorry to bother again, I can create a rule which seems correct (I even use the ep id for the BIND event), but I cannot get it to work.
Do you have an example of a rule that works with this button?
Thanks!
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a single button with only buttonevent value 1002?
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How can I check this for you?
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is te result:
Before press:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 312 100 312 0 0 3870 0 --:--:-- --:--:-- --:--:-- 4216
{
"config": {
"on": true,
"reachable": true
},
"ep": 1,
"etag": "baa02b3bb25ed9ac68ad9bd2bdb405a1",
"manufacturername": "LUMI",
"mode": 1,
"modelid": "lumi.sensor_86sw1",
"name": "lumi.sensor_86sw1 15",
"state": {
"buttonevent": 1002,
"lastupdated": "2017-11-04T19:14:12"
},
"type": "ZHASwitch",
"uniqueid": "00:15:8d:00:01:2a:34:44-01-0006"
}
After pressing:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 312 100 312 0 0 4534 0 --:--:-- --:--:-- --:--:-- 4875
{
"config": {
"on": true,
"reachable": true
},
"ep": 1,
"etag": "92434baa2a93a98e50b3aff433e67bb2",
"manufacturername": "LUMI",
"mode": 1,
"modelid": "lumi.sensor_86sw1",
"name": "lumi.sensor_86sw1 15",
"state": {
"buttonevent": 1002,
"lastupdated": "2017-11-04T19:15:08"
},
"type": "ZHASwitch",
"uniqueid": "00:15:8d:00:01:2a:34:44-01-0006"
}
e395207
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I had to get rid of the BIND for a PUT and it works perfect :)