Is the Dashboard plugging supported with server nodes?

[DLavigneGH]

Hi,
I noticed that if I run a hub and a server setup, I am not able to use the dashboard plugging, is this normal? I am talking about the useful live stream video, log and performance meters, they are not accessible.

Also second thing, when I launch my automation script from my python client to the HUB's endpoint, the list of available devices in the hub's webpage doesn't update. With the normal local server setup it used to toggle the devices to 'BUSY' now with that HUB/server setup it doesn't seem to do that.

[DLavigneGH]

I think I get it, we need to go to the web page that is hosted by the server node and not the hub to get those features, is this it?

One more thing, if I block a device from the server webpage, it doesn't update the hub's webpage. Is most thing from the hub a work in progress? So far I enjoy it, just wishing the hub <> server thing could communicate those kind of things with device availability.

[saikrishna321]

@DLavigneGH Thanks for trying out the plugin.

I am talking about the useful live stream video, log and performance meters, they are not accessible. We are working to make it work better with node and hub concept.

when I launch my automation script from my python client to the HUB's endpoint, the list of available devices in the hub's webpage doesn't update This should not happen, when a new request gets to HUB and if the device is found it will set to BUSY and will not be available for other session. Please provide full logs for this case.

if I block a device from the server webpage, it doesn't update the hub's webpage. This is not the usecase, users should only get access to the HUB and not the node, So you need to block the devices on the HUB UI and it should turn BUSY. Now the device is not available for automation session. Note: This will not update the node as HUB is the decision maker.

[DLavigneGH]

when I launch my automation script from my python client to the HUB's endpoint, the list of available devices in the hub's webpage doesn't update This should not happen, when a new request gets to HUB and if the device is found it will set to BUSY and will not be available for other session. Please provide full logs for this case.

I will double check tomorrow, the script may still have used the endpoint of the server node instead of the HUB by mistake because the server node page was updating.

When you say full logs, do you mean the hub/server nodes log from the terminal or should I launch the server with a debug switch?

[saikrishna321]

logs from terminal

[DLavigneGH]

Morning,
The endpoint was indeed still pointing to the server; it worked as you said once I fixed it.