2020-01-14, 11:35 AM
Leif,
How cool! Thanks.
But as you know by now, I'm a newbie (eager to learn), so here is questions:
I do not know where to do the JSON trick. Which application do I use, or is it in SignalK?
You also talk about a better way to setup PATH in the device, do you mean the ESP?
Then you write:
... {"updates": [{"source": "%sysname%","values":[ {"path":"%valname%","value": %value% }]}]} and in the device set as example "temperature" to "environment.inside.mainCabin.temperature" instead.
PATH must match something good in SignalK, avoid to create your own path if possible.
What do you mean (or where can I read about PATH?
One more: which regards to the UDP port where SignalK is listening. How many ESP can you link to that port? Or is it one port per ESP?
Was there a specific reason why you didn't want to use NodeRed and MQTT?
Hope you can help me.
Best Bart
How cool! Thanks.
But as you know by now, I'm a newbie (eager to learn), so here is questions:
I do not know where to do the JSON trick. Which application do I use, or is it in SignalK?
You also talk about a better way to setup PATH in the device, do you mean the ESP?
Then you write:
... {"updates": [{"source": "%sysname%","values":[ {"path":"%valname%","value": %value% }]}]} and in the device set as example "temperature" to "environment.inside.mainCabin.temperature" instead.
PATH must match something good in SignalK, avoid to create your own path if possible.
What do you mean (or where can I read about PATH?
One more: which regards to the UDP port where SignalK is listening. How many ESP can you link to that port? Or is it one port per ESP?
Was there a specific reason why you didn't want to use NodeRed and MQTT?
Hope you can help me.
Best Bart