If you have finished this instructable prior this update, but want to update the code. First version supported only 1-2 sensors, now there can be as many as Raspberry pi has gpios.Jump to page 10, download the DHT22Logger code again, setup revised and you are good to go. Execution of the code now creates rotating log files to DHT22-Temperature Logger/Debugger/Logs/. Attach sensor to RPI and add sensor configuration to and it is taken into account when executed.

thanksedit: i left the terminal open (the one where i ran sudo noip2 -d) and it updates every 5 minutes. It seems the service file runs noip2 as user "nobody" - the config file would need to have e.g.

644 permissions to be read (but you said you had tried 644).

You can edit /usr/lib/systemd/system/noip2.service, append -d to the command there, run "systemctl reenable noip2; systemctl restart noip2" and see its debugging output in "systemctl status noip2" or "journalctl -u noip2". ⮀ systemctl status noip2.service noip2.service - No-IP Dynamic DNS Update Client Loaded: loaded (/usr/lib/systemd/system/noip2.service; enabled) Active: active (running) since Sat 2013-02-16 CET; 4min 50s ago Process: 3491 Exec Start=/usr/bin/noip2 -d -c /etc/no-ip2(code=exited, status=0/SUCCESS) Main PID: 3492 (noip2) CGroup: name=systemd:/system/noip2.service └─3492 /usr/bin/noip2 -d -c /etc/no-ip2well, i rerun noip2 configure, entered username and pw (like i did 3 times before), left the default time of 30 minutesthen i changed permissions before starting the service (of /etc/no-ip2.conf) to 644started the service and here is what the journal is saying:why do i get this last line today? also, what would be my course of action now - changing the permissions of no-ip2even though so many people use it with the same 644 permissions or maybe something else?

then i left home with laptop, got on another wireless and here's the output of journalctl -u noip2-- Reboot -- Feb 23 wslap noip2[420]: v2.1.9 daemon started with NAT enabled Feb 23 wslap noip2[417]: Can't gethostbyname for dynupdate.Feb 23 wslap noip2[417]: Can't get our visible IP address from ip1.dynupdate.Feb 23 wslap noip2[417]: !

ok, I came back home and it automatically updated the service is working, maybe that other wifi ap somehow blocked the service...anyway, I will mark this as solved.

although i don't even know what was the problem and what fixed it Hello All, I just want to share my systemd configuration.This logger also allows you to set limits for temperatures and is able to send email if sensor temperature drops below set limit..neat feature can be for example used to alarm when it is time to set heating on in your house / carage / greenhouse / you name it.To complete this instructable, you will need following:- Raspberry PI (I used Raspberry PI 1 model B , but should be doable with other models as well)- Power supply for the pi.Run noip2 with -d to see what it's doing; perhaps use -U to modify the update interval (you can modify the service file to use those options).i am a noob kinda, so this may be a stupid question - is it possible that the noip2 service itself can't access the config file?The section of the code responsible for saving looks dubious to me, but I'm not a programmer.