beta testing observations

[sjenkins]

Thought I'd start a topic under eisy-ui for beta minor observations, @bmercier please take in the spirit of constructive feedback, as well know that each of these items will have a different priority to you versus me.  Maybe others who are helping test can add their observations here.

- noticing if I leave the eisy-ui web page up overnight it stops updating ; even if I do a refresh of the page it does not update with no real indication of "heartbeat"; takes a logout/login.  Was wondering what the timeout period was?  Is there a way to do a heartbeat?

- have been noticing differences between the status on the column view versus the detail view.  A refresh does not always fix it.  Again have needed to logout/login.

- the folder retention of expand/contract has been mentioned but also you cannot search for a folder name and then select it to have it open its contents

- really, really, would like to be able to use my cursor controls to move up and down the list ; contract/expand folders.  As a keyboard user the use of the mouse to move one up or down is maddening (personal rant)

- during search as I start typing I am still getting an 'unexpected application crash' regularly.  refresh of page often resets but sometimes requires a logout/login cycle.

 

[bmercier]

13 hours ago, sjenkins said:

- noticing if I leave the eisy-ui web page up overnight it stops updating ; even if I do a refresh of the page it does not update with no real indication of "heartbeat"; takes a logout/login.  Was wondering what the timeout period was?  Is there a way to do a heartbeat?

Thank you very much for the feedback.

There's no specific timeout set. Will need to investigate further as I have never myself let it up overnight. I suspect the websocket connection dies somehow. Will look into it.

13 hours ago, sjenkins said:

- during search as I start typing I am still getting an 'unexpected application crash' regularly.  refresh of page often resets but sometimes requires a logout/login cycle.

Is there a way to get a screenshot? Never seen that happen to me. It might be good to look at the browser console to see what's happening.

[apostolakisl]

@bmercier @sjenkins

I opened the Web UI at my office last week and haven't touched it over the weekend.  I just clicked on that tab and can still see the status of items and control them without doing any refresh or logout/in.  This connection is running over a router to router vpn which further complicates things, and yet, it is still up.  I initiated the connection last week by going to the LAN IP address of my ISY which gets routed through the VPN.  

[sjenkins]

@bmercier ,

Just wanted to let you know that there is still a difference in behaviour between the local AC and the remote AC / Eisy-UI.

Using my hunterDouglas plugin as an example as I know the plumbing:

reportDrivers() does not update the detail fields in the remote AC / Eisy-UI

works fine in the local AC

ISY programs get the data just fine, so this is a display issue.

Examples below:

local AC:

remote AC:

remote Eisy-UI:

 

Note: 

The field that did update are ones which have changed since the Eisy-UI was running.  The remote AC are blank as I had to restart it to switch from local to remote.

When I press query it runs the reportDrivers() function.  This updates the local(if needed), but not the other two remote versions.  Again the programs run fine.

 

[bmercier]

2 hours ago, sjenkins said:

@bmercier ,

Just wanted to let you know that there is still a difference in behaviour between the local AC and the remote AC / Eisy-UI.

Using my hunterDouglas plugin as an example as I know the plumbing:

reportDrivers() does not update the detail fields in the remote AC / Eisy-UI

works fine in the local AC

ISY programs get the data just fine, so this is a display issue.

Examples below:

local AC:

remote AC:

remote Eisy-UI:

 

Note: 

The field that did update are ones which have changed since the Eisy-UI was running.  The remote AC are blank as I had to restart it to switch from local to remote.

When I press query it runs the reportDrivers() function.  This updates the local(if needed), but not the other two remote versions.  Again the programs run fine.

 

This is not a display issue.

This just means that IoX is not sending these events through MQTT because they have not changed. 

Will look into it with Chris.