Jimbo.Automates Posted March 30, 2022 Share Posted March 30, 2022 The Polyglot Version 3 Notification Node server 3.3.0 is ready but not yet released. This version uses a feature that is only available with ISY On Polisy 5.4.2 which was just released today so I am going to hold off and ask if anyone has an issue if I release it. I'm not sure how it will act on older ISY versions. The problem is if I release it and PG3 restarts it will automatically upgrade. I will try to test on my production machine which is not yet upgraded, but in the meantime I want to ask if everyone using it was ok with forcing ISY 5.4.2? Please comment below. It has a really nice new feature: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#short-custom-content Link to comment
mbking Posted March 31, 2022 Share Posted March 31, 2022 I’ve upgraded to IoP 5.4.2 and I’m excited to see the ELK node server get the ability to send messages to the keypads. Thanks for adding the feature @jimboautomates.Sent from my iPhone using Tapatalk Link to comment
brians Posted March 31, 2022 Share Posted March 31, 2022 I am fine you releasing it... that is a nice feature. I currently prefer network resources because I can add in variables etc. and this will make it much easier to do and keep track of. Link to comment
Jimbo.Automates Posted March 31, 2022 Author Share Posted March 31, 2022 @mbking I have it almost working for ELK, hopefully release soon @brians Thanks. Hopefully everyone who isn't responding feels the same Also, you can use Variables and any other system info in Custom Content, the only thing you loose is shorter length, and ability to set other params like device, priorty, sound... but that can always be done from the calling program. I was also thinking to add a single program command which could send all params in one call. Link to comment
asbril Posted March 31, 2022 Share Posted March 31, 2022 1 hour ago, JimboAutomates said: but that can always be done from the calling program Can you explain this ? Link to comment
Jimbo.Automates Posted March 31, 2022 Author Share Posted March 31, 2022 34 minutes ago, asbril said: Can you explain this ? You set the values for device, priorty, sound ... on the service node https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#service-nodes as shown the documentation I already referenced https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#short-custom-content which shows this picture https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/pics/Program_NotifyTestSysShort.png Link to comment
tmorse305 Posted April 1, 2022 Share Posted April 1, 2022 Hi @JimboAutomates, very nice addition. I'm missing something in the example you provided. How is information about it being the ecobee Node server communicated? I see the generic customizations you created but I'm missing how it gets linked to the ecobee ns when the program calls it. Also wouldn't the Short Custom Content line need to be ahead of the Send Sys Short in the example? Thank you. Link to comment
brians Posted April 1, 2022 Share Posted April 1, 2022 I usually set the parameters in programs already instead of doing it all in the NR... I just keep the NR simple. This way they are all similar and I can choose to use the quick custom method currently in PG3 dashboard, or NR and rest of the setup remains consistent. I don't think setting up a NR resource is any more difficult than a customization once you do a couple, but customization makes more sense and would not have the IP address hard-coded in case Polisy IP changes. Here is my Network Resource for Alarm Disarmed - Brian It uses the Envisalink DSC Node server, and I have a Yale Assure Z-Wave lock. The only things I change are top Protocol Information and the Body at lower left. Here is the program that calls it... The only difference would be in the program would call use a customization instead of a Network Resource. Link to comment
Jimbo.Automates Posted April 1, 2022 Author Share Posted April 1, 2022 Hi @JimboAutomates, very nice addition. I'm missing something in the example you provided. How is information about it being the ecobee Node server communicated? I see the generic customizations you created but I'm missing how it gets linked to the ecobee ns when the program calls it. Also wouldn't the Short Custom Content line need to be ahead of the Send Sys Short in the example? Thank you.Yes, the custom content would contain the info about what it wants to post about the Ecobee node server.Sent from my Pixel 6 Pro using Tapatalk Link to comment
tmorse305 Posted April 1, 2022 Share Posted April 1, 2022 41 minutes ago, JimboAutomates said: Yes, the custom content would contain the info about what it wants to post about the Ecobee node server. Yes I get that but the content in the customization is generic. How does it get linked up to ecobee when the message is sent? Are the variables in the customization populated from attributes of the program calling it it? Link to comment
Jimbo.Automates Posted April 1, 2022 Author Share Posted April 1, 2022 Yes I get that but the content in the customization is generic. How does it get linked up to ecobee when the message is sent? Are the variables in the customization populated from attributes of the program calling it it?They can be yes, with ${sys.program.#.name} and ${sys.node.#.ST) https://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_VariablesSent from my Pixel 6 Pro using Tapatalk Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.