The recommended way to get around the problem that the router might give the NANO a new IP after DHCP lease time is passed is to assign the NANO a fixed IP based on its MAC. Most routers allow to do that in their DHCP settings. This circumvents to go to static IP settings in the NANO itself, which might be complicated for some users as they might not be too familiar with Gateway IP, IP mask, and DNS IP and when they enter something wrong here they are disconnected and need to start from scratch.pb2rdf wrote: ↑Fri Aug 31, 2018 2:46 amAnd when someone did forget to configure a fixed IP address, it is possible the MB Nano gets another, or no IPnr if dhcp is configured.
The MB Nano should be configured (imo) with a fixed IPnr by the user, and should be strongly recommended to all MB Nano users.
This counts also for the other meteobridge solutions.
The NANO adds the same storage chip to the console as the original Davis loggers do. Therefore when using pass-through mode on port 22222 on the NANO it behaves like the Davis loggers. You can read out history from there as you are used to.pb2rdf wrote: ↑Fri Aug 31, 2018 2:46 amIs my understanding right in conclusion to your answer, in case of WIFI communication loss, it is always possible to restore and download the archive data from a certain time, dependend of the archive interval, from the MB Nano?
1 minute interval is less back in time as an archive interval of 10 minutes.
What Davis is selling as a logger is mostly a $1 eeprom. All logic is already in the console, they just add this eeprom and a serial to USB converter that allows your PC to communicate with the console. Therefore, it is very easy for the NANO also to provide this eeprom and by having that the console provides all the logging features as with a Davis logger. NANO does not interact with the eeprom directly. All is done via Davis serial communication protocol via the console.
NANO is not providing non-volatile storage for logging console data. I explained in the previous paragraph how that works.
What the NANO does is to listen ongoing to the console live data and keep track of hourly, daily, monthly, yearly highs/lows and averages for all the sensor data. In order not to loose it this is stored every 10 minutes on the Meteobridge server (just the min/max/avg values).
Thanks, I see it the same way.