| 5 Jan 2025 |
@hexa:lossy.network | all regexes in that packages throw warnings, because they are not raw strings 🫠| 19:22:05 |
@hexa:lossy.network | K900: midea-local pep517 pls | 19:22:44 |
@hexa:lossy.network | still says format setuptools | 19:22:52 |
@hexa:lossy.network | midea-local> /nix/store/gq9pbcplpixh9ddp69kpq5faa0nravs7-python3.13-setuptools-75.3.0/lib/python3.13/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
midea-local> !!
midea-local>
midea-local> ********************************************************************************
midea-local> Please avoid running ``setup.py`` directly.
midea-local> Instead, use pypa/build, pypa/installer or other
midea-local> standards-based tools.
midea-local>
midea-local> See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
midea-local> ********************************************************************************
midea-local>
midea-local> !!
| 19:23:17 |
@hexa:lossy.network | also setuptools is annoying me about it | 19:23:26 |
K900 | Ugh I need to focus on one thing at a time and not like eight | 19:25:05 |
@adam:robins.wtf | I’m in that club too | 19:31:39 |
| 6 Jan 2025 |
macaroniskengz | In reply to @hexa:lossy.network we have set up pretty strong isolation for home-assistant in nixos Do you think a container doesnt add anything at all security wise? It runs in a VM already, so that's that | 02:18:51 |
macaroniskengz | * Do you think a container doesnt add anything at all security wise regarding upstream harding? It runs in a VM already, so that's that | 02:19:06 |
@hexa:lossy.network | not too much | 02:20:13 |
@hexa:lossy.network | you need to mount certain things into the container | 02:20:29 |
@hexa:lossy.network | you probably want to run in the host network namespace | 02:20:37 |
macaroniskengz | In reply to @hexa:lossy.network you probably want to run in the host network namespace Actually I dont want that | 02:21:48 |
@hexa:lossy.network | ok, so no multicast things for you | 02:22:49 |
@hexa:lossy.network | no avahi discovery | 02:22:57 |
macaroniskengz | Yes, due to security concerns I already disabled it in my current setup | 02:23:53 |
macaroniskengz | Maybe I am too paranoid, but i dont trust thesd proprietary devices I cant get rid of | 02:24:25 |
@hexa:lossy.network | you'd probably have to review the systemd hardening yourself | 02:25:37 |
@hexa:lossy.network | I can't explain all options to you | 02:25:42 |
@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 |