PG3 ELK Node server send text to keypads

[Jimbo.Automates]

I will have a release of the ELK NS soon which will support sending text to keypads, but it will have the same issue as mentioned here:  https://forum.universal-devices.com/topic/35543-pg3-notification-node-server-330-question/#comment-332635

Please let me know your thoughts on pushing out this update, I hate to break anyone that is currently relying on it.

 

[Bumbershoot]

It won't hurt me, as production is on PG2, and will be for a while yet. 

I like the sounds of what this update will provide, however.  I'll probably install the notification Node server as well due to the Short Custom Content functionality.

[DennisC]

I have been playing around with sending text to Elk keypad. Previously, using the Elk Module, I was sending the OA temp to my keypads and I wanted to reinstate this.

As a test, I have been successful placing the following in the body: 

${sys.date}

${sys.time}

I have even placed ${sys.date} ${sys.time} in the subject and it has worked (does $ & {} count has a character?), even thought I am not sure if it exceeds 16 characters.

However, I can not get the Tempest temperature or humidity value to appear on the keypad using either one in the subject  or both on two lines in the body.

Is this a limitation of the 16 characters and if so, can that be upped so we can pass node server values to the Elk Keypad?

[glarsen]

There is also a restriction on which characters the ELK can display...for instance if a degree or percent symbol is embedded in the string, nothing will display.

Ask me how I know this...?

[Jimbo.Automates]

The $ and { do not count, what counts is what they resolve to.  The 16 character limit is on the ELK, nothing I can do about it.

For illegal characters like the degree, I though the API I was using already took care of that, but sounds like it's not.  I'll put in a fix when I get time, but for now you can add .raw to not get the formatted value.

 

[DennisC]

2 hours ago, glarsen said:

There is also a restriction on which characters the ELK can display...for instance if a degree or percent symbol is embedded in the string, nothing will display.

Ask me how I know this...?

Thanks for that, adding raw to the end worked.

[DennisC]

53 minutes ago, JimboAutomates said:

The $ and { do not count, what counts is what they resolve to.  The 16 character limit is on the ELK, nothing I can do about it.

For illegal characters like the degree, I though the API I was using already took care of that, but sounds like it's not.  I'll put in a fix when I get time, but for now you can add .raw to not get the formatted value.

 

Thanks to @glarsen, using the raw value has it working.

There is no issue with it the way it is, as long as we know the situation. Maybe updating the documentation would help?

[glarsen]

@Javi, @JimboAutomates, I think this update must have broken something with UD Mobile.  I get "java.lang.error: Node Status Relation Cursor is empty. NodeId: 1551. Control:0.500.  I have restarted the ISY and the reloaded the app with no change. 

Edit: The node status fields all display, but none of the CMD fields appear. All of the grouped nodes show.

[Javi]

Thanks @glarsen,  this error is likely related to an invalid init value for a command parameter.

@JimboAutomates,  do you have an init value set to "0"  for a NodeDef.Accepts.Parameter somewhere?

[Jimbo.Automates]

Thanks @glarsen,  this error is likely related to an invalid init value for a command parameter.
@JimboAutomates,  do you have an init value set to "0"  for a NodeDef.Accepts.Parameter somewhere?

Yes, probably in a complex cmdp structure
I'll send you the nodedef when I get home.

Sent from my Pixel 6 Pro using Tapatalk

[Jimbo.Automates]

@Javi, @JimboAutomates, I think this update must have broken something with UD Mobile.  I get "java.lang.error: Node Status Relation Cursor is empty. NodeId: 1551. Control:0.500.  I have restarted the ISY and the reloaded the app with no change. 
Edit: The node status fields all display, but none of the CMD fields appear. All of the grouped nodes show.

Does this happen on sync? Or when you open that node in UD Mobile?

Sent from my Pixel 6 Pro using Tapatalk

[glarsen]

When the Area node is opened in UD Mobile.  The zones are fine.

[Jimbo.Automates]

3 hours ago, glarsen said:

When the Area node is opened in UD Mobile.  The zones are fine.

This is fixed in 3.2.2, but there is still an issue which I think will require an update to UD Mobile.  I apologize to @Javi that I didn't give him access to this to test with the new editor that Chris added before this was released.

[DennisC]

52 minutes ago, JimboAutomates said:

This is fixed in 3.2.2, but there is still an issue which I think will require an update to UD Mobile.  I apologize to @Javi that I didn't give him access to this to test with the new editor that Chris added before this was released.

After running the update and syncing UD Mobile, the error changed to: java.lang.Error:UOM Suffix is null. 500

[Jimbo.Automates]

After running the update and syncing UD Mobile, the error changed to: java.lang.Error:UOM Suffix is null. 500

Yes already provided that info to @Javi

Sent from my Pixel 6 Pro using Tapatalk

[Javi]

12 hours ago, DennisC said:

After running the update and syncing UD Mobile, the error changed to: java.lang.Error:UOM Suffix is null. 500

Thanks, the new UOMs have not been updated on the app side, they should be in the next release.

[DennisC]

On 4/4/2022 at 9:31 AM, Javi said:

Thanks, the new UOMs have not been updated on the app side, they should be in the next release.

Hi @Javi,

Just checking, if the expectations was that the recent releases were to fix the UOM error, it hasn't. I am still getting that error.

[Javi]

3 hours ago, DennisC said:

Hi @Javi,

Just checking, if the expectations was that the recent releases were to fix the UOM error, it hasn't. I am still getting that error.

Hi @Dennis,

Not yet fixed, the last release was already in the pipeline.