DennisC

In my case, the node served updated but the version number never changed. You can check this by restarting and checking the log. The log in my case showed the updated version starting. It's also happening with the Elk node server.

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?

Thanks for that, adding raw to the end worked.

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?

Ok, looking again I can see that. It's a long list and reading through it, I lost sight of it being in Area Node. My bad, sorry.

I restarted the Elk Node Server again with log set to debug. I checked in the log file and I see the following: UDI Python Interface for Polyglot version 3 3.0.38 Starting... I do not see any error messages. There are a couple of warnings as follows: 2022-04-01 13:08:17,674 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2022-04-01 13:08:17,675 MainThread udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2022-04-01 13:08:17,675 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'set': [{'key': 'notices', 'value': {}}]} It took me awhile to see where the message keys listed in help appear. I finally found them under the "Area 1" node. As a suggestion, maybe you want to list the location in the instructions?

I just rebooted Polisy with no change. Notification(6) Current Status: Connected Current Version: 3.2.4 [Production] Time Started: Apr 1, 2022, 10:37:45 AM Uptime: 2 Minute(s) 41 Second(s) ELK(2) Current Status: Connected Current Version: 3.1.4 [Production] Time Started: Apr 1, 2022, 10:10:23 AM Uptime: 1 Minute(s) 49 Second(s)

No it does not, neither does logging out and back in, or restarting Polyglot.

@JimboAutomates, @bpwwer I can confirm the same thing happening when upgrading both Elk & Notification Node Servers. Neither updated the version number. Tried the restart option more than once and ssh in to IoP to insure there were no missed updates.

If all else fails and you feel you have a good backup from before the change, you can do a factory reset as a last option. https://wiki.universal-devices.com/index.php?title=Resetting_Your_ISY

Also for clarity, are you talking about 1 switch or multiple switches and are these switches that have never been included in your ISY?

I have made the change to Polisy at two locations for both Insteon and Zwave. The Insteon backup and restore works well, although manual intervention is required. Zwave backup and restore is not yet available. If you are going to make the switch I suggest you copy to clip board all programs and paste in text document for reference. Also take screenshots of all Network Resources. There is nothing I was doing on ISY that I can't do on Polisy. I believe there is currently a discount on Polisy because of PGC being off line. Check the PGC thread.

I have a disabled program in my favorites in UD Mobile. While mine has no if statement, I run it manually, I thought I remembered the icon changing to indicate running. I just ran the if statement manually and it did display a filled in dot in the corner to indicate running. Not sure if the comparison is the same.

I use to use native ISY text messages to send notifications and alerts. For years this worked fine. After recent changes by my cell provider, there were long delays in receiving messages and long messages were cut off. I recently switched to this Node Server and found it to be beneficial with lots of advantages. Besides being very quick, from within a program you can configure different notification "services", by which I mean creating alert names for specific events. Also within a program you can select different notification sounds, priorities (have an alarm - check emergency alert which need to be acknowledged to stop sending), and the ability to send to different devices. When combined with Network Resources, the same message can be used for different occurrences by implementing substitutions within the notification. One suggestion I can make is to be sure to follow the configuration instructions carefully. If you have difficulty with a specific step, post a question here and someone will assist.

I should of asked this question in my prior post. Wile updated version require the step value to be re-added or is it set once and forget? Will backup and restore set this value?

Much better now! Using a step value of 1 opens setpoint change to one value before the current setpoint. Easy to make changes now. Thank you.

Sounds like you are having communication issues. You should think about improving your Zwave mesh.

I have a separate post under Polisy regarding that issue.

I had restarted Polisy before posting here and it didn't correct the issue. Time and date in Polisy is correct, but Polisy sunrise/sunset is not. I have another post in Polisy help section for UD.

Restarting PG3 corrected the issue. Previously, I rebooted Polisy, so restarting Polisy didn't restart the Node Server?

To the current temperature.

@glarsen I have Time Data running on both PG2 & PG3. Both are showing sunrise for today at 06:08 am and sunset at 17:57. According to google sunrise today was at 7:11 am and sunset at 7:01 pm. Same differences are shown for tomorrow in Time Data. PoI is showing correct current time and DST is set up for correct location on Configuration page.

@Michel Kohanim I have two Polisy running, one on version 5.4.1.1 and one on 5.4.1_2. The one running v5.4.1.1 is at my second location and handled the change to Daylight Saving Time without a problem, however, it has sunrise at 08:12:30 am and sunset at 08:00:17 pm. The one at my main location running 5.4.1._2 had an issue with the change to Daylight Saving Time. None of the scheduled programs ran this morning. A check of next run time indicate none of my scheduled programs were to run today. They were all set to run tomorrow. A reboot of Polisy corrected this issue. However, it has sunrise at 08:12:30 am and sunset at 08:00:17 pm. On both Polisy, the sunrise and sunset readings are taken from the banner at the top of the page. According to google, sunrise today was at 07:11 am and sunset is at 07:01 pm. Both Polisy have the correct time and the correct DST rule set in location on the Configuration page. Checking my programs that are scheduled to run off of sunset indicate the correct next run time based on google's time of sunset.

For my thermostat the value is shown as .0, however, the value is always shown as a whole number (70.0, 71.0). Having the picker open to the current value would be ideal.

@Javi, I received the update and checked out the functionality and here are my findings. 1. When changing setpoint with this update, without making any modifications with the edit screen, there is no picker and you must enter a value. This field is accepting an entered value since the previous update. 2. If you edit the Step value and enter a value of .5, you can enter changes by .5 however, there is no impact on the setpoint because a change of .5 rounds up to the nearest whole number. This ends up having no change. 3. If you edit Step value and enter a value of 1, the picker comes back, starting at 0 and going up to 120. Therefore, you need to scroll from 0 to the value you are looking to change the setpoint to. However, you can not enter a value directly by typing, you must use the picker. It appears you can either set the Step value to 1 and use the picker list and you then need to scroll from 0 to your setpoint, or leave it blank and just type your new setpoint (2 digits required) in to the field. Was this your expected behavior? While I appreciate your efforts, it is quicker and easier to leave the Step value empty and just type your new setpoint in now that the field once again accepts input.