Activity

1. rytilahti commented on May 21, 2025

   

   rytilahti

   on May 21, 2025

   Member

   More actions

   Probably related to #1498
2. DaveGut commented on Jul 11, 2025

   

   DaveGut

   on Jul 11, 2025

   More actions

   I bought a D210 and am working on a HUbitat Environment integration. Found out some interesting things about this and other Battery Powered cameras/doorbells (based on D210 and C425 devices).
   Discovery port

   • 20004 instead of 20002.
   • Has status data unencrypted in the interface. This includes last)alarm_time. I assume you have to then get the last_alarm_type (motion,etc) from the encrypted interface.
     Https and Transport protocols are the same and the API is the same (but some adds, some deletes based on the component capability list).
3. rytilahti commented on Jul 13, 2025

   

   rytilahti

   on Jul 13, 2025

   Member

   More actions

   Hi @DaveGut, interesting findings, thanks for reporting!

   If you wish, feel free to create pull requests to 1) add port 20004 to the discovery, and 2) to contribute a fixture file that can help to extend the support.
4. DaveGut commented on Jul 22, 2025

   

   DaveGut

   on Jul 22, 2025

   More actions

   I am not a python coder. Use Java on the Hubitat platform. For whoever handles this issue (if anyone), the battery powered implementation really messes things up. Evidence is on the Doorbell, but there are now battery cameras out there. Need to manage user expectations if implementating.
   Battery implementation deficiencies (still playing - but look good for now).

   1. Last Alarm Info is NOT updated, either in the 20004 message nor the port 80 API message.
   2. If on battery, no ONVIF/RTSP protocol supported. Documentation says supported if wired doorbell.
   3. You can not use Amazon Alexa as a detection event surrogate. The camera becomes not reachable almost after installing (this may be transient - it worked several days ago and now there are a LOT of complaints on the tagged on the AMAZON TAPO Skill.

   I am still investigating controlling the chime either through the Camera or also directly (it is on wifi and is discovered by the 10002 mesage (selecting chime-type is supported, but activate from integration??), Still recovering from severe disappointment.

   I have tested all of the comands and could regenerate the responses for someone to place in the library. Some of the command execute; howeever, the underlying data does not update. Includes lastAlarmInfo and setAlarmConfiguration. Battery issue????? They may work on the camera when wired to the house????

   Update. You can get the motion or ring based on the setting of setWakeupConfig(motion, ring). When doing the UDP 20004 message returns sleep (true/false) when it transitions to false, the device was awaken by the set wake configuration (trigger). I nave not found a way to do both and the alert messages in that message are only set once in a whild for some reason.
5. github-actions commented on Oct 22, 2025

   

   github-actionsBot

   on Oct 22, 2025 – with GitHub Actions

   More actions

   There hasn't been any activity on this issue recently. This issue has been automatically marked as stale because of that. It will be closed if no further activity occurs.
   Please make sure to update to the latest python-kasa version and check if that solves the issue.
   Thank you for your contributions.
6. github-actions

   added

   stale

   on Oct 22, 2025
7. github-actions

   closed this as not plannedon Oct 29, 2025