As far as I tested, line below is sending to CPE  setParametrValue from provision, but sending getParametrValue from VirtualParameter.
declare(“Device.WiFi.AccessPoint.1.Security.KeyPassphrase”, {value: Date.now()}, {value: ‘testpassword’});
 
Is it meant to be like this?
             
            
              
            
           
          
            
              
                kyob  
              
                  
                    November 20, 2019, 12:57pm
                   
                  2 
               
             
            
              No sure I fully understand your question but you mean something like this:
declare("VirtualParameters.*", {value: Date.now()});
let  myNewVP = declare("VirtualParameters.myNewVP", {value: 1}).value[0];
declare("Device.WiFi.AccessPoint.1.Security.KeyPassphrase", {value: Date.now()}, {value: myNewVP});
 
            
              
            
           
          
            
            
              No, I’m trying to replicate example from documentation, where you can Create an editable virtual parameter for WPA passphrase , but with args[] instead of VALUES.getParameterValue instead setParameterValue:
declare("Device.WiFi.AccessPoint.1.Security.KeyPassphrase", {value: Date.now()}, {value: 'testpass'});
return {writable: true, value: 'testpass'};
But the same declare() statement in a provision script is sending setParameterValue to CPE.
I’m trying to make unified parameters for wifi ssid and passphrase in tr-098 and tr-181 data models.
             
            
              
            
           
          
            
              
                lavira  
              
                  
                    November 21, 2019,  7:51am
                   
                  4 
               
             
            
              AFAIK a declare statement does both!
declare("Device.WiFi.AccessPoint.1.Security.KeyPassphrase", {value: Date.now()});
declare("Device.WiFi.AccessPoint.1.Security.KeyPassphrase", {value: Date.now()}, {value: 'testpass'});if the new value (‘testpass’) is different from the existing one 
I think you perceived it’s behaving differently because in the provision script you have a extra declare at the begining of the script just for refreshing the value and in this case the declare with value to set does just a setParameterValue RPC.
You should use null  for the second parameter to do just a SPV eventually:declare(“Device.WiFi.AccessPoint.1.Security.KeyPassphrase”, null, {value: ‘testpass’});
             
            
              
            
           
          
            
            
              I’m so confused rn.null  for a second parameter and it didn’t work.null in second parameter.
easycwmpd: ACS initiated connectionmy-ip :7547/
 
That’s what I get in CPE log with {value: Date.now()} in second parameter.
easycwmpd: ACS initiated connectionmy-ip :7547/
 
That’s what i get in CPE log when changing Device.WiFi.AccessPoint.1.Security.KeyPassphrase normal way from giu.
easycwmpd: ACS initiated connectionmy-ip :7547/
 
             
            
              
            
           
          
            
              
                zaidka  
              
                  
                    November 23, 2019, 10:05pm
                   
                  6 
               
             
            
              Are you using v1.2 or v1.1?
             
            
              
            
           
          
            
            
              I’m using latest github release v1.2
             
            
              
            
           
          
            
              
                zaidka  
              
                  
                    November 24, 2019,  9:11pm
                   
                  8 
               
             
            
              So that was a bug and I have just fixed it. Try the latest master branch.
             
            
              
            
           
          
            
            
              It’s working well, thanl you. When will it be available in npm?