[support] digiblur's Docker Template Repository

digiblur

By digiblur
in Docker Containers

Recommended Posts

Auden69 Rookie

Auden69

Posted
Posted (edited)

Hello I don't understand why my conbee II is not found :

 

Unraid Version: 6.10.3

Zigbee2MQTT version 1.26.0 

 

  

root@Tower: ls -l /dev/serial/by-id
total 0
lrwxrwxrwx 1 root root 13 Jul 28 08:15 usb-RFXCOM_RFXtrx433_A11P1XIW-if00-port0 -> ../../ttyUSB0
lrwxrwxrwx 1 root root 13 Jul 28 08:56 usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2230164-if00 -> ../../ttyACM0

 

My Z2M configuration :

  

  GNU nano 6.0                                 configuration.yaml                                            
# Home Assistant integration (MQTT discovery)
homeassistant: true

# allow new devices to join
permit_join: true

# MQTT settings
mqtt:
  # MQTT base topic for zigbee2mqtt MQTT messages
  base_topic: zigbee2mqtt
  # MQTT server URL
  server: 'mqtt://192.168.1.100:1883'
  # MQTT server authentication, uncomment if required:
  user: *******
  password: *****

# Serial settings
serial:
  port: >-
    /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2230164-if00 
  adapter: deconz
advanced:
  log_level: info

 

My M2Q log : 

Using '/app/data' as data directory
Zigbee2MQTT:info  2022-07-28 09:22:43: Logging to console and directory: '/app/data/log/2022-07-28.09-22-43' filename: log.txt
Zigbee2MQTT:info  2022-07-28 09:22:43: Starting Zigbee2MQTT version 1.26.0 (commit #cd23aea)
Zigbee2MQTT:info  2022-07-28 09:22:43: Starting zigbee-herdsman (0.14.40)
Zigbee2MQTT:error 2022-07-28 09:22:43: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-07-28 09:22:43: Failed to start zigbee
Zigbee2MQTT:error 2022-07-28 09:22:43: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2022-07-28 09:22:43: Exiting...
Zigbee2MQTT:error 2022-07-28 09:22:43: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2230164-if00 '
    at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
    at SerialPort._error (/app/node_modules/@serialport/stream/lib/index.js:198:14)
    at /app/node_modules/@serialport/stream/lib/index.js:242:12

 

My conbee 2 works. I tried it with ZHA in my VM home assistant (just to try) but only with "dev/serial/by-id/usb-QEMU_QEMU_USB_SERIAL_1-0000:00:07.7-4-if00-port0" as path.

 

Any idea ??

 

Thanks

Edited by Auden69
Link to comment
  • 2 weeks later...
  • Replies 196
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

digiblur
digiblur

With my dive into the Home Automation scene my appetite for additional containers to use on the unRaid server has grown.  All of the templates point to a docker container that I was able to import fro

DtheS
DtheS

Not sure if it's just an issue for me or everybody else as well. Since zigbee2mqtt docker updated to 1.29.1 I am seeing the dreaded orange broken chain "not available" under version in the Docker tab?

digiblur
digiblur

Thanks, I'll take a look at it.

Posted Images

  • 2 weeks later...
bellyup Noob

bellyup

Posted
Posted
On 7/28/2022 at 1:07 AM, Auden69 said:

Hello I don't understand why my conbee II is not found :

 

Unraid Version: 6.10.3

Zigbee2MQTT version 1.26.0 

 

  

root@Tower: ls -l /dev/serial/by-id
total 0
lrwxrwxrwx 1 root root 13 Jul 28 08:15 usb-RFXCOM_RFXtrx433_A11P1XIW-if00-port0 -> ../../ttyUSB0
lrwxrwxrwx 1 root root 13 Jul 28 08:56 usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2230164-if00 -> ../../ttyACM0

 

My Z2M configuration :

  

  GNU nano 6.0                                 configuration.yaml                                            
# Home Assistant integration (MQTT discovery)
homeassistant: true

# allow new devices to join
permit_join: true

# MQTT settings
mqtt:
  # MQTT base topic for zigbee2mqtt MQTT messages
  base_topic: zigbee2mqtt
  # MQTT server URL
  server: 'mqtt://192.168.1.100:1883'
  # MQTT server authentication, uncomment if required:
  user: *******
  password: *****

# Serial settings
serial:
  port: >-
    /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2230164-if00 
  adapter: deconz
advanced:
  log_level: info

 

My M2Q log : 

Using '/app/data' as data directory
Zigbee2MQTT:info  2022-07-28 09:22:43: Logging to console and directory: '/app/data/log/2022-07-28.09-22-43' filename: log.txt
Zigbee2MQTT:info  2022-07-28 09:22:43: Starting Zigbee2MQTT version 1.26.0 (commit #cd23aea)
Zigbee2MQTT:info  2022-07-28 09:22:43: Starting zigbee-herdsman (0.14.40)
Zigbee2MQTT:error 2022-07-28 09:22:43: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-07-28 09:22:43: Failed to start zigbee
Zigbee2MQTT:error 2022-07-28 09:22:43: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2022-07-28 09:22:43: Exiting...
Zigbee2MQTT:error 2022-07-28 09:22:43: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2230164-if00 '
    at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
    at SerialPort._error (/app/node_modules/@serialport/stream/lib/index.js:198:14)
    at /app/node_modules/@serialport/stream/lib/index.js:242:12

 

My conbee 2 works. I tried it with ZHA in my VM home assistant (just to try) but only with "dev/serial/by-id/usb-QEMU_QEMU_USB_SERIAL_1-0000:00:07.7-4-if00-port0" as path.

 

Any idea ??

 

Thanks

Are you sure you passed your device into the docker container?

Link to comment
  • 1 month later...
gravymaker Noob

gravymaker

Posted
Posted (edited)

UNMS DOCKER QUESTION - DISABLING 2FA

 

I've got myself into a bit of a pickle.    I got a new phone and migrated all data and apps, but I didn't realize the Google Authenticator information was not part of the Samsung Sync process.  So now I can't access my UNMS docker as it is requesting the 2FA code.   (Old phone was wiped.)

 

There are instructions on the web for resetting 2FA (https://community.ui.com/questions/reset-2fa-to-local-unms-server/458ddf6a-4ef9-465d-94e5-a3c113d4c8f4) but the UNMS docker doesn't appear to have the "unms-cli" command when I try these instructions.  

 

I've tried running both the docker-compose command at the unraid command line, as well as trying the unms-cli command from a command prompt within the docker itself.

 

Has anyone run into this?   

Edited by gravymaker
Link to comment
gravymaker Noob

gravymaker

Posted
Posted (edited)
On 10/18/2022 at 8:53 AM, gravymaker said:

UNMS DOCKER QUESTION - DISABLING 2FA

 

I've got myself into a bit of a pickle.    I got a new phone and migrated all data and apps, but I didn't realize the Google Authenticator information was not part of the Samsung Sync process.  So now I can't access my UNMS docker as it is requesting the 2FA code.   (Old phone was wiped.)

 

There are instructions on the web for resetting 2FA (https://community.ui.com/questions/reset-2fa-to-local-unms-server/458ddf6a-4ef9-465d-94e5-a3c113d4c8f4) but the UNMS docker doesn't appear to have the "unms-cli" command when I try these instructions.  

 

I've tried running both the docker-compose command at the unraid command line, as well as trying the unms-cli command from a command prompt within the docker itself.

 

Has anyone run into this?   

[SOLVED]

I was able to figure this out by reading the unms-cli file and figuring out what it actually calls.   In this docker, its the "user.js" file that handles things!  

 

So, my command was: 

/home/app/unms/cli # node /home/app/unms/cli/user.js two-factor <<USERID>>

results:
                UNMS Users

┌─────────┬────────────┬────────────────────┬──────────────┬────────────┬───────┐
│ (index) │  username  │       email        │     role     │ two-factor │  sso  │
├─────────┼────────────┼────────────────────┼──────────────┼────────────┼───────┤
│    0    │ '####'     │ '###@##.com'       │ 'superadmin' │   false    │ false │
└─────────┴────────────┴────────────────────┴──────────────┴────────────┴───────┘

 

Just posting for any other idiots that forget to migrate their authenticator data!!

 

 

Edited by gravymaker
cleaned up command
Link to comment
  • 1 month later...
baldfox Noob

baldfox

Posted
Posted

Hi guys,  been using Tasmoadmin. Works great, but has anyone had any success managing to actually update a device? I've tried a whole host of OTA URLs and various options, but I cannot make anything stick and actually complete (minimal then tasmota.bin).

It's as if I am unable to get the files out of github itself.

Link to comment
The Transplant Rookie

The Transplant

Posted
Posted
On 4/20/2021 at 2:25 PM, LeetDonkey said:

I edited the dockerfile to look for the neolink.toml file in a subdirectory rather than /etc/neolink.toml

I don't think this is a good way of doing it since it will no longer follow the thirtythreeforty repository.

Anyways, if you'd like you can simply change the repository to leetdonkey/neolink:

neolink1.png


Then change the neolink_config path configuration:

neolink2.png

 

then put neolink.toml in /etc/mnt/user/appdata/neolink/ and start the docker.
Note that the container use the name neolink.toml instead of config.toml

If there is a way of linking directly to a file instead of a directory I am not aware of it, but I must confess that I am very new at this docker stuff
 

 

After much trial and error I figured out how to get around this issue with the config file.  Uninstall neolink if you have it installed.  Go into the neolink folder and create the config.toml file.  Then install the neolink docker.  It will then work.

Link to comment
  • 2 weeks later...
  • 1 month later...
DtheS Noob

DtheS

Posted
Posted (edited)

Not sure if it's just an issue for me or everybody else as well. Since zigbee2mqtt docker updated to 1.29.1 I am seeing the dreaded orange broken chain "not available" under version in the Docker tab?!?

 

Does anybody else have this?

 

Running Unraid version 6.11.5

Edited by DtheS
  • Like 1
  • Upvote 2
Link to comment
deadnote Apprentice

deadnote

Posted
Posted
10 hours ago, DtheS said:

Not sure if it's just an issue for me or everybody else as well. Since zigbee2mqtt docker updated to 1.29.1 I am seeing the dreaded orange broken chain "not available" under version in the Docker tab?!?

 

Does anybody else have this?

 

Running Unraid version 6.11.5

Same here !

  • Upvote 1
Link to comment
canedje Noob

canedje

Posted
Posted (edited)
On 1/14/2023 at 10:55 PM, DtheS said:

Not sure if it's just an issue for me or everybody else as well. Since zigbee2mqtt docker updated to 1.29.1 I am seeing the dreaded orange broken chain "not available" under version in the Docker tab?!?

 

Does anybody else have this?

 

Running Unraid version 6.11.5

Me too.

Running still 1.29.1. Not able to update to 1.29.2

Edited by canedje
Link to comment
canedje Noob

canedje

Posted
Posted
On 1/17/2023 at 5:33 PM, olympia said:

...and me too.

 

The only way to update to 1.29.2 was to remove the container and reinstall - but then again a receive the same error when checking for updates.

 

When removing and reinstall the docker the devices are still there? You don't need to repair?

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.

×
Go to topic listing