Skip to content
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

[Device Support Request] Eglo CONNECT-Z SENSOR, Zigbee PIR sensor IP44 #2164

Closed
simlun opened this issue Feb 3, 2023 · 3 comments
Closed
Labels
stale Issue is inactivate and might get closed soon support This request is likely unrelated to quirks and more of a support ticket (e.g. network issues)

Comments

@simlun
Copy link

simlun commented Feb 3, 2023

Is your feature request related to a problem? Please describe.

Suport for Eglo Connect-Z Zigbee PIR sensor IP44

I own a couple of art nr 99106 sold in Sweden.

I'm using Home Assistant and ZHA in my home setup and it doesn't pick up my device at all when I scan for new devices.

I'm a software developer and I bought a ConBee II to being able to debug and add this Eglo PIR sensor to ZHA, but I don't know how to get started adding quirks and whatnot so I can use my Eglo PIR sensors at home. I don't know what to install to get started, nor the workflow to add new devices.

Please help me getting started and contribute to ZHA.

Best regards
Simon Lundmark

@simlun simlun changed the title [Device Support Request] Eglo Zigbee PIR sensor IP44 [Device Support Request] Eglo CONNECT-Z SENSOR, Zigbee PIR sensor IP44 Feb 3, 2023
@TheJulianJES TheJulianJES added the support This request is likely unrelated to quirks and more of a support ticket (e.g. network issues) label Feb 3, 2023
@TheJulianJES
Copy link
Collaborator

Is there anything in the logs when you try to pair the devices? Quirks generally don't affect pairing at all.

@DaseineWesen
Copy link

I have the same problem as well, the sensor won´t show up, nether in the logs nor in the dashboard or the device list.

@github-actions
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale Issue is inactivate and might get closed soon label Aug 24, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issue is inactivate and might get closed soon support This request is likely unrelated to quirks and more of a support ticket (e.g. network issues)
Projects
None yet
Development

No branches or pull requests

3 participants