Jimbo.Automates Posted January 26, 2022 Posted January 26, 2022 The Polyglot Version 3 Notification Nodeserver 3.0.3 is released. See the README for more information, including information on moving from PG2. The Release Notes are also available. 1 1
asbril Posted January 26, 2022 Posted January 26, 2022 Question...... Following your explanation yesterday, I am going to copy all the data from my PG3 Notification nodeserver and enter the same in exact same in exact same order in the PG3 nodeserver. You explained that if I use same slot, then (in principle) I should not have to redo my programs. Because I currently have the PG3 nodeserver in a different slot than the PG2 ns, I will have to delete both the PG2 and the PG3 nodeservers and then reinstall the PG3 in the same slot as originally the PG2. Will the system allow me to reinstall the nodeserver without having to pay for the purchase again ?
Jimbo.Automates Posted January 27, 2022 Author Posted January 27, 2022 Question...... Following your explanation yesterday, I am going to copy all the data from my PG3 Notification nodeserver and enter the same in exact same in exact same order in the PG3 nodeserver. You explained that if I use same slot, then (in principle) I should not have to redo my programs. Because I currently have the PG3 nodeserver in a different slot than the PG2 ns, I will have to delete both the PG2 and the PG3 nodeservers and then reinstall the PG3 in the same slot as originally the PG2. Will the system allow me to reinstall the nodeserver without having to pay for the purchase again ?Yes, the license will be fine. Sent from my Pixel 6 Pro using Tapatalk 1
asbril Posted January 27, 2022 Posted January 27, 2022 13 hours ago, Jimbo said: Yes, the license will be fine. Sent from my Pixel 6 Pro using Tapatalk Success ! Thanks to following your instructions step-by-step ? 1
DennisC Posted March 6, 2022 Posted March 6, 2022 @JimboAutomates, I'm curious as to how dependent the Notification Nodeserver using Pushover is on an internet connection to work and how dependent is it on external Pushover services? Can any of the notification methods tied to the N/S function if external Pushover service has an outage or failure? I am trying to determine if it is necessary to establish a secondary notification method for critical notifications?
Jimbo.Automates Posted March 6, 2022 Author Posted March 6, 2022 @JimboAutomates, I'm curious as to how dependent the Notification Nodeserver using Pushover is on an internet connection to work and how dependent is it on external Pushover services? Can any of the notification methods tied to the N/S function if external Pushover service has an outage or failure? I am trying to determine if it is necessary to establish a secondary notification method for critical notifications?The NS is dependent on both. If it detects an error when trying to send it sets an error condition on the node and for most errors it will retry. So, IMO, it is much more reliable than using email or NR from ISY. But, you can check that error status and send a notification another way if you like.I've considered trying to send an email when there is an error that looks to be an issue with the pushover service, but that won't happen for a while.Sent from my Pixel 6 Pro using Tapatalk
DennisC Posted March 6, 2022 Posted March 6, 2022 10 hours ago, JimboAutomates said: The NS is dependent on both. If it detects an error when trying to send it sets an error condition on the node and for most errors it will retry. So, IMO, it is much more reliable than using email or NR from ISY. But, you can check that error status and send a notification another way if you like. I've considered trying to send an email when there is an error that looks to be an issue with the pushover service, but that won't happen for a while. Sent from my Pixel 6 Pro using Tapatalk If an error is thrown after a message delivery failure, is the error specifically for the failed message or a general Pushover error message? Example, if multiple messages are sent around the same time, can you tell which one failed? Also, if you have repeat option set for x number of tries, will the error be thrown after the first failure, or if all retries fail?
Jimbo.Automates Posted March 6, 2022 Author Posted March 6, 2022 3 hours ago, DennisC said: If an error is thrown after a message delivery failure, is the error specifically for the failed message or a general Pushover error message? Example, if multiple messages are sent around the same time, can you tell which one failed? Also, if you have repeat option set for x number of tries, will the error be thrown after the first failure, or if all retries fail? The error types are in the README - Service Nodes There is no way to tell which message caused the error if multiple are sent at the same time, you'd have to handle that in the ISY programs. Unless you can think of how the NS could help with this, I'm not sure what can be done. You can create a unique service node for your emergency messages, and flag the error condition differently on those which will increase your chance of just catching errors for those. The retries is a option specific to Pushover Emergency messages, as mentioned in the README above. It is not related to the NS retrying on a failure to send. A failure to send sets the node status each time it happens, and is not reset back until a message goes thru. The methods used by the NS are a big improvement over using NR's or email directly from ISY, but I'm always open to suggestions for improvement. 1
DennisC Posted March 6, 2022 Posted March 6, 2022 14 minutes ago, JimboAutomates said: The error types are in the README - Service Nodes There is no way to tell which message caused the error if multiple are sent at the same time, you'd have to handle that in the ISY programs. Unless you can think of how the NS could help with this, I'm not sure what can be done. You can create a unique service node for your emergency messages, and flag the error condition differently on those which will increase your chance of just catching errors for those. The retries is a option specific to Pushover Emergency messages, as mentioned in the README above. It is not related to the NS retrying on a failure to send. A failure to send sets the node status each time it happens, and is not reset back until a message goes thru. The methods used by the NS are a big improvement over using NR's or email directly from ISY, but I'm always open to suggestions for improvement. Thanks for taking the time for the extra info. 1
Recommended Posts