Posts: 21
Threads: 3
Joined: Oct 2022
Reputation:
0
Hello everyone, after an update and reinstallation of SignalK installer (version 3.1.15) via Openplotter settings, I no longer have the possibility to activate Pyppilot nor I2C sensors.
I have the following errors on startup:
Checking I2C sensors... | I2C enabled
Unexpected error validating connection: Handshake status 401 Unauthorized
Checking pypilot... | pypilot_hat running | pypilot not running | pypilot_web not running
Unexpected error validating connection: Handshake status 401 Unauthorized
I guess it's a permissions issue, but I'm unable to fix this.
Thanks for your help.
Posts: 21
Threads: 3
Joined: Oct 2022
Reputation:
0
The issue always happens.
I have no devices in security/devices, but I probably messed up quite a bit trying to fix it. I tried without success to recreate connections.
I have two connections in Dashboard: defaults and ama (dev/ttyOP_ama) with no activity.
In connections and plugin status, I have:
sk-to-nmea 0183 = started
ama = connected to /dev/ttyOP_ama
Posts: 2,893
Threads: 59
Joined: Mar 2016
Reputation:
278
- Update all openplotter apps (settings, I2C, pypilot...)
- Delete any device in security/devices
- Delete any value of fields uuid, href and token for any app in ~/.openplotter/openplotter.conf file.
- Run "Check system" from the OpenPlotter menu.
- Connection requests for all your apps should be created in security/access/requests, approve them with read/write permissions
Let me know if this fixes the issue.
Posts: 21
Threads: 3
Joined: Oct 2022
Reputation:
0
Looks like it worked ! Thank you for your help ! But I can't connect a BME 280 by I2C, I'm going to work on it, but I'm a little confused by the fact that there is no longer the "connection" tab on I2C sensors, while it is used in all the tutorials on the net.
Posts: 21
Threads: 3
Joined: Oct 2022
Reputation:
0
It worked fine, I no longer have the error "Unexpected error validating connection: Handshake status 401 Unauthorized".
On the other hand, I have the error "openplotter-I2C-read not running" systematically. I deleted then recreated the BME980 sensor, but I still have this error.
For information: I wanted to test an MPU925x which did not work (probably victim of a connection error), and there, the error "openplotter-I2C-read not running" did not appear, but no data was not circulating. I put the working MPU925x back, and there the error came back.
Posts: 2,893
Threads: 59
Joined: Mar 2016
Reputation:
278
IMUs like the MPU925x are managed by openplotter-pypilot app, not by openplotter-i2c app.
To debug your problem with BME680/688 sensor open a terminal, type openplotter-i2c and set your sensors from scratch, put here any error you get in the terminal. If your sensor is not in the list it will not work.
Posts: 2,893
Threads: 59
Joined: Mar 2016
Reputation:
278
you can ignore those gtk errors.
go to openplotter-settings, click "debugging mode" in "system log" tab and try again.
are you sure you have a BME680/688 sensor?