-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
support Osram Smart+ Motion Sensor? #507
Comments
No, but can be if you have the device and follow: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices |
I recently got one, but it failed while pairing. Tried several factory resets and button presses but kept getting the following error msg:
The sensor blinks blue (searching network) followed by green every other time (indicating successful pairing) and then keeps repeating this sequence after some seconds. Which DEBUG parameters would be helpful to debug? |
I created a log file with DEBUG=cc-znp, would this be helpful? @Koenkk |
Okt 23 15:49:22 raspberrypi npm[602]: zigbee2mqtt:debug 2018-10-23 15:49:22 Check online 0x00124b0014d9dafa 0x00124b0014d9dafa Saving state to file /opt/zigbee2mqtt/data/state.json { |
@kirovilya do you know why these |
@salopette please provide full debug logfile via for pairing please refer to this: https://images-eu.ssl-images-amazon.com/images/I/C18QWX-dFxS.pdf
it could be that you have to keep the device on wakeup by press the button e.g. every second on pairing process themselve. please test again and report. |
I have tried the button-press-keep-awake method. but the device doesnt look like it goes to sleep. it starts repairing after some seconds, well before we get the 10s timeout message in the log file I can get my hands on a fresh spare CC2530 module in a few days, then I can provide a full log with only this motion sensor |
Any news on this? |
I was able to use
does it help? |
@Koenkk anything I can do to help? |
This device probably requires an enroll request (as explained here: zigbeer/zigbee-shepherd#8). As I don't have the device, it is hard for me to work further on this. |
What do you need to get it working? Is a ssh session to my server useful to get it working? Or a teamviewer session? |
@ToTXR4Y can you check if joining works in the: https://github.com/Koenkk/zigbee2mqtt/tree/osram_motion branch? |
@Koenkk looks like it's connected! 😃
|
Tried to write a converter but I couldn't get it to trigger any kind of message... |
Can you try with {
zigbeeModel: ['Motion Sensor-A'],
model: 'Motion Sensor-A',
vendor: 'OSRAM',
description: 'Motion detector',
supports: 'occupancy',
fromZigbee: [],
toZigbee: [],
configure: (ieeeAddr, shepherd, coordinator, callback) => {
const device = shepherd.find(ieeeAddr, 1);
const actions = [
(cb) => device.write('ssIasZone', 'iasCieAddr', coordinator.device.getIeeeAddr(), cb),
(cb) => device.functional('ssIasZone', 'enrollRsp', {enrollrspcode: 0, zoneid: 23}, cb),
];
execute(device, actions, callback, 1000);
},
}, |
awesome 😄 I am now working on the converters
|
Great! 😄 |
As of now I got this working. Still showing "Failed to configure" despite working.... 🤔 Also: I don't know what the tampering flag does... When you press the button for longer than 2 sec it will flip to false but switches back to true immediately after releasing the button. Shouldn't it be the other way round? 😅 According to the manual it should reset the device when presssing 10s, but as I see this, it just sends this flag, no reset possible other than removing the battery. |
Can you provide the log with |
(So many loglines with 12 devices in this network 😅) I could isolate it to the following lines, if you need more just let me know
|
Can you check again with the updated https://github.com/Koenkk/zigbee2mqtt/tree/osram_motion branch. Please repair the device. |
Fantastic work @Koenkk!
After removing and (somehow) pairing the device again, I had to restart zigbee2mqtt before receiving any messages. But now it looks very good. Should I send you a pull request to zigbee-shepherd-converters? In the devices.js file I had two additional line for temperature reporting, copied those off another device at first and I'm not sure the are necessary? But they dont generate any error message either...
|
Looks good, you can keep the bind and report for What does tamper/battery_low mean? How do you get to these messages? For the battery I would prefer a % (to keep it the same as other devices) |
See https://www.nxp.com/docs/en/user-guide/JN-UG-3077.pdf page 459 has a table of flags for |
Tamper should be an "opening" detection of the device itself. |
Can't really see any switch or detection mechanism on the inside @ToTXR4Y |
I second the mentioned behavior in NOT edge, but most recent stable on most recent Hass.IO on firmware 24122018: https://hastebin.com/repifinoga.apache |
@Morphy99 maybe it's not paired correctly? Try repairing it. One note though, I think the instructions given in the manual are not correct, holding the button for >10sec did nothing for me. |
I've done that a few times, I even had the red/purple light you mention but no I idea what that means. AFAIK the pairing mode is when the blue light flashes three times then once it connects it goes to solid green for a second and then off. This is all I get:
|
Ok it's connected finally! I removed the device by sending the
|
Yeah, pairing the motion sensor is a real pain. Took me about 30 minutes to finally get it working. Now it runs fine and gives back motion and temperature. (And thus one thing more than before via Osram Gateway linked to Hass.IO) |
To all: we need some help in order to verify a change which could have impact on this device. Could you check when changing https://github.com/Koenkk/zigbee2mqtt/blob/master/lib/zapp/cie.js#L12 to cieClusters.init('ssIasZone', 'dir', {value: 1}); this device still works? Please re-pair after making this change. |
@Koenkk, Received: Timed out after 10000; Cheers, |
@wossix thanks for testing, when changing it back, does it work again? |
@Koenkk, yes. |
@wossix thanks, we will leave it as is. :) |
* Implement zapp-cie. Koenkk/zigbee2mqtt#507 * Cleanup cie app. Koenkk/zigbee2mqtt#507 * Update package.json * Update zigbee.js
@dreimer1986 How did you managed to pair? I can't make it. Starting from fresh plugged cc2531, fresh shepherd instance (ioBroker in my case). Broker only says "Cannot get the Node Descriptor of the Device (Timed out after 10000ms)" Did some sniffing:
Then it starts again...
Anyone an idea why it does not pair? |
I removed any instance to be found from .db and repaired and it ... just worked then? RePair is a mix of Pushing the button while pluggin in the battery and some fast pushing of the button, I got it by luck... |
How does it look with the sensor? supported devices are listed with. {"id":21,"type":"EndDevice","ieeeAddr":"0x000d6f000f7109a2","nwkAddr":12943,"manufId":4174,"epList":[1,2],"status":"offline","joinTime":null,"endpoints":{"1":{"profId":260,"epId":1,"devId":1026,"inClusterList":[0,1,3,32,1026,1280,2821],"outClusterList":[25],"clusters":{}},"2":{"profId":260,"epId":2,"devId":263,"inClusterList":[0,1,3,1030,2821],"outClusterList":[3],"clusters":{}}},"_id":"JsDtgd6tedXIn12N"} |
Hi, Any News? kind regards |
Yesterday I completely deleted the zigbee2mqtt folder and set everything up again. And the motion detector was immediately recognized correctly |
I got only iobroker.zigbee installed, then i reinstalled it, deleted the zigbee-shepherd-converters folder like in the referred issue. flashed my cc2531 with the latest prod image available. still get "cannot get node descriptor" :( is ther another folder i can delete? or db files? to try this? i´ll tried with zigbee2mqtt and it connects fine, but shows only temperature? not occupancy?
|
Same here.
|
Retry again and again until it finally works. This sensor is a bitch to pair. I had to do so last week, too after I killed my SD card and lost some stuff. Result: I tinkered around... 30 minutes? I removed all entries of the sensor from db while addin inactive and then restart it. At that time the sensor was/has to be without battery, then push the button and put the battery back in. Green LED lighting is a good sign, but as I said... took ages here to pair it properly. Seems like the sensor does strange stuff with the original gateay to be that easily paired. (But many OSRAM devices do funny things, like the lightify 4 way switch...) |
Hi @dreimer1986 , thanks for your reply.
I'm going to try to enable more logging to try to get as much information as possile |
I have a similar issue as @gabrieleantonini : zigbee2mqtt version 1.5.1 (commit #ac3b924)
Any suggestion? |
* Add initial OSRAM Smart+ Motion Sensor support Add zigbeeModel ['Motion Sensor-A'] with converters 'ias_zone_motion_dev_change' and 'ias_zone_motion_status_change'. Note: genPowerCfg maybe not working! See Issue: Koenkk/zigbee2mqtt#507 Co-Authored-By: Koen Kanters <koenkk@users.noreply.github.com> * fix eslint errors * Update fromZigbee.js * Update devices.js * Update devices.js * Update devices.js * Update devices.js
Hello, is Osram Smart + Motion Sensor supported?
https://www.osram-lamps.de/ekatalog/smart-home/smart-home-komponenten/smart-motion-sensor/index.jsp
The text was updated successfully, but these errors were encountered: