Do you know how/when this was introduced? For example, if already running openHABian 1.8 and then upgrading to 4.0, will the suddenly trigger this? Or was it a package upgrade that caused this to happen some time ago when already running openHABian 1.8?
Maybe I wasn’t too clear above: It is NOT an openHAB issue it is Debian bug where someone introduced a wrong symlink behavior as far as I understand. It seems it was fixed in April but I also have the feeling that this is still the part of the openhaben bullseye version - at least I still have the problem.
See the details linked about it here
So, It isn’t an openHAB issue per se but rather part of the bullseye that comes with openhabian. Maybe someone has an idea how we can update bullseye to a point where we know this is not an issue anymore (I currently don’t have the time to do so and try it out as I am happy that my complex OH4 production setup finally runs almost everything like before).
Jacob, do we want to add it into your great list above? How about adding an index above that description that gives a quick overview on all topics like
Upgrade to 4.0 using openHABian doesn’t seem to work at all.
TransformationService of type ‘JS’ is unavailable
ScriptEngine for language ‘application/javascript’ not found
Blocky rules not working: PolyglotException: ReferenceError
High CPU usage
Channel types or config descriptions are missing in the respective registry
Rule does not trigger on Astro event
Shelly: Incompatible units
EnOcean: Handler EnOceanBridgeHandler tried updating the thing status although the handler was already disposed.
openJDK17 fails due top dependencies when you are still in Theo Buster Release of Debian or openHABian
Deconz Conbee II stick not detected on Debian bullseye
I had this issue with 4.0.0 M1 as soon as I upgraded way back in April first reported here
On several occasions I thought I had tracked it down but it is still a problem for me. (happen yesterday) currently running 4.0.0 snapshot 3460
Memory usage
The Java upgrade seems to be using quite some more memory than before and memory reserves are tight particularly if you are on on Raspberry. See corresponding question in the FAQ .
But I couldn’t find the corresponding question here…
BTW: I set
Another work around is to link the equivalent State Channel to a DateTime Item and use the Time is Item trigger for the rule. That works in the UI as well as file based.
I was reading the PR’s, but reading does not mean understanding - thats too complex for my simple mind
Is there a way to check those EventTrigger-Issue for simple “end-users”?
Im running OH with 442 things, 1839 items, 322 rules (all in DSL)… I’ll have a horrible night, thinking of maybe checking everything or maybe updating a massive portion of my configuration…