Using the web interface and stopping the program is just as unreliable as using toolbox and text console. Its luck of the draw if it stops cleanly or not. I would rather not delete the program folder as there are config files saved there I need for my program. For me when it fails to stop I just let it do its thing for 5 mins and it will eventually restart the previous program, and then I can usually just load in or stop the program manually first. Very rarely do I have to power cycle it.?
?
One thing I do notice is it only seems to happen on Slot 1. That is my main AV slot, and I have several subslots for Lighting/HVAC/Shades/etc, and whenever I load to those I never have any issues. I did open a case with tech support (case# 00260226 feel free to reference) and they wanted the Info Tool logs and program as usual and of course are blaming the program as theres errors in the log. I told them no matter what errors are there it shouldnt prevent stopprog from working. This has to be a firmware related issue and I see it on PRO4 and CP4. If I load the same code to a PRO3/CP3 I have no such issues. It is getting very frustrating as I dont know if I am going to completely kill the system. And if I am loading remotely which is 99.9% of the time and I dont have a Wattbox or other to power cycle it I will be screwed.?
