We’re officially releasing the 2.1.000 hotfix for Lighthouse and ORx.
Before I write about what this hotfix includes, I would like to thank the community members for giving us a hand testing the snapshot builds during this sprint. Thank you! <3
What’s new?
This hotfix includes fixes for some of the showstopper bugs that were uncovered following 2.0.000 release, including but not limited to:
- Unicode issues crashing the tuner settings
- SD card corrption issues on ORxPi
- A few bugs preventing smooth indexing of files
- Issues related to selection of different LNB types
- Persstent notifications that can’t be dismissed
There are also two new additions:
- New monitoring script with enhanced heartbeat data and smaller bandwidth consumption
- Enhanced diagnostics data download
Known issues
Intermittent loss of lock
We have observed intermittent lock issue in at least one test Lighthouse. While observng the tuner settings sections on the settings page, you may sometimes se that it says “NO LOCK” and then, after a minute or so resume as if nothing happened. Even though the tuner section says “NO LOCK” the device usually hasn’t lost lock, and resumes downloads in the background. This can be confimed by observing the 3rd LED (one further away from the corner): if it is blinking, it means you actually lost lock, and if it’s not blinking, it means you are seeing this issue. We are still trying to determine why this happens, but it does not seem to be critical to device’s correct operation. If you are seeing this issue, and if you find that you haven’t seen any new content appear in a while, please try restarting your receiver and/or get in touch with us here in the forums.
Monitoring (heartbeat) script does not run
Monitoring may not be running when you boot the device. To find out whether it is running, you can log into your device and issue the following command:
# ORx
grep monitor /var/log/messages
# Lighthouse
grep monitor /var/log/syslog
If it’s not running (you don’t get any output), it is probably missing an activation file (file that tells the script it’s allowed to collect and transmit data) that was never automatically created up to this release, and is only created if monitoring has never run on the device. If you do want the monitoring to run, run the following command:
sudo touch /mnt/persist/monitoring.yes
Downloads
Pi 1: We Moved!
Pi 2: We Moved!
Lighthouse image will be put OTA, but you can also manually download and flash.
Ken
