EventRunner 5

[Sjakie 156]

Jan good morning and the best wishes for 2024!!

I am struggling a bit with date

Please login or register to see this code.

In the first rule you use "-" to include

the second rule you use "-" as separation

Logic should be the same meaning >> include

Thanks

[jgab 2,641]

6 minutes ago, Sjakie said:

Jan good morning and the best wishes for 2024!!

I am struggling a bit with date

Please login or register to see this code.

In the first rule you use "-" to include

the second rule you use "-" as separation

Logic should be the same meaning >> include

Thanks

No, it should be include in the last too, i.e, 1,2,3,4,10

Edited January 1, 2024 by jgab

[jgab 2,641]

16 hours ago, jgab said:

 

Ok, I think I know how to fix that with a custom property....

but that's for tomorrow - now it's time to put on the tuxedo... 🍾

 

Ok, my first attempt with a custom prop

Please login or register to see this code.

:ledOn will use the table values if it's a declared "special led", otherwise call standard turnOn

:ledOn can not be used as a trigger, only an action.

:ledOn on a table of leds will call :ledOn on each of them.

Edited January 1, 2024 by jgab

[jgab 2,641]

One could also patch the standard :on prop function, but then :on for a special led will always go through the table values.

(same mapSpecialLed etc)

 

Please login or register to see this code.

 

Edited January 1, 2024 by jgab

[jgab 2,641]

Ok, pushed v1.0 of ER5  

 

small fixes.

 

One thing that may cause issues is the 

Please login or register to see this code.

that creates a Fibaro global variable will return true if the variable is created and false if it already existed.

This means that you have to be aware if you use it in a condition.

 

but we can now do

Please login or register to see this code.

 

Edited January 1, 2024 by jgab

[ChristianSogaard 71]

Happy Newyear - and great work with with EV5, lets celebrate v1.0 💥🎉

[ChristianSogaard 71]

My Ghost detection rule triggered  again -im going to create a support case.

I am enabling this rule before update, and disabling it again after the update - if it keeps triggering, then i need a reboot

--rule("@@00:05 => log('i am a creep')")
[01.01.2024] [11:19:24] [DEBUG] [QUICKAPP2059]: i am a creep

[jgab 2,641]

2 minutes ago, ChristianSogaard said:

My Ghost detection rule triggered  again -im going to create a support case.

I am enabling this rule before update, and disabling it again after the update - if it keeps triggering, then i need a reboot

--rule("@@00:05 => log('i am a creep')")
[01.01.2024] [11:19:24] [DEBUG] [QUICKAPP2059]: i am a creep

Are you using QA Updater, v:0.72 ? (it disables the QA before update)

[ChristianSogaard 71]

Just now, jgab said:

Are you using QA Updater, v:0.72 ? (it disables the QA before update)

Yes - Updater, v:0.72. 

[jgab 2,641]

Just now, ChristianSogaard said:

Yes - Updater, v:0.72. 

Ok. Then that is not a solution... Would be nice to come up with a minimal QA that always cause a ghost process when saved.

[ChristianSogaard 71]

2 minutes ago, jgab said:

Ok. Then that is not a solution... Would be nice to come up with a minimal QA that always cause a ghost process when saved.

i can PM you the "developing rules"  EV5 i have , it seems to do it often or always. Its not too many rules
I saved it before updating

Edited January 1, 2024 by ChristianSogaard
Typo

[jgab 2,641]

1 minute ago, ChristianSogaard said:

i can PM you the "developing rules"  EV5 i have , it seems to do it often or always. Its not too many rules
I saved it before updating

Yes, I can see if it cause it for me too...

[Neo Andersson 230]

1 hour ago, jgab said:

 

Ok, my first attempt with a custom prop

Please login or register to see this code.

:ledOn will use the table values if it's a declared "special led", otherwise call standard turnOn

:ledOn can not be used as a trigger, only an action.

:ledOn on a table of leds will call :ledOn on each of them.

Thanks, Jan , i will try it,..many thanks

My approach was something similar, but not that neat.

[Neo Andersson 230]

38 minutes ago, jgab said:

Ok. Then that is not a solution... Would be nice to come up with a minimal QA that always cause a ghost process when saved.

@jgab@ChristianSogaard@Sjakie

 

One thing to be added for information..

I have a core ER5, with a Home table set, but without any non time based rule / only @time triggers are present and some rule variable definitions.

This QA never ever started a ghost process.

So this led me to a conclusion, that it is not the core ER5 that causing the ghost process, rather it is some rule, and seems that only when the QA file is getting large..

This is only my  assumption

I have also sent a ticket to support,and I would like to ask you, to do so too,to have them notice that something is really buggy here, but to be honest, i don't await too much of help from them in this matter..

I think we need to find the sepcific reason that triggers these ghosts, to be able to more directly pinpoint the problem for them.

And this is kinda crucial, at least for me, becuase this retains me back from further usage of ER5 on other systems.

I would like to use ER5 on all of my customer's systems, but at this point i can't move on.

Even with those 5 systems that have ER5 i am having really hard times.

So guys, i hoppe, we will find it together somehow..

And Happy New Year for all of you..

 

Edited January 1, 2024 by Neo Andersson

[ChristianSogaard 71]

I created a fresh EV5 v.1.0 QA using the updater.

Please login or register to see this attachment.

 

Do i need to change something to view the extra logging ? 

I only see it from my two other instances.

Please login or register to see this image.

/monthly_2024_01/image.png.769d714c785355ac98fa638d2b7cb840.png" />

 

[jgab 2,641]

17 minutes ago, Neo Andersson said:

@jgab@ChristianSogaard@Sjakie

 

One thing to be added for information..

I have a core ER5, with a Home table set, but without any non time based rule / only @time triggers are present and some rule variable definitions.

This QA never ever started a ghost process.

So this led me to a conclusion, that it is not the core ER5 that causing the ghost process, rather it is some rule, and seems that only when the QA file is getting large..

This is only my  assumption

I have also sent a ticket to support,and I would like to ask you, to do so too,to have them notice that something is really buggy here, but to be honest, i don't await too much of help from them in this matter..

I think we need to find the sepcific reason that triggers these ghosts, to be able to more directly pinpoint the problem for them.

And this is kinda crucial, at least for me, becuase this retains me back from further usage of ER5 on other systems.

I would like to use ER5 on all of my customer's systems, but at this oint i can't move on.

Even with those 5 systems that have ER5 i am having really hard times.

So guys, i hoppe, we will find it together somehow..

And Happy New Year for all of you..

 

Well, the factors I can see are

- setTimeouts. There are several setTimeouts running in parallel. Even with very large system it's usually < 100

- net.HTTPClient calls, usually only done by rules, except for polling system triggers with api/refreshStates

- api.* REST calls to the api. Done by the core system on regular interval.

- The size of the QA - ~200-300kb

- The amount of memory used - however, it's quite stable and doesn't grow continuously. 

 

We only seem to get a ghost when the QA is re-saved (either manually or by QAUpdater). I have not seen a QA spontaneously create a ghost.

Question: can just a restart (without re-save) of the QA create a ghost? I haven't seen that.

 

In my latest QAUpdater 0.72 I disable the QA to be updated. It means that it restarts but don't run :onInit() - which would minimise the factors listed above being a problem. However, @ChristianSogaard still sees ghosts being created.

 

For me that would mean that the ghost is created already when I disable the QA (and it restarts). 

Or, it has nothing to do with what is actually running in the QA (because :onInit() is not run), and it must depend on the number of QA files and their sizes.

Ex. @Neo Andersson has added a number of his own files and experiences a lot of ghosts, so maybe their is some kind of limit here...

 

 

1 minute ago, ChristianSogaard said:

I created a fresh EV5 v.1.0 QA using the updater.

Please login or register to see this attachment.

 

Do i need to change something to view the extra logging ? 

I only see it from my two other instances.

Please login or register to see this link.

 

No, in v1.0 all logging is by default on QUICKAPP<ID>

(it was too confusing with 2 labels)

[Neo Andersson 230]

46 minutes ago, Neo Andersson said:

Thanks, Jan , i will try it,..many thanks

My approach was something similar, but not that neat.

Jan this doesnt work.

Neither when manually turn on a led, nor when from LUA..Colors, brightness never changes, maybe it is due to the key from global variable?

Cause it returns string and define it like below, where night and day are not in quotes. Or it doesnt matter when they are in rule?

 

Please login or register to see this code.

[jgab 2,641]

Just now, Neo Andersson said:

Jan this doesnt work.

Neither when manually turn on a led, nor when from LUA..Colors, brightness never changes, maybe it is due to the key from global variable?

Cause it returns string and define it like below, where night and day are not in quotes. Or it doesnt matter when they are in rule?

 

Please login or register to see this code.

No it doesn't matter.

The 'red' and 'white' needs to be replaced by the string sent to setColor with the RGB values you want.

 

[Neo Andersson 230]

7 minutes ago, jgab said:

No it doesn't matter.

The 'red' and 'white' needs to be replaced by the string sent to setColor with the RGB values you want.

 

they are

 

    blue = {0,0,255,0}

    red = {255,0,0,0}  

    white = {255,255,255,255}

5 minutes ago, Neo Andersson said:

they are

 

    blue = {0,0,255,0}

    red = {255,0,0,0}  

    white = {255,255,255,255}

If i log out ledValues in getProp function i got this

 

Please login or register to see this code.

 

but it seems that it doesnt find the proper value in the table with the dayPart key

 

Yes this logs out nil

 

Please login or register to see this code.

 

Please login or register to see this attachment.

Edited January 1, 2024 by Neo Andersson

[Neo Andersson 230]

39 minutes ago, Neo Andersson said:

they are

 

    blue = {0,0,255,0}

    red = {255,0,0,0}  

    white = {255,255,255,255}

If i log out ledValues in getProp function i got this

 

Please login or register to see this code.

 

but it seems that it doesnt find the proper value in the table with the dayPart key

 

Yes this logs out nil

 

Please login or register to see this code.

 

Please login or register to see this attachment.

Okay, this is what i get from sepcialLed table

 

Please login or register to see this code.

 

evidently, dasyParts are replaced with some numbers