Pro2 Luci interface changes? **solved**
Moderator: Mattk
-
- Fresh Boarder
- Posts: 17
- Joined: Sat Jan 18, 2020 4:38 pm
- Location: Prior Lake, MN USA
- Contact:
Pro2 Luci interface changes? **solved**
upgraded from pro to pro2 and the luci interface is different. Is there a way to use the more advanced version I used on the Pro?
Re: Pro2 Luci interface changes?
No, LUCI is not intended to be used.
-
- Fresh Boarder
- Posts: 17
- Joined: Sat Jan 18, 2020 4:38 pm
- Location: Prior Lake, MN USA
- Contact:
Re: Pro2 Luci interface changes?
on the pro i had to use luci and ssh to mount an external usb. also to add my syslog info so i could get logs sent there.
the luci interface looks a lot diff from the pro. must be the version?
the luci interface looks a lot diff from the pro. must be the version?
Re: Pro2 Luci interface changes?
during backup the default backup script mounts a connected USB device as backup device - and unmounts it when the backup is completed.
When you want to have device mounted e.g. into the exported .../data directory, you can add the mount command as last command to the backup.sh script in \\METEOBRIDGE\data\scripts
e.g.
this assumes that you have created the directory USB in the /tmp/mnt/data directory before (that's what gets exported as SMB share \\METEOBRIDGE\data)
this circumvents having to use Luci with simple means
When you want to have device mounted e.g. into the exported .../data directory, you can add the mount command as last command to the backup.sh script in \\METEOBRIDGE\data\scripts

e.g.
Code: Select all
mount /dev/sda1 /tmp/mnt/data/USB
Code: Select all
mkdir /tmp/mnt/data/USB
WH4000SE 1.6.6/1 x DP1500/4 x GW1000 1.7.7/GW1100 2.3.0/HP1000SE Pro 1.9.3//2 x WH2650 1.7.7/GW2000 3.1.0
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
-
- Fresh Boarder
- Posts: 17
- Joined: Sat Jan 18, 2020 4:38 pm
- Location: Prior Lake, MN USA
- Contact:
Re: Pro2 Luci interface changes?
ill check it out. is there a perm way for me to add/update the logging config so i can utilize my syslog server?
i update it in Luci but after reboot or other means, the server details are erased.
i thing theres a way with logd? i dont want to use tftp, ftp, etc. Rather it be sent as syslog msg to my server.
thanks
i update it in Luci but after reboot or other means, the server details are erased.
i thing theres a way with logd? i dont want to use tftp, ftp, etc. Rather it be sent as syslog msg to my server.
thanks
Re: Pro2 Luci interface changes?
In my proposed solution you don't need any of this - and you get a regular backup.
if the backup script is run out of Meteobridge as a backup event, you can do it every hour.
And even if your external USB media runs full - without you doing housekeeping
-, MB will overwrite the oldest backup with the latest one etc.
If you want to save the logfile (which is unfortunately deleted after each reboot), add a copy command for /tmp/log/meteobridge.log to the backup.sh script and change the file name by adding a time stamp, also to your backup device - directory of your choice or create one like /tmp/mnt/data/log
e.g.
From the SMB share you can then process the log at your convenience.
Make sure you initialize a reboot only after the backup script has run (or create another independent script you call as a MB event) to get the complete logging (if needed).
You want other solutions (no ftp, sftp involved) - get yourself familiar with openWRT and what its ash shell offers as a reduced bash shell in terms of commands and then make your pick or build your script(s).
if the backup script is run out of Meteobridge as a backup event, you can do it every hour.
And even if your external USB media runs full - without you doing housekeeping

If you want to save the logfile (which is unfortunately deleted after each reboot), add a copy command for /tmp/log/meteobridge.log to the backup.sh script and change the file name by adding a time stamp, also to your backup device - directory of your choice or create one like /tmp/mnt/data/log
e.g.
Code: Select all
cd /tmp/log
file_name=meteobridge.log
current_time=$(date "+%Y.%m.%d-%H.%M.%S")
new_fileName=$file_name.$current_time
cp $file_name $new_fileName
cp $new_fileName /tmp/mnt/data/log
Make sure you initialize a reboot only after the backup script has run (or create another independent script you call as a MB event) to get the complete logging (if needed).
You want other solutions (no ftp, sftp involved) - get yourself familiar with openWRT and what its ash shell offers as a reduced bash shell in terms of commands and then make your pick or build your script(s).
WH4000SE 1.6.6/1 x DP1500/4 x GW1000 1.7.7/GW1100 2.3.0/HP1000SE Pro 1.9.3//2 x WH2650 1.7.7/GW2000 3.1.0
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki