[Solved] AltUI v1.17.1264 problem with J_ALTUI_verabox.js on IE 11

Plugins & Plugin Development Alternate UI
1

Hi amg0,

I was just doing some testing and tried to open ALTUI wint Internet Exploder 11, and guess what. Boom…

It throws an fatal error on line 71 : evaluateConditions(deviceid,devsubcat,conditions) {
It want to see a semicolon : in the line.

Not getting the error with Firefox or Chrome.

Cheers Rene

2

[quote=“reneboer, post:1, topic:191590”]Hi amg0,

I was just doing some testing and tried to open ALTUI wint Internet Exploder 11, and guess what. Boom…

It throws an fatal error on line 71 : evaluateConditions(deviceid,devsubcat,conditions) {
It want to see a semicolon : in the line.

Not getting the error with Firefox or Chrome.

Cheers Rene[/quote]
thx, should be fixed in last release

3

Thanks amg0,

Just downloaded it and it does work on openLuup but not on my Veras. It stays on waiting initial data. I did find one warning on the initial data_request that is from a unmatched tag on line 633 od L_ALTUI.lua. So removed that as it looked simple enough and now all browsers failed on that AltuiDebug.SetDebug is not found in J_ALTUI_uimgr.js. After some more tinkering more and more stared to fail, so I have to revert the issue back to you.

Also my plugins that used to have their own drawing routines registered are not drawing on the devices page anymore on openLuup. I see that for RulesEngine it still works, did something change? I am not seeing anything in the log files or Firebug.

I also see a third problem for plugins that call a handler on Vera (still works on openLuup). Each time I try that the handler call fails and I see this in the Vera log files.

 luvd_get_info mg conn can't read /etc/cmh-ludl//data_request/data_request or /etc/cmh-lu//data_request/data_request from filename /data_request/data_request pPtrFile (null)

This is the request parameters in the js console log.

DeviceNum 63 id lr_GetMessages63 output_format json serviceId urn:otgw-tclcode-com:serviceId:OpenThermGateway1 timestamp 1458037372998

Cheers Rene

4

[quote=“reneboer, post:3, topic:191590”]Thanks amg0,

Just downloaded it and it does work on openLuup but not on my Veras. It stays on waiting initial data. I did find one warning on the initial data_request that is from a unmatched tag on line 633 od L_ALTUI.lua. So removed that as it looked simple enough and now all browsers failed on that AltuiDebug.SetDebug is not found in J_ALTUI_uimgr.js. After some more tinkering more and more stared to fail, so I have to revert the issue back to you.

Also my plugins that used to have their own drawing routines registered are not drawing on the devices page anymore on openLuup. I see that for RulesEngine it still works, did something change? I am not seeing anything in the log files or Firebug.

I also see a third problem for plugins that call a handler on Vera (still works on openLuup). Each time I try that the handler call fails and I see this in the Vera log files.

 luvd_get_info mg conn can't read /etc/cmh-ludl//data_request/data_request or /etc/cmh-lu//data_request/data_request from filename /data_request/data_request pPtrFile (null)

This is the request parameters in the js console log.

DeviceNum 63 id lr_GetMessages63 output_format json serviceId urn:otgw-tclcode-com:serviceId:OpenThermGateway1 timestamp 1458037372998

Cheers Rene[/quote]

can you try a full reinstall ( based on v1292 I just posted ) and lets try the trouble shooting from here.

since the LUA module version number increased, the configuration variable was reset to its default meaning if you have plugins which manually registered themselves without using the UPNP api, you have to re-register them, or communciate to me your plugin registrations so I include it in the default.

5

Hi amg0,

For the issues with IE the latest version works as does the data handlers.

For getting stuck on the waiting initial data it is a tiny difference between openLuup and Vera. On openLuup you must use :3480, but on Vera you can use either /port_3480 or :3480 on Firefox and Chrome, but not on IE. IE only works with /port_3480.

The issue with the handlers or my plugins is similar. Works fine on Vera when using /port_3480, fails when using :3480. Any browser.

So in short use /port_3480 on Vera in all cases. Fixed all my reported issues.

Man, I though I was going bonkers on this one :o

I am working a bit more on my plugins, but especially for the Harmony it may be worth to include it in your default release as quite a lot people use it. Once I have it ready I will send you a PM.

Cheers Rene

6

Great , sounds cool.