Retrieving the status of resources even if not acquired

[sessl3r]

Hi,

we want to build up a overview page for all our Labgrid Places and Resources. In this overview we for example want to be able to see the power state of each Place (if it has a PowerPort). This obviously is not the intended way of accessing Resources in current Labgrid. The status must be available regardless of if the Place is currenlty acquired or not.

The "simple" way would be to just do this by getting the information from eg. th power resource(s) of the place and externally reimplementing the power.get functionality, at least for devices where this is possible (eg. MQTT). However for many others this is just not possible and too much duplicated code.

Can you think of a way a (eventually special) ApplicationSession could somehow act on Resources even if those are not acquired / acquired by someone else? Or would it even be interesting to implement some kind of a polled status information for (some) resources which then could simply be retrieved by anyone?

Thanks for your input and any ideas.
Regards,
sessl3r

[sessl3r]

``Hi again,

as this is a higher need for us internally I thought about it and implemented it as an example for TasmotaPowerPort here.

As far as I understand the architecture of Labgrid this might be the most correct location for such code.

Basically as soon as the exporter is running and creating the resource class ResourceExport polls for changed data.
First approach was to implement a poll method (which could be needed for other Resources). But not needed in this case.
Here we just subscribe to relevant topics from the Resource configuration and update the status which is part of the parameter set.

The outcome of this approach is:

$ lgc -p tb-test show
Place 'tb-test':
  matches:
    */tb-test/*
  **acquired: None**
  acquired resources:
  created: 2024-11-09 14:37:17.434108
  changed: 2024-11-21 07:22:19.031263
Matching resource 'power1' (xxx/tb-test/TasmotaPowerPort/power1):
  {'acquired': None,
   'avail': True,
   'cls': 'TasmotaPowerPort',
   'params': {'extra': {'proxy': 'xxx', 'proxy_required': False},
              **'status': 'OFF'}**}

Would this idea be of any interest for upstream?