-
-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot choose channel when creating rule to trigger on Thing Event #1996
Comments
i had the same problem. Also on 4.0.1 |
Would be cool to have e fix for 4.0.2. |
@lolodomo |
ghys
added a commit
that referenced
this issue
Aug 17, 2023
Fix #1996. Better solution IMO than openhab/openhab-core#3761. Signed-off-by: Yannick Schaus <github@schaus.net>
florian-h05
pushed a commit
that referenced
this issue
Aug 18, 2023
Fixes #1996. Regression from #1661. Supersedes openhab/openhab-core#3761. Signed-off-by: Yannick Schaus <github@schaus.net>
florian-h05
pushed a commit
that referenced
this issue
Aug 19, 2023
Fixes #1996. Regression from #1661. Supersedes openhab/openhab-core#3761. Signed-off-by: Yannick Schaus <github@schaus.net> (cherry picked from commit 3eff1fa)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem
I have a fresh install of Openhabian, running Openhab 4.0.0 on a raspberry pi. I want to create a rule to trigger on a thing event. When creating the rule in the UI, I choose "Thing Event". As the thing I choose "Local Sun (astro:sun:local)", which I know for a fact produces events that I can also see at expected intervals in the events log. But when I then click on "channel" to choose the correct one, nothing happens. It doesn’t show a new dialogue, it’s just dead.
Expected behavior
A dialogue should open showing the different thing event channels to choose from.
Steps to reproduce
Click: Settings -> Rules -> (+) -> Add Trigger -> Thing Event -> Choose thing with events (Local Sun in my case) -> Channel
Your environment
Browser console
Additional information
I tried to work around this by manually adding the channelUID to the rule in the code tab, but it fails to trigger from the event, even though I have verified the event itself triggered from the logs. I'm not sure if this is a symptom of the same problem, or a different one.
The text was updated successfully, but these errors were encountered: