ingoogni
ingoogni
Ah, sorry I wasn't quite clear I think. I'd like to use the app without showing the complete UI, just a start/stop button on the 'desktop' or what it is...
Seems all reasonable to me,
Just an idea for starts, red start 'button' one tab, starts logging in the background, button turns blue button turns green when location is stable, maybe show the gps marker...
Instead of "fiddling" with each feed, how about an adaptive interval, moving average based on update frequency in the past. Make a settable min and max bounds 1 min -...
Some background on dynamic intervals https://www.rn.inf.tu-dresden.de/uploads/Publikationen/feedpaper_poster.pdf
I'm getting utterly confused by this opening and closing and moving of discussion. Can't we have a decent mailinglist or even Gitter (meh) for discussing things. This is worse than...
IMO that should be part of your mqtt string if geolocation is important, in principle it is nothing different from "front/door" or "headlight/left".
If geolocation is important, for a moving device, set up a node for it. I think a geo location spec would belong in $unit and would fit the Convention well....
"A location string is very useful for auto-discovery, so I opt for adding it to the convention as optional device property with arbitrary string, e.g. a room name" Lets have...
I have a 'device' that lifts and lowers a hose, it is a spindle with a steppermotor controlled by a Nano over I2C connected to a Wemos over MQTT connected...