| 1 Mar 2025 |
 @hexa:lossy.network | * diff --git a/cmake/onnxruntime_providers_openvino.cmake b/cmake/onnxruntime_providers_openvino.cmake
index 143d002c61..c7ad02b94d 100644
--- a/cmake/onnxruntime_providers_openvino.cmake
+++ b/cmake/onnxruntime_providers_openvino.cmake
@@ -37,7 +37,7 @@
source_group(TREE ${ONNXRUNTIME_ROOT}/core FILES ${onnxruntime_providers_openvino_cc_srcs})
onnxruntime_add_shared_library_module(onnxruntime_providers_openvino ${onnxruntime_providers_openvino_cc_srcs} "${ONNXRUNTIME_ROOT}/core/dll/onnxruntime.rc")
- onnxruntime_add_include_to_target(onnxruntime_providers_openvino onnxruntime_common onnx nlohmann_json::nlohmann_json)
+ onnxruntime_add_include_to_target(onnxruntime_providers_openvino onnxruntime_common onnxruntime_framework onnx nlohmann_json::nlohmann_json)
install(FILES ${PROJECT_SOURCE_DIR}/../include/onnxruntime/core/providers/openvino/openvino_provider_factory.h
DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}/onnxruntime/)
set_target_properties(onnxruntime_providers_openvino PROPERTIES CXX_STANDARD 20)
| 19:17:28 |
| @hexa:lossy.network | no change | 19:17:38 |
| @hexa:lossy.network | https://github.com/microsoft/onnxruntime/issues/9756 | 19:19:46 |
| @hexa:lossy.network | this is also /great/ | 19:19:48 |
| 2 Mar 2025 |
| @hexa:lossy.network | frigate 0.15.0 PR is up, needs more testing https://github.com/NixOS/nixpkgs/pull/386266 | 01:22:27 |
| @hexa:lossy.network | still investigating crashes of the test suite on aarch64-linux | 01:24:27 |
| @hexa:lossy.network | 
Download image.png | 01:36:09 |
| @hexa:lossy.network | 
Download image.png | 01:36:25 |
| @hexa:lossy.network | config now gets copied to /run/frigate/frigate.yml and you can make changes in frigate and see them in there | 01:36:50 |
| @hexa:lossy.network | still need to sync them back, or they'll get reset on restart | 01:36:58 |
|  @dont.wanna.tell:matrix.org joined the room. | 19:52:46 |
| 3 Mar 2025 |
| @hexa:lossy.network | * For Frigate users: SSDlite mobilenet v2 model converted into the OpenVINO IR Format required for the detector: https://shells.darmstadt.ccc.de/~hexa/omz/ | 03:09:38 |
|  bendanm joined the room. | 04:43:41 |
| @hexa:lossy.network | For Home Assistant users: Please check the article on the Wiki for how to get started | 05:17:57 |
| @hexa:lossy.network | (just pinning some messages, since element has been hiding the topic for a while) | 05:18:31 |
| @hexa:lossy.network | * (just pinning some helpful messages, since element has been hiding the topic for a while) | 05:18:35 |
 Lyn (they/she) | been using homeassistant on nixos for a few days now and I kinda struggle with figuring out where to put what, is there any documentation/unofficial wiki for the declerative (YAML) syntax? seems homeassistant themselves in many cases removed the YAML section from their documentation entirely in favor of showing off the UI-flow, how do y'all deal with this when writing config? | 06:19:16 |
| @hexa:lossy.network | hm, they do advertise the yaml config where it is still applicable | 06:20:25 |
| Lyn (they/she) | * been using homeassistant on nixos for a few days now and I kinda struggle with figuring out where to put what, is there any documentation/unofficial wiki for the declarative (YAML) syntax? seems homeassistant themselves in many cases removed the YAML section from their documentation entirely in favor of showing off the UI-flow, how do y'all deal with this when writing config? | 06:20:26 |
| @hexa:lossy.network | if you want to use a component that does not have any yaml config it needs to go into extraComponents | 06:21:00 |
| @hexa:lossy.network | * if you want to use a component that does not have any yaml config it needs to go into extraComponents for the package to come with the required dependencies | 06:21:16 |
| Lyn (they/she) | so I just pull up the docs for the integration and if there is no yaml I configure it inside the UI and it won't get overwritten by nix? | 06:22:04 |
| Lyn (they/she) | * so I just pull up the docs for an integration and if there is no yaml I configure it inside the UI and it won't get overwritten by nix? | 06:22:11 |
| @hexa:lossy.network | yep | 06:22:12 |
|  Jaco joined the room. | 13:21:39 |
 philipp | How are y'all using the nixos module? Currently my setup is in a weird and kinda unmaintainable setup that's half declaratively generated and half created with the webui and I think switching to either fully would be an improvement. I'd like to have it all declarative, but I haven't really found a good workflow. How are you going at it? Write automations/scenes in the webui and then generate nix expressions from that, or do you write them directly in nix? | 19:55:34 |
 Geoffrey Frogeye | Bit of both. For the kind of automations I haven't done before, I do in the webui and convert yaml to nix expressions. Or at least the complicated parts (e.g. interacting with a device I haven't already an automation interacting with it). Otherwise Nix directly, copying existing code and modifying it to my needs. I do have a few helpers (functions and options), making this easier to write on the long run. | 20:10:12 |
| philipp | Thanks! I think I'll try to do something similar, that seems like a reasonable compromise solution. | 20:12:55 |
| philipp | (Let's hope I find the motivation to actually move imperative configs over to nix this time 😅) | 20:13:25 |
 Sandro 🐧 | You already looked at https://wiki.nixos.org/wiki/Home-assistant ; right? | 23:08:16 |
