I added a check for the disabled attribute in my plugin. I found that in the JavaScript code the type of the disabled variable has a type of string in native Vera but number on ALTUI.
var deviceID = api.getCpanelDeviceId();
var deviceObj = api.getDeviceObject(deviceID);
if (deviceObj.disabled === '1') {
Does not evaluates to true on ALTUI because of this type difference. I now added a check for the value of 1 numeric as a workaround, but just wanted to let you know.
Also when you change the value in ALTUI it does show the confirmation dialogue, and there is a message that a LUUP restart will happen, but that does not seem to be the case (not seeing any ‘controller did not respond’ message either).
I added a check for the disabled attribute in my plugin. I found that in the JavaScript code the type of the disabled variable has a type of string in native Vera but number on ALTUI.
var deviceID = api.getCpanelDeviceId();
var deviceObj = api.getDeviceObject(deviceID);
if (deviceObj.disabled === '1') {
Does not evaluates to true on ALTUI because of this type difference. I now added a check for the value of 1 numeric as a workaround, but just wanted to let you know.
Also when you change the value in ALTUI it does show the confirmation dialogue, and there is a message that a LUUP restart will happen, but that does not seem to be the case (not seeing any ‘controller did not respond’ message either).
Cheers Rene[/quote]
thank you. very strange indeed. I checked and ALTUI does not try to be smart here, it gives you back what it received from the “user_data” http request to vera, “?id=user_data&output_format=json” (http://wiki.micasaverde.com/index.php/Luup_Requests)
so if possible, I would be very curious to check your result to this http request for this device to see what you get back here from vera to verify if the issue is not at the “source”.
you could maybe just use == instead of === to avoid forcing the exact identity of type
if (deviceObj.disabled == '1')
Best Home Automation shopping experience. Shop at Ezlo!