Nest Doorbell v1 Issues

It initially works in homekit, but then I start to get this error and am unable to view the feed:
ffmpeg audio talkback streaming process for "Front Door" stopped unexpectedly. Exit code was "0"
Also HKSV isn't working with the same doorbell. I enabled the option in the plugin config so maybe it's the wrong ffmpeg parameters being sent to homekit, preventing recording?
Please let me know how I can provide more verbose logs.
Thank you!

Thanks for reaching out. Are you able to tell me what release version you are using and also if via Hombridge or docker version?
More verbose logging can be enabled in both, Homebridge via Settings/Startup & Environment/Homebridge Debug Mode or Docker version, via "Debug" option in configuration

I am using v0.2.2, and the docker release (latest tag).
I specified the ffmpeg location as /usr/local/bin/ffmpeg and my other wired nest camera works fine.

Thanks for that information. The docker version has an ffmpeg binary in Nest_accfactory/dist and you shouldn't need to specific its location.
Are you able to enabled debug and send its output? I'm sure we can get the bottom. Most of my development on this was done with a Nest Hello v1 also

Thanks for that information. The docker version has an ffmpeg binary in Nest_accfactory/dist and you shouldn't need to specific its location.
Are you able to enabled debug and send its output? I'm sure we can get the bottom. Most of my development on this was done with a Nest Hello v1 also

I apologize, I'm using the homebridge docker container and homebridge-nest-accfactory is installed as a plugin. That is why I had to specify the ffmpeg location.
Here are the debug logs:
[10/11/2024, 4:18:02 PM] [homebridge-nest-accfactory] Successfully authorised using Google account
[10/11/2024, 4:18:02 PM] [homebridge-nest-accfactory] Starting REST API subscribe for connection uuid "xxx"
[10/11/2024, 4:18:02 PM] [homebridge-nest-accfactory] Loaded protobuf support files for Protobuf API
[10/11/2024, 4:18:02 PM] [homebridge-nest-accfactory] Starting Protobuf API trait observe for connection uuid "xxx"
[10/11/2024, 4:18:04 PM] [homebridge-nest-accfactory] HomeKitDevice module using Homebridge backend for "Dining Room"
[10/11/2024, 4:18:04 PM] [homebridge-nest-accfactory] Using Protobuf API as data source for "Dining Room" from connection uuid "xxx"
[10/11/2024, 4:18:04 PM] [homebridge-nest-accfactory] HomeKitDevice module using Homebridge backend for "othercamera camera"
[10/11/2024, 4:18:04 PM] [homebridge-nest-accfactory] Using Protobuf API as data source for "othercamera camera" from connection uuid "xxx"
[10/11/2024, 4:18:04 PM] [homebridge-nest-accfactory] HomeKitDevice module using Homebridge backend for "Front Door"
[10/11/2024, 4:18:04 PM] [homebridge-nest-accfactory] Using Protobuf API as data source for "Front Door" from connection uuid "xxx"
[10/11/2024, 4:18:04 PM] [homebridge-nest-accfactory] Setup Nest Cam (wired) as "othercamera camera"
[10/11/2024, 4:18:04 PM] [homebridge-nest-accfactory]   += HomeKit Secure Video support
[10/11/2024, 4:18:04 PM] [homebridge-nest-accfactory] Using WebRTC streamer for "othercamera camera"
[10/11/2024, 4:18:04 PM] [homebridge-nest-accfactory] Setup Nest Doorbell (wired, 1st gen) as "Front Door"
[10/11/2024, 4:18:04 PM] [homebridge-nest-accfactory]   += HomeKit Secure Video support
[10/11/2024, 4:18:04 PM] [homebridge-nest-accfactory] Using WebRTC streamer for "Front Door"
[10/11/2024, 4:18:04 PM] [homebridge-nest-accfactory] Started buffering for uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/11/2024, 4:18:04 PM] [homebridge-nest-accfactory] Connection started to Google Home Foyer
[10/11/2024, 4:18:04 PM] [homebridge-nest-accfactory] Setup Nest Learning Thermostat (3rd gen) as "Dining Room"
[10/11/2024, 4:18:04 PM] [homebridge-nest-accfactory] Restarting REST API subscribe for connection uuid "xxx"
[10/11/2024, 4:18:04 PM] [homebridge-nest-accfactory] Connection established to Google Home Foyer
[10/11/2024, 4:18:04 PM] [homebridge-nest-accfactory] Sending WebRTC offer for uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/11/2024, 4:18:05 PM] [homebridge-nest-accfactory] WebRTC offer agreed with remote for uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/11/2024, 4:18:05 PM] [homebridge-nest-accfactory] Playback started from WebRTC for uuid "DEVICE_F0EF8XXXXXXXXXX" with session ID "vHJUBYlRXDmpkgoKAAiSWigaIAEQ"
[10/11/2024, 4:18:35 PM] [homebridge-nest-accfactory] Live stream started on "Front Door" with two-way audio
[10/11/2024, 4:18:35 PM] [homebridge-nest-accfactory] Started live stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with two-way audio and sesssion id of "0a44107a-0535-4633-ad5b-edbea4b520fb"
[10/11/2024, 4:18:36 PM] [homebridge-nest-accfactory] Input #0, h264, from 'pipe:0':
  Duration: N/A, start:<PHONE_NUMBER>.491675, bitrate: N/A

[10/11/2024, 4:18:36 PM] [homebridge-nest-accfactory]   Stream #0:0: Video: h264 (Main), yuvj420p(pc, bt709, progressive), 1600x1200 [SAR 1:1 DAR 4:3], 25 fps, 60 tbr, 1200k tbn

[10/11/2024, 4:18:36 PM] [homebridge-nest-accfactory] Input #1, aac, from 'pipe:3':
  Duration: N/A, bitrate: 10 kb/s

[10/11/2024, 4:18:36 PM] [homebridge-nest-accfactory]   Stream #1:0: Audio: aac (LC), 48000 Hz, mono, fltp, 10 kb/s

[10/11/2024, 4:18:36 PM] [homebridge-nest-accfactory] Stream mapping:
  Stream #0:0 -> #0:0 (copy)
  Stream #1:0 -> #1:0 (aac (native) -> aac (libfdk_aac))

[10/11/2024, 4:18:36 PM] [homebridge-nest-accfactory] Output #0, rtp, to 'srtp://<IP_ADDRESS>:61698?rtcpport=61698&pkt_size=1378':
  Metadata:
    encoder         : Lavf61.1.100
  Stream #0:0: Video: h264 (Main), yuvj420p(pc, bt709, progressive), 1600x1200 [SAR 1:1 DAR 4:3], q=2-31, 25 fps, 60 tbr, 90k tbn

[10/11/2024, 4:18:36 PM] [homebridge-nest-accfactory] Output #1, rtp, to 'srtp://<IP_ADDRESS>:53189?rtcpport=53189&localrtcpport=37837&pkt_size=188':
  Metadata:
    encoder         : Lavf61.1.100
  Stream #1:0: Audio: aac (ELD), 16000 Hz, mono, s16, 24 kb/s
      Metadata:
        encoder         : Lavc61.3.100 libfdk_aac

[10/11/2024, 4:18:36 PM] [homebridge-nest-accfactory] [rtp @ 0x7ffed458bab0] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly

[10/11/2024, 4:18:36 PM] [homebridge-nest-accfactory] [vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 21224, current: 19175; changing to 21224. This may result in incorrect timestamps in the output file.
[vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 21224, current: 19541; changing to 21224. This may result in incorrect timestamps in the output file.
[vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 21224, current: 20630; changing to 21224. This may result in incorrect timestamps in the output file.
[vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 21224, current: 21007; changing to 21224. This may result in incorrect timestamps in the output file.

[10/11/2024, 4:18:36 PM] [homebridge-nest-accfactory] [vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133189; changing to 136165. This may result in incorrect timestamps in the output file.

[10/11/2024, 4:18:36 PM] [homebridge-nest-accfactory] [vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133337; changing to 136165. This may result in incorrect timestamps in the output file.
[vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133338; changing to 136165. This may result in incorrect timestamps in the output file.
[vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133339; changing to 136165. This may result in incorrect timestamps in the output file.
[vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133339; changing to 136165. This may result in incorrect timestamps in the output file.
[vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133340; changing to 136165. This may result in incorrect timestamps in the output file.

[10/11/2024, 4:18:36 PM] [homebridge-nest-accfactory] [vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133340; changing to 136165. This may result in incorrect timestamps in the output file.
[vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133344; changing to 136165. This may result in incorrect timestamps in the output file.

[10/11/2024, 4:18:36 PM] [homebridge-nest-accfactory] [vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133345; changing to 136165. This may result in incorrect timestamps in the output file.
[vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133345; changing to 136165. This may result in incorrect timestamps in the output file.

[10/11/2024, 4:18:36 PM] [homebridge-nest-accfactory] [vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133346; changing to 136165. This may result in incorrect timestamps in the output file.

[10/11/2024, 4:18:36 PM] [homebridge-nest-accfactory] [vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133349; changing to 136165. This may result in incorrect timestamps in the output file.
[vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133356; changing to 136165. This may result in incorrect timestamps in the output file.

[10/11/2024, 4:18:36 PM] [homebridge-nest-accfactory] [vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133361; changing to 136165. This may result in incorrect timestamps in the output file.

[10/11/2024, 4:18:36 PM] [homebridge-nest-accfactory] [vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133366; changing to 136165. This may result in incorrect timestamps in the output file.
[vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133394; changing to 136165. This may result in incorrect timestamps in the output file.

[10/11/2024, 4:18:36 PM] [homebridge-nest-accfactory] [vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133396; changing to 136165. This may result in incorrect timestamps in the output file.
[vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133396; changing to 136165. This may result in incorrect timestamps in the output file.

[10/11/2024, 4:18:36 PM] [homebridge-nest-accfactory] [vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133397; changing to 136165. This may result in incorrect timestamps in the output file.

[10/11/2024, 4:18:37 PM] [homebridge-nest-accfactory] [vost#0:0/copy @ 0x7ffed4971350] Non-monotonic DTS; previous: 136165, current: 133397; changing to 136165. This may result in incorrect timestamps in the output file.

[10/11/2024, 4:18:45 PM] [homebridge-nest-accfactory] Stopped live stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/11/2024, 4:18:45 PM] [homebridge-nest-accfactory] Live stream stopped from "Front Door"
[10/11/2024, 4:22:53 PM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/11/2024, 4:22:53 PM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/11/2024, 4:23:02 PM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/11/2024, 4:23:02 PM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/11/2024, 4:23:05 PM] [homebridge-nest-accfactory] Restarting REST API subscribe for connection uuid "xxx"
[10/11/2024, 4:23:07 PM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/11/2024, 4:23:07 PM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/11/2024, 4:23:19 PM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/11/2024, 4:23:19 PM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/11/2024, 4:23:29 PM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/11/2024, 4:23:29 PM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/11/2024, 4:23:38 PM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/11/2024, 4:23:38 PM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/11/2024, 4:28:07 PM] [homebridge-nest-accfactory] Restarting REST API subscribe for connection uuid "xxx"
[10/11/2024, 4:28:08 PM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/11/2024, 4:28:08 PM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/11/2024, 4:28:16 PM] [homebridge-nest-accfactory] Live stream started on "Front Door" with two-way audio
[10/11/2024, 4:28:16 PM] [homebridge-nest-accfactory] Started live stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with two-way audio and sesssion id of "82f87adb-2157-4bd5-bfbb-89e0567323b1"
[10/11/2024, 4:28:17 PM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/11/2024, 4:28:17 PM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[HDS fe80::102f:433d:de00:50cf%eth0] Delegate finished recording stream 1 without sending anything out.        Reason was "TIMEOUT"
[HDS fe80::102f:433d:de00:50cf%eth0] Delegate finished recording stream 1 without sending anything out.        Reason was "TIMEOUT"
[HDS fe80::102f:433d:de00:50cf%eth0] Delegate finished recording stream 1 without sending anything out.       Controller will CANCEL.
[10/11/2024, 4:28:52 PM] [homebridge-nest-accfactory] [in#0/sdp @ 0x7fff163f42f0] Error during demuxing: Operation timed out

[10/11/2024, 4:28:52 PM] [homebridge-nest-accfactory] [aost#0:0/libopus @ 0x7fff16391030] No filtered frames for output stream, trying to initialize anyway.

[10/11/2024, 4:28:52 PM] [homebridge-nest-accfactory] [libopus @ 0x7fff163f6c70] No bit rate set. Defaulting to 96000 bps.
Output #0, data, to 'pipe:1':
  Metadata:
    title           : HomeKit Audio Talkback
    encoder         : Lavf61.1.100
  Stream #0:0: Audio: opus, 48000 Hz, stereo, s16, 96 kb/s
      Metadata:
        encoder         : Lavc61.3.100 libopus

[10/11/2024, 4:28:52 PM] [homebridge-nest-accfactory] [out#0/data @ 0x7fff162e5330] video:0KiB audio:0KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: unknown
[out#0/data @ 0x7fff162e5330] Output file is empty, nothing was encoded(check -ss / -t / -frames parameters if used)

[10/11/2024, 4:28:52 PM] [homebridge-nest-accfactory] size=       0KiB time=N/A bitrate=N/A speed=N/A

[10/11/2024, 4:28:52 PM] [homebridge-nest-accfactory] ffmpeg audio talkback streaming process for "Front Door" stopped unexpectedly. Exit code was "0"
[10/11/2024, 4:28:52 PM] [homebridge-nest-accfactory] Stopped live stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/11/2024, 4:28:52 PM] [homebridge-nest-accfactory] Live stream stopped from "Front Door"
[10/11/2024, 4:33:08 PM] [homebridge-nest-accfactory] Restarting REST API subscribe for connection uuid "xxx"
[10/11/2024, 4:33:59 PM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/11/2024, 4:33:59 PM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/11/2024, 4:34:07 PM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/11/2024, 4:34:07 PM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[HDS fe80::102f:433d:de00:50cf%eth0] Delegate finished recording stream 1 without sending anything out.       Controller will CANCEL.
[10/11/2024, 4:34:12 PM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/11/2024, 4:34:12 PM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/11/2024, 4:34:21 PM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/11/2024, 4:34:21 PM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[HDS fe80::102f:433d:de00:50cf%eth0] Delegate finished recording stream 1 without sending anything out.       Controller will CANCEL.
[10/11/2024, 4:34:32 PM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/11/2024, 4:34:32 PM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/11/2024, 4:34:40 PM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/11/2024, 4:34:40 PM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"

Ok thanks for that information. Out of interest, has your Nest Hello v1 been migrated to the Google Home preview?

Ok thanks for that information. Out of interest, has your Nest Hello v1 been migrated to the Google Home preview?

Yes it has been migrated. Also I did end up getting a single HKSV recording but that was all. When I restart homebridge/homebridge-nest-accfactory, everything works as expected initially but it stops working after a few minutes.

I'll look into it more over the weekend. I'm pretty sure missed something then (as dont have a migrated one enrolled in HomeKit) with migrated cameras. might reach out for some testing of things if thats ok

I'll look into it more over the weekend. I'm pretty sure missed something then (as dont have a migrated one enrolled in HomeKit) with migrated cameras. might reach out for some testing of things if thats ok

Absolutely, I'll respond as quickly as I can 👍

@n0rt0nthec4t it got the homekit recording, which is awesome! Still getting some errors though:
[10/12/2024, 8:29:12 AM] [homebridge-nest-accfactory] Live stream started on "Front Door" with two-way audio
[10/12/2024, 8:29:12 AM] [homebridge-nest-accfactory] Started live stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with two-way audio and sesssion id of "a836dccd-11fe-4e8d-8f95-74f6637fb616"
[10/12/2024, 8:29:21 AM] [homebridge-nest-accfactory] Unsupported reconfiguration request for live stream on "Front Door"
[10/12/2024, 8:29:22 AM] [homebridge-nest-accfactory] Input #0, sdp, from 'pipe:0':
[10/12/2024, 8:29:22 AM] [homebridge-nest-accfactory] N/A, bitrate: N/A
[10/12/2024, 8:29:22 AM] [homebridge-nest-accfactory] Stream mapping:
[10/12/2024, 8:29:33 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 8:29:33 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 8:29:33 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 8:29:47 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 8:29:47 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 8:29:52 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 8:29:52 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 8:29:52 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 8:30:02 AM] [homebridge-nest-accfactory] [in#0/sdp @ 0x7fffb25ac2f0] Error during demuxing: Operation timed out
[10/12/2024, 8:30:02 AM] [homebridge-nest-accfactory] [aost#0:0/libopus @ 0x7fffb2549030] No filtered frames for output stream, trying to initialize anyway.
[10/12/2024, 8:30:02 AM] [homebridge-nest-accfactory] [libopus @ 0x7fffb25aec70] No bit rate set. Defaulting to 96000 bps.
[10/12/2024, 8:30:02 AM] [homebridge-nest-accfactory] [out#0/data @ 0x7fffb249d330] video:0KiB audio:0KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: unknown
[10/12/2024, 8:30:02 AM] [homebridge-nest-accfactory] ffmpeg audio talkback streaming process for "Front Door" stopped unexpectedly. Exit code was "0"

Nope, it stopped working again after a few minutes.
[10/12/2024, 11:40:32 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:40:32 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:40:32 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:40:43 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:40:43 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:40:54 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:40:54 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:40:54 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:41:05 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:41:05 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:42:43 AM] [homebridge-nest-accfactory] Restarting Protobuf API trait observe for connection uuid "a6dd555b-c2e0-4b2b-8460-5600a4870d9c"
[10/12/2024, 11:43:23 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:43:23 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:43:23 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:43:34 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:43:34 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:43:40 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:43:40 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:43:40 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:43:51 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:43:51 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:44:02 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:44:02 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:44:02 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:44:13 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:44:13 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:44:26 AM] [homebridge-nest-accfactory] Restarting REST API subscribe for connection uuid "a6dd555b-c2e0-4b2b-8460-5600a4870d9c"
[10/12/2024, 11:47:45 AM] [homebridge-nest-accfactory] Restarting Protobuf API trait observe for connection uuid "a6dd555b-c2e0-4b2b-8460-5600a4870d9c"
[10/12/2024, 11:48:44 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:48:44 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:48:44 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:48:55 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:48:55 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:49:00 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:49:00 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:49:00 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:49:12 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:49:12 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:49:23 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:49:23 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:49:23 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:49:27 AM] [homebridge-nest-accfactory] Restarting REST API subscribe for connection uuid "a6dd555b-c2e0-4b2b-8460-5600a4870d9c"
[10/12/2024, 11:49:34 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:49:34 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:50:25 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:50:25 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:50:25 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:50:36 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:50:36 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:50:41 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:50:41 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:50:41 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:50:53 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:50:53 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:51:03 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:51:03 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:51:03 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:51:15 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:51:15 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:51:36 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:51:36 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:51:36 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:51:47 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:51:47 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:52:31 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:52:31 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:52:31 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:52:43 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:52:43 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:52:48 AM] [homebridge-nest-accfactory] Restarting Protobuf API trait observe for connection uuid "a6dd555b-c2e0-4b2b-8460-5600a4870d9c"
[10/12/2024, 11:52:48 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:52:48 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:52:48 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:53:00 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:53:00 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:53:11 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:53:11 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:53:11 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:53:22 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:53:22 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:54:27 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:54:27 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:54:27 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:54:28 AM] [homebridge-nest-accfactory] Restarting REST API subscribe for connection uuid "a6dd555b-c2e0-4b2b-8460-5600a4870d9c"
[10/12/2024, 11:54:38 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:54:38 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:54:44 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:54:44 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:54:44 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:54:55 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:54:55 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:55:06 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:55:06 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:55:06 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:55:17 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:55:17 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:55:31 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:55:31 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:55:31 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:55:42 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:55:42 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:55:48 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:55:48 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:55:48 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:55:59 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:55:59 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:56:10 AM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 11:56:10 AM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 11:56:10 AM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 11:56:21 AM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 11:56:21 AM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 11:59:30 AM] [homebridge-nest-accfactory] Restarting REST API subscribe for connection uuid "a6dd555b-c2e0-4b2b-8460-5600a4870d9c"
[10/12/2024, 12:00:04 PM] [homebridge-nest-accfactory] Restarting Protobuf API trait observe for connection uuid "a6dd555b-c2e0-4b2b-8460-5600a4870d9c"
[10/12/2024, 12:04:31 PM] [homebridge-nest-accfactory] Restarting REST API subscribe for connection uuid "a6dd555b-c2e0-4b2b-8460-5600a4870d9c"
[10/12/2024, 12:05:08 PM] [homebridge-nest-accfactory] Restarting Protobuf API trait observe for connection uuid "a6dd555b-c2e0-4b2b-8460-5600a4870d9c"
[10/12/2024, 12:09:33 PM] [homebridge-nest-accfactory] Restarting REST API subscribe for connection uuid "a6dd555b-c2e0-4b2b-8460-5600a4870d9c"
[10/12/2024, 12:09:33 PM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 12:09:33 PM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 12:09:33 PM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 12:09:44 PM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 12:09:44 PM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 12:09:50 PM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 12:09:50 PM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 12:09:50 PM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 12:10:01 PM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 12:10:01 PM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 12:10:12 PM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 12:10:12 PM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 12:10:12 PM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 12:10:23 PM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 12:10:23 PM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 12:11:41 PM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 12:11:41 PM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 12:11:41 PM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 12:11:53 PM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 12:11:53 PM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 12:11:58 PM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 12:11:58 PM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 12:11:58 PM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 12:12:10 PM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 12:12:10 PM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 12:12:21 PM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 12:12:21 PM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 12:12:21 PM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 12:12:32 PM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 12:12:32 PM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 12:12:45 PM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 12:12:45 PM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 12:12:45 PM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 12:12:57 PM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 12:12:57 PM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 12:13:02 PM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 12:13:02 PM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 12:13:02 PM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 12:13:13 PM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 12:13:13 PM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 12:13:24 PM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 12:13:24 PM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 12:13:24 PM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 12:13:35 PM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 12:13:35 PM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 12:13:56 PM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 12:13:56 PM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 12:13:56 PM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 12:14:08 PM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 12:14:08 PM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 12:14:34 PM] [homebridge-nest-accfactory] Restarting REST API subscribe for connection uuid "a6dd555b-c2e0-4b2b-8460-5600a4870d9c"
[10/12/2024, 12:14:59 PM] [homebridge-nest-accfactory] ffmpeg process using for live streaming from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v copy -fps_mode passthrough -reset_timestamps 1 -video_track_timescale 90000 -payload_type 99 -ssrc 15980197 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params L7i64NF8RsmBXzAA+uAQQfaQeGWGagiYEdu97Iwi srtp://<IP_ADDRESS>:55222?rtcpport=55222&pkt_size=1378 -map 1:a:0 -codec:a libfdk_aac -profile:a aac_eld -flags +global_header -ar 16k -b:a 24k -ac 1 -payload_type 110 -ssrc 3673382 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params 6H4GajX1C6lv+V43cJg5/DrfmwF8P8+8PQ4zRJst srtp://<IP_ADDRESS>:51297?rtcpport=51297&localrtcpport=43131&pkt_size=188
[10/12/2024, 12:14:59 PM] [homebridge-nest-accfactory] Live stream started on "Front Door" with two-way audio
[10/12/2024, 12:14:59 PM] [homebridge-nest-accfactory] Started live stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with two-way audio and sesssion id of "e4535d98-85e8-4dd1-b13a-f06375e938fa"
[10/12/2024, 12:14:59 PM] [homebridge-nest-accfactory] Stopped live stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 12:14:59 PM] [homebridge-nest-accfactory] Live stream stopped from "Front Door"
[10/12/2024, 12:15:00 PM] [homebridge-nest-accfactory] ffmpeg process using for live streaming from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v copy -fps_mode passthrough -reset_timestamps 1 -video_track_timescale 90000 -payload_type 99 -ssrc 14348719 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params 9nfOEIcSo/UO1Q8nlXBk7iwefXDmzQJziuCqkYkl srtp://<IP_ADDRESS>:61843?rtcpport=61843&pkt_size=1378 -map 1:a:0 -codec:a libfdk_aac -profile:a aac_eld -flags +global_header -ar 16k -b:a 24k -ac 1 -payload_type 110 -ssrc 13767932 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params ekDbTeVJWZmM5h3LIrAiDJ6XA0KhJT7hN6YRIukf srtp://<IP_ADDRESS>:51738?rtcpport=51738&localrtcpport=44097&pkt_size=188
[10/12/2024, 12:15:00 PM] [homebridge-nest-accfactory] Live stream started on "Front Door" with two-way audio
[10/12/2024, 12:15:00 PM] [homebridge-nest-accfactory] Started live stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with two-way audio and sesssion id of "b47c6ac4-2a72-4fa1-8b27-9b0a30d61e96"
[10/12/2024, 12:15:10 PM] [homebridge-nest-accfactory] Input #0, sdp, from 'pipe:0':
  Metadata:
    title           : HomeKit Audio Talkback
  Duration: N/A, bitrate: N/A

[10/12/2024, 12:15:10 PM] [homebridge-nest-accfactory]   Stream #0:0: Audio: aac (libfdk_aac), 16000 Hz, mono, s16

[10/12/2024, 12:15:10 PM] [homebridge-nest-accfactory] Stream mapping:
  Stream #0:0 -> #0:0 (aac (libfdk_aac) -> opus (libopus))

[10/12/2024, 12:15:20 PM] [homebridge-nest-accfactory] [in#0/sdp @ 0x7fffa6f902f0] Error during demuxing: Operation timed out

[10/12/2024, 12:15:20 PM] [homebridge-nest-accfactory] [aost#0:0/libopus @ 0x7fffa6f2d030] No filtered frames for output stream, trying to initialize anyway.
[libopus @ 0x7fffa6f92c70] No bit rate set. Defaulting to 96000 bps.
Output #0, data, to 'pipe:1':
  Metadata:
    title           : HomeKit Audio Talkback
    encoder         : Lavf61.1.100
  Stream #0:0: Audio: opus, 48000 Hz, stereo, s16, 96 kb/s
      Metadata:
        encoder         : Lavc61.3.100 libopus

[10/12/2024, 12:15:20 PM] [homebridge-nest-accfactory] [out#0/data @ 0x7fffa6e81330] video:0KiB audio:0KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: unknown
[out#0/data @ 0x7fffa6e81330] Output file is empty, nothing was encoded(check -ss / -t / -frames parameters if used)
size=       0KiB time=N/A bitrate=N/A speed=N/A

[10/12/2024, 12:15:20 PM] [homebridge-nest-accfactory] ffmpeg audio talkback streaming process for "Front Door" stopped unexpectedly. Exit code was "0"
[10/12/2024, 12:15:20 PM] [homebridge-nest-accfactory] Stopped live stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 12:15:20 PM] [homebridge-nest-accfactory] Live stream stopped from "Front Door"
[10/12/2024, 12:15:29 PM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 12:15:29 PM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 12:15:29 PM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 12:15:41 PM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 12:15:41 PM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"
[10/12/2024, 12:15:46 PM] [homebridge-nest-accfactory] ffmpeg process using for recording stream from "Front Door" will be called using the following commandline -hide_banner -nostats -use_wallclock_as_timestamps 1 -fflags +discardcorrupt -max_delay 500000 -flags low_delay -f h264 -i pipe:0 -i pipe:3 -map 0:v:0 -codec:v libx264 -preset veryfast -profile:v main -level:v 4.0 -noautoscale -bf 0 -filter:v fps=fps=30 -g:v 120 -b:v 2000k -fps_mode passthrough -movflags frag_keyframe+empty_moov+default_base_moof -reset_timestamps 1 -video_track_timescale 90000 -bufsize 4000k -map 1:a:0 -codec:a libfdk_aac -profile:a aac_low -ar 16k -b:a 16k -ac 1 -f mp4 pipe:1
[10/12/2024, 12:15:46 PM] [homebridge-nest-accfactory] Started recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX" with sesison id of "1"
[10/12/2024, 12:15:46 PM] [homebridge-nest-accfactory] Started recording from "Front Door"
[10/12/2024, 12:15:58 PM] [homebridge-nest-accfactory] Stopped recording stream from uuid "DEVICE_F0EF8XXXXXXXXXX"
[10/12/2024, 12:15:58 PM] [homebridge-nest-accfactory] Recording from "Front Door" completed with error. Reason was "TIMEOUT"

Been able to reproduce at my end, so now need to work on a fix :-)
Seems things are a bit more finicky once camera has been migrated to Google Home

testing fix in 0.2.3-alpha.5


Fix up Actions issues

Issues identified:

Within a job, TSV.ps1 is now failing fast when the first spec fails, instead of verifying all specs and collecting the errors.

The parallel jobs are also configured to fail fast, so they all cancel when one fails, which we don't want either.

With fixes:
TypeSpec Validation now shows an error, continues processing and then fails the build:

TypeSpec Validation All now shows an error, continues processing, and then fails the build and all jobs run until completion:

@mikeharder I'm merging this now as it fixes the immediate issue. We can do a longer term fix in the near future.


test-branch/execute-job/quoted-authorization/0900ab4a-9f93-4dd9-85a0-ec29d74dd47f

PR for testing 11ac06a1526dcdba6d593047eb21d24afe225bc0

/canonical/self-hosted-runners/run-workflows 11ac06a1526dcdba6d593047eb21d24afe225bc0


Adding a photo to a thread from Textile itself doesn't carry over the description

Huawei P9 lite, Android 7, Textileversion 1.6.6

The app doesn't support adding captions to photos in the Textile wallet. If you share a photo from your camera roll or the Textile wallet to a thread with a comment, that comment is only associated with the share in that particular thread. The comment isn't added to the photo in the Textile wallet.


How many iters for training?

Hi there
When training (volumetric) there is an output in the terminal of the amount of iters done.
420000 iters done.
How many iters need to be completed for the training to be complete?
Are 'iters' the amount of images to be processed?
Thanks.

Hi, @jamalknight!
Can you share your loss plots?
To be honest, I don't remember the exact number of iterations, but it took about a week on a single NVIDIA P40 GPU.

Hi @karfly
How do I share my loss plots?
(I am using a batch size of 1, so expecting my model to take longer than yours to train)

@jamalknight, just screenshot will be okay.

Hi @karfly
Below are screengrabs of tensorboard logs:
(alternatively http://localhost:6006/#scalars)

Hi @karfly
Any estimation when training will be done?

A week of training on my machine took approx 200 000 iters
4 weeks of training tool 825 000 iters


[Bug] Improve handling of schema.items qualifiers

Description
Previously, schema.items qualifiers ignored top-level schema qualifiers and only returned qualifiers for the items. This change introduces additional checks to determine if and when qualifiers should be evaluated and concatenate them as needed.
Motivation and Context
Provides better coverage of schema.items type.
How Has This Been Tested?
Tested with Petstore API. See deploy preview for working example.

Before:

After (note that minItems and maxItems is now included):


invoices+channeldb: introduce InvoicesDB interface

Change Description
Deals with the first two points of issue #6288.

Eliminate the invoice registry's dependency on the raw channel db pointer
Expose the new interface as part of the set of defined DatabaseInstances

This is a minimal version, I'm currently researching what would be needed to invert the dependency relation between channeldb and invoices packages. Ideally InvoicesDB would live in the invoices package.

Replaced by https://github.com/lightningnetwork/lnd/pull/7215


bug get request is post？？？

https://developers.weixin.qq.com/doc/offiaccount/Custom_Menus/Deleting_Custom-Defined_Menu.html
https://github.com/ArtisanCloud/PowerWeChat/pull/301

👍 pls check v3.0.28
It must be replaced when we upgraded v2->v3.
thank you for you help!


Material breaking change

Seems like updating the pods in #6 and #7 introduced new bug in presenting View Controllers using ToolbarController from Material.

Investigate this problem and mitigate the graphical glitches.

Issue reported in Material repository.

Update resolved the issue


Issue 41 benchmarks

In principle, this should setup the workflows for the benchmarks. I tried the benchmarks on my computer and they worked well (see https://pybamm-team.github.io/liionpack-bench/). At the moment there is only one data point so there is no graph available.

Thanks Ferran, could you add a section on benchmarks to the contributing document explaining how they run a little bit. I'm not that familiar with how it works so how would I test this PR? Thanks

I have added a CONTRIBUTING doc with benchmarks (and some other things that were applicable to liionpack straight out of PyBaMM's document). I can improve it later on.

@brosaplanella there was already a contributing.md in the docs subfolder which I had edited from pybamm but removed quite a bit. Could you put your changes there please

Sorry, didn't see it! Let me know if it is OK now :)

Thanks a lot @brosaplanella


Error in ADS-B Exchange install script?

Checking for and removing any old style ADS-B Exchange setups if any exist...
Checking for any preexisting older style setups...
Checking if the netcat startup line is contained within the file /etc/rc.local...
Checking for any running adsbexchange-netcat_maint.sh processes...
Removing the netcat startup script line to the file /etc/rc.local...
/home/pi/adsb-receiver/bash/feeders/adsbexchange.sh: line 154: /d: No such file or directory
Installing packages needed to build and fulfill dependencies...
Checking if the package curl is installed...sed: -e expression #1, char 4: extra characters after command

https://github.com/jprochazka/adsb-receiver/blame/d8e49c245d3117734537e3aa49b882e25f7bfbd2/bash/feeders/adsbexchange.sh#L154
Line 154:
sudo sed -i /$RECEIVER_BUILD_DIRECTORY\/adsbexchange\/adsbexchange-netcat_maint.sh &/d /etc/rc.local 2>&1

Doesnt seem worth creating a branch to fix these but there are a number of unquoted sed strings which will fail when expected to look for a string with whitespace in it :/

In this particular case as well as the case with any other unquoted sed command I am not looking for white spaces so there is no need to "fix" them. To go back and quote them would be pointless for sure.
The problem is as the error states: "No such file or directory" which has nothing to do with the RegEx portion of the sed command. This is more than likely referring to the system not being able to find /etc/rc.local which on most newer distros using systemd no longer exists unless created by the user.
Either I need to remove the offending code which is very legacy anyways and only undid changes made to by the script before ADS-B Exchange introduced the ability to use mlat-client or check to make sure that rc.local in facts exists and if not skip the check.


[Bug]: 404 page image alignment is wrong

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
If you visit an invalid application on Appsmith, the platform will display a 404 page. On this page the image alignment is incorrect.
Steps To Reproduce

Visit any incorrect link on Appsmith platform
See the page.

Environment
Release
Version
Cloud

In the latest version of Appsmith, this issue is back again. We seem to have regressed.


Topics added

Closes: #5
please add level3, gssoc and gssoc-ext labels

@adarsh-singh01 please check this pr as well

@NK-Works Merged


How to directly post without get for example for login

How to directly post without get for example for login
Here is my end point user/login that takes input un, pwd and returns user object
let newAccount = { "username"<EMAIL_ADDRESS>"password":"moorthi"};
// POST /User/Login
this.restangular.all('/users/login').post(newAccount);

hey @moorthi07 Can you please create this issue at ngx-restangular. Project was renamed due to Angular SemVer.


when try a Generic invoke in triple Protocol, I got a error like this：Triple Server received remote reset errorCode=8

when try a Generic invoke in triple Protocol, I got a error like this：Triple Server received remote reset errorCode=8，I not konw the
mean and how to resolve it
I am sure my provider is running and I can use dubbo-go invoke it ,but java can't work
	ReferenceConfig<GenericService> reference = new ReferenceConfig<GenericService>();
	reference.setApplication(applicationConfig);
	reference.setInterface(iface);
	reference.setVersion(version);
	reference.setGeneric(true);
	reference.setTimeout(30000);
	reference.setGroup(group);
	reference.setProxy("jdk");
	reference.setUrl("tri://localhost:8889");

//		reference.setProtocol("tri");
reference.setRetries(0);

@zhanghan810810 请问请求参数是不是pb类型呢？

No news is good news. Please feel free to create a new issue if you have any question.


Allow more complex filtering

This PR duplicates the existing code then converts it from a module-based into a Class-based approach. The main reason for this to add extra functionality on the addition check (i.e. I want to be able to programmatically decide when to include additional based on the type of parent object and the current path)
This type of change was just not possible with the previous code implementation. I have reused the existing methods and avoided changing the interface so this can be used as a drop-in replacement for the previous code. The advantage of this approach is that rebasing changes from the master branch is do as should pick up any changes which are not to the core diffing method automatically.

Hi @dwhenry!
Would it be OK to apply the changes to lib/json-diff/diff.rb?
Your code organization looks good, and it seems backwards-compatible; am I wrong?
In terms of versioning, it feels awkward to have both a v2 and a version 0.5.0-dwhenry.


.vsts-ci.yml does not create a build definition for new projects

I've noticed, that if I create a new project in Azure DevOps and initialize it using my existing local git repo which includes '.vsts-ci.yml' file, a build definition doesn't get created automatically and in order to trigger one to be created I need to make some changes to the file and push those changes up to the origin.
The thing is that I have the '.vsts-ci.yml' file inside of my project template and I'd really like it to automatically generate the build definition straight on the initial push (so that I could then go and configure branch policies for the master to depend on this build).
Is this an expected behavior or it's actually a bug?
Thanks!

Same problem... any work around?

This started affecting us as well. We have hundreds of projects that all use .vsts-ci.yml and this is causing confusion across our org.
Our Workaround

Create .azure-pipelines.yml in the repo and push
Verify the build was scaffolded correctly
Rename .azure-pipelines.yml to .vsts-ci.yml
Open up Azure Pipelines and edit the Pipeline Settings
Rename the YAML File Path to .vsts-ci.yml

This is quite a manual effort to use the old convention. Is it possible to make this configurable

Hi, is this issue still on ? i'm also still not able to create automatically the build pipeline.
Even apply the workaround, it does not work.
New project, empty repo, created the file and pushed.


Next version 0.7.0+

(To avoid online doc being outdated, that might be a solution (work on a "next" branch where we can submit PR on (PRception)).

Will release after my bednight :)

we need to talk about workflow a little bit. I'm tracking next in some branchs. Maybe just don't auto deploy docs on Travis and do it locally when releasing ?

I think keeping master as a reflect of the current released package is a good thing. And when public API become stable enough, having doc auto deployed is also a good thing.
Maybe I should just not delete the "next" branch. I will keep it up to date with master.


I.e. a connection is closed, even when an external TransactionManager is present.
Is that intendet?

As I see it, the connection comes from
dataSource.getConnection() (line 194)
Usually a DataSource provides connections from a connection pool.  Calling close() on a connection obtained from a pool is mandatory to give the connection back to the pool so it is freed for reusage. The connection is not really closed.

@hdconradi @h-thurow That is correct.
My company used to use the Bitronix JTA Transaction Manager, and so I know that SansOrm works with that JTM.  We now use the [internal Transaction Manager(https://github.com/brettwooldridge/SansOrm/blob/master/src/main/java/com/zaxxer/sansorm/transaction/TxTransactionManager.java), because we never had multiple, distirbuted, databases, but wanted the Connection sharing/thread-association behavior.


Write Datasets to Battery Archive Format

After discussing with @ypreger , the next step in integration between this toolkit and the data infrastructure will be the ability to read/write data into Battery Archive format.
That format is described in an sql schema file and the importer tends to read files.
The general theme of the output will be to:

write different CSV files for each type of data (metadata, timeseries, cycle stats)
convert the names of columns (though I hope that will not be necessary, and that we can adapt our schema)
chunk larger files into small enough to ingest into the system without much issue

To be tested by @ypreger and her team before we close this


Capture functionality

Changed capture functionality to download file instead of opening in new window, due to Chrome deprecation of window.open functionality:
https://developers.google.com/web/updates/2017/03/chrome-58-deprecations#remove_content-initiated_top_frame_navigations_to_data_urls

Thanks @madsstenhoj looks good! I made some minor changes to style the link properly instead of using a button inside a link.


Fixes #1391 - Provide a simplistic simulation of mesos for scale testing

Create a new sub module to separate simulation code from production code.
Also use a guice provider to instantiate the driver so that
we could substitute the provider to instatiate a simulated driver.
There were some global variable references that had to be removed for this to work.

Couple of comments, but a good first step! :+1:
Overall it feels not ready for merge.
Do you want to integrate the tests first, so the picture is more clear?

Hmm. It is already useful like it is. You can start the app with simulated Mesos.
What concerns did you not mention? I think most of your comments relate to the driver holder which is not beautiful but overall wasn't my idea (I just made the idea more explicit).
Your other concern was using ??? in the simulation module.
Did I miss something?

I was under the impression you are in the process of creating also some automated scale tests. Otherwise :ship: it.

@aquamatthias Now I have added a test which collects stats/metrics and a utility which prints them in a sensible form.

Was able to execute the scale tests :+1:
Can we find a better way for Provider[MesosSchedulerDriver]?


Error running filter _extensions/quarto-journals/acm/add-bibliography.lua

I'm trying to Render a .qmd file that has as part of its front matter:
format: acm-pdf
keep-tex: true

acm-metadata:
  final: true

  # lines omitted

  ccs:  # omitted
  keywords: # omitted

When I hit render, I get the error:
Error running filter _extensions/quarto-journals/acm/add-bibliography.lua:
_extensions/quarto-journals/acm/add-bibliography.lua:57: attempt to call a nil value (field 'is_format')
stack traceback:

(no traceback is offered)
I just installed quarto and the quarto-journals/acm extension today, and have my RStudio is v2022.07.01

I installed Quarto and the ACM template today on a new machine and have the same issue. No problem on an older installation.

Oh, I think I found the problem. The default download for Quarto is v.1.1.xxx and it needs 1.2.xx.
@soumyaray You can find the download for the pre-release of 1.2 here: https://quarto.org/docs/download/prerelease.html

This fixed it!! Thanks @Sumidu. I'll close the issue now as it seems to be just a back-compatibility issue, and @cscheid is welcome to reopen it if there is anything to be done on their side.

We should add a warning to quarto-journals about running v1.2 pre-release versions.


C# No Input

When using the xamarin nuget package 1.15.0. if no input is recognized(silence/no input),
The IntentRecognizer doesn't throw an SpeechEndDetected, SessionStopped or Canceled event anymore.
Some times a SpeechEndDetected is thrown but most of the time it just silently stopps.
This results in an faulty state where the application thinks it's still listening but the listening already stopped.
The normal behavior would be:
SessionStarted =>(SpeechStartDetected)=>(SpeechEndDetected)=>SessionStopped
Current faulty behavior:
SessionStarted => silent stop
I'm currently testing on Android.

Version 1.14.0 is working as expected...

@SOliasS thanks for reporting this. We're investigating now and will circle back ASAP.

@SOliasS looking into this, we've found that some of the timing details of when events get fired versus when futures resolve (e.g. in C#, when await recognizer... calls come back with a result) likely changed in 1.15.
That'd mean that, if you had code that disposed of a recognizer after its RecognizeOnceAsync operation finishes (future resolves / await returns), it may get and do something with the events before 1.15 (since the events fired before the operation finished) and not get them after 1.15 (since the events fire after the operation finished, which would be after the object is disposed) -- which I believe might be consistent with what you're seeing. There's no contractual guarantee on the relationship between the future and async events, though, so that's not a pattern we would advise (instead relying on something like a TaskCompletionSource tied to the events you're interested in for the lifetime of the recognizer).
Could you share the code/pattern you've calling that's reproducing this problem? We can advise further based on those details.

sry but i'm not 100% what you want to tell me...
until now Luis exposes these events
           ```

//live text
intentRecognizer.Recognizing += Recognizing;
//Init
intentRecognizer.SessionStarted += SessionStarted;
//Start Speech detected
intentRecognizer.SpeechStartDetected += SpeechStartDetected;
//Speech end detected
intentRecognizer.SpeechEndDetected += SpeechEndDetected;
//Session Stopped
intentRecognizer.SessionStopped += SessionStopped;
//Recognized
intentRecognizer.Recognized += Recognized;
//Timeout
intentRecognizer.Canceled += Canceled;

These events signaled in which state LUIS is at the moment.
Depending in which state it is i could display text, display the state to the user and in the end start the execution of the desired action.
Therefore i need to rely on the consitent pattern for these events...
This is the only consitent way to use LUIS because until now RecognizeOnceAsync might get destroyed 5-10 seconds after the listening is done... which is no way an acceptable timeframe for waiting to continue with the next action...

Thanks.
How are you creating and disposing of the IntentRecognizer in the code above? To clarify what I mentioned before, a pattern like this may work with 1.14 but not with 1.15:
using (var recognizer = new IntentRecognizer(...)) {
  recognizer.Recognized += (_, e) => // success! this is expected to be observed
  await recognizer.RecognizeOnceAsync(); // will block until "done"
}

With 1.14, it looks like .Recognized will pretty consistently (but not always!) fire before the await finishes and recognizer is Dispose()d at the end of the using block. With 1.15, meanwhile, the await often finishes before Recognized would be raised, meaning that recognizer is Dispose()d and the event handler is unsubscribed before anything can happen.
That could explain at least the "end" events (EndDetected/SessionStopped/Recognized/Canceled) being different. It's just a hypothesis, though -- seeing your code that creates and disposes of the recognizer would be a huge help in knowing more.

The Problem is like i said StartContinuousRecognitionAsync does not get awaited like RecognizeOnceAsync therefore can not be awaited and so the only option left for working with both is the event system...
 public async Task StartDication(List<string>? phraseList = null)
        {
            UtilityFactory.Log.TrackeventAsync(LoggingVersions.Speech, new object?[] { });
            try
            {
                await InitIntentRecognizer(phraseList);

                if (intentRecognizer != null)
                {
                    await PrivateThreading.BeginInvokeOnMainThreadAsync(() => StartRecognition(new Func<Task>(intentRecognizer.StartContinuousRecognitionAsync), ListeningHandlerState.Dictation));

                }
            }
            catch (Exception ex)
            {
                Crashes.TrackError(ex);
            }
            //UtilityFactory.Log.TrackeventAsync(LoggingVersions.Speech, new object?[] { }, "Finish StartDication");
        }

@trrwilson is there any plan for how to handle StartContinuousRecognitionAsync now?

@pankopon intentRecognizer.StartKeywordRecognitionAsync is also not awaited...

@SOliasS Fix for the event vs. awaited result ordering has been made and will be released in the next public release. Closing the issue.

@jhakulin whats the solution? will await work or will events work? or both?

@SOliasS Solution would be the to make sure ordering of events and awaited result e.g. for RecognizeOnceAsync comes in order where events comes first and at the end there is awaited result. I think this is what was in 1.14.0, does that sound ok ?
We have not yet implemented solution where StartContinuousRecognitionAsync would be awaited for all results, there is a work item for that, but that probably goes to future API considerations.

@jhakulin sounds good so far, looking forward to the next release.

@SOliasS We have release new 1.17.0 release now, let us know if you see any problems with that.

@jhakulin
I may have encountered the same problem, I used the version: v1.20 + WPF + Net 6.
Yesterday, my BuildSrtAsync worked fine and SpeechEndDetected could notify me that the task was completed, but today it doesn't
public async Task<List<Subtitle>> BuildSrtAsync(AudioConfig audioConfig)
{
    var recognizer = new SpeechRecognizer(SpeechConfig, audioConfig);
    var subtitles = new List<Subtitle>();

    var start = TimeSpan.Zero;
    var end = TimeSpan.Zero;

    recognizer.Recognized += (sender, e) => {
        start = TimeSpan.FromMilliseconds(e.Result.OffsetInTicks / 10000);
        end = start + e.Result.Duration;
        subtitles.Add(new(e.Result.Text, start, end)); // work fine.
    };

    // not raise.
    recognizer.SessionStopped += async (sender, e) => {
        Debug.WriteLine(">>> SessionStopped.");
        await recognizer.StopContinuousRecognitionAsync();
    };

    // not raise.
    recognizer.Canceled += async (sender, e) => {
        Debug.WriteLine(">>> Canceled.");
        await recognizer.StopContinuousRecognitionAsync();
    };

    // completed, but not raise.
    recognizer.SpeechEndDetected += (sender, e) => {
        _tcs.TrySetResult(true);
    };

    await recognizer.StartContinuousRecognitionAsync();

    await _tcs.Task;

    return subtitles;
}


Add network bind plug

This PR will resolve https://github.com/canonical/chip-tool-snap/issues/18
To install and configure the snap with the changes introduced by this PR, follow these steps:
$ sudo snap install chip-tool --channel=edge/pr-19

$ sudo snap connect chip-tool:avahi-observe
$ sudo snap connect chip-tool:bluez
$ sudo snap connect chip-tool:process-control

$ snap connections chip-tool
Interface        Plug                       Slot              Notes
avahi-observe    chip-tool:avahi-observe    :avahi-observe    manual
bluez            chip-tool:bluez            :bluez            manual
network          chip-tool:network          :network          -
network-bind     chip-tool:network-bind     :network-bind     -
process-control  chip-tool:process-control  :process-control  manual

After installation, the interactive mode command should run without any errors:
$ sudo chip-tool interactive server

$ sudo chip-tool interactive start
...
>>> pairing onnetwork<PHONE_NUMBER>1
>>> onoff toggle 110 1

@ihidchaos Could you please test the snap from channel edge/pr-19 as described above to see if it resolves the issue you reported? Thanks.

It shwos error: requested a non-existing branch on latest/edge for snap "chip-tool": pr-19

It shows `error: requested a non-existing branch on latest/edge for snap "chip-tool": pr-19`

@ihidchaos It had been released only for amd64, but you were trying to install it on an arm64 platform.
Please try again using the same command. I just built and uploaded it for arm64.
sudo snap install chip-tool --channel=latest/edge/pr-19

@ihidchaos It had been released only for amd64, but you were trying to install it on an arm64 platform.
Please try again using the same command. I just built and uploaded it for arm64.
sudo snap install chip-tool --channel=latest/edge/pr-19

Thanks for pointing this out, after testing this fix works and I can now successfully launch interactive mode.


Stuttering with Monterey 12.3

Before updating to Monterey 12.3, Aerial was buttery smooth on my Mac.  Now, the videos have a slight stuttering.  My setup is a 14" MBP M1 Max (24 core GPU) connected to a 5k LG Ultrafine monitor.  I have the screensaver displayed on both the external monitor and laptop screen.

Hi @lankox
I'm running the betas right now so I haven't seen it personnally, but it wouldn't surprise me there's a specific bug with video decoding in 12.3.
Are you using HDR ? Usually this is the shakiest part of macOS video decoding and in Monterey in general it's been bad.
There's 0 reason it should lag on a M1 Max in any case so I think it's likely something they'll fix in 12.4.

@lankox are you still experiencing the issue ? I believe this was fixed in a subsequent Monterey build

Not sure.  I switched the video format to 4k HEVC from 4k HDR and that immediately solved the problem.
On Aug 16, 2022, at 10:29 AM, Guillaume Louel @.***> wrote:
@lankox https://github.com/lankox are you still experiencing the issue ? I believe this was fixed in a subsequent Monterey build
—
Reply to this email directly, view it on GitHub https://github.com/JohnCoates/Aerial/issues/1239#issuecomment-1216939929, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJOHOTP5QPXCAD7FCPS6JKLVZPFYPANCNFSM5T7S77JA.
You are receiving this because you were mentioned.

Thanks for taking the time to answer. I'm 99% sure this is fixed if you want to switch. It's definitely fixed in the Ventura betas I'm using right now. Take care !


New Server method add_service_rpc_handler

Taken from
#8742
"""
The issue is in avoiding the situation of an application creating a ServiceRpcHandler, registering it with a server using add_generic_rpc_handlers, and then the server having to do dynamic type inspection and special casing along the lines of "well, which of the handlers just registered are ServiceRpcHandlers and which are merely GenericRpcHandlers?" when the application had that information on its side of the API. It's been really nice that we've been able to avoid dynamic type inspection so far and I'd like to keep it up.
With that pushing in the direction of a Server.add_service_rpc_handlers method the question of the design of the ServiceRpcHandler type is raised. How should it be called to service an RPC? By full-size /my_package.my_subpackage.MyService/MyMethod string? Or just by MyMethod string? Should ServiceRpcHandlers be free to refuse service of an RPC?
I think these questions can be answered in a way that allows ServiceRpcHandler to inherit the service method from GenericRpcHandler. Do you foresee any problems?
"""

Stealing this issue because I think it will be affected by whether or not we want to use grpc_server_request_registered_call as part of our performance improvement story.
@yang-g, @ctiller: how likely do you think it will be that using grpc_server_request_registered_call rather than grpc_server_request_call will be part of the Python performance improvement work? @a11r indicated that he suspect it would be but I'd like to hear it from you and to hear if there would be any reason for it other than "of course RPC method dispatch in C will be faster than RPC method dispatch in Python".


Record in compressed format

Hi, I am trying to modify the code to record directly in AAC format. I’ve tried to change parameters at AudioStreamBasicDescrption for iOS but no success.
I think this would be possible, do you?. Any advice to continue or is there a possibility to enhance the code?
Thanks a lot.

Sorry I've not looked into supporting any other formats, though I do think it should be possible.  If you're able to get it working please send a PR!

Thanks anyway. I will continue looking for a solution. If I get it I will inform you.


We don't install the latest bug fixes for default packages in the ubuntu image

We should probably run: apt-get update -y  and apt-get upgrade -y after we've finished installing just to make sure we've got the latest bug fixes

Docker best practices discourage doing a broad apt-get upgrade. For when we need to update vulnerable packages we will upgrade these individually until they are included in the base Ubuntu image.


fix: check PR mergeable for tars

When there is a PR conflict, the API call to update the PR does not report an error, so it causes the mechanism to update the PR after the push event to fail.

/assign @Mini256
PTAL~ Thanks!

@Mini256 PTAL~

/merge


[WIP] Fix contract injection in release mode compilation

As reported by Eric, contract proxy type check fails due to compiler optimisation of the reference execution proxy type when the node is compiled in release mode.
This PR solves this issue by not injecting optimised lines when contract patcher is compiled in release mode.
Additional fix added:
An additional commit includes a fix for a security issue when deploying a new contract with the existing code of another system contract, that causes overwriting contract code's registration and changes its privilege to normal.

:x: Build AElf <IP_ADDRESS>52 failed (commit https://github.com/AElfProject/AElf/commit/08b6d22bb2 by @aerkol)

:x: Build AElf <IP_ADDRESS>58 failed (commit https://github.com/AElfProject/AElf/commit/db159f0688 by @aerkol)


fix(input): removed card type

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.006%) to 84.457%

Totals

Change from base Build<PHONE_NUMBER>:
-0.006%

Covered Lines:
9753

Relevant Lines:
10669

💛  - Coveralls


Attempting to recreate simple example fails on a syntax error

Rust v1.0
[cqlsh 4.1.1 | Cassandra 2.0.14 | CQL spec 3.1.1 | Thrift protocol 19.39.0]

My code is nearly the same as the code in examples/
extern crate cassandra;
use cassandra::*;
static CONTACT_POINTS:&'static str = "<IP_ADDRESS>";

fn main() {
  println!("Before cluster connect");
  let cluster = &CassCluster::new()
                      .set_contact_points(CONTACT_POINTS).unwrap()
                      .set_load_balance_round_robin().unwrap();

  println!("Before session connect");
  let mut session = CassSession::new().connect(&cluster).wait().unwrap();
  println!("Before session execute");
  let result = session.execute("SELECT keyspace_name FROM system.schema_keyspaces;", 0).wait().unwrap();

  println!("{:?}", result);

  session.close().wait().unwrap();
}

And I get the output & error:
in Ticks/ on master
› cargo run --verbose
       Fresh gcc v0.3.5
       Fresh libc v0.1.7
       Fresh cql_bindgen v0.0.11
       Fresh cassandra v0.2.5
       Fresh time v0.1.25
       Fresh Ticks v0.1.0 (file:///Users/cschneid/Code/Rust/Ticks)
     Running `target/debug/Ticks`
Before cluster connect
Before session connect
Before session execute
thread '<main>' panicked at 'called `Result::unwrap()` on an `Err` value: "Syntax error"', /Users/rustbuild/src/rust-buildbot/slave/stable-dist-rustc-mac/build/src/libcore/result.rs:729
Process didn't exit successfully: `target/debug/Ticks` (exit code: 101)

The query runs fine in the cqlsh interface, so there's something else going on with the result, or result unwraping.  I have the c++ library linked from their homebrew recipe, which is 1.0.0.

Hmmm...odd. I copied your exact code and just changed the ip address to be <IP_ADDRESS> and it runs perfectly on my linux laptop, running DSE 4.6, which is the same as Cassandra 2.0:
Before cluster connect
Before session connect
Before session execute
Result row count: 11
'"metrics"'
'"dse_system"'
'"tester"'
'"HiveMetaStore"'
'"examples"'
'"system"'
'"cfs_archive"'
'"system_traces"'
'"crustfs"'
'"cfs"'
'"dse_security"
You might turn on debug logging on the server to get a better idea. I'll keep thinking about this, and let me know if you any other thoughts.

Oh, also, do the built in examples work for you?

So I've now seen this happen twice. Once with a run of target/debug/basic and another time with target/debug/collections. I'm going to try running wireshark to capture all data between client and server and see if I can reproduce it again.

I think the issue may have to do with how CString#as_ptr() is used in statement.rs:80. According to the CString#as_ptr() documentation, the returned C string is only valid as long as the query: CString is valid. As the variable is deallocated after returning from the function, the memory location for the C string may be overridden before the FFI library uses the string. The documentation suggests that CString#into_raw() or CString#into_ptr() along with CString#from_raw() or CString#from_ptr() would be more appropriate.
I ran into this problem while learning Rust FFI. I could be mistaken about your use case, though. Hope this helps!

Nevermind, the CassStatement documentation states that cass_statement_new copies the input string.

I believe later refactorings and bug fixes resolved a race condition that could cause this. Please reopen if you see it again.


IntelliJ theme

The gray theme  is by far my favourite theme of all time :). Could it be possible to have this on Jetbrains products as well?

That's a good idea :smiley:, but recently I am busy with doing research, so I might not have time to start right away...


Remove auto-type config

In the docs
https://github.com/CasperLaiTW/laravel-fb-messenger/issues/39#issuecomment-257206067

If Facebook doesn't get HTTP 200, it will keep sending the same message over and over again until 20 seconds.

Auto-type should be enabled by default and can't be disabled

I think let developer to make decision