2020-07-11, 02:38 PM
I've been playing with this for a while too.
I tried UDP and ran into some problems around the UDP connection plugin, not being happy about the source names being different in the incoming JSON.
I found that in order to log to influx-db I need to use the setting to synthesise the date as if replaying from logs, but this is not ideal. I would like to know if there's a way to take the ESP system date and put that in the message?
As the only thing I'm really interested in is long term logging of this data, I'm working in celsius for now.
I've also tried using custom rules to produce signalK JSON if anyone's interested:
I tried UDP and ran into some problems around the UDP connection plugin, not being happy about the source names being different in the incoming JSON.
I found that in order to log to influx-db I need to use the setting to synthesise the date as if replaying from logs, but this is not ideal. I would like to know if there's a way to take the ESP system date and put that in the message?
As the only thing I'm really interested in is long term logging of this data, I'm working in celsius for now.
I've also tried using custom rules to produce signalK JSON if anyone's interested:
Code:
on System#Boot do
timerSet,1,1
endon
On Rules#Timer=1 do
Publish /vessels/self/environment/temperature/Fridge1K/, '{"updates": [{"source": "Fridge1Rule","values":[ {"path":"environment.temperature.fridge1","value": '[fridge1#temp]' }]}]}'
Publish /vessels/self/environment/temperature/Fridge2K/, '{"updates": [{"source": "Fridge2Rule","values":[ {"path":"environment.temperature.fridge2","value": '[fridge2#temp]' }]}]}'
timerSet,1,1
endon