Firmware not connected

[tebbbb]

Hi,

i am using a RPI4B with Ubuntu on it. I changed the interface in the docker-compose to AMA0 and when i start, this is what i get:

14:35:38:181 discovery server date: Sun, 08 Oct 2023 14:35:38 GMT 14:35:38:181 local time seems to be ok 14:35:40:519 DEV Tick.Init: booted after 8000 seconds 14:35:48:595 dev /dev/ttyAMA0 14:35:53:019 start reconnect to network 14:35:58:269 failed to reconnect to network try=1 14:36:02:604 dev /dev/ttyAMA0 14:36:03:518 failed to reconnect to network try=2 14:36:08:518 try to reconnect to network try=3

and it says Firmware Not connected in the UI

[senilio]

What device do you have?

Paste full compose file

[tebbbb]

Raspberry Pi 4B with Ubuntu 23.04 (also tried out 22.04 LTS before with same result) and Raspbee II

version: "2"
services:
  deconz:
    image: deconzcommunity/deconz
    container_name: deconz
    restart: always
    ports: 
      - 80:80
      - 443:443
    volumes:
      - /opt/deconz:/opt/deCONZ
    devices:
      - /dev/ttyAMA0
    environment:
      - DECONZ_WEB_PORT=80
      - DECONZ_WS_PORT=443
      - DEBUG_INFO=1
      - DEBUG_APS=0
      - DEBUG_ZCL=0
      - DEBUG_ZDP=0
      - DEBUG_OTA=0

[senilio]

Can you try setting the DECONZ_DEVICE environment variable as well? Also is the Raspbee recognized by the host OS?

[tebbbb]

How do i set this variable with using docker-compose? docker-compose up -d -e DECONZ_DEVICE=/dev/ttyAMA0 ? How can i check if the host OS recognized the Raspbee?

[phdelodder]

version: "2"
services:
  deconz:
    image: deconzcommunity/deconz
    container_name: deconz
    restart: always
    ports: 
      - 80:80
      - 443:443
    volumes:
      - /opt/deconz:/opt/deCONZ
    devices:
      - /dev/ttyAMA0
    environment:
      - DECONZ_WEB_PORT=80
      - DECONZ_WS_PORT=443
      - DEBUG_INFO=1
      - DEBUG_APS=0
      - DEBUG_ZCL=0
      - DEBUG_ZDP=0
      - DEBUG_OTA=0
      - DECONZ_DEVICE=/dev/ttyAMA0

[tebbbb]

It looks a little bit different now, but still says "Firmware Not connected"

14:51:21:034 COM: /dev/ttyAMA0 / serialno: , RaspBee
14:51:22:035 dev /dev/ttyAMA0
14:51:22:035 COM: /dev/ttyAMA0 / serialno: , RaspBee
14:51:24:321 start reconnect to network
14:51:26:025 dev /dev/ttyAMA0
14:51:26:026 COM: /dev/ttyAMA0 / serialno: , RaspBee
14:51:27:039 dev /dev/ttyAMA0
14:51:27:040 COM: /dev/ttyAMA0 / serialno: , RaspBee
14:51:27:872 Invalid admin password hash
14:51:29:571 failed to reconnect to network try=1
14:51:31:032 dev /dev/ttyAMA0
14:51:31:032 COM: /dev/ttyAMA0 / serialno: , RaspBee
14:51:31:035 created username: 9045D44E6D, devicetype: Phoscon#B1925x1153
14:51:32:027 dev /dev/ttyAMA0
14:51:32:028 COM: /dev/ttyAMA0 / serialno: , RaspBee
14:51:33:357 New websocket 192.168.1.131:33964 (state: 3) 
14:51:33:572 Websocket disconnected 192.168.1.131:33964, state: 0, close-code: 1001, reason: 
14:51:34:821 failed to reconnect to network try=2
14:51:35:170 New websocket 192.168.1.131:33968 (state: 3) 
14:51:36:030 dev /dev/ttyAMA0
14:51:36:030 COM: /dev/ttyAMA0 / serialno: , RaspBee
14:51:37:025 dev /dev/ttyAMA0
14:51:37:025 COM: /dev/ttyAMA0 / serialno: , RaspBee
14:51:38:215 Websocket disconnected 192.168.1.131:33968, state: 0, close-code: 1001, reason: 
14:51:39:588 New websocket 192.168.1.131:44882 (state: 3) 
14:51:39:820 failed to reconnect to network try=3
14:51:41:027 dev /dev/ttyAMA0
14:51:41:027 COM: /dev/ttyAMA0 / serialno: , RaspBee
14:51:42:026 dev /dev/ttyAMA0
14:51:42:026 COM: /dev/ttyAMA0 / serialno: , RaspBee
14:51:44:820 failed to reconnect to network try=4
14:51:46:028 dev /dev/ttyAMA0
14:51:46:029 COM: /dev/ttyAMA0 / serialno: , RaspBee
14:51:47:022 dev /dev/ttyAMA0
14:51:47:022 COM: /dev/ttyAMA0 / serialno: , RaspBee

[phdelodder]

Can you do a ls -all /dev/tty* to see if even the device exists?

[tebbbb]

Yes, its listed like this:

crw-rw---- 1 root dialout 204, 64 Okt 11 20:57 /dev/ttyAMA0

[phdelodder]

When checking in dmesg do you find /dev/ttyAMA0? Is it recognized as a Raspbee?

[tebbbb]

All i find with dmesg | grep "AMA0" is

[0.887869] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 36, base_baud = 0) is a PL011 rev2

[phdelodder]

Around the timestamp do you see any more info?

[tebbbb]

Nothing unusual i think

` [ 0.793941] zswap: loaded using pool zstd/z3fold [ 0.798431] Key type .fscrypt registered [ 0.798447] Key type fscrypt-provisioning registered [ 0.813475] Key type encrypted registered [ 0.813502] AppArmor: AppArmor sha1 policy hashing enabled [ 0.813534] ima: No TPM chip found, activating TPM-bypass! [ 0.813566] ima: Allocated hash algorithm: sha1 [ 0.813591] ima: No architecture policies found [ 0.813645] evm: Initialising EVM extended attributes: [ 0.813651] evm: security.selinux [ 0.813657] evm: security.SMACK64 [ 0.813663] evm: security.SMACK64EXEC [ 0.813669] evm: security.SMACK64TRANSMUTE [ 0.813674] evm: security.SMACK64MMAP [ 0.813679] evm: security.apparmor [ 0.813685] evm: security.ima [ 0.813690] evm: security.capability [ 0.813696] evm: HMAC attrs: 0x1 [ 0.818025] uart-pl011 fe201000.serial: there is not valid maps for state default [ 0.819836] uart-pl011 fe201000.serial: cts_event_workaround enabled [ 0.819932] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 36, base_baud = 0) is a PL011 rev2 [ 0.826376] of_cfs_init [ 0.826472] of_cfs_init: OK [ 0.862516] mmc0: SDHCI controller on fe340000.mmc [fe340000.mmc] using ADMA [ 0.871089] Freeing unused kernel memory: 5568K [ 0.898935] Checked W+X mappings: passed, no W+X pages found [ 0.898967] Run /init as init process [ 0.898974] with arguments: [ 0.898981] /init [ 0.898986] fixrtc [ 0.898991] splash [ 0.898995] with environment: [ 0.899000] HOME=/ [ 0.899005] TERM=linux [ 1.752733] usb_phy_generic phy: dummy supplies not allowed for exclusive requests [ 1.764321] bcmgenet fd580000.ethernet end0: renamed from eth0 [ 1.773977] xhci_hcd 0000:01:00.0: enabling device (0000 -> 0002) [ 1.774052] xhci_hcd 0000:01:00.0: xHCI Host Controller [ 1.774096] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1 [ 1.774542] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0000e40000000890 [ 1.775008] xhci_hcd 0000:01:00.0: xHCI Host Controller

[phdelodder]

Seems fine indeed! The issue is I can't reproduce it.

[tebbbb]

Can it be related to me running an external harddrive instead of using an SD card? I had really weird problems in the past (for example if the harddrive is too close to the raspberry pi, the bluetooth doesnt work anymore and so on)

[senilio]

It can absolutely be related to interference. Especially when running the OS on an SSD drive. You should try ruling that out by booting on an SD card or moving the SSD for away on an extension cable etc.

[senilio]

If the problem persists after 100% ruling out interference issues, reopen this issue.