esilva
b364931c80
automatic setup for devices
...
Its not close to being done and still need to work out the flows due to
who arrives first: telemetry or the peripheral?
2026-09-21 15:27:42 +01:00
esilva
263d3c29a3
services decoupling
2026-09-21 11:45:10 +01:00
esilva
5d5b7bfdc3
working on the peripheral state handling
2026-09-20 21:44:15 +01:00
esilva
a5c465a203
has way too many things
...
In short: added the ability to detect when a device has disconnected.
From this we have to achieve a way of:
- reconnecting the device
- re-subscribing to the fields it needs (it should already be subscribed
since the ESDI didn't stop tho - but for the sake of it, or in case a
device joins later)
- start sending data to it (which should be automatic given how we are
handling the devices)
2026-09-20 15:06:48 +01:00
esilva
174b27004f
added error returns to the SendData method on the peripheral interface
2026-09-18 16:37:30 +01:00
esilva
c888dc5436
remove commented code and made the subscription be based on a list
2026-09-18 00:05:50 +01:00
esilva
dda300ce6b
decoupled the winIDs from the telemetry data
...
hell yeah, brother!
2026-09-17 23:55:54 +01:00
esilva
1ac4ab1865
logger fixes on cdashdisplay device implementation
2026-09-17 23:08:36 +01:00
esilva
a6ab64117c
this is a doozy - device auto discovery and handling
...
The main goal was to decouple more things
We got devices being looked for in the background and the stream view
is like a device now too
2026-09-17 23:01:50 +01:00
esilva
c1366b010f
remove this very verbose log
2026-09-17 23:01:50 +01:00
esilva
afc4b794bb
Created a devices service and moved the CDashDisplay service to the sahdow realm
2026-09-17 23:01:50 +01:00
esilva