Hi,
I would suggest to add igate asl elevation in configuration json file (maybe in bme section?), so pressure correction can be made without source editing.
Thank you for your amazing project!
Marco IZ0HCD
Hi,
I would suggest to add igate asl elevation in configuration json file (maybe in bme section?), so pressure correction can be made without source editing.
Thank you for your amazing project!
Marco IZ0HCD
<!-- github-sync-id:1909914915 -->
It is partially quite complicated.
A we can have two different localisations because of two different WiFi, so it cannot be single value in bme section, but better two values in wifi.AP sections. Of course you can have two identical values as somebody can have possibility to use two different home wifi networks.
And then recalculation in bme_utils.cpp.
Sorry, I do not know yet how to write patch and do request pull.
It is partially quite complicated.
A we can have two different localisations because of two different WiFi, so it cannot be single value in bme section, but better two values in wifi.AP sections. Of course you can have two identical values as somebody can have possibility to use two different home wifi networks.
And then recalculation in bme_utils.cpp.
Sorry, I do not know yet how to write patch and do request pull.
<!-- github-comment-id:1917922215 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Hi,
I would suggest to add igate asl elevation in configuration json file (maybe in bme section?), so pressure correction can be made without source editing.
Thank you for your amazing project!
Marco IZ0HCD
It is partially quite complicated.
A we can have two different localisations because of two different WiFi, so it cannot be single value in bme section, but better two values in wifi.AP sections. Of course you can have two identical values as somebody can have possibility to use two different home wifi networks.
And then recalculation in bme_utils.cpp.
Sorry, I do not know yet how to write patch and do request pull.
this is a solution I will try to implement soon
#define HEIGHT_CORRECTION xxxx // in meters
Hello Ricardo, do you have updates on this suggestion?
Thanks
Height Correction has been added on WebUI on V.1.0.3 web installer