Zorb

Members
 View Profile  See their activity

  • Posts

    27

  • Joined

  • Last visited

 Content Type 

Posts posted by Zorb

    SSH users/Using VORTA from a client machine with unraid as remote share

    in General Support

    Posted · Edited by Zorb

    For now I have it working this way:

    - installed borg with nerdtools plugin

    - installed ssh plugin 

    - created a user per machine (e.g. macbookpro13)

    - create a share for this machine (could've used home folder come to think of it) 

    - turn on ssh for this user, only giving access to before mentioned share)

    - generate seperate borg ssh id on client

    - ssh-copy-id with the borg ssh id 

    - setup vorta 

     

    ----

     

    This works fine actually. But I do think it is a bit cumbersome, so wondering if there is indeed an easier way :)

    SSH users/Using VORTA from a client machine with unraid as remote share

    in General Support

    Posted

    Hi there,

     

    My apologies if this has been answered many time. I tried some searches, but couldn't really find what I was looking for. 

     

    I'm running vorta on different desktop clients (mostly mac) in my home. 

    Want to add unraid as a remote backup repository. 

     

    I'd like to have one ssh user with key authentication per client, with only read/write access to a subfolder so all backups are seperate.

     

    Is there an easy way to do this from unraid? (create ssh user, give it acces to only certain folder/share, and accept key that we use in borg) 

     

    Thanks for your time !

     

    [solved] Postgres docker preventing disk spin down

    in General Support

    Posted

    On 5/4/2021 at 4:37 PM, itimpi said:

    These things are always much easier when you already know the answer :)

     

    There are continual improvements being made to the online documentation so always worth checking there.   Often the Help built into the GUI helps as well. 

    I'll dig deeper next time. 

     

    But thanks for showing me what a friendly and helpful community this is. My trial was almost over and on the fence to buy or not. There are some caveats here and there (zfs support only when at least one normal array, turbo write things, custom plugins for ssd trimming etcetera) but there seems to be a solution for most of these things I came across either in the docs/forums/plugins and the forum users seem to be a helpful bunch of people! 

     

    (long irrelevent story short; I'm buying.. it feels like a decent product with a nice community behind it. )

     

    • Like 1

    [solved] Postgres docker preventing disk spin down

    in General Support

    Posted

    40 minutes ago, itimpi said:

    Your 'system' share (which contains the docker.ing file) is on disk1 which so running any container will tend to keep it (and parity) spun up. 

     

    You can follow the steps outlined here  in the online documentation that can be accessed via the Manual link at the bottom of the Unraid GUI to get it moved to the cache.

    Thank you! Worked perfectly.

     

    I feel I should've been able to figure this out myself. So thank you for taking the time to respond to my nooby question! 

    [solved] Postgres docker preventing disk spin down

    in General Support

    Posted · Edited by Zorb

    Hi all;

     

    there are multiple topics on this subject, but I did not want to hijack a thread pointing to a different cause. 

    After searching for multiple days I've found my postgress container is the one causing my first drive in the array (and parity) to not spin down anymore.

     

    Any idea what I might be able to do to fix this? Do I need to move the docker.img file somehow? or is it postgres specific? 
    I really like the idea of consuming energy as much as possible by spinning down disks when I am not actively using my nas. 

     

    Any help much appreciated. 

    6.9.2 Prefer cache - Mover does not move files from array to cache

    in General Support

    Posted

    On 4/11/2021 at 3:40 PM, Squid said:

    @JorgeB can you see if this fixes it: (and doesn't cause any other issues - It shouldn't)

     

    Save the attached as /usr/local/sbin/mover  (and give it executable permissions)

     

    mover 4.07 kB · 7 downloads

    I had a similar issue with appdata for containers. this solved it for me, moved everything i was expecting.

     

    so THANK YOU! 

     

    Does still seem to have an issue with .folderd (.icons in my case). Not an issue for me since those will be deleted anyway, but perhaps good to know. 

     

    I see errors like:

    May 3 14:23:30 Zorby move: move: file /mnt/disk1/appdata/binhex-preclear/home/.icons/BLACK-Ice-Numix-FLAT/scalable/actions/reply-rtl-symbolic.svg
    May 3 14:23:30 Zorby move: move_object: /mnt/disk1/

     

    Upon checking these files do actually exist. 

    [Support] Flight777 - "Just Works" Container Repository

    in Docker Containers

    Posted

    1 minute ago, Flight777 said:


    Good! :)

    The official author of the docker image has a knack of silently adding, changing or removing environment variables with each minor release.... Had this problem before, sometimes really annoying haha. I saw this variable did not exist anymore in the official repo, but because you didn't get an error it was just a guess.. 

    So I'll adjust the template now as well to remove it :P

     

    Perfect! thanks again for your time :)

     

     

    [Support] Flight777 - "Just Works" Container Repository

    in Docker Containers

    Posted

    11 minutes ago, Flight777 said:

    Could you remove the DATALOGGER INPUT METHOD: variable entirely and try again?

    SUCCESSSSSS!!! :)

     

    'serial' apparantly not being picked up correctly? 

    removed it; which restarts/recreates the container, look in web interface: data immediatly! 

     

    Thanks for your help! 

    If you are going to change that setting let me know if you need me to test something :)

    [Support] Flight777 - "Just Works" Container Repository

    in Docker Containers

    Posted

    Did an extra test from the console of DSMR; looks to be forwarded well also:

      

    > command:
microcom /dev/ttyUSB0 

> output: 
/ISK5\2M550T-1013

1-3:0.2.8(50)
0-0:1.0.0(210429180648S)
0-0:96.1.1(4530303534303037363738363237383230)
1-0:1.8.1(000725.696*kWh)
1-0:1.8.2(000729.424*kWh)
1-0:2.8.1(000000.000*kWh)
1-0:2.8.2(000000.000*kWh)
0-0:96.14.0(0002)
1-0:1.7.0(00.274*kW)
1-0:2.7.0(00.000*kW)
0-0:96.7.21(00005)
0-0:96.7.9(00002)
1-0:99.97.0()
1-0:32.32.0(00000)
1-0:52.32.0(00000)
1-0:72.32.0(00000)
1-0:32.36.0(00001)
1-0:52.36.0(00001)
1-0:72.36.0(00001)
0-0:96.13.0()
1-0:32.7.0(234.4*V)
1-0:52.7.0(234.8*V)
1-0:72.7.0(234.8*V)
1-0:31.7.0(000*A)
1-0:51.7.0(001*A)
1-0:71.7.0(000*A)
1-0:21.7.0(00.000*kW)
1-0:41.7.0(00.238*kW)
1-0:61.7.0(00.034*kW)
1-0:22.7.0(00.000*kW)
1-0:42.7.0(00.000*kW)
1-0:62.7.0(00.000*kW)
0-1:24.1.0(003)
0-1:96.1.0(4730303738353635353935353936383230)
0-1:24.2.1(210429180508S)(00739.963*m3)
!55EA
/ISK5\2M550T-1013

1-3:0.2.8(50)
0-0:1.0.0(210429180649S)
0-0:96.1.1(4530303534303037363738363237383230)
1-0:1.8.1(000725.696*kWh)
1-0:1.8.2(000729.424*kWh)
1-0:2.8.1(000000.000*kWh)
1-0:2.8.2(000000.000*kWh)
0-0:96.14.0(0002)
1-0:1.7.0(00.283*kW)
1-0:2.7.0(00.000*kW)
0-0:96.7.21(00005)
0-0:96.7.9(00002)
1-0:99.97.0()
1-0:32.32.0(00000)
1-0:52.32.0(00000)
1-0:72.32.0(00000)
1-0:32.36.0(00001)
1-0:52.36.0(00001)
1-0:72.36.0(00001)
0-0:96.13.0()
1-0:32.7.0(234.6*V)
1-0:52.7.0(235.0*V)
1-0:72.7.0(234.9*V)
1-0:31.7.0(000*A)
1-0:51.7.0(001*A)
1-0:71.7.0(000*A)
1-0:21.7.0(00.000*kW)
1-0:41.7.0(00.249*kW)
1-0:61.7.0(00.037*kW)
1-0:22.7.0(00.000*kW)
1-0:42.7.0(00.000*kW)
1-0:62.7.0(00.000*kW)
0-1:24.1.0(003)
0-1:96.1.0(4730303738353635353935353936383230)
0-1:24.2.1(210429180508S)(00739.963*m3)
!96D9
/ISK5\2M550T-1013

1-3:0.2.8(50)
0-0:1.0.0(210429180650S)
0-0:96.1.1(4530303534303037363738363237383230)
1-0:1.8.1(000725.696*kWh)
1-0:1.8.2(000729.424*kWh)
1-0:2.8.1(000000.000*kWh)
1-0:2.8.2(000000.000*kWh)
0-0:96.14.0(0002)
1-0:1.7.0(00.275*kW)
1-0:2.7.0(00.000*kW)
0-0:96.7.21(00005)
0-0:96.7.9(00002)
1-0:99.97.0()
1-0:32.32.0(00000)
1-0:52.32.0(00000)
1-0:72.32.0(00000)
1-0:32.36.0(00001)
1-0:52.36.0(00001)
1-0:72.36.0(00001)
0-0:96.13.0()
1-0:32.7.0(234.8*V)
1-0:52.7.0(235.2*V)
1-0:72.7.0(235.0*V)
1-0:31.7.0(000*A)
1-0:51.7.0(001*A)
1-0:71.7.0(000*A)
1-0:21.7.0(00.000*kW)
1-0:41.7.0(00.241*kW)
1-0:61.7.0(00.034*kW)
1-0:22.7.0(00.000*kW)
1-0:42.7.0(00.000*kW)
1-0:62.7.0(00.000*kW)
0-1:24.1.0(003)
0-1:96.1.0(4730303738353635353935353936383230)
0-1:24.2.1(210429180508S)(00739.963*m3)
!4C3E
/ISK5\2M550T-1013

1-3:0.2.8(50)
0-0:1.0.0(210429180651S)
0-0:96.1.1(4530303534303037363738363237383230)
1-0:1.8.1(000725.696*kWh)
1-0:1.8.2(000729.424*kWh)
1-0:2.8.1(000000.000*kWh)
1-0:2.8.2(000000.000*kWh)
0-0:96.14.0(0002)
1-0:1.7.0(00.275*kW)
1-0:2.7.0(00.000*kW)
0-0:96.7.21(00005)
0-0:96.7.9(00002)
1-0:99.97.0()
1-0:32.32.0(00000)
1-0:52.32.0(00000)
1-0:72.32.0(00000)
1-0:32.36.0(00001)
1-0:52.36.0(00001)
1-0:72.36.0(00001)
0-0:96.13.0()
1-0:32.7.0(234.6*V)
1-0:52.7.0(235.0*V)
1-0:72.7.0(235.3*V)
1-0:31.7.0(000*A)
1-0:51.7.0(001*A)
1-0:71.7.0(000*A)
1-0:21.7.0(00.000*kW)
1-0:41.7.0(00.241*kW)
1-0:61.7.0(00.033*kW)
1-0:22.7.0(00.000*kW)
1-0:42.7.0(00.000*kW)
1-0:62.7.0(00.000*kW)
0-1:24.1.0(003)
0-1:96.1.0(4730303738353635353935353936383230)
0-1:24.2.1(210429180508S)(00739.963*m3)
!25F4
/ISK5\2M550T-1013

1-3:0.2.8(50)
0-0:1.0.0(210429180652S)
0-0:96.1.1(4530303534303037363738363237383230)
1-0:1.8.1(000725.696*kWh)
1-0:1.8.2(000729.424*kWh)
1-0:2.8.1(000000.000*kWh)
1-0:2.8.2(000000.000*kWh)
0-0:96.14.0(0002)
1-0:1.7.0(00.275*kW)
1-0:2.7.0(00.000*kW)
0-0:96.7.21(00005)
0-0:96.7.9(00002)
1-0:99.97.0()
1-0:32.32.0(00000)
1-0:52.32.0(00000)
1-0:72.32.0(00000)
1-0:32.36.0(00001)
1-0:52.36.0(00001)
1-0:72.36.0(00001)
0-0:96.13.0()
1-0:32.7.0(234.6*V)
1-0:52.7.0(235.0*V)
1-0:72.7.0(235.1*V)
1-0:31.7.0(000*A)
1-0:51.7.0(001*A)
1-0:71.7.0(000*A)
1-0:21.7.0(00.000*kW)
1-0:41.7.0(00.240*kW)
1-0:61.7.0(00.034*kW)
1-0:22.7.0(00.000*kW)
1-0:42.7.0(00.000*kW)
1-0:62.7.0(00.000*kW)
0-1:24.1.0(003)
0-1:96.1.0(4730303738353635353935353936383230)
0-1:24.2.1(210429180508S)(00739.963*m3)
!4EB0
/ISK5\2M550T-1013

1-3:0.2.8(50)
0-0:1.0.0(210429180653S)
0-0:96.1.1(4530303534303037363738363237383230)
1-0:1.8.1(000725.696*kWh)
1-0:1.8.2(000729.424*kWh)
1-0:2.8.1(000000.000*kWh)
1-0:2.8.2(000000.000*kWh)
0-0:96.14.0(0002)
1-0:1.7.0(00.270*kW)
1-0:2.7.0(00.000*kW)
0-0:96.7.21(00005)
0-0:96.7.9(00002)
1-0:99.97.0()
1-0:32.32.0(00000)
1-0:52.32.0(00000)
1-0:72.32.0(00000)
1-0:32.36.0(00001)
1-0:52.36.0(00001)
1-0:72.36.0(00001)
0-0:96.13.0()
1-0:32.7.0(234.5*V)
1-0:52.7.0(235.0*V)
1-0:72.7.0(235.0*V)
1-0:31.7.0(000*A)
1-0:51.7.0(001*A)
1-0:71.7.0(000*A)
1-0:21.7.0(00.000*kW)
1-0:41.7.0(00.242*kW)
1-0:61.7.0(00.032*kW)
1-0:22.7.0(00.000*kW)
1-0:42.7.0(00.000*kW)
1-0:62.7.0(00.000*kW)
0-1:24.1.0(003)
0-1:96.1.0(4730303738353635353935353936383230)
0-1:24.2.1(210429180508S)(00739.963*m3)
!36C5
/ISK5\2M550T-1013

     

    [Support] Flight777 - "Just Works" Container Repository

    in Docker Containers

    Posted

    8 minutes ago, Flight777 said:


    You are sure /dev/ttyUSB0 is a path that exists for UNRAID itself as well? You can check this by opening your system log. remove USB from your computer and plug it back it. You should then in the log see to which path it gets assigned.

     

    A thousand percent; If I open up a bash shell on unraid I can do a ```screen /dev/ttyUSB0 115200``` and I actually see dsmr data scrolling by.. 

    [Support] Flight777 - "Just Works" Container Repository

    in Docker Containers

    Posted

    Thanks for the 12.5 image!! The settings that come with it by default are the same I did earlier. Perhaps postgress 10 template had some issues.

    Anyways; Just to make sure I deleted al containers, added the 12.5 postgress from your repo, and after that added the dsmr one again (with a added custom device of /dev/ttyUSB0 )

     

    Connection to postgress works perfectly now. And dsmrreader starts up with no errors. 

    Yet still no data; do you know of a way to check what de dsmr deamon is doing? 

    [Support] Flight777 - "Just Works" Container Repository

    in Docker Containers

    Posted

    30 minutes ago, Flight777 said:


    You have to add the device itself, that's true, I said that in the description as well, but I can clarify that more :P This is because I can not make the device parameter optional in Unraid templates, so for people that would not need it the template would otherwise error out.

    First observation that I now realise, you are trying to use Postgres 10, while only 11 or 12 is supported officially by DSMRReader. I just created a net template for 12.5 which I'm using myself, should be up in the Community Repository within the hour. Please try that one after filling out the user, pass and db for dsmrreader in the parameters.

    Now second question regarding your smart meter, do you know what type it is and which DSMR version it supports? Because it might be your baudrate needs to be different. The settings in the description are for v5 protocol, but could be yours is older. 

    Could you maybe also attached the log the container is spitting out when you try and start it up (click on the container logo ---> logs)?

     

    Allright, I should've read more carefully. Sorry.

    I have a "iskra smr 5.0 am550-td2" -> SMR 5.0. I've tried with screen command on the unraid host on 115200 bauds and seems to work correctly. 

     

    I can recheck with postgress 12 (or wait for your update in the repo :) ) 

     

    Logs for dsmr stopping and starting:

      

    
2021-04-29 15:14:10,250 INFO exited: dsmr_datalogger (exit status 0; expected)
2021-04-29 15:14:10,737 INFO spawned: 'dsmr_datalogger' with pid 623
2021-04-29 15:14:12,343 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-04-29 15:14:16,512 INFO exited: dsmr_datalogger (exit status 0; expected)
2021-04-29 15:14:17,515 INFO spawned: 'dsmr_datalogger' with pid 624
2021-04-29 15:14:18,580 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-04-29 15:14:23,280 INFO exited: dsmr_datalogger (exit status 0; expected)
2021-04-29 15:14:24,282 INFO spawned: 'dsmr_datalogger' with pid 625
2021-04-29 15:14:25,944 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-04-29 15:14:30,058 INFO exited: dsmr_datalogger (exit status 0; expected)
2021-04-29 15:14:30,381 INFO spawned: 'dsmr_datalogger' with pid 626
2021-04-29 15:14:32,045 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-04-29 15:14:36,160 INFO exited: dsmr_datalogger (exit status 0; expected)
2021-04-29 15:14:36,472 INFO spawned: 'dsmr_datalogger' with pid 627
2021-04-29 15:14:38,136 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-04-29 15:14:42,249 INFO exited: dsmr_datalogger (exit status 0; expected)
2021-04-29 15:14:42,464 INFO spawned: 'dsmr_datalogger' with pid 628
Operations to perform:
Apply all migrations: admin, auth, contenttypes, dsmr_api, dsmr_backend, dsmr_backup, dsmr_consumption, dsmr_datalogger, dsmr_dropbox, dsmr_frontend, dsmr_influxdb, dsmr_mindergas, dsmr_mqtt, dsmr_notification, dsmr_pvoutput, dsmr_stats, dsmr_weather, sessions
Running migrations:
No migrations to apply.

0 static files copied to '/var/www/dsmrreader/static', 562 unmodified.
Updating password of superuser "admin"
Deactivating any other existing superusers
2021-04-29 15:16:07,061 INFO Set uid to user 0 succeeded
2021-04-29 15:16:07,367 INFO RPC interface 'supervisor' initialized
2021-04-29 15:16:07,367 INFO supervisord started with pid 16
2021-04-29 15:16:07,061 INFO Set uid to user 0 succeeded
2021-04-29 15:16:07,367 INFO RPC interface 'supervisor' initialized
2021-04-29 15:16:07,367 INFO supervisord started with pid 16
2021-04-29 15:16:08,369 INFO spawned: 'dsmr_backend' with pid 18
2021-04-29 15:16:08,371 INFO spawned: 'dsmr_datalogger' with pid 19
2021-04-29 15:16:08,373 INFO spawned: 'dsmr_webinterface' with pid 20
2021-04-29 15:16:08,375 INFO spawned: 'nginx' with pid 21
2021-04-29 15:16:10,236 INFO success: dsmr_backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-04-29 15:16:10,236 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-04-29 15:16:10,236 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-04-29 15:16:12,238 INFO success: dsmr_webinterface entered RUNNING state, process has stayed up for > than 3 seconds (startsecs)
2021-04-29 15:16:14,355 INFO exited: dsmr_datalogger (exit status 0; expected)
2021-04-29 15:16:15,358 INFO spawned: 'dsmr_datalogger' with pid 27
2021-04-29 15:16:15,358 INFO spawned: 'dsmr_datalogger' with pid 27
2021-04-29 15:16:17,015 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-04-29 15:16:17,015 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-04-29 15:16:21,128 INFO exited: dsmr_datalogger (exit status 0; expected)
2021-04-29 15:16:21,128 INFO exited: dsmr_datalogger (exit status 0; expected)
2021-04-29 15:16:22,131 INFO spawned: 'dsmr_datalogger' with pid 28
2021-04-29 15:16:23,792 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-04-29 15:16:27,916 INFO exited: dsmr_datalogger (exit status 0; expected)
2021-04-29 15:16:28,919 INFO spawned: 'dsmr_datalogger' with pid 29
2021-04-29 15:16:30,571 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

     

    [Support] Flight777 - "Just Works" Container Repository

    in Docker Containers

    Posted

    19 minutes ago, Zorb said:

    @Flight777 when using serial device; shouldn;t the container be started with the --device flag to map my locak /dev/ttyUSB to the container device? 

      

    
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='DSMRReader' --net='bridge' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'DJANGO_DATABASE_HOST'='192.168.178.60' -e 'DSMRREADER_ADMIN_USER'='admin' -e 'DSMRREADER_ADMIN_PASSWORD'='dsmrreader' -e 'DATALOGGER_MODE'='standalone' -e 'DATALOGGER_INPUT_METHOD'='serial' -e 'DATALOGGER_SERIAL_PORT'='/dev/ttyUSB0' -e 'DATALOGGER_SERIAL_BAUDRATE'='115200' -e 'VIRTUAL_HOST'='localhost' -e 'DJANGO_DATABASE_PORT'='5432' -e 'DJANGO_DATABASE_NAME'='dsmrdb' -e 'DATALOGGER_SLEEP'='10' -e 'PUID'='99' -e 'PGID'='100' -e 'SD_USER'='nobody' -e 'SD_GROUP'='users' -p '7777:80/tcp' -v '/mnt/user/appdata/dsmr-reader/backups':'/home/dsmr/app/backups':'rw' 'xirixiz/dsmr-reader-docker'
8af852d990ea4bd6e8ffea19d27a99024afdefc6ef83e3aa786282d77f9e6170


     

     

    Even when I add device in the ui of unraid, still does not seem to do anything in DSMReader webui:

     

    See end command now adds the device: 

    root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='DSMRReader' --net='bridge' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'DJANGO_DATABASE_HOST'='192.168.178.60' -e 'DSMRREADER_ADMIN_USER'='admin' -e 'DSMRREADER_ADMIN_PASSWORD'='dsmrreader' -e 'DATALOGGER_MODE'='standalone' -e 'DATALOGGER_INPUT_METHOD'='serial' -e 'DATALOGGER_SERIAL_PORT'='/dev/ttyUSB0' -e 'DATALOGGER_SERIAL_BAUDRATE'='115200' -e 'VIRTUAL_HOST'='localhost' -e 'DJANGO_DATABASE_PORT'='5432' -e 'DJANGO_DATABASE_NAME'='dsmrdb' -e 'DATALOGGER_SLEEP'='10' -e 'PUID'='99' -e 'PGID'='100' -e 'SD_USER'='nobody' -e 'SD_GROUP'='users' -p '7777:80/tcp' -v '/mnt/user/appdata/dsmr-reader/backups':'/home/dsmr/app/backups':'rw' --device='/dev/ttyUSB0' 'xirixiz/dsmr-reader-docker'
81968b755bf127210e7d0ccd2cbdd12e4c1af42bda4c33a93ee1b228135f8bd6


    In the console of the DSMR container I can see that it now indeed has a /dev/ttyUSB0

     

    .. but still no data. Has this been tested on serial, or are you doing networkbased yourself? 

    [Support] Flight777 - "Just Works" Container Repository

    in Docker Containers

    Posted

    @Flight777 when using serial device; shouldn;t the container be started with the --device flag to map my locak /dev/ttyUSB to the container device? 

      

    root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='DSMRReader' --net='bridge' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'DJANGO_DATABASE_HOST'='192.168.178.60' -e 'DSMRREADER_ADMIN_USER'='admin' -e 'DSMRREADER_ADMIN_PASSWORD'='dsmrreader' -e 'DATALOGGER_MODE'='standalone' -e 'DATALOGGER_INPUT_METHOD'='serial' -e 'DATALOGGER_SERIAL_PORT'='/dev/ttyUSB0' -e 'DATALOGGER_SERIAL_BAUDRATE'='115200' -e 'VIRTUAL_HOST'='localhost' -e 'DJANGO_DATABASE_PORT'='5432' -e 'DJANGO_DATABASE_NAME'='dsmrdb' -e 'DATALOGGER_SLEEP'='10' -e 'PUID'='99' -e 'PGID'='100' -e 'SD_USER'='nobody' -e 'SD_GROUP'='users' -p '7777:80/tcp' -v '/mnt/user/appdata/dsmr-reader/backups':'/home/dsmr/app/backups':'rw' 'xirixiz/dsmr-reader-docker'
8af852d990ea4bd6e8ffea19d27a99024afdefc6ef83e3aa786282d77f9e6170


     

    [Support] Flight777 - "Just Works" Container Repository

    in Docker Containers

    Posted

    On Unraid the p1 seems to work; I get data if I screen on my unraid bash console:

     

    `root@Zorby:~# screen /dev/ttyUSB0 115200`

    -- snip --
    1-0:71.7.0(000*A)
    1-0:21.7.0(00.000*kW)
    1-0:41.7.0(00.240*kW)
    1-0:61.7.0(00.082*kW)
    1-0:22.7.0(00.000*kW)
    1-0:42.7.0(00.000*kW)
    1-0:62.7.0(00.000*kW)
    0-1:224.2.1(210429133508S)(00737.535*m3)
    !5A1C
    0-0:96.13.0()
    1-0:32.7.0(233.4*V)
    1-0:52.7.0(2/ISK5\2M550T-1013

    1-3:0.2.8(50)
    0-0:1.0.0(210429133948S)
    0-0:96.1.1(4530303534303037363738363237383230)
    1-0:1.8.1(000725.696*kWh)
    -- snip -- 

     

    DSMR settings point to this USB with same baudrate:

     

    image.thumb.png.3d54da625cae9509bb3c57fa49c3d6bb.png

     

    But does not seem to work. 

    For completion btw this is my postgress setting now:

    image.thumb.png.db06e1d902d3e36cc7116c33c62f977f.png

     

    [Support] Flight777 - "Just Works" Container Repository

    in Docker Containers

    Posted

    5 minutes ago, Flight777 said:

    Glad it's working, but you should not have to do that manually. The containter variables for Postgress shoukd work... 

    Can you still show me your config of that container, then I can help tto atleast double check ;)

    Sure thing.

    I feel like a complete and utter noob in unraid though; When I switch from basic to advanced view i'd expect the XML to popup somewhere. It doesn't however. 

     

    I'll digg through the filesystem to check where the xml's are stored (tips welcome :) ) 

     

     

     

    [Support] Flight777 - "Just Works" Container Repository

    in Docker Containers

    Posted

    10 minutes ago, Flight777 said:

     

    Could you share your postgress template settings? You might not be using the right environment variables 😛

     

    Just to double check. 

    Thanks for responding so quickly!

    I've managed to get it working now :)


    - I deleted everything and started from scratch.

    - Left postgress (10) template on default settings in the template (postgres/postgres/postgres for user/pass/db

    - Used pgadmin4 to create a user 'dsmrreader' 

    - Used pgadmin4 to create a db 'dsmrdb'

     

    Started dsmrreader container again and it works now. (I thought I could just fill out the postgress template to have dsmrreader etc; but perhaps this should've been the way all along) 

    [Support] Flight777 - "Just Works" Container Repository

    in Docker Containers

    Posted

    22 minutes ago, Zorb said:

    Thanks for these apps/docker templates. 

    I tried setting up dsrmreader; but the user/pass/db mentioned in the text info is different from what I see in the xml in your github.

    apart from that i created a new postgress11 with different combinations in the user/pass/db fields for postgress but I continously get the following errors in postgress logs:

    2021-04-29 11:40:24.177 CEST [77] DETAIL: Role "dsmrreader" does not exist.
    Connection matched pg_hba.conf line 95: "host all all all md5"
    2021-04-29 11:40:25.941 CEST [78] FATAL: password authentication failed for user "dsmrreader"
    2021-04-29 11:40:25.941 CEST [78] DETAIL: Role "dsmrreader" does not exist.

     

    can you do a quick write up how to configure these 2 to work together? would be much appreciated :)
    (do I need to manually add a db in postgress instead of setting the postgress template settings to above mentioned credentials?) 

    Seems to be something wrong with postgress docker; whatever I set in the template, user/pass will always remain to be postgres/postgres. So I'll try to go the manual create DB route. 

    [Support] Flight777 - "Just Works" Container Repository

    in Docker Containers

    Posted

    Thanks for these apps/docker templates. 

    I tried setting up dsrmreader; but the user/pass/db mentioned in the text info is different from what I see in the xml in your github.

    apart from that i created a new postgress11 with different combinations in the user/pass/db fields for postgress but I continously get the following errors in postgress logs:

    2021-04-29 11:40:24.177 CEST [77] DETAIL: Role "dsmrreader" does not exist.
    Connection matched pg_hba.conf line 95: "host all all all md5"
    2021-04-29 11:40:25.941 CEST [78] FATAL: password authentication failed for user "dsmrreader"
    2021-04-29 11:40:25.941 CEST [78] DETAIL: Role "dsmrreader" does not exist.

     

    can you do a quick write up how to configure these 2 to work together? would be much appreciated :)
    (do I need to manually add a db in postgress instead of setting the postgress template settings to above mentioned credentials?) 

    Turbo write

    in Lounge

    Posted

    On 3/29/2021 at 7:00 PM, trurl said:

    There is a plugin. Do you have Community Applications installed? Have you searched the Apps page?

    I have, just wanted to make sure the plugin is still needed, since this thread, and the part I quoted was from 2016 (!) 

    • Like 1

    Turbo write

    in Lounge

    Posted

    On 9/22/2016 at 3:38 AM, RobJ said:

    Currently, you only have the option to use the old method or the new (currently the Auto option means the old method).  But the plan is to add the true Auto option that will use the old method by default, *unless* all of the drives are currently spinning.  If the drives are all spinning, then it slips into Turbo.  This should be enough for many users.  It would normally use the old method, but if you planned a large transfer or a bunch of writes, then you would spin up all of the drives - and enjoy faster writing.

    Am I correct in assuming this is still on the wishlist of things to implement? given the mention of a plugin in the last page of this thread?