[Support] Flight777 - "Just Works" Container Repository


Recommended Posts

Hi all,

Being a relative new user to UNRAID, but having worked with docker extensively myself before, I've find that some useful docker applications do not yet have a working UNRAID template in the app store, or there are very outdated versions that do not work anymore without major adjustments.

So that's why I've decided to contribute by creating these templates under the "Just Works" branding, and this support thread will still evolve further while I find the time. Similarly to my GITHUB, which is still very basic: https://github.com/Flight777/unraid_justworks_templates

List of containers:

 

Feel free to ask away if you need any help setting up one of my templates!

 

Kind regards,

Rob

Edited by Flight777
  • Like 1
Link to comment
  • Flight777 changed the title to [Support] Flight777 - "Just Works" Container Repository

Hello.

 

So I installed this docket to give it a try and is running fine.

 

Quote

2021-01-28 09:55:15 INFO: UDP relay enabled
2021-01-28 09:55:15 INFO: initializing ciphers... chacha20-ietf-poly1305
2021-01-28 09:55:15 INFO: using nameserver: 8.8.8.8,8.8.4.4
2021-01-28 09:55:15 INFO: tcp server listening at 0.0.0.0:8388
2021-01-28 09:55:15 INFO: udp server listening at 0.0.0.0:8388

 

I'm trying looking for a guide to use it once it is installed. Currently, I'm using swag to access some of my container (radarr/sonarr/etc) remotely. Do I need to do the same for Shadowsocks?

 

Thanks

Link to comment

Hi Bugster,

Thanks for reaching out :)

Shadowsocks works over both TCP and UDP so Swag (NGINX) will not be able to direct UDP traffic. There are ways, with the V2ray plugin installed, but I'm not familiar with them, maybe someone else can comment: https://github.com/shadowsocks/v2ray-plugin/issues/188

However, to make Shadowsocks work, you will have to forward the port (TCP and UDP) 8388 (or any other port you set in the "PORT" variables) in your router/firewall to the UNRAID IP., so you can connect via your public IP or domainname.

 

You can then install a client and connect to Shadowsocks with your set details: https://shadowsocks.org/en/download/clients.html
 

Shadowsocks takes care of encrypting the connection, hence the encryption method specified.


Here is another good write-up: https://upcloud.com/community/tutorials/install-shadowsocks-libev-socks5-proxy/ 

Link to comment
4 minutes ago, Banuseka said:

HI @Flight777

 

can you advise on how to pass a password to a password-protected redis docker?

 

Best, Banu


Hi Banu,

This is not possible in this container, you have to manage the Redis settings via the Barcodebuddy Webui and this does not allow for password entry yet. You can request this feature from the original developer on Github here: https://github.com/Forceu/barcodebuddy

However, why would you want to password protect your Redis if you do not expose it to the outside world? Especially for a barcode scanner, which is a secondary function, I would just use Redis for this specific use without a password for now :)

Link to comment
40 minutes ago, Flight777 said:


Hi Banu,

This is not possible in this container, you have to manage the Redis settings via the Barcodebuddy Webui and this does not allow for password entry yet. You can request this feature from the original developer on Github here: https://github.com/Forceu/barcodebuddy

However, why would you want to password protect your Redis if you do not expose it to the outside world? Especially for a barcode scanner, which is a secondary function, I would just use Redis for this specific use without a password for now :)

I already use a redis docker for nextcloud, and NC wants to use redis with a password. that was my intention instead of setting up a second redis docker ;)

 

I'll prob. go for a feature request.

 

Best, Banu

Link to comment

Hi Banu

16 minutes ago, Banuseka said:

I already use a redis docker for nextcloud, and NC wants to use redis with a password. that was my intention instead of setting up a second redis docker ;)

 

I'll prob. go for a feature request.

 

Best, Banu


For Redis, best practice is actually to give every application you want an own Redis instance, so a new Redis container. They have a very light footprint anyway.

Edited by Flight777
  • Thanks 1
Link to comment
  • 1 month later...

Hi,

I seem to have some issues passing barcodedata from my scanner to barcodepubbdy, i've got it hooked up to the machine, and it is passing into the docker container:

image.thumb.png.bc3ae48c25dbed68ee1c61541fdf52d9.png

If i temporalraly set ATTACH_BARCODESCANNER to false and run the evtest inside barcode buddy i get this:

 

root@08553912ebe4:/# evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event1:      ᄅSymbol Technologies, Inc, 2002 Symbol Bar Code Scanner
Select the device event number [0-1]: 1
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x5e0 product 0x1200 version 0x110
Input device name: "ᄅSymbol Technologies, Inc, 2002 Symbol Bar Code Scanner"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 1 (KEY_ESC)
    Event code 2 (KEY_1)
    Event code 3 (KEY_2)
    Event code 4 (KEY_3)
    Event code 5 (KEY_4)
    Event code 6 (KEY_5)
    Event code 7 (KEY_6)
    Event code 8 (KEY_7)
    Event code 9 (KEY_8)
    Event code 10 (KEY_9)
    Event code 11 (KEY_0)
    Event code 12 (KEY_MINUS)
    Event code 13 (KEY_EQUAL)
    Event code 14 (KEY_BACKSPACE)
    Event code 15 (KEY_TAB)
    Event code 16 (KEY_Q)
    Event code 17 (KEY_W)
    Event code 18 (KEY_E)
    Event code 19 (KEY_R)
    Event code 20 (KEY_T)
    Event code 21 (KEY_Y)
    Event code 22 (KEY_U)
    Event code 23 (KEY_I)
    Event code 24 (KEY_O)
    Event code 25 (KEY_P)
    Event code 26 (KEY_LEFTBRACE)
    Event code 27 (KEY_RIGHTBRACE)
    Event code 28 (KEY_ENTER)
    Event code 29 (KEY_LEFTCTRL)
    Event code 30 (KEY_A)
    Event code 31 (KEY_S)
    Event code 32 (KEY_D)
    Event code 33 (KEY_F)
    Event code 34 (KEY_G)
    Event code 35 (KEY_H)
    Event code 36 (KEY_J)
    Event code 37 (KEY_K)
    Event code 38 (KEY_L)
    Event code 39 (KEY_SEMICOLON)
    Event code 40 (KEY_APOSTROPHE)
    Event code 41 (KEY_GRAVE)
    Event code 42 (KEY_LEFTSHIFT)
    Event code 43 (KEY_BACKSLASH)
    Event code 44 (KEY_Z)
    Event code 45 (KEY_X)
    Event code 46 (KEY_C)
    Event code 47 (KEY_V)
    Event code 48 (KEY_B)
    Event code 49 (KEY_N)
    Event code 50 (KEY_M)
    Event code 51 (KEY_COMMA)
    Event code 52 (KEY_DOT)
    Event code 53 (KEY_SLASH)
    Event code 54 (KEY_RIGHTSHIFT)
    Event code 55 (KEY_KPASTERISK)
    Event code 56 (KEY_LEFTALT)
    Event code 57 (KEY_SPACE)
    Event code 58 (KEY_CAPSLOCK)
    Event code 59 (KEY_F1)
    Event code 60 (KEY_F2)
    Event code 61 (KEY_F3)
    Event code 62 (KEY_F4)
    Event code 63 (KEY_F5)
    Event code 64 (KEY_F6)
    Event code 65 (KEY_F7)
    Event code 66 (KEY_F8)
    Event code 67 (KEY_F9)
    Event code 68 (KEY_F10)
    Event code 69 (KEY_NUMLOCK)
    Event code 70 (KEY_SCROLLLOCK)
    Event code 71 (KEY_KP7)
    Event code 72 (KEY_KP8)
    Event code 73 (KEY_KP9)
    Event code 74 (KEY_KPMINUS)
    Event code 75 (KEY_KP4)
    Event code 76 (KEY_KP5)
    Event code 77 (KEY_KP6)
    Event code 78 (KEY_KPPLUS)
    Event code 79 (KEY_KP1)
    Event code 80 (KEY_KP2)
    Event code 81 (KEY_KP3)
    Event code 82 (KEY_KP0)
    Event code 83 (KEY_KPDOT)
    Event code 85 (KEY_ZENKAKUHANKAKU)
    Event code 86 (KEY_102ND)
    Event code 87 (KEY_F11)
    Event code 88 (KEY_F12)
    Event code 89 (KEY_RO)
    Event code 90 (KEY_KATAKANA)
    Event code 91 (KEY_HIRAGANA)
    Event code 92 (KEY_HENKAN)
    Event code 93 (KEY_KATAKANAHIRAGANA)
    Event code 94 (KEY_MUHENKAN)
    Event code 95 (KEY_KPJPCOMMA)
    Event code 96 (KEY_KPENTER)
    Event code 97 (KEY_RIGHTCTRL)
    Event code 98 (KEY_KPSLASH)
    Event code 99 (KEY_SYSRQ)
    Event code 100 (KEY_RIGHTALT)
    Event code 102 (KEY_HOME)
    Event code 103 (KEY_UP)
    Event code 104 (KEY_PAGEUP)
    Event code 105 (KEY_LEFT)
    Event code 106 (KEY_RIGHT)
    Event code 107 (KEY_END)
    Event code 108 (KEY_DOWN)
    Event code 109 (KEY_PAGEDOWN)
    Event code 110 (KEY_INSERT)
    Event code 111 (KEY_DELETE)
    Event code 113 (KEY_MUTE)
    Event code 114 (KEY_VOLUMEDOWN)
    Event code 115 (KEY_VOLUMEUP)
    Event code 116 (KEY_POWER)
    Event code 117 (KEY_KPEQUAL)
    Event code 119 (KEY_PAUSE)
    Event code 121 (KEY_KPCOMMA)
    Event code 122 (KEY_HANGUEL)
    Event code 123 (KEY_HANJA)
    Event code 124 (KEY_YEN)
    Event code 125 (KEY_LEFTMETA)
    Event code 126 (KEY_RIGHTMETA)
    Event code 127 (KEY_COMPOSE)
    Event code 128 (KEY_STOP)
    Event code 129 (KEY_AGAIN)
    Event code 130 (KEY_PROPS)
    Event code 131 (KEY_UNDO)
    Event code 132 (KEY_FRONT)
    Event code 133 (KEY_COPY)
    Event code 134 (KEY_OPEN)
    Event code 135 (KEY_PASTE)
    Event code 136 (KEY_FIND)
    Event code 137 (KEY_CUT)
    Event code 138 (KEY_HELP)
    Event code 140 (KEY_CALC)
    Event code 142 (KEY_SLEEP)
    Event code 150 (KEY_WWW)
    Event code 152 (KEY_SCREENLOCK)
    Event code 158 (KEY_BACK)
    Event code 159 (KEY_FORWARD)
    Event code 161 (KEY_EJECTCD)
    Event code 163 (KEY_NEXTSONG)
    Event code 164 (KEY_PLAYPAUSE)
    Event code 165 (KEY_PREVIOUSSONG)
    Event code 166 (KEY_STOPCD)
    Event code 173 (KEY_REFRESH)
    Event code 176 (KEY_EDIT)
    Event code 177 (KEY_SCROLLUP)
    Event code 178 (KEY_SCROLLDOWN)
    Event code 179 (KEY_KPLEFTPAREN)
    Event code 180 (KEY_KPRIGHTPAREN)
    Event code 183 (KEY_F13)
    Event code 184 (KEY_F14)
    Event code 185 (KEY_F15)
    Event code 186 (KEY_F16)
    Event code 187 (KEY_F17)
    Event code 188 (KEY_F18)
    Event code 189 (KEY_F19)
    Event code 190 (KEY_F20)
    Event code 191 (KEY_F21)
    Event code 192 (KEY_F22)
    Event code 193 (KEY_F23)
    Event code 194 (KEY_F24)
    Event code 240 (KEY_UNKNOWN)
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
  Event type 17 (EV_LED)
    Event code 0 (LED_NUML) state 0
    Event code 1 (LED_CAPSL) state 0
    Event code 2 (LED_SCROLLL) state 0
    Event code 3 (LED_COMPOSE) state 0
    Event code 4 (LED_KANA) state 0
Key repeat handling:
  Repeat type 20 (EV_REP)
    Repeat code 0 (REP_DELAY)
      Value    250
    Repeat code 1 (REP_PERIOD)
      Value     33
Properties:
Testing ... (interrupt to exit)
Event: time 1615564068.160604, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70022
Event: time 1615564068.160604, type 1 (EV_KEY), code 6 (KEY_5), value 1
Event: time 1615564068.160604, -------------- SYN_REPORT ------------
Event: time 1615564068.168588, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70022
Event: time 1615564068.168588, type 1 (EV_KEY), code 6 (KEY_5), value 0
Event: time 1615564068.168588, -------------- SYN_REPORT ------------
Event: time 1615564068.176596, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70021
Event: time 1615564068.176596, type 1 (EV_KEY), code 5 (KEY_4), value 1
Event: time 1615564068.176596, -------------- SYN_REPORT ------------
Event: time 1615564068.184593, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70021
Event: time 1615564068.184593, type 1 (EV_KEY), code 5 (KEY_4), value 0
Event: time 1615564068.184593, -------------- SYN_REPORT ------------
Event: time 1615564068.192596, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7001e
Event: time 1615564068.192596, type 1 (EV_KEY), code 2 (KEY_1), value 1
Event: time 1615564068.192596, -------------- SYN_REPORT ------------
Event: time 1615564068.200586, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7001e
Event: time 1615564068.200586, type 1 (EV_KEY), code 2 (KEY_1), value 0
Event: time 1615564068.200586, -------------- SYN_REPORT ------------
Event: time 1615564068.208598, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7001f
Event: time 1615564068.208598, type 1 (EV_KEY), code 3 (KEY_2), value 1
Event: time 1615564068.208598, -------------- SYN_REPORT ------------
Event: time 1615564068.216599, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7001f
Event: time 1615564068.216599, type 1 (EV_KEY), code 3 (KEY_2), value 0
Event: time 1615564068.216599, -------------- SYN_REPORT ------------
Event: time 1615564068.224601, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7001f
Event: time 1615564068.224601, type 1 (EV_KEY), code 3 (KEY_2), value 1
Event: time 1615564068.224601, -------------- SYN_REPORT ------------
Event: time 1615564068.232588, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7001f
Event: time 1615564068.232588, type 1 (EV_KEY), code 3 (KEY_2), value 0
Event: time 1615564068.232588, -------------- SYN_REPORT ------------
Event: time 1615564068.240597, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70024
Event: time 1615564068.240597, type 1 (EV_KEY), code 8 (KEY_7), value 1
Event: time 1615564068.240597, -------------- SYN_REPORT ------------
Event: time 1615564068.248597, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70024
Event: time 1615564068.248597, type 1 (EV_KEY), code 8 (KEY_7), value 0
Event: time 1615564068.248597, -------------- SYN_REPORT ------------
Event: time 1615564068.256598, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7001e
Event: time 1615564068.256598, type 1 (EV_KEY), code 2 (KEY_1), value 1
Event: time 1615564068.256598, -------------- SYN_REPORT ------------
Event: time 1615564068.264594, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7001e
Event: time 1615564068.264594, type 1 (EV_KEY), code 2 (KEY_1), value 0
Event: time 1615564068.264594, -------------- SYN_REPORT ------------
Event: time 1615564068.272602, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7001f
Event: time 1615564068.272602, type 1 (EV_KEY), code 3 (KEY_2), value 1
Event: time 1615564068.272602, -------------- SYN_REPORT ------------
Event: time 1615564068.280591, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7001f
Event: time 1615564068.280591, type 1 (EV_KEY), code 3 (KEY_2), value 0
Event: time 1615564068.280591, -------------- SYN_REPORT ------------
Event: time 1615564068.288599, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70024
Event: time 1615564068.288599, type 1 (EV_KEY), code 8 (KEY_7), value 1
Event: time 1615564068.288599, -------------- SYN_REPORT ------------
Event: time 1615564068.296593, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70024
Event: time 1615564068.296593, type 1 (EV_KEY), code 8 (KEY_7), value 0
Event: time 1615564068.296593, -------------- SYN_REPORT ------------
Event: time 1615564068.304597, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70024
Event: time 1615564068.304597, type 1 (EV_KEY), code 8 (KEY_7), value 1
Event: time 1615564068.304597, -------------- SYN_REPORT ------------
Event: time 1615564068.312598, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70024
Event: time 1615564068.312598, type 1 (EV_KEY), code 8 (KEY_7), value 0
Event: time 1615564068.312598, -------------- SYN_REPORT ------------
Event: time 1615564068.320595, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70024
Event: time 1615564068.320595, type 1 (EV_KEY), code 8 (KEY_7), value 1
Event: time 1615564068.320595, -------------- SYN_REPORT ------------
Event: time 1615564068.328594, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70024
Event: time 1615564068.328594, type 1 (EV_KEY), code 8 (KEY_7), value 0
Event: time 1615564068.328594, -------------- SYN_REPORT ------------
Event: time 1615564068.336600, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70026
Event: time 1615564068.336600, type 1 (EV_KEY), code 10 (KEY_9), value 1
Event: time 1615564068.336600, -------------- SYN_REPORT ------------
Event: time 1615564068.344594, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70026
Event: time 1615564068.344594, type 1 (EV_KEY), code 10 (KEY_9), value 0
Event: time 1615564068.344594, -------------- SYN_REPORT ------------
Event: time 1615564068.352596, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70021
Event: time 1615564068.352596, type 1 (EV_KEY), code 5 (KEY_4), value 1
Event: time 1615564068.352596, -------------- SYN_REPORT ------------
Event: time 1615564068.360598, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70021
Event: time 1615564068.360598, type 1 (EV_KEY), code 5 (KEY_4), value 0
Event: time 1615564068.360598, -------------- SYN_REPORT ------------

 

This would mean that the datat is passed (possibly double??)
But when i set the variable back to true, nothing happens when i scan.

Am i doing something wrong?
Tnx for the help!

Kind regards,

Kevin



 

Link to comment
  • 1 month later...

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?) 

Link to comment
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. 

Link to comment
1 minute ago, Zorb said:

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. 

 

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

 

Just to double check. 

Link to comment
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) 

Link to comment
23 minutes ago, Zorb said:

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) 

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 ;)

Link to comment
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 :)

 

 

 

Link to comment

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

 

Link to comment

@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


 

Link to comment
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? 

Link to comment
17 minutes ago, Zorb said:

 

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? 


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)?

Link to comment
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)

 

Link to comment
Posted (edited)
2 hours ago, Zorb said:

ps:

image.thumb.png.a00d0b983d98eb883470d0497b9f9ca7.png

 

DB name seems to be dsmrdb instead of dsmreaderDB  

 

The new postgres template is up and processed by the community plugins app now. So you should be able to find it, look for "Postgres12.5" :)

Regarding your above comment, let me check, that's written a bit confusin indeed. As long as you make sure the DB you create with the Postgres container is the same as you give as parameter to DSMRREADER you are good to go.

Edited by Flight777
Link to comment

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? 

Link to comment
1 minute ago, Zorb said:

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? 


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.

 

Link to comment
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.. 

Link to comment
5 minutes ago, Zorb said:

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.. 

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

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.