-
-
Notifications
You must be signed in to change notification settings - Fork 36
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 for Eufy S1 Pro #83
Comments
Mine arrives Tuesday, also happy to help get this working |
Me too |
Depends on #68 |
They promised to think about supporting matter. So we'll see. UPS says it should be here tomorrow. For starters, I can do without the HA integration. |
I got mine set up and running. Integration sees the device but no entities. Happy to help with integration/ testing if you need a guinea pig. |
Same here, I received mine and can help out with testing. |
Does this work with the S1? |
I also would like the S1 Pro to be integrated. The current setup only shows a single sensor with no feedback. |
Depending on how active that PR is, I'll either keep pushing through on my fork or integrate directly into that PR with my codes for the S1 Pro |
Would love to have my S1 Pro integrated. I can help testing or buy coffee for support. :-) |
I talked to customer service last week and they confirmed that the S1 Pro is not matter compatible and that there is no schedule for this compatibility, so I don't think it's comming anytime soon. Hopefully we can add the S1 Pro to this integration! |
Has there been any movement on this? |
+1 |
+1 Just received mine yesterday. 😕 |
do you guys think, there will be a update on this? |
See #68 (comment) |
will there be support for the s1 pro in home assistant not homey |
@MasonColoretti if you follow the link I shared you'll see that multiple devs are working on it |
The S1 Pro is currently recognized but only as device. It has no entities at all.
Do you plan to support the S1 Pro as well or maybe need some help with testing when you are working on it?
The text was updated successfully, but these errors were encountered: