Closed ako-3004 closed 3 years ago
See forum post https://community.openhab.org/t/issues-after-update-to-oh-3/115352
... Loading model 'home.mqtt.wohnzimmer.led.rules' ... Loading model 'home.mqtt.wohnzimmer.wohnwand.rules'
The filenames using dot notation with the same words are the problem.
Sometimes things are fixed quite easy... thanks a lot! That did it!
Sorry to open another issue with this behaviour, found other issues with a similar - but not the same behavior. The problem is also discussed here https://community.openhab.org/t/rules-stopped-working-after-upgrading-to-oh3/112201 but the solution does not work for me - it seems there is still a bug.
I already own a OH2.5 on a raspberry 3, for not running into conflicts my decision was to start from scratch and build up a new and clean system. So I set up a completely new OH3 based on openhabian-image on raspberry pi 4 (8 GB). There I created the first things, items and rules based on files from my OH2.5.
Based on many tests I can confirm that all rules run fine and without errors after beeing edited and saved, but never run after a system reboot.
On system boot the log reports 2 rule files to be loaded successful:
one rule for example has this simple code. I tried wit logInfo() on many rules, after reboot none of them ever fires.
so it should be triggered after system start and every 10 seconds. But it does not. then after a reboot I just have to open the rule file, change it and safe it. Almost instant, the rule begins to work and fires based on its cron setting.
All rules work correctly after beeing manually initialized (Some switches and LED RGB Controls) without any errors. But never after a reboot.
I would describe myself as a basic OH user, with basic experience. I try my best to give needed information for finding a solution for this.