-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Could not retrieve encryption keys using victronconnect on Windows 11 #27
Comments
That is what I found as well, the sqlite file mentioned in the README is empty. You can pair a Victron controller to a Windows computer but the app will not connect to that paired device. The Windows VictronConnect app specifically says when clicking "Don't see the product you were looking for?" section "No Bluetooth on Windows" I had to find a co-worker who had a Mac machine to get the keys That begs the question: @keshavdv, why does the README for the repo suggest that the advertisement key is retrievable from a Windows machine? Is there something @adrusa and I are missing? |
I'm running VictronConnect 5.9 on macOS and also find that the sqlite file's advertisementKeys table is empty. @theHurc, your colleague with the Mac, was he using an older version of VictronConnect do you know? |
I finally used Linux Appimage on Ubuntu live usb to retrieve the keys and it worked well. |
@kaeser-sosae, you still need to pair the Victron device with your Mac and connect to it in the app, that process will initiate the key transfer. He was using version 5.90 |
you can now access to advertisment keys in the victron application => settings => product information => encryption data |
Yes! It works!!! Thanks for the update. This really makes commissioning a bunch of these devices easier. BTW, the Encryption Data section in the app also contains the MAC address which is really handy. |
What application? Android app? Windows app? Something else? |
Yeah I don't see these keys in the MacOS app... |
No advertisement keys in windows sqlite file
The text was updated successfully, but these errors were encountered: