| 6 Jan 2025 |
@hexa:lossy.network | https://blog.ceard.tech/2025/01/ha-voice-pe.html | 17:58:36 |
| 7 Jan 2025 |
netpleb | right now my frigate config is very basic and I have something like:
# amcrest cameras
cameras.driveway = {
ffmpeg.inputs = [ {
path = "rtsp://<user>:<password>:554/cam/realmonitor?channel=1&subtype=1"
roles = [ "detect" ]
} ];
};
but I seem to be unable to get any audio from the cameras (I have enabled AAC audio in the camera's UI itself). Is there some additional thing I need to add to frigate/ffmpeg so that it will stream/record audio too?
| 19:24:56 |
netpleb | I do not have amcrest integration in hass turned on, nor am I using go2rtc in frigate (i am new to all these things), so I am having a hard time grasping what is the minimum I need to setup to get audio working. Any help much appreciated! | 19:27:26 |
netpleb | because I am doing this all on nixos using hexa's excellent modules for hass and frigate, I am also confused about things like: http://card.camera/#/README -- are we still able to use that frigate card, or no? | 19:33:19 |
netpleb | for anyone coming along later, I figured out how to get audio working. It seems to have required: ffmpeg.output_args.record = "preset-record-generic-audio-copy"; instead of ffmpeg.output_args.record = "preset-record-generic-audio-aac"; not sure why but whatever ;) | 20:16:52 |
netpleb | * for anyone coming along later, I figured out how to get audio working. It seems to have required: ffmpeg.output_args.record = "preset-record-generic-audio-copy"; instead of ffmpeg.output_args.record = "preset-record-generic-audio-aac"; not sure why but whatever ;-) | 20:17:01 |
| 8 Jan 2025 |
laurynasp | Does anyone use esp32 boards? How far did you managed to get with declarative (or at least programatic) way to reflash the devices?
I have enabled services.esphome, which seems to use /var/lib/private/esphome as workdirectory directory. However, if files in the work directory symlink to elsewher (e.g. /run/secrets/esp/esp32-test.yaml) it complains with the following message.
ERROR Exception in callback functools.partial(<function WebSocketProtocol._run_callback.<locals>.<lambda> at 0xffffa09fc0e0>, <Task finished name='Task-3531' coro=<EsphomeCommandWebSocket.on_message() done, defined at /nix/store/qz8753g0sgf8xy253kpbpbrr3r4j340r-esphome-2024.4.2/lib/python3.11/site-packages/esphome/dashboard/web_server.py:175> exception=ValueError("'/run/secrets.d/11/esp/esp32-test.yaml' is not in the subpath of '/var/lib/private/esphome' OR one path is relative and the other is absolute.")>)
| 01:49:36 |
@hexa:lossy.network | I maintain the esphome package but I have never used the module | 01:50:37 |
@hexa:lossy.network | I run various esp32 though | 01:50:45 |
@hexa:lossy.network | honestly, that sounds like a base path restriction due to symlinks | 01:51:51 |
@hexa:lossy.network | * honestly, that sounds like a base path restriction hit due to symlinks | 01:52:00 |
laurynasp | what is your setup for managing / flashing the devices?
do you flash from nix develop? | 01:52:26 |
@hexa:lossy.network | that error is printed by pathlib | 01:52:55 |
@hexa:lossy.network | I have a devshell, yeah | 01:53:07 |
@hexa:lossy.network | and when I feel like it (mostly on updates) I run the dashboard and let it update everything | 01:53:23 |
laurynasp | Do you mean, this stems from the ESPhome python code opinion symlinks vs regular files | 01:53:31 |
@hexa:lossy.network | please don't use threads for everything I say | 01:54:57 |
@hexa:lossy.network | nobody else is here, so we can just talk here | 01:55:10 |
@hexa:lossy.network | the context is super clear 😄 | 01:55:20 |
@hexa:lossy.network | esphome somewhere uses path.relative_to("/var/lib/private/esphome") | 01:55:39 |
laurynasp | Yeah, I was thinking that if I was to go forward with ESPHome dashboard (services.esphome), then I guess my best option would be PR to add an option for systemd services pre-Exec, where I could cp a file across. Would feel hacky.
However, my ultimate goal is to automate managament of esp32 devices, so if there is better way, then i would go with that | 01:55:42 |
@hexa:lossy.network | and path is not inside that directory | 01:55:46 |
@hexa:lossy.network | https://github.com/search?q=repo%3Aesphome%2Fesphome%20relative_to&type=code | 01:58:06 |
@hexa:lossy.network | probably in dashboard_settings.py | 01:58:15 |
@hexa:lossy.network |
Raises ValueError if not relative to ESPHome config folder
| 01:58:23 |
@hexa:lossy.network | the esphome service to me feels like a stateful way of dealing with configs | 01:59:04 |
@hexa:lossy.network | you can certainly instruct your secrets management to install the files into /var/lib/private/esphome though | 01:59:26 |
@hexa:lossy.network | just a symlink won't do | 01:59:31 |
laurynasp | just doing a test run to check that ESPhome is happy with secrets.yaml being outside the config dir | 02:16:33 |
@hexa:lossy.network | good luck 😄 | 02:18:18 |