"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

[henri-allauch 4]

Please login or register to see this code.

Thank's for your answer

[Tony270570 107]

hi @henri-allauch unfortunately not solved in 4.161, I still have the message after the update. 

[Guest RichardHoman]

I've been talking to different owners of Fibaro's HC2. All being neatly updated to the latest firmware. 

 

Some of them do not have this problem. This leads me to think that it's something the users do that upsets the system. 

This is still a bug ofcourse and should be fixed by Fibaro ASAP. But this also means that there must be a way for users to circumvent this problem.

 

@Fibaro, is there any information available which may help us to minimize the impact of this bug until an actual fix is published by you guys?

Edited March 7, 2018 by RichardHoman

[SmartHomeUser 4]

4.162 still produces the error message "Cannot Query Interpreter State".

Seems like Fibaro is unable, for some reason, to take this seriously and come up with a solution.

... or is the problem to complex to fix ??

Edited March 12, 2018 by SmartHomeUser

[dareszek 7]

+1

[henri-allauch 4]

Please login or register to see this code.

Followed by many User concerned

No response No action From FIBARO

Disappointing

 

[Guest RichardHoman]

Just got an answer from Fibaro:

 

Quote

Dear Richard Thank you for your email. It looks like you received the info about case being closed by default from our case management system. We cannot influence it, sorry about that. But it doesn’t mean that your case was abandoned. Our software developers discovered that this problem has much bigger severity than they expected, thus it is taking so long. However today we received information that they plan to release a hotfix in next update. It should be available by the end of this month. We apologize that you are waiting for so long. Please let me know if you have any questions. --  Pozdrawiam,  Regards,  Roman Schmidt  Key Account Engineer  Fibar Group S.A.  ul. Lotnicza 1  60-421 Poznań  Poland  Email: [email protected]  Tel: +48 61 880 1000  Web: www.fibaro.com  NIP: 781 185 80 97  KRS: 0000553265  KZ: 1.063.850,00 PLN

 

Let's hope this is accurate....

[Guest RichardHoman]

After testing for a little under one day with 4.170, it seems that this update has actually fixed the issue!

For me at least...

Edited March 23, 2018 by RichardHoman

[SmartHomeUser 4]

It really seems to have been corrected in 4.170.
Running for several hours now and still not a single error message !!

Thank you very much for this Fibaro

[speedy 64]

@RichardHoman @SmartHomeUser

There is no notes of this in the changelog so i think its not fixed as Fibaro said, its a massive bug so it would be featured in that is it was fixed.

 

The message might be gone (removed) but the freeze is still there, and its even more prominent than before!

*I can get it to freeze by just starting 1 scen after further testing.. this update is a nightmare..

 

Tested with this simple scene and got the standard 10 sec freeze and a minute freeze directly.

 

Look at these times from debug window, 14.22.21 to 14.23.21 a minute freeze and suddenly 5 scenes, with complete block of HC2 and CPU freeze.

Please login or register to see this attachment.

 

CPU freeze

 

Please login or register to see this attachment.

 

Scene is as simple as can be, jus try to quickly start 1-2 scenes with the "play" button (don't have time to post video right now)

Change scene number 166 to the same number of your scene.

Please login or register to see this code.

 

The scene order can also be shifted, so the scenes switch places and are not executed in the correct order.. according to debug window.

Please login or register to see this image.

/monthly_2018_03/5ab5055060886_Sceneorder.png.6dad8718a03a509e0c39320d43ed7000.png" />

 

 

Edited March 23, 2018 by speedy

[Guest RichardHoman]

Without even testing the scene above, I have to say I do still notice some weirdly long delays every now and then.
Seems like they indeed just removed the notice. But the error remains!

 

However: During these time-outs I do not see CPU usage drop to zero.

Edited March 23, 2018 by RichardHoman
Added the however

[speedy 64]

6 minutes ago, RichardHoman said:

Without even testing the scene above, I have to say I do still notice some weirdly long delays every now and then.

Definitely sound like the freeze issue.

 

6 minutes ago, RichardHoman said:

However: During these time-outs I do not see CPU usage drop to zero.

My CPU does not drop to 0, it just happened to freeze right there while testing.

It freezes where the CPU usage is at the moment.

 

[Guest RichardHoman]

3 minutes ago, speedy said:

It freezes where the CPU usage is at the moment.

 

 

CPU usage still goes up and down while I'm waiting for a scene to run (or finish running). I may start one or more scenes which will not run/complete until the freeze is over. But even during the freeze, CPU usage is active, not staying at a certain percentage.

Edited March 23, 2018 by RichardHoman

[speedy 64]

5 minutes ago, RichardHoman said:

But even during the freeze, CPU usage is active, not staying at a certain percentage.

 

Interesting, so there might be several issues then, a freeze that doesn't block CPU GUI, but scenes are blocked anyway.

I use OSX (latest) and Safari (latest 11.0.3) while looking at CPU.

Edited March 23, 2018 by speedy

[Guest RichardHoman]

24 minutes ago, speedy said:

 

Interesting, so there might be several issues then, a freeze that doesn't block CPU but scenes are blocked anyway.

I use OSX (latest) and Safari (latest 11.0.3) while looking at CPU.

 

I'm on Win10 and Chrome, but I can not imagine that active webclients have anything to do with this.. you never know though..

Edited March 23, 2018 by RichardHoman

[speedy 64]

6 minutes ago, RichardHoman said:

I'm on Win10 and Chrome, but I can not image that active webclients have anything to do with this.. you never know though..

Tried it with parallels, my CPU gets frozen at the current % so no change due to webclient.

[dareszek 7]

The problem of "freezing" still remained unchanged, but the message "can not ..." does not appear in the scenes ...

[net 8]

I would like to read an official comment from Fibaro.........

After 4 months..

Right now, removing the message gives me the impression if they are sweeping it under the carpet.

Edited March 26, 2018 by net

[T.Konopka 8]

The issue has not been completely solved. If we will be sure about that, you will see a mention in the release notes.

 

For now, we addressed the issue and we achieved 'something' - mainly, we limited the occurrence frequency. The issue is treated with high priority - I was assured about that.

[T.Konopka 8]

Guys, as you tested the solution with scenes that can reproduce the issue, please, send me those scenes via private message. Title the message "Cannot query interpreter state - scene for tests".