Yes, I used exactly this guide.EddyG wrote: ↑Monday 15 March 2021 22:05 Did you follow all these steps? https://www.zigbee2mqtt.io/getting_star ... 2mqtt.html
No Zigbee2mqtt on the Hardware list
Moderator: leecollings
-
- Posts: 20
- Joined: Thursday 06 August 2020 14:20
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2020.2
- Location: Prague
- Contact:
Re: No Zigbee2mqtt on the Hardware list
-
- Posts: 20
- Joined: Thursday 06 August 2020 14:20
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2020.2
- Location: Prague
- Contact:
Re: No Zigbee2mqtt on the Hardware list
True, I just wanted to answer to the friend asking to check Domoticz log
- jvdz
- Posts: 2328
- Joined: Tuesday 30 December 2014 19:25
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 4.107
- Location: Netherlands
- Contact:
Re: No Zigbee2mqtt on the Hardware list
Right...but what is the answer? is it working or is it not?
...and when it is not: Where are you with getting it sorted?
Jos
...and when it is not: Where are you with getting it sorted?
Jos
New Garbage collection scripts: https://github.com/jvanderzande/GarbageCalendar
-
- Posts: 20
- Joined: Thursday 06 August 2020 14:20
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2020.2
- Location: Prague
- Contact:
Re: No Zigbee2mqtt on the Hardware list
Still no progress. I am following all the advices here, but basically, I'm stuck. Still this message:
Code: Select all
pi@raspberrypi:/opt/zigbee2mqtt $ npm start
> [email protected] start /opt/zigbee2mqtt
> node index.js
Zigbee2MQTT:info 2021-03-15 21:13:31: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2021-03-15.21-13-30' filename: log.txt
Zigbee2MQTT:info 2021-03-15 21:13:31: Starting Zigbee2MQTT version 1.18.1 (commit #a43d1f3)
Zigbee2MQTT:info 2021-03-15 21:13:31: Starting zigbee-herdsman (0.13.71)
Zigbee2MQTT:error 2021-03-15 21:13:32: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-03-15 21:13:32: Failed to start zigbee
Zigbee2MQTT:error 2021-03-15 21:13:32: Exiting...
Zigbee2MQTT:error 2021-03-15 21:13:32: Error: Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'
at Znp.<anonymous> (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:136:32)
at Generator.next (<anonymous>)
at /opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71
at new Promise (<anonymous>)
at __awaiter (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12)
at SerialPort.<anonymous> (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:134:49)
at SerialPort._error (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14)
at /opt/zigbee2mqtt/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2021-03-15T21_13_32_530Z-debug.log
This is probably not a problem with npm. There is likely additional logging output above.
Just to mention that before I had it set up okay, Domoticz could see "zigbee2mqtt" in the Hardware. This time the big struggle is to have Domoticz and Hoobs. I feel that the problems start when I install Hoobs. Maybe I do something completely wrong when installing hoobs. I read that some prefer to install it with docker. But looks extremely complicated for my zero knowledge.
What I did was in this order. Debian, ssh, mosquitto brocker, Zigbee2mqtt, domoticz. And then, the below to install Hoobs:
Code: Select all
wget -q -O - http://bit.ly/get-hoobs | sudo bash -
thats all
- jvdz
- Posts: 2328
- Joined: Tuesday 30 December 2014 19:25
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 4.107
- Location: Netherlands
- Contact:
Re: No Zigbee2mqtt on the Hardware list
Ok so there is an issue were zigbee2mqtt fails to connect to the usb controller. so , what did you define in the configuration.yaml file for the usb port
and what is the output of this command?:
or in case of rights issues:
Code: Select all
serial:
port: /dev/???????
Code: Select all
ls -l /dev/serial/by-id
Code: Select all
sudo ls -l /dev/serial/by-id
New Garbage collection scripts: https://github.com/jvanderzande/GarbageCalendar
-
- Posts: 20
- Joined: Thursday 06 August 2020 14:20
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2020.2
- Location: Prague
- Contact:
Re: No Zigbee2mqtt on the Hardware list
port:jvdz wrote: ↑Monday 15 March 2021 23:12 Ok so there is an issue were zigbee2mqtt fails to connect to the usb controller. so , what did you define in the configuration.yaml file for the usb portand what is the output of this command?:Code: Select all
serial: port: /dev/???????
or in case of rights issues:Code: Select all
ls -l /dev/serial/by-id
Code: Select all
sudo ls -l /dev/serial/by-id
Code: Select all
homeassistant: false
permit_join: true
mqtt:
base_topic: zigbee2mqtt
server: 'mqtt://localhost:1883'
serial:
port: /dev/ttyACM0
devices:
'0x54ef4410000182bf':
friendly_name: '0x54ef4410000182bf'
Code: Select all
total 0
lrwxrwxrwx 1 root root 13 Mar 15 23:28 usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001938618A-if00 -> ../../ttyACM0
And I just connected RPi to my screen and I realised, I don't have even bluetooth now.
Code: Select all
pi@raspberrypi:~ $ blueman-applet
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
(blueman-applet:1341): Gtk-CRITICAL **: 23:35:17.628: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
(blueman-applet:1341): Gtk-CRITICAL **: 23:35:17.653: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Traceback (most recent call last):
File "/usr/bin/blueman-applet", line 121, in <module>
BluemanApplet()
File "/usr/bin/blueman-applet", line 52, in __init__
setup_icon_path()
File "/usr/lib/python3/dist-packages/blueman/Functions.py", line 178, in setup_icon_path
ic.prepend_search_path(ICON_PATH)
AttributeError: 'NoneType' object has no attribute 'prepend_search_path'
- waltervl
- Posts: 5846
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2024.7
- Location: NL
- Contact:
Re: No Zigbee2mqtt on the Hardware list
What is this Hoobs doing? Did it work before you installed Hoobs?
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
-
- Posts: 744
- Joined: Saturday 30 May 2015 22:40
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Contact:
Re: No Zigbee2mqtt on the Hardware list
Is this hoobs thing claiming your usb key? (Since it wants to connect accessories to a home automation system)
-
- Posts: 20
- Joined: Thursday 06 August 2020 14:20
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2020.2
- Location: Prague
- Contact:
Re: No Zigbee2mqtt on the Hardware list
Yes! Domoticz was working fine, and zigbee2mqtt was visible in Hardware.
(The thing is that having only Domoticz without Homebridge or Hoobs is 50% of what I need, as I need the integration with Apple's home)
-
- Posts: 20
- Joined: Thursday 06 August 2020 14:20
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2020.2
- Location: Prague
- Contact:
Re: No Zigbee2mqtt on the Hardware list
Re: No Zigbee2mqtt on the Hardware list
Simple check:
Pull Hoobs out of the usb of the raspberry, wait a few second, and put it in again and wait a few seconds.
Now run on your raspberry.
And post the last few lines here, it should be something like:
Pull Hoobs out of the usb of the raspberry, wait a few second, and put it in again and wait a few seconds.
Now run on your raspberry.
Code: Select all
dmesg
Code: Select all
[174494.956398] usb 1-1.1: new full-speed USB device number 4 using xhci_hcd
[174495.095279] usb 1-1.1: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
[174495.095295] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[174495.095308] usb 1-1.1: Product: TI CC2531 USB CDC
[174495.095320] usb 1-1.1: Manufacturer: Texas Instruments
[174495.095331] usb 1-1.1: SerialNumber: __0X00124B0012023155
[174495.326135] cdc_acm 1-1.1:1.0: ttyACM0: USB ACM device
[174495.328489] usbcore: registered new interface driver cdc_acm
[174495.328503] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
-
- Posts: 20
- Joined: Thursday 06 August 2020 14:20
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2020.2
- Location: Prague
- Contact:
Re: No Zigbee2mqtt on the Hardware list
Hello,EddyG wrote: ↑Wednesday 17 March 2021 10:42 Simple check:
Pull Hoobs out of the usb of the raspberry, wait a few second, and put it in again and wait a few seconds.
Now run on your raspberry.And post the last few lines here, it should be something like:Code: Select all
dmesg
Code: Select all
[174494.956398] usb 1-1.1: new full-speed USB device number 4 using xhci_hcd [174495.095279] usb 1-1.1: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09 [174495.095295] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [174495.095308] usb 1-1.1: Product: TI CC2531 USB CDC [174495.095320] usb 1-1.1: Manufacturer: Texas Instruments [174495.095331] usb 1-1.1: SerialNumber: __0X00124B0012023155 [174495.326135] cdc_acm 1-1.1:1.0: ttyACM0: USB ACM device [174495.328489] usbcore: registered new interface driver cdc_acm [174495.328503] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
maybe there is some misunderstanding. Hoobs is a piece of software, it's not hardware, it's not some USB stick or smth. Hoobs stands for "Homebridge Out Of the Box.. something". Hoobs is taking the devices that Domoticz discovers through the zigbee sniffer and makes them available to Apple's Home app. Here, I used the quick installation command https://support.hoobs.org/docs/5e763e30e87d1e02b6c19d33.
Now, I tried also to flash Hoobs in the SD https://support.hoobs.org/docs/5e875c220ab68b0344e872ca, but booting the RPi this way, I couldn't SSH for some reason. And there is no GUI, so I couldn't even do it with a screen connected to the RPi.
So, actually, there are two USB ports in use right now. One for the zigbee sniffer and one for the wireless mouse adapter.
Nevertheless, I am attaching the code from the command you are suggesting (the whole thing)
Code: Select all
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 5.10.17-v7+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1403 SMP Mon Feb 22 11:29:51 GMT 2021
[ 0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[ 0.000000] CPU: div instructions available: patching division code
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] Reserved memory: created CMA memory pool at 0x37400000, size 64 MiB
[ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000000000000-0x000000003b3fffff]
[ 0.000000] Normal empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000000000-0x000000003b3fffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000003b3fffff]
[ 0.000000] On node 0 totalpages: 242688
[ 0.000000] DMA zone: 2133 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 242688 pages, LIFO batch:63
[ 0.000000] percpu: Embedded 20 pages/cpu s50700 r8192 d23028 u81920
[ 0.000000] pcpu-alloc: s50700 r8192 d23028 u81920 alloc=20*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 240555
[ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=fddaa439-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[ 0.000000] Kernel parameter elevator= does not have any effect anymore.
Please use sysfs to set IO scheduler for individual devices.
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] Memory: 879832K/970752K available (9216K kernel code, 1311K rwdata, 2940K rodata, 1024K init, 860K bss, 25384K reserved, 65536K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] ftrace: allocating 31910 entries in 63 pages
[ 0.000000] ftrace: allocated 63 pages with 6 groups
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] Rude variant of Tasks RCU enabled.
[ 0.000000] Tracing variant of Tasks RCU enabled.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] random: get_random_bytes called from start_kernel+0x3ac/0x580 with crng_init=0
[ 0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[ 0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[ 0.000020] Switching to timer-based delay loop, resolution 52ns
[ 0.000301] Console: colour dummy device 80x30
[ 0.000373] printk: console [tty1] enabled
[ 0.000428] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[ 0.000456] pid_max: default: 32768 minimum: 301
[ 0.000667] LSM: Security Framework initializing
[ 0.000903] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 0.000926] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 0.002481] Disabling memory control group subsystem
[ 0.002597] CPU: Testing write buffer coherency: ok
[ 0.003074] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.004292] Setting up static identity map for 0x100000 - 0x10003c
[ 0.004476] rcu: Hierarchical SRCU implementation.
[ 0.005379] smp: Bringing up secondary CPUs ...
[ 0.006526] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.007798] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[ 0.009001] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[ 0.009158] smp: Brought up 1 node, 4 CPUs
[ 0.009180] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[ 0.009192] CPU: All CPU(s) started in HYP mode.
[ 0.009203] CPU: Virtualization extensions available.
[ 0.010234] devtmpfs: initialized
[ 0.027929] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[ 0.028169] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.028198] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[ 0.031404] pinctrl core: initialized pinctrl subsystem
[ 0.032530] NET: Registered protocol family 16
[ 0.036773] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[ 0.042473] audit: initializing netlink subsys (disabled)
[ 0.042784] audit: type=2000 audit(0.040:1): state=initialized audit_enabled=0 res=1
[ 0.043373] thermal_sys: Registered thermal governor 'step_wise'
[ 0.044531] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[ 0.044546] hw-breakpoint: maximum watchpoint size is 8 bytes.
[ 0.044811] Serial: AMBA PL011 UART driver
[ 0.063305] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[ 0.080115] raspberrypi-firmware soc:firmware: Attached to firmware from 2021-02-25T12:12:09, variant start
[ 0.090126] raspberrypi-firmware soc:firmware: Firmware hash is 564e5f9b852b23a330b1764bcf0b2d022a20afd0
[ 0.139232] bcm2835-dma 3f007000.dma: DMA legacy API manager, dmachans=0x1
[ 0.141707] SCSI subsystem initialized
[ 0.141968] usbcore: registered new interface driver usbfs
[ 0.142032] usbcore: registered new interface driver hub
[ 0.142103] usbcore: registered new device driver usb
[ 0.144218] clocksource: Switched to clocksource arch_sys_counter
[ 1.920799] VFS: Disk quotas dquot_6.6.0
[ 1.920915] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 1.921117] FS-Cache: Loaded
[ 1.921385] CacheFiles: Loaded
[ 1.932090] NET: Registered protocol family 2
[ 1.933067] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
[ 1.933125] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
[ 1.933340] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 1.933533] TCP: Hash tables configured (established 8192 bind 8192)
[ 1.933706] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 1.933763] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 1.934323] NET: Registered protocol family 1
[ 1.935136] RPC: Registered named UNIX socket transport module.
[ 1.935149] RPC: Registered udp transport module.
[ 1.935161] RPC: Registered tcp transport module.
[ 1.935173] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 1.936991] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[ 1.940755] Initialise system trusted keyrings
[ 1.941021] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[ 1.950610] zbud: loaded
[ 1.952683] FS-Cache: Netfs 'nfs' registered for caching
[ 1.953532] NFS: Registering the id_resolver key type
[ 1.953583] Key type id_resolver registered
[ 1.953596] Key type id_legacy registered
[ 1.953761] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 1.955020] Key type asymmetric registered
[ 1.955035] Asymmetric key parser 'x509' registered
[ 1.955104] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[ 1.955118] io scheduler mq-deadline registered
[ 1.955131] io scheduler kyber registered
[ 1.958483] bcm2708_fb soc:fb: FB found 1 display(s)
[ 1.965907] Console: switching to colour frame buffer device 90x30
[ 1.971904] bcm2708_fb soc:fb: Registered framebuffer for display 0, size 720x480
[ 1.975412] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
[ 1.976173] bcm2835-aux-uart 3f215040.serial: there is not valid maps for state default
[ 1.977927] bcm2835-rng 3f104000.rng: hwrng registered
[ 1.978370] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
[ 1.979196] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[ 1.991482] brd: module loaded
[ 2.003450] loop: module loaded
[ 2.005112] Loading iSCSI transport class v2.0-870.
[ 2.006712] libphy: Fixed MDIO Bus: probed
[ 2.007019] usbcore: registered new interface driver lan78xx
[ 2.007087] usbcore: registered new interface driver smsc95xx
[ 2.007112] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[ 2.735288] Core Release: 2.80a
[ 2.735305] Setting default values for core params
[ 2.735334] Finished setting default values for core params
[ 2.935716] Using Buffer DMA mode
[ 2.935729] Periodic Transfer Interrupt Enhancement - disabled
[ 2.935741] Multiprocessor Interrupt Enhancement - disabled
[ 2.935755] OTG VER PARAM: 0, OTG VER FLAG: 0
[ 2.935782] Dedicated Tx FIFOs mode
[ 2.936367] WARN::dwc_otg_hcd_init:1074: FIQ DMA bounce buffers: virt = b7514000 dma = 0xf7514000 len=9024
[ 2.936397] FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
Interrupt/Control Split Transaction hack enabled
[ 2.936411] dwc_otg: Microframe scheduler enabled
[ 2.936482] WARN::hcd_init_fiq:457: FIQ on core 1
[ 2.936499] WARN::hcd_init_fiq:458: FIQ ASM at 807be568 length 36
[ 2.936516] WARN::hcd_init_fiq:497: MPHI regs_base at bb810000
[ 2.936538] dwc_otg 3f980000.usb: DWC OTG Controller
[ 2.936575] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[ 2.936622] dwc_otg 3f980000.usb: irq 89, io mem 0x00000000
[ 2.936675] Init: Port Power? op_state=1
[ 2.936686] Init: Power Port (0)
[ 2.937058] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[ 2.937076] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.937092] usb usb1: Product: DWC OTG Controller
[ 2.937106] usb usb1: Manufacturer: Linux 5.10.17-v7+ dwc_otg_hcd
[ 2.937121] usb usb1: SerialNumber: 3f980000.usb
[ 2.937875] hub 1-0:1.0: USB hub found
[ 2.937941] hub 1-0:1.0: 1 port detected
[ 2.938989] dwc_otg: FIQ enabled
[ 2.939002] dwc_otg: NAK holdoff enabled
[ 2.939014] dwc_otg: FIQ split-transaction FSM enabled
[ 2.939031] Module dwc_common_port init
[ 2.939353] usbcore: registered new interface driver usb-storage
[ 2.939560] mousedev: PS/2 mouse device common for all mice
[ 2.940729] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[ 2.943620] sdhci: Secure Digital Host Controller Interface driver
[ 2.943633] sdhci: Copyright(c) Pierre Ossman
[ 2.944346] mmc-bcm2835 3f300000.mmcnr: could not get clk, deferring probe
[ 2.945021] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
[ 2.945254] sdhci-pltfm: SDHCI platform and OF driver helper
[ 2.947006] ledtrig-cpu: registered to indicate activity on CPUs
[ 2.947425] hid: raw HID events driver (C) Jiri Kosina
[ 2.947598] usbcore: registered new interface driver usbhid
[ 2.947611] usbhid: USB HID core driver
[ 2.952326] Initializing XFRM netlink socket
[ 2.952370] NET: Registered protocol family 17
[ 2.952521] Key type dns_resolver registered
[ 2.953326] Registering SWP/SWPB emulation handler
[ 2.953473] registered taskstats version 1
[ 2.953503] Loading compiled-in X.509 certificates
[ 2.954538] Key type ._fscrypt registered
[ 2.954551] Key type .fscrypt registered
[ 2.954564] Key type fscrypt-provisioning registered
[ 2.966109] uart-pl011 3f201000.serial: cts_event_workaround enabled
[ 2.966222] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 114, base_baud = 0) is a PL011 rev2
[ 2.968426] bcm2835-aux-uart 3f215040.serial: there is not valid maps for state default
[ 2.969065] printk: console [ttyS0] disabled
[ 2.969195] 3f215040.serial: ttyS0 at MMIO 0x3f215040 (irq = 86, base_baud = 50000000) is a 16550
[ 2.969445] printk: console [ttyS0] enabled
[ 2.970409] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
[ 2.972073] mmc-bcm2835 3f300000.mmcnr: mmc_debug:0 mmc_debug2:0
[ 2.972089] mmc-bcm2835 3f300000.mmcnr: DMA channel allocated
[ 2.998526] sdhost: log_buf @ (ptrval) (f7513000)
[ 3.037978] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[ 3.039639] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 3.041304] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 3.044396] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[ 3.047258] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[ 3.050282] of_cfs_init
[ 3.050528] of_cfs_init: OK
[ 3.051466] Waiting for root device PARTUUID=fddaa439-02...
[ 3.111077] random: fast init done
[ 3.133078] mmc1: new high speed SDIO card at address 0001
[ 3.135161] mmc0: host does not support reading read-only switch, assuming write-enable
[ 3.138876] mmc0: new high speed SDHC card at address aaaa
[ 3.139734] mmcblk0: mmc0:aaaa SC16G 14.8 GiB
[ 3.143249] mmcblk0: p1 p2
[ 3.154390] Indeed it is in host mode hprt0 = 00021501
[ 3.178706] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 3.178789] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[ 3.179624] devtmpfs: mounted
[ 3.216093] Freeing unused kernel memory: 1024K
[ 3.264710] Run /sbin/init as init process
[ 3.264722] with arguments:
[ 3.264733] /sbin/init
[ 3.264745] splash
[ 3.264756] with environment:
[ 3.264767] HOME=/
[ 3.264778] TERM=linux
[ 3.364280] usb 1-1: new high-speed USB device number 2 using dwc_otg
[ 3.364442] Indeed it is in host mode hprt0 = 00001101
[ 3.604650] usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
[ 3.604674] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 3.605498] hub 1-1:1.0: USB hub found
[ 3.605623] hub 1-1:1.0: 4 ports detected
[ 3.891071] systemd[1]: System time before build time, advancing clock.
[ 3.924279] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[ 4.044357] NET: Registered protocol family 10
[ 4.045809] Segment Routing with IPv6
[ 4.054666] usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
[ 4.054692] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 4.055528] hub 1-1.1:1.0: USB hub found
[ 4.055654] hub 1-1.1:1.0: 3 ports detected
[ 4.119443] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[ 4.120417] systemd[1]: Detected architecture arm.
[ 4.154368] usb 1-1.3: new full-speed USB device number 4 using dwc_otg
[ 4.178340] systemd[1]: Set hostname to <raspberrypi>.
[ 4.301607] usb 1-1.3: New USB device found, idVendor=413c, idProduct=8505, bcdDevice=11.19
[ 4.301632] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4.301648] usb 1-1.3: Product: Dell Universal Receiver
[ 4.301663] usb 1-1.3: Manufacturer: Dell
[ 4.310497] input: Dell Dell Universal Receiver as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:413C:8505.0001/input/input0
[ 4.375709] hid-generic 0003:413C:8505.0001: input,hidraw0: USB HID v1.11 Keyboard [Dell Dell Universal Receiver] on usb-3f980000.usb-1.3/input0
[ 4.387397] input: Dell Dell Universal Receiver Mouse as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.1/0003:413C:8505.0002/input/input1
[ 4.387773] usb 1-1.1.2: new full-speed USB device number 5 using dwc_otg
[ 4.388505] input: Dell Dell Universal Receiver Consumer Control as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.1/0003:413C:8505.0002/input/input2
[ 4.464726] input: Dell Dell Universal Receiver System Control as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.1/0003:413C:8505.0002/input/input3
[ 4.465095] hid-generic 0003:413C:8505.0002: input,hidraw1: USB HID v1.11 Mouse [Dell Dell Universal Receiver] on usb-3f980000.usb-1.3/input1
[ 4.472203] hid-generic 0003:413C:8505.0003: hiddev96,hidraw2: USB HID v1.11 Device [Dell Dell Universal Receiver] on usb-3f980000.usb-1.3/input2
[ 4.552052] usb 1-1.1.2: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
[ 4.552078] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4.552095] usb 1-1.1.2: Product: TI CC2531 USB CDC
[ 4.552111] usb 1-1.1.2: Manufacturer: Texas Instruments
[ 4.552126] usb 1-1.1.2: SerialNumber: __0X00124B001938618A
[ 4.854290] usb 1-1.1.1: new high-speed USB device number 6 using dwc_otg
[ 4.984844] usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800, bcdDevice= 3.00
[ 4.984868] usb 1-1.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 5.010008] systemd[1]: Configuration file /etc/systemd/system/hoobs.service is marked executable. Please remove executable permission bits. Proceeding anyway.
[ 5.149712] random: systemd: uninitialized urandom read (16 bytes read)
[ 5.169559] random: systemd: uninitialized urandom read (16 bytes read)
[ 5.170415] systemd[1]: Listening on Journal Audit Socket.
[ 5.170730] random: systemd: uninitialized urandom read (16 bytes read)
[ 5.171541] systemd[1]: Listening on fsck to fsckd communication Socket.
[ 5.175588] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[ 5.177374] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ 5.177858] systemd[1]: Listening on initctl Compatibility Named Pipe.
[ 5.178988] systemd[1]: Listening on Journal Socket.
[ 5.249857] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): No External EEPROM. Setting MAC Speed
[ 5.252612] libphy: lan78xx-mdiobus: probed
[ 5.301296] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): int urb period 64
[ 5.335407] i2c /dev entries driver
[ 5.912595] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 6.045724] systemd-journald[114]: Received request to flush runtime journal from PID 1
[ 6.985177] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[ 6.988760] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[ 6.988787] [vc_sm_connected_init]: start
[ 6.996765] mc: Linux media interface: v0.10
[ 7.000211] [vc_sm_connected_init]: installed successfully
[ 7.066651] videodev: Linux video capture interface: v2.00
[ 7.103059] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[ 7.108673] bcm2835_audio bcm2835_audio: card created with 8 channels
[ 7.112975] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[ 7.117039] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[ 7.129668] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[ 7.136879] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[ 7.146348] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
[ 7.175306] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[ 7.175363] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[ 7.179242] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[ 7.179293] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[ 7.185965] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[ 7.186017] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[ 7.237018] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13
[ 7.274779] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14
[ 7.287223] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15
[ 7.287699] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16
[ 7.287734] bcm2835-isp bcm2835-isp: Register output node 0 with media controller
[ 7.287764] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
[ 7.287788] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
[ 7.287812] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
[ 7.288136] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
[ 7.507237] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 7.717165] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 7.824635] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 7.844882] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 7.847651] usbcore: registered new interface driver brcmfmac
[ 7.891026] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt failed with error -2
[ 8.003561] cdc_acm 1-1.1.2:1.0: ttyACM0: USB ACM device
[ 8.025294] usbcore: registered new interface driver cdc_acm
[ 8.025316] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 8.127942] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 8.138222] random: crng init done
[ 8.138240] random: 7 urandom warning(s) missed due to ratelimiting
[ 8.143245] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Jan 4 2021 19:56:29 version 7.45.229 (617f1f5 CY) FWID 01-2dbd9d2e
[ 10.889145] 8021q: 802.1Q VLAN Support v1.8
[ 11.334512] Adding 102396k swap on /var/swap. Priority:-2 extents:1 across:102396k SSFS
[ 11.642561] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[ 12.115894] 8021q: adding VLAN 0 to HW filter on device eth0
[ 17.227211] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 18.504578] fuse: init (API version 7.32)
Re: No Zigbee2mqtt on the Hardware list
Sorry my bad/mistake. Did not research what it actually was, and assumed some kind of USB stick.
What I found is that Hoobs is IP based, so Hoobs has nothing to do with some USB-ports, am I correct?
Was it so that when Hoobs was de-installed that zigbee2mqtt was working as it should?
This was present in the output of dmesg
Is there any reference to USB in that file?
Did you try adding the user pi to the group 'dialout', just to find out if Hoobs might remove the 'dialout' group.
You can find out if user pi belong to 'dialout' by
If not add pi to 'dialout' by
Yo be sure that the zigbee stick is working fine.
Pull zigbeestick and
Put in the (not working) zigbeestick and
Is that output the same as before? And test if the port is still writable.
Somewhere there should be a file 'config.json' probably
Is in that file any reference to USB?
I also saw that on the Hoobs image in /home there is 1 user: hoobs and that user belongs to group dialout.
Do you have besides user pi an user hoobs, and belongs that user to group 'dialout'?
What I found is that Hoobs is IP based, so Hoobs has nothing to do with some USB-ports, am I correct?
Was it so that when Hoobs was de-installed that zigbee2mqtt was working as it should?
This was present in the output of dmesg
Code: Select all
[ 5.010008] systemd[1]: Configuration file /etc/systemd/system/hoobs.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Did you try adding the user pi to the group 'dialout', just to find out if Hoobs might remove the 'dialout' group.
You can find out if user pi belong to 'dialout' by
Code: Select all
id
Code: Select all
sudo usermod -a -G dialout pi
Pull zigbeestick and
Code: Select all
sudo dmesg -C
Code: Select all
dmesg
Code: Select all
test -w /dev/ttyACM0 && echo success || echo failure
Code: Select all
~/.hoobs/etc/config.json
I also saw that on the Hoobs image in /home there is 1 user: hoobs and that user belongs to group dialout.
Do you have besides user pi an user hoobs, and belongs that user to group 'dialout'?
-
- Posts: 20
- Joined: Thursday 06 August 2020 14:20
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2020.2
- Location: Prague
- Contact:
Re: No Zigbee2mqtt on the Hardware list
Okay okay, too many infoEddyG wrote: ↑Thursday 18 March 2021 10:58 Sorry my bad/mistake. Did not research what it actually was, and assumed some kind of USB stick.
What I found is that Hoobs is IP based, so Hoobs has nothing to do with some USB-ports, am I correct?
Was it so that when Hoobs was de-installed that zigbee2mqtt was working as it should?
This was present in the output of dmesgIs there any reference to USB in that file?Code: Select all
[ 5.010008] systemd[1]: Configuration file /etc/systemd/system/hoobs.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Did you try adding the user pi to the group 'dialout', just to find out if Hoobs might remove the 'dialout' group.
You can find out if user pi belong to 'dialout' byIf not add pi to 'dialout' byCode: Select all
id
Yo be sure that the zigbee stick is working fine.Code: Select all
sudo usermod -a -G dialout pi
Pull zigbeestick andPut in the (not working) zigbeestick andCode: Select all
sudo dmesg -C
Is that output the same as before? And test if the port is still writable.Code: Select all
dmesg
Somewhere there should be a file 'config.json' probablyCode: Select all
test -w /dev/ttyACM0 && echo success || echo failure
Is in that file any reference to USB?Code: Select all
~/.hoobs/etc/config.json
I also saw that on the Hoobs image in /home there is 1 user: hoobs and that user belongs to group dialout.
Do you have besides user pi an user hoobs, and belongs that user to group 'dialout'?

So, I will go one by one.
Hoobs should have nothing to do with USB.
Not "de-installed". In previous installations (by installation I mean installing debian and mosquitto, zigbee2mqtt, and Domoticz) everything was fine. I found zigbee2mqtt in Hardware of Domoticz and I was able to find my zigbee devices. This is the first time I am trying with Hoobs, before I had Homebridge. (Hoobs is based on Homebridge but gives more control and better interface and blah blah blah)
"Is there any reference to USB in that file?" – I am sorry, I don't get in what file you are referring to

Did you try adding the user pi to the group 'dialout', just to find out if Hoobs might remove the 'dialout' group.
You can find out if user pi belong to 'dialout' by Again, I don't know what is the dialout group, but running id I get:
Code: Select all
uid=1000(pi) gid=1000(pi) groups=1000(pi),4(adm),20(dialout),24(cdrom),27(sudo),29(audio),44(video),46(plugdev),60(games),100(users),105(input),109(netdev),112(bluetooth),117(lpadmin),997(gpio),998(i2c),999(spi)
If you mean, to unplug the zigbee stick — run sudo dmesg -C — Plug it again — run dmesg. I did it:
Code: Select all
pi@raspberrypi:~ $ sudo dmesg -C
pi@raspberrypi:~ $ dmesg
[ 1374.251348] usb 1-1.1.2: new full-speed USB device number 7 using dwc_otg
[ 1374.421724] usb 1-1.1.2: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
[ 1374.421741] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1374.421749] usb 1-1.1.2: Product: TI CC2531 USB CDC
[ 1374.421756] usb 1-1.1.2: Manufacturer: Texas Instruments
[ 1374.421763] usb 1-1.1.2: SerialNumber: __0X00124B001938618A
[ 1374.424340] cdc_acm 1-1.1.2:1.0: ttyACM0: USB ACM device
pi@raspberrypi:~ $ test -w /dev/ttyACM0 && echo success || echo failure
success
Now the interesting part. I went to look for the file but the folder hoobs is empty (???) This doesn't look correct right?
I feel I will redo the whole thing from zero. Stop after Domoticz installation and check if I see "zigbee2mqtt". If I see it, I will set up my devices and then I will continue with Hoobs installation. Sounds correct?
Re: No Zigbee2mqtt on the Hardware list
Yes, that might be a good Idea.
-
- Posts: 744
- Joined: Saturday 30 May 2015 22:40
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Contact:
Re: No Zigbee2mqtt on the Hardware list
My assumption, which i still have, is that this Hoobs software claims the USB device and therefore z2m had no access to it anymore.063405 wrote: ...
Hoobs should have nothing to do with USB.
...
Re: No Zigbee2mqtt on the Hardware list
That was my idea too, so I looked into the image of Hoobs, but could find any trace of that in the image, but still Hoobs could.
-
- Posts: 20
- Joined: Thursday 06 August 2020 14:20
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2020.2
- Location: Prague
- Contact:
Re: No Zigbee2mqtt on the Hardware list
So, finally I reinstalled everything... and for some reason, everything is working!
Domoticz, Homebridge, Hoobs, everything.
A bit frustrating not to know what was the issue, but still I am happy!
Really thank you guys for your time, support and patience!
Domoticz, Homebridge, Hoobs, everything.
A bit frustrating not to know what was the issue, but still I am happy!
Really thank you guys for your time, support and patience!
Who is online
Users browsing this forum: No registered users and 1 guest