Restart Signalk when can01 is "lost"
Is it possible to trigger an restart of the signalk service when a connection is lost? i.e. no data is recieved as in the screenshot? The reason being is that after the can01 is lost, the derived-data plugin continues to calculate incorrect values, based on latest measurments from the can01 (along with other gps data?). See screenshot for forther details. Restart the service will stop the derived-data from computing.
Thanks!
10 Replies
if I were you i would create a node-RED flow that will send a
null value to those paths if there is no new data for themah that sounds smart, will test if i can create such a flow
how would i fetch the latest timestamp for a path in node red? the subscribe only seems to work on "active" paths
You are not thinking node-red here
Google and u shall receive
https://cookbook.nodered.org/basic/trigger-timeout
ah many thanks, still quite new to node-red so not sure what to search for just yet
i think it should work now, will try tomorrow when im at the boat 🙂
@Scott Bender I think there was code in place that detected can0 to go mute and then 'reconnect'?
Yes
But that won’t fix this issue
Derived data should probably be fixed…
Server implementing timeouts, nulling values, would also solve this