That’s good to hear, thanks for your feedback.
Hi, try to compare Token in your camera configuration and the one in App’s Diagnostics Log when motion is detected.
Search for “-- Event detected” and then see the token sent from NVR.
If I recall correctly, I had to change VideoSourceToken00x to VideoSourceConfigurationToken00x.
Thanks so much — you were right! Changed the Token field from VideoSourceToken00X to VideoSourceConfigurationToken00X and motion detection is working again after being broken for ~2 months. For anyone else finding this thread: the token strings can appear to “match” numerically in the Diagnostics Log without actually triggering anything — only after making this change did I see “Event Trigger” / “Turned off event alarm” lines appear, which is what actually updates the Motion Alarm capability. Really appreciate you posting this fix!
Did you manage to take a look at my log @Adrian_Rockall ?
What is the IP address of the doorbell?
I can see 4 IP address, so it would be easier to wade through I can narrow down the IP.
10.0.1.29 is the doorbell cam.
I can’t see anything unusual in the log and it appears that everything is working, even getting one snapshot succesfully.
The snapshot URL is unusual as it points to a server on the internet and not the local camera, so it’s possible that is only a temporary image that is captured when the camera detects motion or someone presses the button and then disappears soon after.
Is this a battery powered device?
I have seen that many battery powered devices go to sleep to conserve power and only wake up when something happens. That can cause timing issues with starting the live stream as the camera is not ready when Homey tries to connect.
In that case I don’t know. The only snapshot record in the log is:
9:21:31.950: Snapshot URL: http://www.########.com/manage/Upload/Pic/20147914514701.jpg
9:21:31.975: Registering Now image (10.0.1.29)
9:21:31.993: registered Now image (10.0.1.29)
9:21:32.014: SnapShot save file (10.0.1.29) = eventimageurn_uuid_06435685_0dd2_21b2_a205_4a1783502455.jpg
9:21:32.028: Initialising event image (10.0.1.29)
9:21:32.045: Fetching event image (10.0.1.29)
9:21:32.057: Fetching (10.0.1.29) Motion Event image with no Auth from: http://www.########.com/manage/Upload/Pic/20147914514701.jpg
9:21:32.609: Live video stream to URL: rtsp://10.0.1.29:8554/Streaming/Channels/101
9:21:32.621: Setting Live video stream to rtsp://#########@10.0.1.29:8554/Streaming/Channels/101
9:21:32.870: SnapShot fetch result (10.0.1.29): Status: true, Message: OK, Code: 200
9:21:32.884: Event Image Updated (10.0.1.29)
9:21:34.886: Registering event image (10.0.1.29)
9:21:34.911: registered event image (10.0.1.29)
So it appears that everything is fine when the doorbell is added.
Could you send another log after you see those errors?
Recreated the errors and just send you a new log.
Anything i can test with the visitor detection (doorbell press), as this one isn’t working too.
I can see one problem. The snapshot URI URL is redirected to a web page that returns OK, but no image.
If you open that page do you see any image?
Can you login to that website and see an image?
If you can, then do you use the same credentials as for the camera?
For the live feed, can you try opening the stream in VLC or ffplay using the same URL as shown in your log?
The website returns nothing but a blank page. Google states that Gwelltimes is Chinese a IOT video company.
Rtsp stream is not playing in VLC with the url in the log. The url in the log does work in Surveillance Station.
That doesn’t surprise me as it is probably a Chinese product.
If that the case then I doubt Homey can play it as I believe it uses the VLC video engine. Maybe you can find out if there is a secondary stream in a different codec and use that by adding the URL to the Homey device advanced setting.
Is it a Yoosee camera?
That has developer Gwell
https://play.google.com/store/apps/developer?id=Gwell&hl=en
These apps are usually filed heavily with ads and subscriptions (because the cameras barely make any profit since they’re so cheap). I know at least YI and the V-series apps (V360 Pro, V380, V380 Pro) all have that. Probably they don’t have ONVIF support to push you toward the cloud subscription or the ads inside the app.
Edit: hardware appears to be the same as V380, which is a heavily ad-filled app with very long ads everywhere. Does Yoosee have any ads?
I give up. I’ll maybe try to find another stream. Thnx for the help Adrian!
@smarthomesven It’s not a Yoosee camera, it’s a Marmitek doorbell with camera (Buzz LO).
