EventRunner 6/7

[jgab 2,647]

Because your vremote variable is undefined (nil). 
The error message could be better so in v0.0.47 it will complain that the variable is nil.

[Sjakie 156]

Hello Jan,

Fibaro changed the background in debug window into white and the date, QA id also.

Do you know if it is possible to change it back?

All my colored debugs are more or les unreadable.

Thanks in advanced

[jgab 2,647]

Isn’t there a dark mode (skin) option?

[Sjakie 156]

Yes there is but then all screens are black.

Must get used to it if this the new set up is from Fibaro

Edited October 6, 2025 by Sjakie
Fibaro

[Sjakie 156]

Jan, is it possible to  add what is causing this error?

Please login or register to see this code.

 

[jgab 2,647]

3 hours ago, Sjakie said:

Jan, is it possible to  add what is causing this error?

Please login or register to see this code.

 

Yes, I fix it in next version. 
You have a rule with ".... <X>:<prop>...." where the "object" X is nil. Probably your HT that is faulty or misspelled? 

[Sjakie 156]

Jan perhaps my question was not clear.How I can give the ER Qa a self chosen ID visible in Debug?

When I add child devices I have my QA's at the end of the list.

for example:  "prefix_ID_name_ID_number"

Please login or register to see this attachment.

[jgab 2,647]

Set __TAG to the label ?

Ex.

__TAG = "MyER"

 

[Sjakie 156]

Jan, No debug in  version .48

 

Please login or register to see this attachment.

[jgab 2,647]

Did you set the __TAG and the debug output appears on another label?

Edited October 10, 2025 by jgab

[jgab 2,647]

.

Edited October 10, 2025 by jgab

[Sjakie 156]

Jan, thanks sorry I did something wrong is fixed now.

The only problem is the old "Quickapp580" is still visible in Debug drop downlist.

If click the old notification screen is empty as it should be.

Restart did not clear the old notification how to get rid of it?

Edited October 11, 2025 by Sjakie
remove

[jgab 2,647]

32 minutes ago, Sjakie said:

Jan, thanks sorry I did something wrong is fixed now.

The only problem is the old "Quickapp580" is still visible in Debug drop downlist.

If click the old notification screen is empty as it should be.

Restart did not clear the old notification how to get rid of it?

Ask Fibaro  

[Sjakie 156]

hahaha, nice one!

 

[petrkl12 228]

@jgab

 

there is typo in version 0.0.49

 

Please login or register to see this image.

/monthly_2025_10/image.png.4c311ecb973d18bac2ece491c2441bb6.png" />

[jgab 2,647]

Yes,  there was a bug in my release script.
I've uploaded v0.0.50 where it should be fixed.

[petrkl12 228]

@jgab How to create rule for checking if motion sensor is without moving detection more than 2 days? I would like to change Fibaro Home Profile to Vacation.

 

Using of TrueFor is problematic because my Fibaro has problem with stability and every night there is restart (Unexpected error ... )

 

Fibaro Home Profile states:

Please login or register to see this image.

/monthly_2025_10/image.png.158fb2e5c392ad61faaa39d6704cc1f9.png" />

[jgab 2,647]

I haven't been able to verify it but I think this would work.

Please login or register to see this code.

The sensor:last will return time since the sensor changed state (in seconds).

We .start() the rule so if the sensor is safe it will start to count down (minus the time since the sensor became safe).

This will allow the QA to restart and continue with the time left up until 2 days...

If breached and the sensor later becomes safe the rule will trigger and sensor:last should be close to 0 which will give us 2 days...

 

There is a more complicated way to solve it by implementing some kind of persistent timer that survives restarts, but it is more prone to errors...

[petrkl12 228]

5 hours ago, jgab said:

I haven't been able to verify it but I think this would work.

Please login or register to see this code.

The sensor:last will return time since the sensor changed state (in seconds).

We .start() the rule so if the sensor is safe it will start to count down (minus the time since the sensor became safe).

This will allow the QA to restart and continue with the time left up until 2 days...

If breached and the sensor later becomes safe the rule will trigger and sensor:last should be close to 0 which will give us 2 days...

 

There is a more complicated way to solve it by implementing some kind of persistent timer that survives restarts, but it is more prone to errors...

OK, thanks

 

and is there support for home profiles (read/write)?

[jgab 2,647]

13 hours ago, petrkl12 said:

OK, thanks

 

and is there support for home profiles (read/write)?

I made a change in v0.0.51 so it may work better for some corner cases in trueFor...

 

No, there is no default profile functions. You can add them yourself

Please login or register to see this code.