Edited
Just added some notes for other people knowing what’s going on here,
so I edit the files as indicated in the blynk docs but nothing seems to be taken into account
I suggest that you put the Blynk Local Server jar file in the same directory /home/pi/Blynk as all other *.properties
files.
Currently, your jar file is at /home/pi
, and your *.properties
, dataFolder
are all in /home/pi/Blynk
from your command to start Blynk server:
java -jar /home/pi/server-0.41.11-java8.jar -dataFolder /home/pi/Blynk
It’s better you start over from reading README.md in
For example:
Create file mail.properties within same folder where server.jar is
in
Enabling mail on Local server
To enable mail notifications on Local server you need to provide your own mail credentials. Create file mail.properties within same folder where server.jar is. Mail properties:
mail.smtp.auth=true
mail.smtp.starttls.enable=true
mail.smtp.host=smtp.gmail.com
mail.smtp.port=587
mail.smtp.username=YOUR_EMAIL_HERE
mail.smtp.password=YOUR_EMAIL_PASS_HERE
You can also move all *.properties
files out to /home/pi
, but this is not a clean solution.
I’m afraid you have some confusion because the mistake in the above-mentioned README.md
, such as
java -jar /home/pi/server-0.41.12-java8.jar -dataFolder /home/pi/Blynk &
in this paragraph suggesting you placing the jar file in home/pi
, not in home/pi/Blynk
Enabling server auto restart on unix-like systems
To enable server auto restart find /etc/rc.local file and add:
java -jar /home/pi/server-0.41.12-java8.jar -dataFolder /home/pi/Blynk &
If you move the jar file to /home/pi/Blynk
, remember to change the command to
java -jar /home/pi/Blynk/server-0.41.11-java8.jar -dataFolder /home/pi/Blynk &
- If I understand correctly what you meant here:
Is it normal for files to change ssh to not show up with registered items?
est que c'est normal que les fichiers changer en ssh ne sont pas rafraîchit/afficher dans la page web de configuration de Blynk.
is it normal for files to change using SSH (Secure Shell) are not refreshed / displayed in the Blynk Server configuration web page.
That was answered in 1. because Blynk jar expects the *.properties
files are in the same folder. Otherwise, it just uses the default version of *.properties
files in memory, and pretending to save (actually saving to its Memory) and displaying V Save Changes
. Certainly it’s not saving to not-found physical files
.
If use use SSH to log and edit the files located in correct folder, everything will be refreshed / displayed / used after you restart the Blynk Server (kill-restart-jar, or reboot, etc.
- The old log files will be saved in an
archive
subfolder, where the file name is something likeblynk.log.2019-12-05
, and you can specify the level of logging to avoid using too much space by specifying which one you pick
#log debug level. trace|debug|info|error. Defines how precise logging will be.
log.level=error
#log.level=info