Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot open AccessPoint with BerryLan App on RaspberryPi3A+ #38

Closed
blasco991 opened this issue Apr 20, 2020 · 4 comments · Fixed by nymea/libnymea-networkmanager#8
Closed
Assignees

Comments

@blasco991
Copy link

blasco991 commented Apr 20, 2020

Hì, i have a Raspberry Pi 3 Model A Plus Rev 1.0

With just the clean image downloaded from http://www.berrylan.org/ i can use the BerryLan mobile App and successfully connect to an existing WiFi, but when i try to create an Access Point with the relative button on the App, i give it the SSID and PSW but look at the syslog on the raspberry i get this error log:

pi@raspberrypi:~ $ sudo nymea-networkmanager -m start
 I | Application: Using configuration file from: "/etc/nymea/nymea-networkmanager.conf"
 I | Application: =====================================
 I | Application: Starting nymea-networkmanager "0.5.2+202003241320~buster+rpi1"
 I | Application: =====================================
 I | Application: Advertising name: "BT WLAN setup"
 I | Application: Platform name: "nymea-box"
 I | Application: Mode: Core::ModeStart
 I | Application: Timeout: 60
 W | NymeaService: Invalid D-Bus HardwareManager interface.
 W | NymeaService: Could not init nymea D-Bus services
 I | Application: Networkmanager is now available.
 I | Application: Starting the Bluetooth service because of "start" mode.
 W | NymeaService: Could not enable/disable bluetooth hardware resource. D-Bus interface not available.
 W | qt.bluetooth: Using BlueZ kernel ATT interface
 I | Application: Bluetooth server started
 I | Application: Bluetooth client connected
 W | qt.bluetooth.bluez: sending error response; request: 16 handle: 51 code: 10
 W | qt.bluetooth.bluez: sending error response; request: 8 handle: 1 code: 10
 W | qt.bluetooth.bluez: sending error response; request: 8 handle: 26 code: 10
 W | qt.bluetooth.bluez: sending error response; request: 8 handle: 39 code: 10
 W | NetworkManager: "org.freedesktop.NetworkManager.Settings.Connection.InvalidProperty" "802-11-wireless-security.proto: can't set property of type 'GStrv' from value of type 's'"

 
@blasco991 blasco991 changed the title Cannot open Access Point with BerryLan App Cannot open #AccessPoint with BerryLan App on #RaspberryPi3A+ Apr 20, 2020
@blasco991 blasco991 changed the title Cannot open #AccessPoint with BerryLan App on #RaspberryPi3A+ Cannot open AccessPoint with BerryLan App on RaspberryPi3A+ Apr 20, 2020
@t-mon
Copy link
Member

t-mon commented Apr 20, 2020

Hi @blasco991

thanks for reporting this, I noticed this behavior already and I'm working on a fix.
Looks like on the buster version of the network-manager something changed on the dbus side and should be quiet easy to fix.

I'll let you know once I have a build to test if it's working again.

@mzanetti
Copy link
Member

The bug has been fixed in libnymea-networkmanager and is in the experimental repository now.

Thanks for reporting.

@blasco991
Copy link
Author

The bug has been fixed in libnymea-networkmanager and is in the experimental repository now.

Thanks for reporting.

thank you, when should this fix be available on the packet that you install with apt-get?

@mzanetti
Copy link
Member

mzanetti commented May 6, 2020

It will be released with nymea 0.21. Should be in a few weeks, two maybe. We just released 0.20 when you reported this... Needs to go through the testing repository and QA tested still.

If you're feeling adventurous, you can also enable the experimental repository and test it right away by adding this to /etc/apt/sources.list.d/nymea.list

deb http://ci-repo.nymea.io/experimental-silo buster rpi

then you'll get it with apt-get upgrade

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants