-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
question: Using photOS offline #105
Comments
My workaround was to use an old router (TPlink WR710) after setup (connected to the internet). Then the pictures are downloaded. This may also be done manually to this folder: /data/photoframe/images_local/ |
That sounds like a solution, but unfortunately i would prefer to run it without a additional device (since i would have to purchase it). |
Would be a better solution in my eyes to start up no matter if there is a wifi signal or not, show the saved pictures and check (using a cronjob) ever x min/hours if a signal is available. What do you think? |
I stumbled upon the same issue and in the WiKi I found a hint that helped me. My scenario: Pi Zero W boots up using my mobile phone hotspot to sync and to prevent Panic reboots. Shutting down the hotspot or moving away from Pi keeps it alive, cycling the stored pictures. Solutions for your request @Notonegoro: Create file os.conf by using SSH, enabling PhotOS to boot without network:
In that case, PhotOS will boot without network, no update, no remote control. To use same setup as described above, please use following SSH commands:
The instructions given at the end of the FAQ are not working as they are creating a file netwatch.conf that is not used by OS. |
Hi,
is there an option, that i could run photOS offline, because on the location i want to use it, there is no wifi.
As a workaround i could think of trying to run the WebDav server local on the same raspberry. (I guess that's to experimental)
So is it maybe possible to just use a folder on the SD-card or on a mounted external storrage?
The text was updated successfully, but these errors were encountered: