Hmmbob

Results 77 comments of Hmmbob

Pychromecast fails to start Spotify

Yes, indeed it did. ```py 2023-09-03 20:35:06.439 ERROR (Thread-15) [pychromecast.socket_client] [(192.168.88.113):8009] Exception caught while sending message to controller SpotifyController: Message urn:x-cast:com.spotify.chromecast.secure.v1 from 540d6d97-a77a-4043-a45b-42cf5ba5f411 to sender-0: {'type': 'getInfoResponse', 'payload': {'version': '2.9.0',...

Uncaught (in promise) {code: 'not_found', message: 'Subscription not found.'}

![image](https://user-images.githubusercontent.com/33529490/211259820-71a81f9c-cbe8-45db-adce-45d8ce1c4cfb.png) Still happening on 2023.1.1

ForecastSolar throws trace when API rate limit is hit

As discussed over Discord, it would be great if this error is caught and just prints a single error/line in the log

Trigger Update Coordinator: Running script requires passing in a context

Still there on 2023.9.2

Trigger Update Coordinator: Running script requires passing in a context

And still here on 2023.10.0b2

Trigger Update Coordinator: Running script requires passing in a context

Still here on 2023.11.0b0

Trigger Update Coordinator: Running script requires passing in a context

Just a note to indicate it is still existing on 2023.12.0b1 (which makes sense because the PR hasn't been merged yet)

Trigger Update Coordinator: Running script requires passing in a context

And still existing on 2024.1.0b5 (so it also isn't fixed by anything else, is my point ;) )

Trigger Update Coordinator: Running script requires passing in a context

Just dropping a note to prevent this becoming stale, as it is still occurring on 2024.2.0b1

Use `input_datetime` for completion time

That's actually a fair point. I'm not sure how I envisioned this 😉 This request (or example) makes little sense, as most lowest prices in our (NL) weekends happen Saturday...