Request for integration with Tuya

Feature requests
121

Voilà, ‹ no candidate ›

[2026-08-01T11:48:56.692Z] [INFO] [tuya] [Tuya][media] movement_detect_pic event fired (device=ext:ext-dev-tuya-2:device:bf0e59548489fcb4ea62of)
[2026-08-01T11:48:56.927Z] [WARN] [tuya] [Tuya][media] no candidate host served the movement_detect_pic snapshot (device=ext:ext-dev-tuya-2:device:bf0e59548489fcb4ea62of)
[2026-08-01T11:48:56.928Z] [WARN] [tuya] [Tuya][media] no candidate host served the movement_detect_pic snapshot (device=ext:ext-dev-tuya-2:device:bf0e59548489fcb4ea62of)
[2026-08-01T11:48:59.226Z] [WARN] [tuya] [Tuya][media] no candidate host served the movement_detect_pic snapshot (device=ext:ext-dev-tuya-2:device:bf0e59548489fcb4ea62of)
[2026-08-01T11:49:10.358Z] [WARN] [tuya] [Tuya][media] no candidate host served the movement_detect_pic snapshot (device=ext:ext-dev-tuya-2:device:bf0e59548489fcb4ea62of)
[2026-08-01T11:49:19.402Z] [WARN] [tuya] [Tuya][media] no candidate host served the movement_detect_pic snapshot (device=ext:ext-dev-tuya-2:device:bf0e59548489fcb4ea62of)
[2026-08-01T11:49:29.578Z] [WARN] [tuya] [Tuya][media] no candidate host served the movement_detect_pic snapshot (device=ext:ext-dev-tuya-2:device:bf0e59548489fcb4ea62of)

However, I have a ton of lines (every 10 seconds, it tries to fetch the image)!

122

@GBoulvin, thank you so much!!

Your log was exactly what was needed — thank you! :folded_hands: It’s clear: the motion image is stuck on download, not on decryption.

  • The ring gives you a complete pre-signed URL → image OK :white_check_mark:
  • The motion gives you a Tuya reference (?param=…) that S3 storage refuses (403) → not downloadable this way. Decryption, on the other hand, is ready on the code side — it’s just waiting for us to know how to retrieve the file.

I also fixed the spam (the no candidate every 10 seconds): update :dev-doorbell one last time, these lines should disappear.

:right_arrow: You can switch your doorbell to prod (:latest) safely: ring + ring image + motion event + live-view, everything is there and stable. The motion image becomes a small research project on my side (resolving the Tuya download URL) — I’ll keep you posted if I unlock it, it will also benefit PTZ cameras. Thank you again for your golden tests! :rocket:

123

Voilà!

Spam cleared:

image
image715×179 20.7 KB

No issue with this feature on my end since it triggers at the slightest movement (car, person, but also cat and moving leaf), so not used daily.

Kudos to Claude for the development and to you for the guidance and perseverance :wink:

124

It was with great pleasure!! This might lead me to go to Action after all :sweat_smile:

Looking forward to new adventures ^^

125

:joy: :joy: :joy:

126

A small thing, now that I’m putting it into practice and could have said earlier. The selector in the scenes isn’t intuitive for the doorbell:

image
image521×271 7.47 KB

But what category does it fall under? Zero urgency!

127

@Terdious we need to add the supported_options here! (PR Gladys + PR Tuya if not already handled)

128

Proposal made (feat(device-feature): add a DOORBELL category with a RING type by Terdious · Pull Request #2745 · GladysAssistant/Gladys · GitHub) to add a new category ‹ doorbell › / a new type ‹ ring › with the idea of being able to have related actions / visuals later => example totally « not worked on », a box like the one for the camera dedicated to doorbells (or conversely the same box with automatic detection) => I’m thinking of automatic association with a vibrating bell, a little motion detection man, a blinking light, one day if possible the activation of a microphone if dual stream is possible etc… ^^

In short, this new category leaves the door open for core automations later!

EDIT: Just published, already labeled!! I love it :heart_eyes:

129

… And already reviewed!!

130

for a doorbell, that’s normal, right? :joy:

131

:rofl: :smiling_face_with_three_hearts: