scene triggered by a not listed trigger

[muc 1]

Long ago I created a scene (id=205), automatically triggered by
--[[
%% globals
Sens1HWert
--]]

Some time later I set it to manual trigger, scene did nothing, I did not delete it.
(Sens1HWert is still used by another scene.)

 

Some days ago I re-activated this scene 205 with a completely different LUA program
with first lines
--[[
%% properties
5 power
--]]
Now this scene was triggered by device with ID=5, BUT by global Sens1HWert TOO !!

 

So I changed the LUA program to ONLY 2 lines

srcTr= fibaro:getSourceTrigger()
print(json.encode(srcTr))

 

Now every time Sens1HWert changes, debug window shows a new line
[DEBUG] 16:37:23: {"type":"global","name":"Sens1HWert","varName":"Sens1HWert"}
or
[DEBUG] 16:38:26: {"type":"global","varName":"Sens1HWert","name":"Sens1HWert"}
or
[DEBUG] 16:39:28: {"varName":"Sens1HWert","name":"Sens1HWert","type":"global"}
or...

 

Have I really to delete this scene?
Or can anyone stop this strange triggering?

 

A happy christmas time to everybody!

 

[cag014 731]

Could you please post the entire code of your scene?

[muc 1]

ONLY 2 lines:

srcTr= fibaro:getSourceTrigger()
print(json.encode(srcTr))

 

NO first lines

--[[

%% ...

--]]

 

it is still the scene with id=205,

which - long time ago - was triggered by global Sens1HWert (still in use by other scenes)

Edited December 22, 2020 by muc

[muc 1]

"solution": restart HC2