meteohub.de

Hi there,

I have a Meteobridge Pro2 receiving data from a Davis Vantage Pro2.

SW Version: Meteobridge 6.4 (Sep 19 2026, build 6426), FW 1.5


The setup works perfectly fine in Wireless LAN mode. However, when I switch to Stand-Alone mode and reboot then I get the the following error message under the Network tab:

"Error: WLAN AP passphrase needs to be at least 8 characters long".

I am slightly confused as to which passphrase this is or where to set it. The AP Passphrase under Stand-Alone is still the default (meteobridge). The Passphrase under Wireless LAN is 8 characters long, but it should not be used anyway.

Not sure if the following issues is related to this, under the Database --> Edit Hour Data it says:

"Database Error: Cannot prepare read tables RAM (0 tries, 1ms): unable to open database file"

Something is not working as it should. Any advice is much appreciated.

Best wishes,
Sebastian

When Meteobridge is in stand-alone-mode it does not connect to a computer network, but it provides its own WiFi which allows your Laptop to connect to it and by that to allow you to use the Metebridge web GUI to do the admin things. Therefore, it needs a passphrase for this own WiFi. You can set it up on "network" tab.

The database error is puzzling me. Does this just occur when unit is in stand-alone mode? Do you have permanent storage of per minute data enabled on "database - admin" tab?

I am currently on travel, so I don't have a PRO2 at hand to mimic the stand-alone issues you report.

Thanks for the response.

The password for the Stand-Alone mode is set, I use the default "meteobridge" (11 characters). I can connect to the Pro2's own Wireless AP in Stand-Alone mode and access the web GUI without any problems. But then, still in Stand-Alone mode, as I go to the Network tab the error message about the 8 character password appears. It does not affect my connectivity. Connectivity works without any problems, both in Stand-Alone mode and in Wireless LAN mode, but something else is throwing up this error.

The database issue only appears in Stand-Alone mode. When I switch back to Wireless LAN it works fine. Having said that, in Stand-Alone mode, the database issues appears to have disappeared now after about 24 hours. I did not change anything, just left it running over night. I will do some more testing.

Thanks for the help.

The invalid password message is fixed with next release. Thanks for spotting this. Not may users work with stand-alone mode so it remained unspotted for a while.