[Solved] Strange Rule Behavior

Hi guys… it’s been a while since my last post…

actually I’m running OH 5.0.2 Release Build

I’ have a rule which switches the lightscenes in my livingroom which works fine.

a few days ago I began integrating an external display running openhasp which communicates via mqtt with json…

I wrote some rules for the communication to bind some items to the openhasp buttons, etc. on the display.

and now to my problem:
when I change the lightscene via openhab webui or android app everything works fine, even the openhasp dropdown gets updated to the right value and text…
BUT when I chose from the dropdown on the openhasp display, the item also changes, even the app and webui reflect the change - and so the log does, but the lightscene rule does not get fired even if the triggeritem changes which makes me wonder because i see no difference…

in both cases the item changes but only “internal changes” out of openhab seem to be recognized by the rule…

JSRule({

name: “Lighting - LightScenes”,

description: “manage livingroom lightscenes”,

triggers: \[triggers.ItemStateChangeTrigger(“LightScene”), triggers.ItemStateChangeTrigger(“MaxBrightness”)\],

execute: (data) => {

and this is logged:

[openhab.event.ItemStateChangedEvent ] - Item 'LightScene' changed from LAZY to Mexico

I tried to fix this for some days now… several restarts etc but after all it still feels weird that the item changes but the rule is not firing - and if I do the same out of OH the rule fires and everything is fine…

maybe anyone had some similar behavior? to be honest I have no idea what happens…

Ok, I realized it was probem case sensivity in the commands from openhasp…

Everything runs fine now… Sometimes when you stare at a thing for to long it becomes a bit fuzzy.

So sry my fault to not realize such an obviious error :wink: