I can see this warning upon restart of the computer related to the problem I faced today:
2026-01-20 09:58:48.913 [WARN ] [el.core.internal.ModelRepositoryImpl] - DSL model 'lights.rules' has errors, therefore ignoring it: There is no context to infer the closure's argument types from. Consider typing the arguments or put the closures into a typed context.
There is no context to infer the closure's argument types from. Consider typing the arguments or put the closures into a typed context.
There is no context to infer the closure's argument types from. Consider typing the arguments or put the closures into a typed context.
There is no context to infer the closure's argument types from. Consider typing the arguments or put the closures into a typed context.
When I search on the error, I found this:
I am not a software engineer, but I understand the explanation in the linked topic that it is better to avoid definition of the variable types.
I checked the rule file and I can only see the following declarations:
var Timer tmrLightHall
var Timer tmrLightOffice
var Timer tmrLightOfficeButton
var Timer tmrChristmassLights
var Timer tmrFrontEntranceLights
var Timer tmrLightBBQ
var Timer tmrLightKitchen
var Timer tmrLightCarport
var LightBedroomColorCurrentState = LightBedroomColor.state as HSBType
val pState = lamp.persistedState(now.minusDays(7), "rrd4j")
The last declaration appears 4 times, and that is “enhancement“ by Google Gemini that I used to correct ZonedDateTime warnings on my presence simulation that was working for 5-6 years.
I suspect this is the problem, since I see also 4 entries at the start.
On the other hand, if the machine is running and I tried changing the extension to something and back to rules, all started working. No logs no errors.