-
Notifications
You must be signed in to change notification settings - Fork 502
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
Bosch ZigBee Wireless Motion Detector RFDL-ZB-MS #2289
Comments
Can you please provide additional info as described in the wiki? Also, please make sure having the attributes read before taking the screenshots. |
Is there any insigt in when the next build will be done? I don't want to be pushing anyone, but i just want to know when the next build will be. The last one was from over 2 months ago, and i'm ready to test the fix. |
You may want to compile the current version yourself and give it a try? |
I would like to do this, but it's not that easy. But what should be te expected behaviour? |
Well, from your initial post, I conclude you do not see any sensors exposed through deconz' REST API and therefore also not in Hass.io. |
Does anyone know whether the RFDL-ZB-MS is identical to the model sold as Smart Home motion sensor https://www.bosch-smarthome.com/uk/en/shop?url=products/smart-system-solutions/motion-detector ? |
So i compiled the latest version and runned the rest plugin into a virtual machine: I removed the old Deconz integration from home assistant. All my sensors are now added, but I can't find a new motion sensor. Am i looking into the wrong place? Or is there anything i'm missing ? |
Did the sensor search give you a green indication of a successful pairing process with the Bosch sensor? Have you queried the deconz REST API for all sensors and double checked? |
Hm, can you double check in deconz GUI (IAS Zone cluster) if the sensor is enrolled? Also, please check deconz REST API if the state changes there. |
I'm afraid the screenshots are not much of a help since they neither show the read attributes of the IAS Zone cluster nor answer the question, if you've checked the REST API. |
Thanks for the screenshot, that one is workable. It is strange that it hasn't been enrolled automatically (which should have happened). I can check the code once mor to see if I've overlooked something. You can have a look here regarding API usage: #2373 (comment) |
Did you have a momment to check if there was an issue in the code ? I'm not technical enough I think to enroll it manually |
Yes, but haven't spotted anything suspicious so far.
This is really just like 3 clicks and typing the MAC address of your conbee/raspbee in there. Looks worse than it is. I'm dependent on you with this since I don't have that device, otherwise I cannot really help. |
That doesn't sound too bad, great. Say, do you get reasonable battery readings from your device? My feeling would say no. |
I don't get any battery readings. |
Already prepared an update. |
Cool! |
Available already in my repo, so go for it. |
It seems this issue is resolved. If it is not, please re-open or create another issue. |
I'll have a look later. Anyway, thanks for confirming! |
@SwoopX any change of pointing me in a direction ? |
This one drowned, sorry for that. Can you please read the IAS cluster attributes of both? I'd assume the missing ones are not enrolled. |
Hm, that's odd. You could try entering sensor search in Phoscon again and trigger one of the problematic devices my provocing motion. In addition to that, it might be a good idea to push the physical button on the device. Alternatively, you may want to try removing the batteries and re-inserting them while searching for sensors. |
I tried to pair a couple of Bosch zigbee motion detectors.
I was hoping it would work out of the box as the devices should support Zigbee HA1.2:
https://zigbeealliance.org/zigbee_products/radion-tritech-zb-4/
For the Zigbee2mqtt project there has also been a request:
Koenkk/zigbee2mqtt#769
It pairs ok, but not shure what i need to do to get it working.
Ultimate i want to connect it to Home Assistant.
The text was updated successfully, but these errors were encountered: