Open jpm-canonical opened 5 months ago
Manually connection for gpio worked:
$ sudo matter-pi-gpio-commander.test-blink
GPIO: 4
GPIOCHIP: 4
Failed to request output line.
Permission denied
$ sudo snap connect matter-pi-gpio-commander:custom-gpio matter-pi-gpio-commander:custom-gpio-dev
$ sudo matter-pi-gpio-commander.test-blink
GPIO: 4
GPIOCHIP: 4
Setting GPIO 4 to Off
Setting GPIO 4 to On
Setting GPIO 4 to Off
Setting GPIO 4 to On
^C
Assertion file: https://pastebin.canonical.com/p/NpqPcyv3Jr/
The Custom GPIO interface doesn't auto connect on Ubuntu Core. See: https://forum.snapcraft.io/t/approval-and-auto-connection-for-custom-device-interface-on-matter-pi-gpio-commander/38891/7
The workaround, as mentioned, is to connect manually:
sudo snap connect matter-pi-gpio-commander:custom-gpio \
matter-pi-gpio-commander:custom-gpio-dev
On Raspberry Pi 5, the custom-device
plug is unavailable on the stable branch (v1.1.0) for both Ubuntu Server 24.04 and Ubuntu Core 24.
skoll@ubuntu:~$ sudo snap install matter-pi-gpio-commander
matter-pi-gpio-commander 1.1.0 from Canonical IoT Labs installed
skoll@ubuntu:~$ sudo snap connections matter-pi-gpio-commander
Interface Plug Slot Notes
avahi-control matter-pi-gpio-commander:avahi-control - -
bluez matter-pi-gpio-commander:bluez - -
dbus matter-pi-gpio-commander:otbr-dbus-wpan0 - -
gpio-memory-control matter-pi-gpio-commander:gpio-memory-control - -
network matter-pi-gpio-commander:network :network -
network-bind matter-pi-gpio-commander:network-bind :network-bind -
skoll@ubuntu:~$ sudo snap connect matter-pi-gpio-commander:custom-gpio
error: snap "matter-pi-gpio-commander" has no plug named "custom-gpio"
This gave the same error as jpm's second example when triggering the test blink.
skoll@ubuntu:~$ sudo matter-pi-gpio-commander.test-blink
GPIO: 4
Oops: Unable to determine board revision from /proc/cpuinfo
-> No "Hardware" line
-> You'd best google the error to find out why.
However, the --beta
branch (v2.0.0) worked for me on server 24.04:
skoll@ubuntu:~$ sudo snap install matter-pi-gpio-commander --beta
matter-pi-gpio-commander (beta) 2.0.0 from Canonical IoT Labs installed
skoll@ubuntu:~$ sudo snap set matter-pi-gpio-commander gpio=4
skoll@ubuntu:~$ sudo snap set matter-pi-gpio-commander gpiochip=4
skoll@ubuntu:~$ sudo matter-pi-gpio-commander.test-blink
GPIO: 4
GPIOCHIP: 4
Setting GPIO 4 to Off
Setting GPIO 4 to On
Setting GPIO 4 to Off
Setting GPIO 4 to On
...
And the --beta
branch (v2.0.0) worked for me on UC 24:
secondskoll@localhost:~$ sudo snap install matter-pi-gpio-commander --beta
matter-pi-gpio-commander (beta) 2.0.0 from Canonical IoT Labs installed
secondskoll@localhost:~$ sudo snap connections matter-pi-gpio-commander
Interface Plug Slot Notes
avahi-control matter-pi-gpio-commander:avahi-control - -
bluez matter-pi-gpio-commander:bluez - -
custom-device - matter-pi-gpio-commander:custom-gpio-dev -
custom-device matter-pi-gpio-commander:custom-gpio - -
dbus matter-pi-gpio-commander:otbr-dbus-wpan0 - -
network matter-pi-gpio-commander:network :network -
network-bind matter-pi-gpio-commander:network-bind :network-bind -
secondskoll@localhost:~$ sudo snap connect matter-pi-gpio-commander:custom-gpio \
matter-pi-gpio-commander:custom-gpio-dev
secondskoll@localhost:~$ sudo snap connections matter-pi-gpio-commander
Interface Plug Slot Notes
avahi-control matter-pi-gpio-commander:avahi-control - -
bluez matter-pi-gpio-commander:bluez - -
custom-device matter-pi-gpio-commander:custom-gpio matter-pi-gpio-commander:custom-gpio-dev manual
dbus matter-pi-gpio-commander:otbr-dbus-wpan0 - -
network matter-pi-gpio-commander:network :network -
network-bind matter-pi-gpio-commander:network-bind :network-bind -
secondskoll@localhost:~$ sudo snap set matter-pi-gpio-commander gpio=4
secondskoll@localhost:~$ sudo snap set matter-pi-gpio-commander gpiochip=4
secondskoll@localhost:~$ sudo matter-pi-gpio-commander.test-blink
GPIO: 4
GPIOCHIP: 4
Setting GPIO 4 to Off
Setting GPIO 4 to On
Setting GPIO 4 to Off
Setting GPIO 4 to On
Setting GPIO 4 to Off
^C
I've just promoted 2.0+chip-v1.3.0.0
from candidate to stable. The custom-device interface should now be available on stable, but a manual connection is still required on Ubuntu Core.
I can confirm the current steps in the documentation now work as described on UC24.
secondskoll@localhost:~$ sudo snap remove matter-pi-gpio-commander --purge
matter-pi-gpio-commander removed
secondskoll@localhost:~$ sudo snap install matter-pi-gpio-commander
matter-pi-gpio-commander 2.0+chip-v1.3.0.0 from Canonical IoT Labs installed
secondskoll@localhost:~$ sudo snap set matter-pi-gpio-commander args="--passcode 1234"
secondskoll@localhost:~$ sudo snap connect matter-pi-gpio-commander:custom-gpio \
matter-pi-gpio-commander:custom-gpio-dev
secondskoll@localhost:~$ sudo snap set matter-pi-gpio-commander gpio=4
secondskoll@localhost:~$ sudo snap set matter-pi-gpio-commander gpiochip=4
secondskoll@localhost:~$ sudo matter-pi-gpio-commander.test-blink
GPIO: 4
GPIOCHIP: 4
Setting GPIO 4 to Off
Setting GPIO 4 to On
Setting GPIO 4 to Off
Setting GPIO 4 to On
Setting GPIO 4 to Off
Setting GPIO 4 to On
^C
Beta version of snap, following Wiki:
Release version of snap following docs:
Beta version following #60 - these steps work on Ubuntu Server 24.04 on Raspberry Pi 5, but not when using Core 24:
System info