Hello, I am having a similar issue. Prime 2.0, upgraded controllers from 184.108.40.206 to 220.127.116.11. Have you been able to work out why ? We have found that if you remove the controller from Prime and add it again it works fine, this issue only seems to occur if you upgrade a controller that was allready being monitored by Prime.
... View more