ELK Email substitute Values do not work since moving from ISY to EISY

[JSchumann]

I use email substitute extensively.  When I swapped from ISY to EISY, The ELK substitute values quit working, but the ISY/EIISY ones still work.

Some examples:

${elk.zone.2.name} returns the code in the customization: ${elk.zone.2.name}

${elk.zone.2.status} returns the code in the customization: ${elk.zone.2.status}, not the actual status

Alert.Control should return Home (in one case) but gives GV0

Alert.Action gives Disarmed (seems to work)

Any help Appreciated.  I have a ticket in with UD

I also asked Jimbo, but he said he needs it posted in the forum

Thanks,

John

 

[Jimbo.Automates]

Yes, it's always best to post in the forum first so you get the help of the community and help others in the future.

Those elk references are for the old elk module which isn't available in eisy. The elk plugin substitutions are shown on the PG3 UI under the elk nodes page. I can provide more details if necessary when at a computer. Some more in is in my document https://www.jimboautomates.com/pg3-node-servers
If that doesn't provide the information you need then I'll try to add it.


Sent from my Pixel 8 Pro using Tapatalk

[JSchumann]

So why would we remove/change perfectly good substitures?

Can we get a list or table that shows all the current notifications that work with EISY?  They are scattered throughout the document, and in some cases the GVXX numbers are used for two different things, so it is confusing.  I built an Excel of the commands I found in the document if that helps.

I see GV0 through GV25 commands (minus GV18 and GV20).  I also see ST, name and status being used, are they valid?

So all the commands use the format sys.node.#. command (being GVxx, ST, name and status).  Are there any others, Like Alert Variables, or System variables (sys.node.#.??)?

I assume all the ELK variables are dead (elk.x.#.command)

I am aware of the notifications plugin and how to use it.

Thanks,

John

[Jimbo.Automates]

15 minutes ago, JSchumann said:

So why would we remove/change perfectly good substitures?

Because the Elk module is not supported on Polisy or Eisy, it's a PG3 Plugin now.

16 minutes ago, JSchumann said:

So why would we remove/change perfectly good substitures?

Can we get a list or table that shows all the current notifications that work with EISY?  They are scattered throughout the document, and in some cases the GVXX numbers are used for two different things, so it is confusing.  I built an Excel of the commands I found in the document if that helps.

I see GV0 through GV25 commands (minus GV18 and GV20).  I also see ST, name and status being used, are they valid?

Did you go to the PG3 -> Elk -> Nodes page as I suggested?  No need to build a table, just find the one you want and hit the copy icon on the right.

17 minutes ago, JSchumann said:

I assume all the ELK variables are dead (elk.x.#.command)

Yes, the module is no longer supported.

 

[JSchumann]

Jimbo, Thanks.  I did go to the link you posted but it was the nodes readme, not the table.  I will check it out!

Why couldn't the substitutes be ported over.  Anyway no I need to rewrite a lot of my customizations.

Appreciate your dedication to the module and all your help.

Regards,

John 

[JSchumann]

So Jimbo, what do you recommend I use in these cases.  I have several programs that call a customization.  The custom just calls for the zone that triggered the event and what the trigger is.  i.e. gun safe violated or gun safe clear.  Furnace temp violated or furnace temp normal....and so on

What commands do you recommend I use in the customization?

I previously used alert. Control and alert action.......now don't work.

Thanks,

John

[Jimbo.Automates]

Easiest way is with using a Simple shareable notifications where you use 

${sys.node.#.name} ${sys.node.#.GV0}

For Physical Status, or this for Logical Status

${sys.node.#.name} ${sys.node.#.ST}