openhab-addons: [telegram] errors on startup, binding only working after refreshing rules
Expected Behavior
Telegram binding working in rules
Current Behavior
after restarting OpenHab multiple log file entries appear in openhab.log:
The field Tmp_eventRules.telegramAction refers to the missing type Object
Possible Solution
workaround: After restarting Openhab I have to edit a rule to reload it. After this the Telegram binding is working
Steps to Reproduce (for Bugs)
happens after every reboot
Context
community forum: Link
Your Environment
- Version used: openHAB 3.0.1 with Telegram binding 3.0.1
- Operating System and version (desktop or mobile, Windows 10, Raspbian Buster, …): Raspbian current version with Docker
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 19 (7 by maintainers)
I get the same error and all the rules that contains TelegramActions can’t run. They just give me the following error
[ERROR] [internal.handler.ScriptActionHandler] - Script execution of rule with UID ‘machineStates-4’ failed: null in machineStates
The errors goes away after reloading of the rule and everything works as it should until next reboot. All my rules are file based
Hi @Skinah , Unfortunately it is not fixed. At least it is still happening here. Thank you!
Thanks for the feedback. Since this is not related to a particular binding and most likely it was a core issue. I will close this issue as there have been no recent reports of this on the forum so its probably fixed, if not it should be reported as a core issue.
The same workaround that cybermcm verified above works for me as well. Regarding 2) same issue with different bindings, i got the same error with mqtt binding and I can confirm that the same workaround fixad the issue with that binding as well. So, as Skinah suspected this seems more like a bug in the core and not in the binding. I did a really quick search in the core for already open issues, but didn’t find any
@cybermcm workaround works, but it’s not a solution. It seems to be not only a Telegram actions problem, but a common action problem. I have the same behavior with MQTT binding.
val mqttActions = getActions("mqtt","mqtt:broker:exxxxxxxx5")mqtt actions are not working after openhab3 restart. But after a rules file modification the actions are working.