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

PIR Motion Sensor - Manufacturer ID _TZE200_3towulqd TS0601 no motion detected #780

Open
TzK069 opened this issue Mar 6, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@TzK069
Copy link

TzK069 commented Mar 6, 2024

It senses motion (turns red) but it not reports in the homey pro 2023

image

@TzK069 TzK069 added the bug Something isn't working label Mar 6, 2024
@Boechie
Copy link

Boechie commented Apr 8, 2024

There is development going on for this device. See PR #724 and #740. Maybe those PRs will solve this.

@MartinSjoberg
Copy link

MartinSjoberg commented Apr 30, 2024

Hi Guys. I am having the same issue described above with the sensor. I am on app version v0.2.25test. Is the above mentioned PRs not released yet or is there a problem with them? Thank you for your work.

@Wuma68
Copy link

Wuma68 commented May 7, 2024

Hi again to all, it seams that all work on this have stoped at februari or is it still going on without our knowledge! :)

@MartinSjoberg
Copy link

Yeah well 503 open issues and 5 issues closed the last month. Too bad it looks like a nice little sensor :-) I guess the maintainers are to few and overworked.

@Boechie
Copy link

Boechie commented May 7, 2024

@Wuma68 @MartinSjoberg Yes development is still going on. Multiple people including @MihaiINW (my colleague) and @maccyber are working on it. See PR #724 and #740 . The problem is that there are apparently 2 different hardware versions of the device, but they both report as the same device. The solutions from both PRs work (for 1 of the hardware versions each), but we are still figuring out how to merge them. So for now only 1 hardware version is supported. Apparently you have the other unsupported hardware version. In our company we use many (>40) of these devices and it turns out we have a mix of both hardware versions. So having a proper solution that supports both version is of great importance to ourselves. The problem is that development capacity to do work for free is very scarce...

@MartinSjoberg
Copy link

No worries. Just tell me if I can help with anything. I have no exprience with adding sensors to homey though. :-)

@Wuma68
Copy link

Wuma68 commented May 7, 2024

Exactly no worries, we are just glad that someone working on it.

@Boechie Is the config only stored in driver or is it moved to device after you have set up a new device?

@ericvanbeurden
Copy link

Confirmed, experiencing the same bug.
Device is recognized however doesn't give any alarms.
I will wait until the next update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Development

No branches or pull requests

5 participants