Script.disable not working 5500NAC firmware 1.15.0

[Benny_A]

after updating 5500NAC to 1.15.0 it seems that script.disable() is not working 

i have resident script with the below code 

log('Script running')
script.disable('test')

but it appears script dose not get disabled and the script keeps logging 

[Krishnakant]

@Benny_A 

We tried to reproduce the issue you mentioned with v1.15.0 but were unsuccessful. Can you help us gather more information about the issue? Specifically, we would like to know:

1. More details about the exact script name and script content. Please note that script names and function names are case-sensitive.
2. Was this script written in v1.15.0, or was it already present and stopped working after upgrading the controller to v1.15.0?
3. any additional information that could help us identify the root cause of the issue

[Benny_A]

HI,

So

1- firmware was 1.14.0 then upgraded to 1.15.0

2- then i decided to make new resident script (script was not present under1.14.0)

3- new resident script called "test" all lower case

4- resident script 'test' has only the following code

log('Script running')

script.disable('test')

5- script continues to log 'Script running' and is not disabled. 

[Erwin-vd-Zwart]

could you try script.disable(_SCRIPTNAME) and see if that does work or not?

And can you also perform a log(_SCRIPTNAME) as that should return the name of current script so you can compare it with your entered scriptname.

[Benny_A]

Hi,

i changed it to script.disable(_SCRIPTNAME) - same result script is not disabled and keeps logging

log(_SCRIPTNAME) returns 'test' - as expected.

just to see if it made any difference I changed the name of the script from 'test' to 'test123' now it works... and script is disabling... 

are there any script names that are not allowed? is the word 'test' related to some internal variable perhaps?

[Erwin-vd-Zwart]

Hi,

I just checked and i think you might have found a bug (:

Do you perhaps have a resident/event/scheduled script with the same script name 'test' ?

I think you do and script.disable is disabling that other script with the same name.

I will report to R&D that it should not be possible to have a event/resident/scheduled script with the same name because that is possible at this moment and will cause conflict with script.enable/disable.

Could you let me now if you have another script with the same name?

[Benny_A]

Hi Erwin, 

Yes after looking I have also a Scheduled script with the name 'test'

[Erwin-vd-Zwart]

That clarifies it, for now make sure to use unique script names when you combine it with script.disable/script.enable and i already have reported it, feedback i got so far is that it always has been like this, but they will look into it for future FW versions.