Crashes when attempting to connect to Shunts and chargers. Each new release seems to be much more unreliable than the last. I'm really starting to get frustrated with the lack of support for the Mac.
WHEN IS VICTRON GOING TO FIX ALL THESE CRASHES???
This site is now in read-only archive mode. Please move all discussion, and create a new account at the new Victron Community site.
Crashes when attempting to connect to Shunts and chargers. Each new release seems to be much more unreliable than the last. I'm really starting to get frustrated with the lack of support for the Mac.
WHEN IS VICTRON GOING TO FIX ALL THESE CRASHES???
Hi all, fixed. v5.55 was released this morning. Thank you @jonmarinello@gmail.com for the quick report and help to get it sorted!
This issue has been raised many times here in the community since the release of macOS 12. Victron has already commented on this and clearly stated that the problem lies with Apple and that there is currently hardly any possibility of eliminating the problem in the short term. 12.2 makes no difference.
I think there is no need for a new thread since everything has already been said about it. A search results in the following threads:
https://community.victronenergy.com/questions/106551/is-victronconnect-stable-on-macos-1201.html
Hi Stephanie,
You are confusing two completely distinct problems.
The problem you are referring to has to do with connecting to a victron device for the first time and needing to enter the bluetooth pin and it is just ignored. That is not what this posting is referring to.
In my case, I have been using this computer to access devices that were setup long ago and have always worked fine until 5.54. Now, VictronConnect just crashes as soon as it tries to connect to existing previously working devices. THIS IS A NEW REGRESSION IN 5.54. And it make the application utterly useless.
I am familiar with the threads you posted. This is not the same issue. BTW - the first link results in a 404 error.
Can someone from Victron please respond ASAP?
Thanks!
Hello Jon,
no, I am not confusing anything. Until the update to macOS 12.2 I also had a device that luckily still worked because it was paired via Bluetooth before the update to Monterey.
In my opinion it was only a matter of time before this device also stopped working due to subsequent macOS updates. It worked wonderfully with macOS 12.1 AND VictronConnect 5.54, unfortunately not with 12.2.
While I'm not a programmer, it's clear that Victron software developers are stuck here without Apple's help. And they don't seem to be getting that support at the moment. So we have to be patient, as frustrating as that can be sometimes.
edit: fixed the broken link
This has gone from bad to worse. Now not seeing BMV712 Smart or MPPT 250/100 since update to VictronConnect 5.54 with Monterey 12.2.
It has been 2 months now since the pin code stopped working on both devices since the changeover to Monterey, and now VictronConnect cannot see the devices at all.
How much longer do we have to wait before Victron and Apple get this mess sorted out? Please Victron - fix this issue urgently.
MacBook Pro (15-inch, 2018)
2.6 GHz 6-Core Intel Core i7
16 GB 2400 MHz DDR4
Intel UHD Graphics 630 1536 MB
MacOS Monterey V12.2
VictronConnect 5.54
Victron:
These crashes are instantly and reliably reproducible.
Steps to Reproduce:
Then fix this bug and get a point release our ASAP.
I think if this crashes would be that easy to fix Victron would have already fixed them.
Hi, I can confirm that a bug was made in VictronConnect v5.54, related to Monterey, causing the crash. Or more precisely: it brings back the crash that was first fixed in another recent version.
My apologies for this, it should not happen.
We'll release a new version that fixes this real soon.
I do have to warn - unfortunately - that we're not close at all to fixing the pairing issue in combination with Apple macOS Monterey, for which this is the main thread on Community:
I've just now clearly mentioned both issues in the VictronConnect change log.
mvader: Thanks for getting back to us and for the honesty. Appreciate you addressing this. Please post a link to the proposed fix and I can test and confirm the crash (and only the crash is fixed).
Hi @jonmarinello@gmail.com , it went quicker than I thought: a version to test is available here:
https://www.dropbox.com/s/yf22nqwjph8jzww/VictronConnect.dmg?dl=0
Its version 5.55.
43 People are following this question.