I can’t seem to find my Homebridge v2 devices in the Home app!
Homebridge is installed on a Raspberry Pi, as well as the web GUI and the homebridge-smartthings-v2 plugin. The Homebridge app is installed in the Smartthings app on my iPhone and I selected two devices in Homebridge and saved.
How do I then see these two devices in the Home app so I can add them there? Do I need to add something else to the config.json file?
Here is the daemon.log file:
pi#raspberrypi:~ $ tail -f daemon.log
Jan 8 14:34:41 raspberrypi rngd[322]: stats: FIPS tests speed: (min=4.682; avg=6.870; max=7.093)Mibits/s
Jan 8 14:34:41 raspberrypi rngd[322]: stats: Lowest ready-buffers level: 2
Jan 8 14:34:41 raspberrypi rngd[322]: stats: Entropy starvations: 0
Jan 8 14:34:41 raspberrypi rngd[322]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
Jan 8 14:49:19 raspberrypi systemd[1]: Stopping Homebridge...
Jan 8 14:49:19 raspberrypi homebridge[15987]: [1/8/2020, 2:49:19 PM] Got SIGTERM, shutting down Homebridge...
Jan 8 14:49:24 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=143/n/a
Jan 8 14:49:24 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
Jan 8 14:49:24 raspberrypi systemd[1]: Stopped Homebridge.
Jan 8 14:50:01 raspberrypi systemd[1]: Started Homebridge.
Jan 8 14:50:10 raspberrypi homebridge[16635]: [1/8/2020, 2:50:10 PM] Loaded config.json with 0 accessories and 3 platforms.
Jan 8 14:50:10 raspberrypi homebridge[16635]: [1/8/2020, 2:50:10 PM] ---
Jan 8 14:50:10 raspberrypi homebridge[16635]: [1/8/2020, 2:50:10 PM] Loaded plugin: homebridge-config-ui-x
Jan 8 14:50:10 raspberrypi homebridge[16635]: [1/8/2020, 2:50:10 PM] Registering platform 'homebridge-config-ui-x.config'
Jan 8 14:50:10 raspberrypi homebridge[16635]: [1/8/2020, 2:50:10 PM] ---
Jan 8 14:50:13 raspberrypi homebridge[16635]: [1/8/2020, 2:50:13 PM] Loaded plugin: homebridge-ring
Jan 8 14:50:13 raspberrypi homebridge[16635]: [1/8/2020, 2:50:13 PM] Registering platform 'homebridge-ring.Ring'
Jan 8 14:50:13 raspberrypi homebridge[16635]: [1/8/2020, 2:50:13 PM] ---
Jan 8 14:50:14 raspberrypi homebridge[16635]: [1/8/2020, 2:50:14 PM] Loaded plugin: homebridge-smartthings-v2
Jan 8 14:50:14 raspberrypi homebridge[16635]: [1/8/2020, 2:50:14 PM] Registering platform 'homebridge-smartthings-v2.SmartThings-v2'
Jan 8 14:50:14 raspberrypi homebridge[16635]: [1/8/2020, 2:50:14 PM] ---
Jan 8 14:50:15 raspberrypi homebridge[16635]: [1/8/2020, 2:50:15 PM] Loading 3 platforms...
Jan 8 14:50:15 raspberrypi homebridge[16635]: [1/8/2020, 2:50:15 PM] [Config] Initializing config platform...
Jan 8 14:50:15 raspberrypi homebridge[16635]: [1/8/2020, 2:50:15 PM] [Config] Spawning homebridge-config-ui-x with PID 16672
Jan 8 14:50:15 raspberrypi homebridge[16635]: [1/8/2020, 2:50:15 PM] [Ring] Initializing Ring platform...
Jan 8 14:50:15 raspberrypi homebridge[16635]: [1/8/2020, 2:50:15 PM] [SmartThings-v2] Initializing SmartThings-v2 platform...
Jan 8 14:50:15 raspberrypi homebridge[16635]: INFO: Homebridge Version: 2.4
Jan 8 14:50:15 raspberrypi homebridge[16635]: INFO: SmartThings-v2 Plugin Version: 2.1.5
Jan 8 14:50:15 raspberrypi homebridge[16635]: INFO: Checking Package Version for Updates...
Jan 8 14:50:15 raspberrypi homebridge[16635]: [1/8/2020, 2:50:15 PM] Loading 0 accessories...
Jan 8 14:50:15 raspberrypi homebridge[16635]: INFO: Configure Cached Accessory: Security Alarm, UUID: c3f254e2-85d5-4602-9813-25452e80e35b
Jan 8 14:50:15 raspberrypi homebridge[16635]: Setup Payload:
Jan 8 14:50:15 raspberrypi homebridge[16635]: X-HM://0023IX8JIMK71
Jan 8 14:50:15 raspberrypi homebridge[16635]: Scan this code with your HomeKit app on your iOS device to pair with Homebridge:
...
Jan 8 14:50:15 raspberrypi homebridge[16635]: Or enter this code with your HomeKit app on your iOS device to pair with Homebridge:
Jan 8 14:50:15 raspberrypi homebridge[16635]:
Jan 8 14:50:15 raspberrypi homebridge[16635]: ┌────────────┐
Jan 8 14:50:15 raspberrypi homebridge[16635]: │ 033-44-254 │
Jan 8 14:50:15 raspberrypi homebridge[16635]: └────────────┘
Jan 8 14:50:15 raspberrypi homebridge[16635]:
Jan 8 14:50:15 raspberrypi homebridge[16635]: INFO: Fetching SmartThings-v2 Devices. NOTICE: This may take a moment if you have a large number of device data is being loaded!
Jan 8 14:50:15 raspberrypi homebridge[16635]: 2020-01-08T20:50:15.762Z '[FileStreamRotator] Failed to store log audit at:' 'logaudit.json' 'Error:' { Error: EACCES: permission denied, open 'logaudit.json'
Jan 8 14:50:15 raspberrypi homebridge[16635]: at Object.openSync (fs.js:439:3)
Jan 8 14:50:15 raspberrypi homebridge[16635]: at Object.writeFileSync (fs.js:1190:35)
Jan 8 14:50:15 raspberrypi homebridge[16635]: at Object.FileStreamRotator.writeAuditLog (/usr/local/lib/node_modules/homebridge-smartthings-v2/node_modules/file-stream-rotator/FileStreamRotator.js:246:12)
Jan 8 14:50:15 raspberrypi homebridge[16635]: at Object.FileStreamRotator.addLogToAudit (/usr/local/lib/node_modules/homebridge-smartthings-v2/node_modules/file-stream-rotator/FileStreamRotator.js:320:27)
Jan 8 14:50:15 raspberrypi homebridge[16635]: at EventEmitter.<anonymous> (/usr/local/lib/node_modules/homebridge-smartthings-v2/node_modules/file-stream-rotator/FileStreamRotator.js:437:36)
Jan 8 14:50:15 raspberrypi homebridge[16635]: at EventEmitter.emit (events.js:194:15)
Jan 8 14:50:15 raspberrypi homebridge[16635]: at /usr/local/lib/node_modules/homebridge-smartthings-v2/node_modules/file-stream-rotator/FileStreamRotator.js:483:20
Jan 8 14:50:15 raspberrypi homebridge[16635]: at process._tickCallback (internal/process/next_tick.js:61:11)
Jan 8 14:50:15 raspberrypi homebridge[16635]: at Function.Module.runMain (internal/modules/cjs/loader.js:745:11)
Jan 8 14:50:15 raspberrypi homebridge[16635]: at startup (internal/bootstrap/node.js:283:19)
Jan 8 14:50:15 raspberrypi homebridge[16635]: errno: -13,
Jan 8 14:50:15 raspberrypi homebridge[16635]: syscall: 'open',
Jan 8 14:50:15 raspberrypi homebridge[16635]: code: 'EACCES',
Jan 8 14:50:15 raspberrypi homebridge[16635]: path: 'logaudit.json' }
Jan 8 14:50:15 raspberrypi homebridge[16635]: New LogFile Created | newFilename: /var/lib/homebridge/homebridge-smartthings-v2-2020-01-08-14.log
Jan 8 14:50:15 raspberrypi homebridge[16635]: [1/8/2020, 2:50:15 PM] Homebridge is running on port 51826.
Jan 8 14:50:17 raspberrypi homebridge[16635]: NOTICE: setting temperature_unit to (F)
Jan 8 14:50:17 raspberrypi homebridge[16635]: NOTICE: Updating Global Values | HubIP: 192.168.1.10 | UseLocal: true
Jan 8 14:50:17 raspberrypi homebridge[16635]: WARN: Devices to Remove: (0)
Jan 8 14:50:17 raspberrypi homebridge[16635]: INFO: Devices to Update: (1)
Jan 8 14:50:17 raspberrypi homebridge[16635]: GOOD: Devices to Create: (0)
Jan 8 14:50:17 raspberrypi homebridge[16635]: INFO: Loading Existing Device (Security Alarm) | (alarmSystemStatus_9da00d0e-6ae7-4a73-b1f7-10433f8f7a58)
Jan 8 14:50:17 raspberrypi homebridge[16635]: ALERT: Total Initialization Time: (2 seconds)
Jan 8 14:50:17 raspberrypi homebridge[16635]: NOTICE: Unknown Capabilities: []
Jan 8 14:50:17 raspberrypi homebridge[16635]: INFO: SmartThings DeviceCache Size: (1)
Jan 8 14:50:17 raspberrypi homebridge[16635]: INFO: WebServer Initiated...
Jan 8 14:50:17 raspberrypi homebridge[16635]: INFO: Sending StartDirect Request to SmartThings | SendToLocalHub: (true)
Jan 8 14:50:17 raspberrypi homebridge[16635]: INFO: Direct Connect Active | Listening at 192.168.1.80:8000
Jan 8 14:50:17 raspberrypi homebridge[16635]: INFO: SmartThings-v2 Hub Communication Established
Jan 8 14:50:17 raspberrypi homebridge[16635]: INFO: SmartThings-v2 Hub Communication Established
Jan 8 14:50:17 raspberrypi homebridge[16635]: INFO: SmartThings-v2 Hub Communication Established
Jan 8 14:50:18 raspberrypi homebridge[16635]: INFO: SmartThings-v2 Hub Communication Established
Jan 8 14:50:18 raspberrypi homebridge[16635]: [1/8/2020, 2:50:18 PM] [Ring] Configuring 1 cameras and 1 devices for location "Shavano Park" - locationId: ae6fb12d-d377-431c-4d14-3c458a7be038
Jan 8 14:50:18 raspberrypi homebridge[16635]: [1/8/2020, 2:50:18 PM] [Ring] Adding new accessory doorbell_v4 Front Door
Jan 8 14:50:18 raspberrypi homebridge[16635]: [1/8/2020, 2:50:18 PM] Front Door is running on port 35019.
Jan 8 14:50:18 raspberrypi homebridge[16635]: [1/8/2020, 2:50:18 PM] Please add [Front Door] manually in Home app. Setup Code: 033-44-254
Jan 8 14:50:24 raspberrypi homebridge[16635]: INFO: INFO: Your plugin version is up-to-date
Jan 8 14:50:24 raspberrypi homebridge[16635]: NOTICE: Sending Plugin Status to SmartThings | UpdateAvailable: false
[Config]Homebridge Config UI X v4.6.7 is listening on :: port 8080
Update:
Seems I had an incorrect token to talk between Home and Homebridge. I also had to clear the Homebridge cache by deleting everything in the persist and accessories directories. All devices are now in the Accessories tab of the Homebridge web GUI. But, now I see some of my devices in Home but not all of them, my Kwikset door locks do not show up. And, my two light switches are not active even though they show up in the Home. Is there some trick I am missing?
Related
After trying for quite a long time to create a udev rule to automatically mount a USB-Stick to a directory, I have to realize that I can't get any further without help.
Here is my udev-rule stored at /etc/udev/rules.d/60-usbspecialmount.rules
ACTION=="add", SUBSYSTEMS=="usb", KERNEL=="sd?", ATTRS{serial}=="3f980000.usb", RUN+="/bin/mount /dev/%k /media/securitycam
ACTION=="remove", SUBSYSTEMS=="usb", KERNEL=="sd?", RUN+="/bin/umount /dev/%k"
after restarting the udev service with:
sudo service udev restart
and plugging in the USB-Device, the SYSLOG-File says following:
Sep 13 05:47:17 raspberrypi systemd[1]: Stopping Rule-based Manager for Device Events and Files...
Sep 13 05:47:17 raspberrypi systemd[1]: systemd-udevd.service: Succeeded.
Sep 13 05:47:17 raspberrypi systemd[1]: Stopped Rule-based Manager for Device Events and Files.
Sep 13 05:47:17 raspberrypi systemd[1]: systemd-udevd.service: Consumed 1.424s CPU time.
Sep 13 05:47:17 raspberrypi systemd[1]: Starting Rule-based Manager for Device Events and Files...
Sep 13 05:47:17 raspberrypi systemd[1]: Started Rule-based Manager for Device Events and Files.
Sep 13 05:48:04 raspberrypi kernel: [ 6571.111154] usb 1-1.4: new high-speed USB device number 25 using dwc_otg
Sep 13 05:48:04 raspberrypi kernel: [ 6571.242509] usb 1-1.4: New USB device found, idVendor=090c, idProduct=2000, bcdDevice=11.00
Sep 13 05:48:04 raspberrypi kernel: [ 6571.242543] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Sep 13 05:48:04 raspberrypi kernel: [ 6571.242563] usb 1-1.4: Product: Flash Disk
Sep 13 05:48:04 raspberrypi kernel: [ 6571.242581] usb 1-1.4: Manufacturer: USB
Sep 13 05:48:04 raspberrypi kernel: [ 6571.243643] usb-storage 1-1.4:1.0: USB Mass Storage device detected
Sep 13 05:48:04 raspberrypi kernel: [ 6571.244623] usb-storage 1-1.4:1.0: Quirks match for vid 090c pid 2000: 800000
Sep 13 05:48:04 raspberrypi kernel: [ 6571.244816] scsi host0: usb-storage 1-1.4:1.0
Sep 13 05:48:04 raspberrypi mtp-probe: checking bus 1, device 25: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4"
Sep 13 05:48:04 raspberrypi mtp-probe: bus: 1, device: 25 was not an MTP device
Sep 13 05:48:04 raspberrypi mtp-probe: checking bus 1, device 25: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4"
Sep 13 05:48:04 raspberrypi mtp-probe: bus: 1, device: 25 was not an MTP device
Sep 13 05:48:05 raspberrypi kernel: [ 6572.491851] scsi 0:0:0:0: Direct-Access USB Flash Disk 1100 PQ: 0 ANSI: 6
Sep 13 05:48:05 raspberrypi kernel: [ 6572.492586] sd 0:0:0:0: Attached scsi generic sg0 type 0
Sep 13 05:48:05 raspberrypi kernel: [ 6572.493253] sd 0:0:0:0: [sda] 61736960 512-byte logical blocks: (31.6 GB/29.4 GiB)
Sep 13 05:48:05 raspberrypi kernel: [ 6572.493639] sd 0:0:0:0: [sda] Write Protect is off
Sep 13 05:48:05 raspberrypi kernel: [ 6572.493663] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
Sep 13 05:48:05 raspberrypi kernel: [ 6572.494095] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 13 05:48:05 raspberrypi kernel: [ 6572.498538] sda: sda1
Sep 13 05:48:05 raspberrypi kernel: [ 6572.500805] sd 0:0:0:0: [sda] Attached SCSI removable disk
Sep 13 05:48:06 raspberrypi kernel: [ 6572.599846] F2FS-fs (sda): Magic Mismatch, valid(0xf2f52010) - read(0x0)
Sep 13 05:48:06 raspberrypi kernel: [ 6572.599878] F2FS-fs (sda): Can't find valid F2FS filesystem in 1th superblock
Sep 13 05:48:06 raspberrypi kernel: [ 6572.600343] F2FS-fs (sda): Magic Mismatch, valid(0xf2f52010) - read(0x0)
Sep 13 05:48:06 raspberrypi kernel: [ 6572.600358] F2FS-fs (sda): Can't find valid F2FS filesystem in 2th superblock
Sep 13 05:48:06 raspberrypi systemd-udevd[3817]: sda: Process '/bin/mount /dev/sda /media/securitycam' failed with exit code 32.
Sep 13 05:48:06 raspberrypi usbmount[3825]: USAGE: /dev/sda:PTUUID="7f81bc38"PTTYPE="dos"
Sep 13 05:48:06 raspberrypi usbmount[3825]: /dev/sda does not contain a filesystem or disklabel
Sep 13 05:48:06 raspberrypi systemd-udevd[3817]: sda: Process '/usr/share/usbmount/usbmount add' failed with exit code 1.
Sep 13 05:48:06 raspberrypi usbmount[3845]: USAGE: filesystem
Sep 13 05:48:06 raspberrypi usbmount[3845]: executing command: mount -tvfat -osync,noexec,nodev,noatime,nodiratime,uid=jonas,gid=users,dmask=0002,fmask=0003 /dev/sda1 /media/usb0
Sep 13 05:48:06 raspberrypi kernel: [ 6573.003468] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Sep 13 05:48:06 raspberrypi usbmount[3845]: executing command: run-parts /etc/usbmount/mount.d
Here is what fdisk -l says about my USB-Device:
Disk /dev/sda: 29.44 GiB, 31609323520 bytes, 61736960 sectors
Disk model: Flash Disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x7f81bc38
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 224 61736959 61736736 29.4G c W95 FAT32 (LBA)
My idea is that it has something to do with the Devicename. In syslog it says:
usbmount[3825]: /dev/sda does not contain a filesystem or disklabel
so maybe usbmount should look for /dev/sda1 which includes a filesystem
as you can see with the command:
sudo blkid -p /dev/sda1
/dev/sda1: LABEL="PHILIPS UFD" UUID="863A-2B54" VERSION="FAT32" BLOCK_SIZE="512" TYPE="vfat" USAGE="filesystem" PART_ENTRY_SCHEME="dos" PART_ENTRY_UUID="7f81bc38-01" PART_ENTRY_TYPE="0xc" PART_ENTRY_FLAGS="0x80" PART_ENTRY_NUMBER="1" PART_ENTRY_OFFSET="224" PART_ENTRY_SIZE="61736736" PART_ENTRY_DISK="8:0"
Regrettably the bash script /usr/share/usbmount/usbmount has a variable called: $DEVNAME when it processes the condition "add" from the udev-rule and this variable includes /dev/sda as you can see in the syslog-file.
Is there a possibility to change the variable name or is my solution approach completely wrong?
I tried to realize a WebRTC communication, a RPi with a webcam to stream, and can be seen on web browser on another computer, both under the same WIFI
*RPi:
Collect streaming data.
WebRTC server
*Another computer: see the streaming image on web browser through WebRTC
*I choose UV4L to have WebRTC function.
After installing UV4L (I used uv4l-uvc) and
set the /etc/systemd/system/uv4l_raspicam.service
[Unit]
Description=UV4L Raspicam
[Service]
Type=simple
ExecStart=/usr/bin/uv4l -f -k --sched-fifo --mem-lock --config-file=/etc/uv4l/uv4l-uvc.conf --driver=uvc --device-path=001:007 --driver-config-file=/etc/uv4l/uv4l-uvc.conf --server-option=--editable-config-file=/etc/uv4l/uv4l-uvc.conf
Restart=on-abnormal
LimitNOFILE=65536
[Install]
WantedBy=multi-user.target
then start the uv4l_raspicam service
sudo service uv4l_raspicam status
then check the status
● uv4l_raspicam.service - UV4L Raspicam
Loaded: loaded (/etc/systemd/system/uv4l_raspicam.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2022-06-20 17:05:24 CST; 55min ago
Main PID: 3922 (uv4l)
Tasks: 11 (limit: 1936)
CGroup: /system.slice/uv4l_raspicam.service
└─3922 /usr/bin/uv4l -f -k --sched-fifo --mem-lock --config-file=/etc/uv4l/uv4l-uvc.conf --driver=uvc --device-path=001:007 --driver-config-file=/etc/uv4l/uv4l-uvc.conf --server-option=--editable-config-file=/etc/uv4l/uv4l-uvc.conf
Jun 20 17:05:24 raspberrypi uv4l[3922]: <notice> [server] HTTP/HTTPS Streaming & WebRTC Signalling Server v1.1.130 built on Jan 16 2022
Jun 20 17:05:24 raspberrypi uv4l[3922]: <warning> [server] SSL is not enabled for the Streaming Server. Using unsecure HTTP.
Jun 20 17:05:24 raspberrypi uv4l[3922]: <notice> [core] Streaming Server loaded!
Jun 20 17:05:24 raspberrypi uv4l[3922]: <warning> [core] Cannot create /dev/video0 because file already exists
Jun 20 17:05:24 raspberrypi uv4l[3922]: <notice> [core] Registering device node /dev/video1
Jun 20 17:05:24 raspberrypi uv4l[3922]: <notice> [server] Web Streaming Server listening on port 8090
Jun 20 17:06:06 raspberrypi uv4l[3922]: <notice> [webrtc] WebRTC Renderer extension successfully loaded
Jun 20 17:06:06 raspberrypi uv4l[3922]: <notice> [server] WebRTC, Signalling Server and STUN Server extensions successfully loaded
Jun 20 17:06:06 raspberrypi uv4l[3922]: <notice> [webrtc] STUN server listening to 0.0.0.0:3478
It seems that the service works fine.
I then tried to access http://rpihostname:8090/stream
it worked. The streaming from my webcam(on RPi) works.
However, when I tried http://rpihostname:8090/stream/webrtc
after pressing "call" button it stucked and nothing happened... then checked on the status of uv4l_raspicam, it still showed
● uv4l_raspicam.service - UV4L Raspicam
Loaded: loaded (/etc/systemd/system/uv4l_raspicam.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2022-06-20 17:05:24 CST; 55min ago
Main PID: 3922 (uv4l)
Tasks: 11 (limit: 1936)
CGroup: /system.slice/uv4l_raspicam.service
└─3922 /usr/bin/uv4l -f -k --sched-fifo --mem-lock --config-file=/etc/uv4l/uv4l-uvc.conf --driver=uvc --device-path=001:007 --driver-config-file=/etc/uv4l/uv4l-uvc.conf --server-option=--editable-config-file=/etc/uv4l/uv4l-uvc.
Jun 20 17:05:24 raspberrypi uv4l[3922]: <notice> [server] HTTP/HTTPS Streaming & WebRTC Signalling Server v1.1.130 built on Jan 16 2022
Jun 20 17:05:24 raspberrypi uv4l[3922]: <warning> [server] SSL is not enabled for the Streaming Server. Using unsecure HTTP.
Jun 20 17:05:24 raspberrypi uv4l[3922]: <notice> [core] Streaming Server loaded!
Jun 20 17:05:24 raspberrypi uv4l[3922]: <warning> [core] Cannot create /dev/video0 because file already exists
Jun 20 17:05:24 raspberrypi uv4l[3922]: <notice> [core] Registering device node /dev/video1
Jun 20 17:05:24 raspberrypi uv4l[3922]: <notice> [server] Web Streaming Server listening on port 8090
Jun 20 17:06:06 raspberrypi uv4l[3922]: <notice> [webrtc] WebRTC Renderer extension successfully loaded
Jun 20 17:06:06 raspberrypi uv4l[3922]: <notice> [server] WebRTC, Signalling Server and STUN Server extensions successfully loaded
Jun 20 17:06:06 raspberrypi uv4l[3922]: <notice> [webrtc] STUN server listening to 0.0.0.0:3478
Any comments on this? Thanks in advance!
I need to configure the [TRM240 modem][1] to work with a Raspbian system. I followed the procedure reported in the answer [here][2], but the connection isn't working.
I attach some screenshots documenting the procedure and the commands that I issued.
First, look for connected modems:
pi#raspberrypi:~ $ mmcli -L
Found 1 modems:
/org/freedesktop/ModemManager1/Modem/0 [QUALCOMM INCORPORATED] QUECTEL Mobile Broadband Module
Check the unique modem found:
pi#raspberrypi:~ $ mmcli -m 0
/org/freedesktop/ModemManager1/Modem/0 (device id 'e308f44de689f834e8cbc5b2122a4ffca8ddd3f5')
-------------------------
Hardware | manufacturer: 'QUALCOMM INCORPORATED'
| model: 'QUECTEL Mobile Broadband Module'
| revision: 'EC21ECGAR06A04M1G'
| supported: 'gsm-umts
| lte
| gsm-umts, lte'
| current: 'gsm-umts, lte'
| equipment id: '864394040056931'
-------------------------
System | device: '/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2'
| drivers: 'option1, qmi_wwan'
| plugin: 'Generic'
| primary port: 'cdc-wdm0'
| ports: 'ttyUSB0 (qcdm), ttyUSB2 (at), cdc-wdm0 (qmi), wwan0 (net), ttyUSB3 (at)'
-------------------------
Numbers | own : 'unknown'
-------------------------
Status | lock: 'unknown'
| unlock retries: 'unknown'
| state: 'failed'
| failed reason: 'sim-missing'
| power state: 'unknown'
| access tech: 'unknown'
| signal quality: '0' (cached)
-------------------------
Modes | supported: 'allowed: 2g, 3g, 4g; preferred: none'
| current: 'allowed: any; preferred: none'
-------------------------
Bands | supported: 'unknown'
| current: 'unknown'
-------------------------
IP | supported: 'ipv4, ipv6, ipv4v6'
-------------------------
SIM | path: 'none'
-------------------------
Bearers | paths: 'none'
Here, the Status section leaves me a little bit puzzled, but I try to go on.
I tried the following command using different options for ifname: cdc-wdm0, ttyUSB2 and ttyUSB3. They all end up to the same result.
pi#raspberrypi:~ $ sudo nmcli c add type gsm ifname cdc-wdm0 con-name modem apn mobile.vodafone.it
Connection 'modem' (9c34027f-5df5-4fd6-9792-223e225dfd41) successfully added.
Check the connections and try to take up modem:
pi#raspberrypi:~ $ nmcli con
NAME UUID TYPE DEVICE
br-12ff13c2c4e0 26450e11-6671-47c2-91af-6bf96405921b bridge br-12ff13c2c4e0
br-acc4bdcbe6e7 440cfcc0-5318-4a9e-9259-3fb8700cf240 bridge br-acc4bdcbe6e7
docker0 8af67071-3cb2-4235-882f-1cc1f50fa7ca bridge docker0
modem 9c34027f-5df5-4fd6-9792-223e225dfd41 gsm --
Try to take up:
pi#raspberrypi:~ $ nmcli con up modem
Error: Connection activation failed: No suitable device found for this connection.
Status of service NetworkManager:
pi#raspberrypi:~ $ systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2020-08-21 07:46:57 UTC; 2h 35min ago
Docs: man:NetworkManager(8)
Main PID: 710 (NetworkManager)
Tasks: 3 (limit: 4915)
Memory: 13.8M
CPU: 3.862s
CGroup: /system.slice/NetworkManager.service
└─710 /usr/sbin/NetworkManager --no-daemon
Aug 21 07:48:53 raspberrypi NetworkManager[710]: <info> [1597996133.0883] device (veth6ffb100): link connected
Aug 21 08:14:11 raspberrypi NetworkManager[710]: <error> [1597997651.4341] audit: failed to open auditd socket: Protocol not supported
Aug 21 08:14:11 raspberrypi NetworkManager[710]: <info> [1597997651.4343] audit: op="device-managed" arg="managed:1" pid=11841 uid=0 result="success"
Aug 21 08:16:48 raspberrypi NetworkManager[710]: <info> [1597997808.9388] audit: op="device-autoconnect" arg="autoconnect:1" pid=12910 uid=1000 result="fail" reason="Not authorized to perform this operat
Aug 21 08:17:41 raspberrypi NetworkManager[710]: <info> [1597997861.0575] audit: op="connection-add-activate" pid=13286 uid=1000 result="fail" reason="gsm: GSM mobile broadband connection requires a 'gsm
Aug 21 08:25:25 raspberrypi NetworkManager[710]: <info> [1597998325.2594] audit: op="connection-add-activate" pid=16224 uid=1000 result="fail" reason="gsm: GSM mobile broadband connection requires a 'gsm
Aug 21 10:06:31 raspberrypi NetworkManager[710]: <info> [1598004391.9223] audit: op="connection-activate" uuid="06583333-e03e-431f-9376-94c38b6b607d" name="modem" result="fail" reason="No suitable device
Aug 21 10:19:24 raspberrypi NetworkManager[710]: <info> [1598005164.3349] keyfile: add connection /etc/NetworkManager/system-connections/modem-9c34027f-5df5-4fd6-9792-223e225dfd41 (9c34027f-5df5-4fd6-979
Aug 21 10:19:24 raspberrypi NetworkManager[710]: <info> [1598005164.3386] audit: op="connection-add" uuid="9c34027f-5df5-4fd6-9792-223e225dfd41" name="modem" pid=27261 uid=0 result="success"
Aug 21 10:20:29 raspberrypi NetworkManager[710]: <info> [1598005229.6409] audit: op="connection-activate" uuid="06583333-e03e-431f-9376-94c38b6b607d" name="modem" result="fail" reason="No suitable device
lines 1-21/21 (END)
Here I see the error <error> [1597997651.4341] audit: failed to open auditd socket: Protocol not supported...
Status of service ModemManager (there are warnings, but not errors):
pi#raspberrypi:~ $ systemctl status ModemManager
● ModemManager.service - Modem Manager
Loaded: loaded (/lib/systemd/system/ModemManager.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2020-08-21 07:46:57 UTC; 2h 35min ago
Main PID: 712 (ModemManager)
Tasks: 5 (limit: 4915)
Memory: 8.7M
CPU: 4.123s
CGroup: /system.slice/ModemManager.service
├─712 /usr/sbin/ModemManager
└─884 /usr/lib/libqmi/qmi-proxy
Aug 21 07:47:19 raspberrypi ModemManager[712]: [/dev/cdc-wdm0] Registered 'nas' (version 1.25) client with ID '2'
Aug 21 07:47:20 raspberrypi ModemManager[712]: [/dev/cdc-wdm0] Allocating new client ID...
Aug 21 07:47:20 raspberrypi ModemManager[712]: [/dev/cdc-wdm0] Registered 'wms' (version 1.10) client with ID '1'
Aug 21 07:47:20 raspberrypi ModemManager[712]: [/dev/cdc-wdm0] Allocating new client ID...
Aug 21 07:47:20 raspberrypi ModemManager[712]: [/dev/cdc-wdm0] Registered 'uim' (version 1.46) client with ID '1'
Aug 21 07:47:20 raspberrypi ModemManager[712]: <warn> (ttyUSB2): port attributes not fully set
Aug 21 07:47:20 raspberrypi ModemManager[712]: <warn> couldn't load Supported Bands: 'QMI operation failed: Cannot send message: QMI service 'dms' version '1.1' required, got version '1.0''
Aug 21 07:47:20 raspberrypi ModemManager[712]: <warn> couldn't load Power State: 'QMI operation failed: Cannot send message: QMI service 'dms' version '1.1' required, got version '1.0''
Aug 21 07:47:55 raspberrypi ModemManager[712]: <warn> Modem couldn't be initialized: Couldn't check unlock status: Couldn't get SIM lock status after 6 retries
Aug 21 07:47:55 raspberrypi ModemManager[712]: <info> Modem: state changed (unknown -> failed)
System info:
pi#raspberrypi:~ $ uname -a
Linux raspberrypi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
pi#raspberrypi:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 9.13 (stretch)
Release: 9.13
Codename: stretch
It may be that the SIM is not working properly or the modem is not recognizing it.
This is what the output
-------------------------
Status | lock: 'unknown'
| unlock retries: 'unknown'
| state: 'failed'
| failed reason: 'sim-missing'
| power state: 'unknown'
| access tech: 'unknown'
| signal quality: '0' (cached)
-------------------------
points out.
Check this answer.
(I didn't find it before posting my question.)
BTW, I am trying to install OpenMediaVault on a Raspberry Pi 1, however, whenever I try and install OpenMediaVault on a Raspberry Pi 1, I get problems with the monit package, the FastCGI Process Manager and the openmediavault package too. Here is what happens with the package monit:
monit.service - LSB: service and resource monitoring daemon
Loaded: loaded (/etc/init.d/monit; generated)
Active: failed (Result: exit-code) Since Fri 2020-05-22 13:49:54 BST; 30min ago
Docs: man:systemd-sysv-generator(8)
May 22 13:49:54 raspberrypi systemd[1]: Starting LSB: service and resource monitoring daemon...
May 22 13:49:54 raspberrypi monit[4940]: Starting daemon monitor: monitSegmentation fault
May 22 13:49:54 raspberrypi monit[4940]: failed!
May 22 13:49:54 raspberrypi systemd[1]: monit.service: Control process exit, code=exited,
status=1/FAILURE
May 22 13:49:54 raspberrypi systemd[1]: monit.service: Failed with result 'exit-code'.
May 22 13:49:54 raspberrypi systemd[1]: Failed to start LSB: service and resource monitoring
daemon.
Here is what happens with the FastCGI Process Manager:
php7.3-fpm.service - The PHP 7.3 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.3-fpm.service; enabled; vendor preset: enabled)
Active: failed (Resul: signal) since Fri 2020-05-22 14:33:21 BST; 6min ago
Docs: man:php-fpm7.3(8)
Main PID: 416 (code=killed, signal=ILL)
May 22 14:33:15 raspberrypi systemd[1]: Starting The PHP 7.3 FastCGI Process Manager...
May 22 14:33:15 raspberrypi systemd[1]: php7.3-fpm.service: Main process exited, code=killed,
status=4/ILL
May 22 14:33:15 raspberrypi systemd[1]: php7.3-fpm.service: Failed with result 'signal'.
May 22 14:33:15 raspberrypi systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
And here is what happens with the package openmediavault:
dpkg: dependency problems prevent configuration of openmediavault:
openmediavault depends on monit; however
Package monit is not configured yet.
dpkg: error processing package openmediavault (--configure):
dependency problems - leaving unconfigured
Could anyone help with this problem?
I'm trying to install Plex media server on my raspberrypi zero w and i keep getting this error:
plexmediaserver.service - Plex Media Server for Linux
Loaded: loaded (/lib/systemd/system/plexmediaserver.service; enabled;
vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2018-09-06 18:22:09 UTC; 12s ago
Process: 1043 ExecStart=/bin/sh -c LD_LIBRARY_PATH=/usr/lib/plexmediaserver "/usr/lib/plexmediaserv
Process: 1039 ExecStartPre=/bin/sh -c /usr/bin/test -d "${PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR
Main PID: 1043 (code=exited, status=132)
Sep 06 18:22:04 raspberrypi systemd[1]: plexmediaserver.service: Unit entered failed state.
Sep 06 18:22:04 raspberrypi systemd[1]: plexmediaserver.service: Failed with result 'exit-code'.
Sep 06 18:22:09 raspberrypi systemd[1]: plexmediaserver.service: Service hold-off time over, scheduli
Sep 06 18:22:09 raspberrypi systemd[1]: Stopped Plex Media Server for Linux.
Sep 06 18:22:09 raspberrypi systemd[1]: plexmediaserver.service: Start request repeated too quickly.
Sep 06 18:22:09 raspberrypi systemd[1]: Failed to start Plex Media Server for Linux.
Sep 06 18:22:09 raspberrypi systemd[1]: plexmediaserver.service: Unit entered failed state.
Sep 06 18:22:09 raspberrypi systemd[1]: plexmediaserver.service: Failed with result 'exit-code'.
If anyone can help I'd really appreciate it, Thanks!
(btw I'm quite a noob when it comes to raspberry pi's)
As far as I know it is not supported anymore due to lots of API changes of Plex resulting in the discontinued support of ARM v61 (Pi Zero W has ARM v61) and only "supports" ARM v7 and v8 (v64)
See also: https://forums.plex.tv/t/pi-zero-w-problems/191899/7