ALTUI : Best Practice on how to report an Issue

Thread for reporting issues with ALTUI

feel free to create a new msg thread for your issue so that lengthy discussion can happen if needed.
please be as precise as you can when reporting an issue. at least I would need:

[ol][li]- browser type & version[/li]
[li]- Vera type & version[/li]
[li]- Javascript console log extract[/li]
[li]- Ideally a screen shot showing the problem[/li][/ol]

Console Chrome ( Ctrl + Shift J )

[ol][li]Click on the 3 horizontal lines button.
[/li][li]Go to More tools[/li]
[li]Choose JavaScript console[/li][/ol]

EDIT : I unstick this topic so that we can have one thread per issue.

I am trying the Multi State control on a custom panel. I can create it, and set its properties. But often the ‘Variable’ property will change on me after I click Save. But not always. If I correct the Variable a few times it will usually stick at some point.

In my example I am using the Multi State to arm/disarm a motion sensor. I set Variable to Armed and set up the other properties. After saving I look and variable is now Mode Setting and not Armed. Another time it changed to Version Info. There are no errors in the debug console as I do this.

Once I get the Variable to stick the Multi State control appears to work perfectly.

Vera3 / Chrome v44 / AltUI v0.64.596

–David

[quote=“dklinkman, post:2, topic:188331”]I am trying the Multi State control on a custom panel. I can create it, and set its properties. But often the ‘Variable’ property will change on me after I click Save. But not always. If I correct the Variable a few times it will usually stick at some point.

In my example I am using the Multi State to arm/disarm a motion sensor. I set Variable to Armed and set up the other properties. After saving I look and variable is now Mode Setting and not Armed. Another time it changed to Version Info. There are no errors in the debug console as I do this.

Once I get the Variable to stick the Multi State control appears to work perfectly.

Vera3 / Chrome v44 / AltUI v0.64.596

–David[/quote]

Very strange, I cannot reproduce it. let me know if you find a way to reproduce it easily.
on the other hand, you can go to Misc / Debug and press the “Javascript code” button.
then type in: PageManager.getPageFromName(“xxxx”) where xxx is the name of your custom page, if you can do this at several time so we see when the button variable is being changed

Hmm, new update and now I can’t launch DM. No button to go to the DM GUI.

Can you go into ALTUI device, chec the “Config” variable ? you can click on "view " to see it in a nicer JSON editor. you need to find the entry with " urn:schemas-cd-jackson-com:device:DataMine:1 "

if not, please erase it, click “default configuration”, click “set configuration” and reloap luup + refresh browser and try again.

default should be :

{"urn:schemas-micasaverde-com:device:PowerMeter:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawPowerMeter","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-micasaverde-com:device:SmokeSensor:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawSmoke","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-a-lurker-com:device:InfoViewer:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawInfoViewer","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-upnp-org:device:IPhoneLocator:1":{"StyleFunc":"ALTUI_IPhoneLocator.getStyle","DeviceDrawFunc":"ALTUI_IPhoneLocator.drawIPhone","ScriptFile":"J_ALTUI_iphone.js"},"urn:antor-fr:device:SamsungTVRemote:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawBinaryLight","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-upnp-org:device:HVAC_ZoneThermostat:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawHeater","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-futzle-com:device:CountdownTimer:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawCountDown","ScriptFile":"J_ALTUI_plugins.js"},"urn:demo-micasaverde-com:device:weather:1":{"DeviceIconFunc":"ALTUI_PluginDisplays.drawWeatherIcon","DeviceDrawFunc":"ALTUI_PluginDisplays.drawWeather","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-micasaverde-com:device:DoorLock:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawDoorLock","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-upnp-org:device:DimmableLight:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawDimmable","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-upnp-org:device:altui:1":{"DeviceDrawFunc":"ALTUI_IPhoneLocator.drawAltUI","ScriptFile":"J_ALTUI_iphone.js"},"urn:schemas-micasaverde-com:device:DoorSensor:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawDoorSensor","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-micasaverde-com:device:HumiditySensor:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawHumidity","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-upnp-org:device:cplus:1":{"DeviceDrawFunc":"ALTUI_IPhoneLocator.drawCanalplus","ControlPanelFunc":"ALTUI_IPhoneLocator.drawCanaplusControlPanel","ScriptFile":"J_ALTUI_iphone.js"},"urn:schemas-upnp-org:device:DigitalSecurityCamera:2":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawCamera","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-cd-jackson-com:device:DataMine:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawDataMine","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-upnp-org:device:DigitalSecurityCamera:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawCamera","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-futzle-com:device:holidayvirtualswitch:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawVacation","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-upnp-org:device:RGBController:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawBinaryLight","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-upnp-org:device:BinaryLight:1":{"StyleFunc":"ALTUI_PluginDisplays.getStyle","DeviceDrawFunc":"ALTUI_PluginDisplays.drawBinaryLight","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-micasaverde-com:device:MotionSensor:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawMotion","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-micasaverde-com:device:TemperatureSensor:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawTempSensor","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-micasaverde-com:device:PowerMeter:2":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawPowerMeter","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-upnp-org:device:Heater:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawHeater","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-micasaverde-com:device:LightSensor:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawLight","ScriptFile":"J_ALTUI_plugins.js"},"urn:schemas-micasaverde-com:device:WindowCovering:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawWindowCover","ScriptFile":"J_ALTUI_plugins.js"}}

EDIT: just tested it on my test box, it shows up fine so , should be a simple config problem I suppose.

[quote=“amg0, post:3, topic:188331”][quote=“dklinkman, post:2, topic:188331”]I am trying the Multi State control on a custom panel. I can create it, and set its properties. But often the ‘Variable’ property will change on me after I click Save. But not always. If I correct the Variable a few times it will usually stick at some point.

In my example I am using the Multi State to arm/disarm a motion sensor. I set Variable to Armed and set up the other properties. After saving I look and variable is now Mode Setting and not Armed. Another time it changed to Version Info. There are no errors in the debug console as I do this.

Once I get the Variable to stick the Multi State control appears to work perfectly.

Vera3 / Chrome v44 / AltUI v0.64.596

–David[/quote]

Very strange, I cannot reproduce it. let me know if you find a way to reproduce it easily.
on the other hand, you can go to Misc / Debug and press the “Javascript code” button.
then type in: PageManager.getPageFromName(“xxxx”) where xxx is the name of your custom page, if you can do this at several time so we see when the button variable is being changed[/quote]

I can reproduce this pretty easily. I drag a Multi State onto the page, then click on it and choose the device, in this case a different motion sensor, then choose Armed as the variable, off action is SetArmed to 0, on action is SetArmed to 1, and nothing in the off label or on label. Then click Save Changes. When I click the Multi State again the variable has now been changed to VersionInfo.

I don’t know what I am looking for with the Javascript code under Debug but the output does include the incorrect variable also

“properties”: {
“deviceid”: “0-162”,
“service”: “urn:micasaverde-com:serviceId:ZWaveDevice1”,
“variable”: “VersionInfo”,
“inverted”: false,
“labels”: [
“”,
“”
],

I tried adding a gauge also, using it to display temperature from a thermostat. Something similar is happening where variable is changing from CurrentTemperature to ModeStateForEnergy. But after changing that back to CurrentTemperature a few times it finally stuck and now its working.

Hello amg0, I was out on vacation for a little bit. I came home and installed the latest version .596. I reported that the heat set point on the thermostat didn’t display the decimal while the other values did. You had created V 0.63.550 for me to check this.

Here’s my original thread: http://forum.micasaverde.com/index.php?topic=30310.675
Post #686

Please let me know what else to provide to you.

[quote=“tomtcom, post:7, topic:188331”]Hello amg0, I was out on vacation for a little bit. I came home and installed the latest version .596. I reported that the heat set point on the thermostat didn’t display the decimal while the other values did. You had created V 0.63.550 for me to check this.

Here’s my original thread: http://forum.micasaverde.com/index.php?topic=30310.675
Post #686

Please let me know what else to provide to you.[/quote]

Tomtcot,
if 569 is not displaying float values , then can you please try this
a) go to ALTUI device setting and press default configuration, then set configuration, then reload luup & refresh browser

b) if still not displayed, then go to MISC / Debug , choose “one devices’s state” , in the dialog box type the id of the device like 0-21 ( assuming this is a single controller setup ) and please give me the result

thank you

[quote=“dklinkman, post:6, topic:188331”][quote=“amg0, post:3, topic:188331”][quote=“dklinkman, post:2, topic:188331”]I am trying the Multi State control on a custom panel. I can create it, and set its properties. But often the ‘Variable’ property will change on me after I click Save. But not always. If I correct the Variable a few times it will usually stick at some point.

In my example I am using the Multi State to arm/disarm a motion sensor. I set Variable to Armed and set up the other properties. After saving I look and variable is now Mode Setting and not Armed. Another time it changed to Version Info. There are no errors in the debug console as I do this.

Once I get the Variable to stick the Multi State control appears to work perfectly.

Vera3 / Chrome v44 / AltUI v0.64.596

–David[/quote]

Very strange, I cannot reproduce it. let me know if you find a way to reproduce it easily.
on the other hand, you can go to Misc / Debug and press the “Javascript code” button.
then type in: PageManager.getPageFromName(“xxxx”) where xxx is the name of your custom page, if you can do this at several time so we see when the button variable is being changed[/quote]

I can reproduce this pretty easily. I drag a Multi State onto the page, then click on it and choose the device, in this case a different motion sensor, then choose Armed as the variable, off action is SetArmed to 0, on action is SetArmed to 1, and nothing in the off label or on label. Then click Save Changes. When I click the Multi State again the variable has now been changed to VersionInfo.

I don’t know what I am looking for with the Javascript code under Debug but the output does include the incorrect variable also

“properties”: {
“deviceid”: “0-162”,
“service”: “urn:micasaverde-com:serviceId:ZWaveDevice1”,
“variable”: “VersionInfo”,
“inverted”: false,
“labels”: [
“”,
“”
],

I tried adding a gauge also, using it to display temperature from a thermostat. Something similar is happening where variable is changing from CurrentTemperature to ModeStateForEnergy. But after changing that back to CurrentTemperature a few times it finally stuck and now its working.[/quote]

Thank you for your patience, I have got it ! I will post a fix
EDIT: in 0.64.600

I think the alignment buttons used when editing the custom page have stopped working. Drag two devices onto the page, use mouse to select them, click on any of the alignment buttons and nothing happens. Nothing in the debug console. I noticed this with the prior version also.

Vera3 / Chrome v44 / AltUI v0.64.600

[quote=“dklinkman, post:10, topic:188331”]I think the alignment buttons used when editing the custom page have stopped working. Drag two devices onto the page, use mouse to select them, click on any of the alignment buttons and nothing happens. Nothing in the debug console. I noticed this with the prior version also.

Vera3 / Chrome v44 / AltUI v0.64.600[/quote]

ok thx ! fix in v602

[quote=“amg0, post:11, topic:188331”][quote=“dklinkman, post:10, topic:188331”]I think the alignment buttons used when editing the custom page have stopped working. Drag two devices onto the page, use mouse to select them, click on any of the alignment buttons and nothing happens. Nothing in the debug console. I noticed this with the prior version also.

Vera3 / Chrome v44 / AltUI v0.64.600[/quote]

ok thx ! fix in v602[/quote]
And looking good!!

[quote=“amg0, post:8, topic:188331”][quote=“tomtcom, post:7, topic:188331”]Hello amg0, I was out on vacation for a little bit. I came home and installed the latest version .596. I reported that the heat set point on the thermostat didn’t display the decimal while the other values did. You had created V 0.63.550 for me to check this.

Here’s my original thread: http://forum.micasaverde.com/index.php?topic=30310.675
Post #686

Please let me know what else to provide to you.[/quote]

Tomtcot,
if 569 is not displaying float values , then can you please try this
a) go to ALTUI device setting and press default configuration, then set configuration, then reload luup & refresh browser

b) if still not displayed, then go to MISC / Debug , choose “one devices’s state” , in the dialog box type the id of the device like 0-21 ( assuming this is a single controller setup ) and please give me the result

thank you[/quote]

The first option did not work. Attached is the output.

[quote=“tomtcom, post:13, topic:188331”][quote=“amg0, post:8, topic:188331”][quote=“tomtcom, post:7, topic:188331”]Hello amg0, I was out on vacation for a little bit. I came home and installed the latest version .596. I reported that the heat set point on the thermostat didn’t display the decimal while the other values did. You had created V 0.63.550 for me to check this.

Here’s my original thread: http://forum.micasaverde.com/index.php?topic=30310.675
Post #686

Please let me know what else to provide to you.[/quote]

Tomtcot,
if 569 is not displaying float values , then can you please try this
a) go to ALTUI device setting and press default configuration, then set configuration, then reload luup & refresh browser

b) if still not displayed, then go to MISC / Debug , choose “one devices’s state” , in the dialog box type the id of the device like 0-21 ( assuming this is a single controller setup ) and please give me the result

thank you[/quote]

The first option did not work. Attached is the output.[/quote]

Tomtcot, can you please confirm the device_type of this device ?
I think I got it; I saw this here
“NOTE: On UI7, urn:upnp-org:serviceId:TemperatureSetpoint1_Heat and urn:upnp-org:serviceId:TemperatureSetpoint1_Cool are obsolete.”

you are on UI7 I suppose
can you try this version and let me know the result ? if ok I ll integrate in the release

[quote=“amg0, post:14, topic:188331”][quote=“tomtcom, post:13, topic:188331”][quote=“amg0, post:8, topic:188331”][quote=“tomtcom, post:7, topic:188331”]Hello amg0, I was out on vacation for a little bit. I came home and installed the latest version .596. I reported that the heat set point on the thermostat didn’t display the decimal while the other values did. You had created V 0.63.550 for me to check this.

Here’s my original thread: http://forum.micasaverde.com/index.php?topic=30310.675
Post #686

Please let me know what else to provide to you.[/quote]

Tomtcot,
if 569 is not displaying float values , then can you please try this
a) go to ALTUI device setting and press default configuration, then set configuration, then reload luup & refresh browser

b) if still not displayed, then go to MISC / Debug , choose “one devices’s state” , in the dialog box type the id of the device like 0-21 ( assuming this is a single controller setup ) and please give me the result

thank you[/quote]

The first option did not work. Attached is the output.[/quote]

Tomtcot, can you please confirm the device_type of this device ?
I think I got it; I saw this here
“NOTE: On UI7, urn:upnp-org:serviceId:TemperatureSetpoint1_Heat and urn:upnp-org:serviceId:TemperatureSetpoint1_Cool are obsolete.”

you are on UI7 I suppose
can you try this version and let me know the result ? if ok I ll integrate in the release[/quote]

Hello amg0, please see the screenshot for the result of the file you sent me.

ok thank you, I ll fix the rounding to one decimal in the next release

ok thank you, I ll fix the rounding to one decimal in the next release[/quote]

Understood, thank you very much.

[quote=“amg0, post:1, topic:188331”]Thread for reporting issues with ALTUI

feel free to create a new msg thread for your issue so that lengthy discussion can happen if needed.
please be as precise as you can when reporting an issue. at least I would need:

[ol][li]- browser type & version[/li][li]

  • Vera type & version[/li][li]
  • Javascript console log extract[/li][li]
  • Ideally a screen shot showing the problem[/li][/ol]

EDIT : I unstick this topic so that we can have one thread per issue.[/quote]

amg0, when you have time, would you mind including common ways to get to the Javascript console log? I frequently forget, I know I can google it but perhaps it will help get you all the info the first time for others. You have awesome knowledge but I do like to be able to get all that you need and try all that I can do before reporting issues to you. It’s the least I can do for you.

For Chrome:

  1. Click on the 3 horizontal lines button.
  2. Go to More tools.
  3. Choose JavaScript console.

I actually just solved a problem I had using the console…lol…no need to ask you. ;D

If I mark a device as a ‘favourite’ by clicking the * in its titlebar it doesn’t seem to persist for long. Initially it works but that attribute gets lost after a while.

K

[quote=“XAPPO, post:19, topic:188331”]If I mark a device as a ‘favourite’ by clicking the * in its titlebar it doesn’t seem to persist for long. Initially it works but that attribute gets lost after a while.

K[/quote]

That setting is stored in the HTML local storage of the client device so:
a) it is different on different clients ( phone, PC, tablet )… each peripheral has its own
b) if something clears the local storage, you may lose it but honestly this is unlikely, I ma not aware of things that would clear local storage
c) I ll check if I see a bug