Just came across this gem (I don't know how I missed it!)

This is now going to keep me up a bit - and likely save me over a hundred network rules!

No joy

I get this received:

with this RAW payload:
{"device_type": "device_status", "device": "${sys.node.#.name}", "id": "#", "property": "ST", "value": ${sys.node.#.ST.raw}, "status": "${sys.node.#.ST}"}

This is the program triggering the NR:

I've been meaning to test that as well. [emoji20] Also hoping program name can also be used?

Sent from my Pixel 6 Pro using Tapatalk

5 hours ago, MWareman said:

No joy

I get this received:

with this RAW payload:
{"device_type": "device_status", "device": "${sys.node.#.name}", "id": "#", "property": "ST", "value": ${sys.node.#.ST.raw}, "status": "${sys.node.#.ST}"}

This is the program triggering the NR:

Some show d.quotations around them and one doesn't.

@MWareman,

Looking into it.

With kind regards,
Michel

I don't know how I missed that Michel misspelled Insteon in fix #1.  I guess the love affair is truly over.

-Tom

12 hours ago, larryllix said:

Some show d.quotations around them and one doesn't.

Correct.

In JSON - for strings you put the value in quotes. For numbers, you omit the quotes. If the substitutions operated then the quotes (or lack of) would make far more sense!

7 hours ago, Michel Kohanim said:

@MWareman,

Looking into it.

With kind regards,
Michel

Thank you Sir!

Michael.

I get this most times when I first login. The next logins work fine after inserting my ISY creds. Later the same thing happens again. I will recheck this later and tomorrow to see if it forgets again.

@MWareman,

Can you please temporarily add ${alert.event} to your resource string just to see if the event that caused the program to run is what you expected?

With kind regards,
Michel

@larryllix,

Definitely related to PG2 and mongo. It's fixed in PG3.

With kind regards,
Michel

8 minutes ago, Michel Kohanim said:

@MWareman,

Can you please temporarily add ${alert.event} to your resource string just to see if the event that caused the program to run is what you expected?

With kind regards,
Michel

I get this when I test with that:


I know it's invalid JSON (for testing only) - but this is the resource string:
{"device_type": "device_status", "device": "${sys.node.#.name}", "id": "#", "property": "ST", "value": ${sys.node.#.ST.raw}, "status": "${sys.node.#.ST}"} ${alert.event}

In case it matters - here is the resource config:

Could be one of a few possibilities .. it looks like there is no event occuring that is causing the program to run (i.e. manually doing a 'Run Then'), or, for some reason we are not properly storing the event with the program, or, the event gets cleared from the program prior to the NR being used.

We'll take a look at it, and hopefully reproduce the problem here.

On 11/10/2021 at 10:00 AM, Chris Jahn said:

Could be one of a few possibilities .. it looks like there is no event occuring that is causing the program to run (i.e. manually doing a 'Run Then'), or, for some reason we are not properly storing the event with the program, or, the event gets cleared from the program prior to the NR being used.

We'll take a look at it, and hopefully reproduce the problem here.

I could understand that (manually being triggered - though I would hope it would put a 'default' value in based on the use of 'runThen', 'runElse' etc).

In my case - it's a program triggering from the change in status of an Insteon device. The NR is called from the 'Then' clause of the program. The Insteon device involved is exposed to Google Assistant - and I am using Google Assistant to turn the Insteon device on and off - triggering the program and then the NR.

@MWareman,

Thank you very much for the feedback and definitely high on the list after:

Time zone is changing by itself!
Nodedef upload from Portal does not work

And, right now, we hope to have initial version of Z-Wave out before the end of the month. We're getting there!
 

With kind regards,
Michel