a53eebe2f3
the main error was a suppressed update when the value does not change, but the readerror gets None this error was the reason for strange behaviour in frappy.proxy while finding the cause, other improvements were done: - nodeStateChange: add 'activating' to the possible online states - improve status handling in proxy Change-Id: I2a1873065ab051bdba2200f50e6ad09ae55e168e Reviewed-on: https://forge.frm2.tum.de/review/c/secop/frappy/+/33901 Tested-by: Jenkins Automated Tests <pedersen+jenkins@frm2.tum.de> Reviewed-by: Enrico Faulhaber <enrico.faulhaber@frm2.tum.de> Reviewed-by: Markus Zolliker <markus.zolliker@psi.ch>