Just a quick update for the other users in this thread: I spent some time in a shared session this morning with Pulseway support. They gathered a lot of information, and are doing some internal testing to try and reproduce this issue. Once more is understood about this issue, and more headway is made, I will update here.

The support team is still trying to figure out this issue. Nothing new to report.

Hey everyone,

 

Lewnatick worked with us and we've identified the issue. If there is anyone that still has the problem please contact support [at] pulseway [dot] com.

 

Regards,

Chris

Pulseway Team

  On 1/20/2015 at 9:22 PM, Chris said:

Hey everyone,

 

Lewnatick worked with us and we've identified the issue. If there is anyone that still has the problem please contact support [at] pulseway [dot] com.

 

Regards,

Chris

Pulseway Team

 

I can vouch for what Chris said above. The support team did indeed get things working again, and I greatly appreciate their help.

Many thanks Lewnatick and Chris - been running the fix for a couple of days and it's back to normal. Appreciate both your efforts.