update disdroDL to v0.3.3. in all PARs and THIES devices

[andrecastro0o]

Using Ansible disdrodl-playbook

Parsivels:

ansible-playbook ansible/playbook-update-disdro.yml --limit parsivel

parsivel001pi              : ok=8    changed=5    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
parsivel002pi              : ok=8    changed=5    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
parsivel003pi              : ok=8    changed=5    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
parsivel004pi              : ok=8    changed=5    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
parsivel005pi              : ok=8    changed=5    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
parsivel006pi              : ok=1    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0   
parsivel007pi              : ok=8    changed=5    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
parsivel008pi              : ok=8    changed=5    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
parsivel009pi              : ok=2    changed=1    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0   

Failed:

• parsivel006Pi Slufter: more description of the issue in PAR006 Sluften is sending noisy telegrams #36
• parsivel009pi due to network issues in Ludjewad

Thies:

ansible-playbook ansible/playbook-update-disdro.yml --limit thies

thies001pi                 : ok=8    changed=5    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
thies003pi                 : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0   
thies005pi                 : ok=8    changed=5    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
thies006pi                 : ok=8    changed=6    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
thies008pi                 : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0   

Failed

• thies003pi,thies008pi - not connected

[andrecastro0o]

done in all but thies003pi,thies008pi as they are not

[andrecastro0o]

@andrecastro0o figure out what happenied with PAR009 and clean the old versions

[andrecastro0o]

@andrecastro0o figure out what happenied with PAR009 and clean the old versions

due to the network issues in Lutejwad disdrodl has not been updated since 41f1fd0 (2024.08.26) . I re-started the disdrodl service (2024.09.23) .

Parsivel data is being written to the database
sqlite3 /data/disdroDL/disdrodl.db "SELECT * FROM disdrodl ORDER BY id DESC LIMIT 1"

18737|1727095680.6683|2024-09-23T12:48:00.668301+00:00|PAR009|01:0000.000; 02:0000.00; 03:00; 04:00;

It is likely that the NetCDF cannot get to project drive, due to network issues, but they should remain stored the Pi, so they can be copies to the Project Drive at a later date.

CC: @msourzac @mschleiss