This is actually strange. The only possible reason I can think of is if runtime error happens in the script. In this case script is interpreted as if it would return true (this will be reworked in next release). But script run-time error would be visible in the log file. And your script looks to be correct.
I would increase active discovery interval to 3600 - this is to make sure that discovery processes would stop. Then try setting server debug level to 6 (hopefully it's a test environment with not too many nodes - otherwise there will be too many lines in the log). And try to run discovery scan manually - select the range and click scan. The log should have detailed information on how discovery is happening.
Hi,
I think that we should have TR-069 support. I have registered it as feature request: https://track.radensolutions.com/issue/NX-1777. I'll try to experiment with it as time permits.
Best regards,
Victor
