"Cannot query interpreter state" in Scene

[pos 22]

Hi

 

I have had a scene running for 6 month without issues. Now it gives an error "[ERROR] 06:43:01: Cannot query interpreter state". This must be due to changes from 4.140 to any of the betas (I only updated to a beta to "eventually solve locking issued with Popp thermostat). No row references of the issue in the LUA... Couldn't be to hard to track this down when I have some spare time. But in the meantime... Anyone with knowledge of where to start looking and what could have caused it?

 

 

/Peo

[morpheus75 77]

I run the 4.153 beta and have seen it a few times on my system. So unfortunately not completely gone yet. I can say that it is less frequent on this beta compared to 4.150

[Jacek Stark 44]

Hey

This issue is when scene is running many time, for exaple in each minute.

 

I set in my scenes maximum instances for 10 and in the end of script i was writen "fibaro:sleep(800);"

Since that i never seen this issue any more. 

 

My ver. fm is 4.152 (HC2)

 

[morpheus75 77]

That would explain why I mainly see in my alarm scenes....

But it didn't happen before the 4.150 update

[speedy 64]

On 1/10/2018 at 11:20 AM, Jacek Stark said:

 

This issue is when scene is running many time, for exaple in each minute.

I set in my scenes maximum instances for 10 and in the end of script i was writen "fibaro:sleep(800);"

Since that i never seen this issue any more. 

My ver. fm is 4.152 (HC2)

 

 

This can also happen if you have separate scenes starting at the same time.

So the delay in (a) our multiple scenes is not a solution.

(ex scene starting when opening the door with a doorsensor scene, IR sensor scene for lights)

 

 

On 1/10/2018 at 9:03 AM, I.Srodka said:

Have you experienced it on the latest beta?

 

Have you changed anything in the code to adress the issue?

There was no mention of this in the change log.

 

I can try (the latest beta) as soon as i get back to the office.

 

*UPDATE.

@I.Srodka

Issue is still here.

This is a BIG problem.

I was at a customers house that uses Fibaro alarm and he gets massive +30s delay in actions when Fibaro alarm is activated (breached).

So no siren, no smokemachine, and some actions are even "lost" so actions that are supposed to happen are not happening.

Image of test debug window on my HC2 (latest beta).

 

Please login or register to see this attachment.

 

Edited January 11, 2018 by speedy

[Jacek Stark 44]

@speedy

 

5 minut temu, speedy napisał:

So the delay in (a) our multile scenes is not a solution.

 

Yes, you are right. But for this moment it is enough for me.

All time I am waiting for the solution of the problem by Fibaro.

[henri-allauch 4]

I confirm 

Please login or register to see this link.

  : This can also happen if you have separate scenes starting at the same time.

I do not know when the error happens if the scene is systematically performed correctly

[speedy 64]

Evidence of issue with Fibaro alarm. (history from version 4.150 but the issue is still present in beta 4.153)

(There was no issues in 4.140)

 

Door device breach @ 11.22.20

Device actions @ 11.22.45 (in event panel) but they never happened, siren was not enabled and no smoke was fired from the smoke machine.

Delay of 25 seconds regarding alarm actions, but what is the most disturbing is that the actions where never started!

 

Event panel:

Please login or register to see this attachment.

 

Fibaro alarm event panel:

Please login or register to see this attachment.

 

 

 

*Post 2, tried with latest 4.154 beta.

 

Issue is still here in beta 4.154.

Depending on your system and scenes activated the freeze can go on for some time.

(Watch the times in the debug window@ 13 and 33 seconds, scenes gets "stopped" mid scene, and continues after the freeze is finished)

 

@Fibaro Please make this a high priority issue, it affects the core stability and function of the entire system.

It has been 4 betas now since the problem was found without a fix.

 

Video:

Please login or register to see this attachment.

 

Screenshot:

Please login or register to see this attachment.

 

 

Edited January 11, 2018 by speedy

[SmartHomeUser 4]

Hi all,

 

I can (unfortunately) confirm the findings of "speedy".

 

The problem is still present in the new beta version 4.154.

Some scenes in my system, called on a timer basis, still occasionally produces the error message "Cannot Query Interpreter State".

 

Fibaro - please investigate this issue and make corrections to the system, using the older versions of firmware there were no problems with exactly the same scenes.

A properly designed real time system should definitely not behave like this.

 

Edited January 16, 2018 by SmartHomeUser

[henri-allauch 4]

Please login or register to see this code.

Thank's

 

[dareszek 7]

Hello also: FIBARO probably did not try, I still have the same problem in version 4.160.
Thanks

[speedy 64]

I can confirm @dareszek findings in version V4.160 

Same problem is sill here, what is going on Fibaro?

 

Please login or register to see this attachment.

[SmartHomeUser 4]

I have also found that the defect is still there in version 4.160  

Seemingly random error reports ""Cannot Query Interpreter State" are generated.

 

Is this really impossible to correct ??

[henri-allauch 4]

Since beta that followed 4.140
We are many to have this message without modify our scenarios.
The message is always present in the 4.160
Other users certainly have also this message, but do not watch their debug messages cyclically.

What are the reasons for this message ?
Has it been added intensionally ? 
Is it a modification of the scene management ?
Is there a hidden event in addition to the message ?

 Could you inform us about the consideration of this problem?

[blokl 2]

I use 4.160. And still the same problem Cannot query interpreter state on a simple lua script.

 

--[[
%% autostart
%% properties
757 value
746 value
747 value
%% weather
%% events
%% globals
--]]

--fibaro:debug( tonumber(fibaro:getValue(421, "value")))
--fibaro:debug( tonumber(fibaro:getValue(757, "value")))
if (
-- ((fibar((fibaro:getValue(421, "value")) == '1' )
--and
 ((fibaro:getValue(757, "value")) < '19.5' )
)
then
    fibaro:call(396, "turnOn");
  --fibaro:debug("aan ")
else
    fibaro:call(396, "turnOff")
  --fibaro:debug("uit ")
end
 

 

[net 8]

Same problem here: New script 4:160

[DEBUG] 14:05:02: klaar
[ERROR] 07:37:00: Cannot query interpreter state

 

A scene checking which zone required heat during the night

 

Please login or register to see this code.

 

[Guest dimonius88]

Im tired to tell my clients that scene delay start is temperary issue......more than one month issue with time delay up to 50sec makes smart home system absolutly useless. 

So dear Fibaro....how we can cooperate with you? 

 

[SmartHomeUser 4]

Hello all,

is there anybody who have heard anything new from Fibaro regarding this issue ??
The system (4.160) still produces loads of unwanted messages :"Cannot Query Interpreter State".

 

Will this ever be solved ??

Edited February 7, 2018 by SmartHomeUser

[domin12 9]

+1

[henri-allauch 4]

@SmartHomeUser  No news from fibaro 

 

I have scene without trigger activated Two time a day ( 5h00 and 17h00 ) who delete debug messages in all scenes and virtual devices

at 5:00 this morning while everything is quiet enough it produced the error "Cannot Query Interpreter State".

 

 

Edited February 9, 2018 by henri-allauch

[speedy 64]

I haven't heard anything, Its really hard saying "Fibaro is working on it" for months now to customers, they start loosing trust in the system.

Its such a critical bug its should have been elevated to "hot fix" status and fixed immediately.

 

Having scenes not working, events not happening, complete freeze in the system and alarm functions not happening, what could be more important to fix?