Replies: 2 comments 2 replies
-
Why were Sensors removed in #129 ? |
Beta Was this translation helpful? Give feedback.
2 replies
-
Thank you for the info! Really appreciate your work.
On Wed, Jan 18, 2023 at 5:06 PM Barrett Palmer ***@***.***>
wrote:
…
On Wed, Jan 18, 2023 at 8:06 AM Joshua Mulliken ***@***.***>
wrote:
> They were removed because it was hammering the Wyze servers and they
> threatened to shut down all of our access if we didn't reduce the load
>
> —
> Reply to this email directly, view it on GitHub
> <#166 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABIOZVV6ONBMXG7LW76JENDWTAIHTANCNFSM44R6FLTQ>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***
> com>
>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
With PR 5 in Wyzeapy, Wyze sensor (v1) implementation is super simple:
binary_sensor.py
It would also make sense to rename
class WyzeCameraMotion()
toclass WyzeSensor()
, andcameras
tosensor
inasync_setup_entry()
As an option, a new class can be introduced parallel to WyzeCameraMotion(). Or in fact, the following classes could be introduced:
class WyzeCameraMotion
: Binary Sensor: motionclass WyzeCameraSound
: Binary Sensor: soundclass WyzeCameraFire
: Binary Sensor: gas ([Feature Request] Fire alarm / Co2 Alarm #161) (EDIT) - hard to reverse engineer; need to set off alarm :-)class WyzeCameraCo2
: Binary Sensor: smoke ([Feature Request] Fire alarm / Co2 Alarm #161) (EDIT) - hard to reverse engineer; need to set off alarm :-)class WyzeContactSensor
: Binary Sensor: door (or window, or opening)class WyzeMotionSensor
: Binary Sensor: motionContact and Motion sensors would benefit from exposing RSSI and Battery level. Learnings can be made from fork I think.
Opinions or proposed way forward?
Beta Was this translation helpful? Give feedback.
All reactions