fsedarkalex

Same issue here with kubeadm 1.23.4 / CRI-O 1.23 / Flannel on Debian 11

@MadMakz dann wohl eher einen alive-check des daemon durch ansprechen desselben. Nciht der GameServer. Wennd er Daemon weg ist Meldung an den Admin. Oder aber blind auf den Daemon vertrauen....

I would highly appreciate storing the password two-way-encrypted somewhere so that a reload of the page does not require a relogin... Currently every app change in NC does a full...

nextcloud/server#2044 is merged now. I noticed current version of JSXC on NC12 is a bit more stable but also loses connection after a while.

I second this request and I love the duggestion of @verement - much cooler (and more stable) than my approach (same idea but other selector)

Confirmed. ``` 2024-02-12 13:58:36.562 ERROR (MainThread) [homeassistant.components.automation.bad_jalousie] Bad-Jalousie: Error executing script. Unexpected error for call_service at pos 2: 'position' Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 485, in _async_step...

Weird thing for me is, it actually moves but crashed the automations afterwards.

My automation does not proceed after setting the tilt angle. The trace shows the error outlined before.Sent from NineVon: Brian ***@***.***>Gesendet: Montag, 12. Februar 2024 22:56An: home-assistant/coreCc: fsedarkalex; CommentBetreff: Re:...

Unfortunately for me this workaround would not work.I'd be required to redesign the automation in a much more complex way.Will just wait for the fix.Sent from NineVon: Brian ***@***.***>Gesendet: Dienstag,...

This is a great idea. Maybe configurable as an option per step "continue on error" just as it is with timeouts in wait steps. ------ Originalnachricht ------ Von "Brendan White"...