THERE IS AN UPDATE AVAILABLE.
I just rebooted the Meteobridge and it is working again!!!
Search found 9 matches
- Wed Mar 10, 2021 10:55 pm
- Forum: Meteobridge PRO/PRO2/NANOSD/RPI/VM Discussion
- Topic: No data after firmware update. **solved**
- Replies: 8
- Views: 2887
- Wed Mar 10, 2021 9:48 am
- Forum: Meteobridge PRO/PRO2/NANOSD/RPI/VM Discussion
- Topic: No data after firmware update. **solved**
- Replies: 8
- Views: 2887
No data after firmware update. **solved**
This morning i restarted the Meteobridge Pro.
It booted, but there is no data coming in.
I use a Davis Envoy 8x.
In the log i see this:
logger (10.03.2021 08:42:47): databases connected. Update interval 3600 seconds.
logger (10.03.2021 08:42:47): data logger (version 5.1e, build 14348) started ...
It booted, but there is no data coming in.
I use a Davis Envoy 8x.
In the log i see this:
logger (10.03.2021 08:42:47): databases connected. Update interval 3600 seconds.
logger (10.03.2021 08:42:47): data logger (version 5.1e, build 14348) started ...
- Tue Jun 26, 2018 10:13 am
- Forum: Meteobridge PRO/PRO2/NANOSD/RPI/VM Discussion
- Topic: Error: Fout: maximum aantal vertalingen bereikt (1000): /home/meteohub//Dutch.lang **solved**
- Replies: 7
- Views: 3647
Error: Fout: maximum aantal vertalingen bereikt (1000): /home/meteohub//Dutch.lang **solved**
This message is shown with the new firmware (3.7)
Fout: maximum aantal vertalingen bereikt (1000): /home/meteohub//Dutch.lang

Fout: maximum aantal vertalingen bereikt (1000): /home/meteohub//Dutch.lang

- Sun Mar 12, 2017 10:55 pm
- Forum: Meteobridge PRO/PRO2/NANOSD/RPI/VM Discussion
- Topic: Can't select Meteotemplate as Weather Nets **solved**
- Replies: 3
- Views: 3185
Can't select Meteotemplate as Weather Nets **solved**
I just loaded the new firmware (3.2 as of 12 march).
If i try to select Meteotemplate as a service it is not selected and the dropdownmenu changes back to 'choose network'.
Is to early to use or a bug?
If i try to select Meteotemplate as a service it is not selected and the dropdownmenu changes back to 'choose network'.
Is to early to use or a bug?
- Wed Feb 08, 2017 10:44 am
- Forum: Meteobridge PRO/PRO2/NANOSD/RPI/VM Discussion
- Topic: Time on Graphs page resets to UTC **solved**
- Replies: 4
- Views: 3575
Re: Time on Graphs page resets to UTC
You are right. Same problem here.
- Sun Dec 25, 2016 6:35 pm
- Forum: Meteobridge PRO/PRO2/NANOSD/RPI/VM Discussion
- Topic: Database problems
- Replies: 5
- Views: 4184
Re: Database problems
After removing all services and posts to Weather Nets and a reboot with forced rebuild, it's running again. I am now trying to restart the services and the posts to the Weather Nets. The Meteobridge is running for 19 hours without problems. Fingers crossed...
- Sun Dec 25, 2016 6:30 pm
- Forum: Meteobridge PRO/PRO2/NANOSD/RPI/VM Discussion
- Topic: Time on Graphs page resets to UTC **solved**
- Replies: 4
- Views: 3575
Re: Time on Graphs page resets to UTC
After a reboot the time is correct.
- Sat Dec 24, 2016 11:56 am
- Forum: Meteobridge PRO/PRO2/NANOSD/RPI/VM Discussion
- Topic: Time on Graphs page resets to UTC **solved**
- Replies: 4
- Views: 3575
Time on Graphs page resets to UTC **solved**
I was looking at the Graphs page and noted that the time in the graphs has changed to UTC instead of local time and i can't rememeber that i changed something. Is there a way to get the local time back?
- Fri Dec 23, 2016 5:05 pm
- Forum: Meteobridge PRO/PRO2/NANOSD/RPI/VM Discussion
- Topic: Database problems
- Replies: 5
- Views: 4184
Database problems
I just setup my new Meteobridge Pro.
Now i am receiving these messages:
database (23.12.2016 15:59:10): cannot commit RAM (after 100 tries in 9090ms): database is locked
database (23.12.2016 15:59:19): cannot insert into data10num_hour RAM (after 100 tries in 9272ms): database is locked
database ...
Now i am receiving these messages:
database (23.12.2016 15:59:10): cannot commit RAM (after 100 tries in 9090ms): database is locked
database (23.12.2016 15:59:19): cannot insert into data10num_hour RAM (after 100 tries in 9272ms): database is locked
database ...