OK so I tracked the down the back end issue……
I had a typo in my ‘allowed addresses’ on the IP of the Mikrowizard box….
HOWEVER, the core issue still remains, it’s one thing for something to ‘not work’ and ‘error’ and it be hard to track down….
It’s another that because Python freaked out about getting booted from SSH it kept running the script over and over….
So basically, a REBOOT command should not be sent to the router, unless all previous ssh related activities are completed without error… and/or the python script that’s trying to do all this stuff, should be fixed, so that when it can’t connect to SSH it doesn’t cause a panic exit / death of the python script and handles it properly and gracefully…
in other words, if SSH is ‘refused’ for one reason or another, Python shouldn’t freak the heck out, and it should log an error of “SSH Connection failed”
and in the instance of firmware check / update / upgrade, the background task should also GO AWAY, instead of trying over and over, and causing devices to reboot several to potentially infinite numbers of times.
