Eddie

> For the sake of isolating the problems, can you disable all hardware acceleration and see if the job advancing? As a data point: I am not using hw acceleration...

This is the error I am getting in v123.0, right before the jobs start hanging. ``` immich_server | [Nest] 8 - 01/06/2025, 9:23:27 AM ERROR [Microservices:JobService] Unable to run job...

> On my side, it still persists. I have to pause the job and run it with gaps; otherwise, my server will just consume unlimited power aka money 😄 Where...

Just wanted to mention that adding matplotlib also can lead to this error. Adding `deepdiff>7.0.0` fixes the issue.

I'd like to throw in my two cents. I case room level accuracy is enough, and I think it is enough for the vast amount of people, then a neural...

> @dekiesel Yeah, it's probably the most classic application for NN. Though at such small scale it's apparent that it's just curve fitting based on statistics. So calling it AI/NN/etc...

Slight correction, the same happens when using `datetime.time` ``` def initialize(self): run_at_time_object = datetime.time.fromisoformat(run_at_time) self.run_at(self.run_actions, run_at_time_object) ``` This yields the same outcome: `run_at` triggers immediately when the time is in...

Am I really the only one with this issue? Is there a workaround? Or am I just using it incorrectly?

As a workaround I've created a file in `helpers` called `time_functions.py` with the following content: ``` from datetime import time from datetime import datetime, date def seconds_to(run_at_time: time | str)...

Wow this is embarrassing. I've been using appdaemon for at least four years now and your comment made me realize just now that `listen_state` is just a shorthand for `listen_event("state_changed")`...