question

frangar avatar image
frangar asked

VictronConnect Bluetooth pairing on macOS 12.1 aka Monterey broken?

Ive just upgraded to Mac OS 12.1 and VictronConnect is still not paring with devices it seems. Has victron registered the issue with Apple? As a developer its likely to have more clout than us as users. It would be really useful to get this sorted. Im using the Beta Test version of the connect app.

BluetoothmacOS
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

4 Answers
mvader (Victron Energy) avatar image
mvader (Victron Energy) answered ·

UPDATE 2022-02-28: on the latest macOS beta, Bluetooth pairing works again. This is 12.3 beta 4. We couldn't find any official information about when it is due for release, but in some blogs people mention March. Also our support ticket with Apple had an update: a potential fix is identified and will be added into a future OS update.


Original:

Hi @Frangar , and any one else. Indeed, unfortunately Bluetooth pairing with a new Victron device does not work on a Apple device running macOS v12, also known as Monterey.

We're working to fix that, and in touch with Apple about that. Progress on this is slow, there is no solution on the horizon at the moment; its a real difficult one to fix or work around without Apple themselves fixing something.


Note that there was another issue with Monterey, which was that VictronConnect crashed during connecting - which is solved in the latest VictronConnect version, 5.52, released a week ago.



27 comments
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

ps. I'd like to use this thread as the main one for this issue, so its easy to find for anyone else running into this. So I cleaned the title up a bit and answers as well - hope that is ok!
0 Likes 0 ·
kevinvh avatar image kevinvh mvader (Victron Energy) ♦♦ ·
You cleaned it up alright. You removed all comments except your‘S and the one from Bob Fijn. What has changed with Monterey to cause the pairing issue? Who has the lead for fixing it - Victron or Apple? Are you both cooperating to fix the issue - reading between the lines indicates that you have reached a stalemate?

VictronConnect 5.54 has made the situation worse - now can’t see Bluetooth devices at all. The longer the issue is allowed to exist, the greater damage will be done to Victron’s and Apple’s good reputation.

0 Likes 0 ·

Hi Kevin, I'm sorry to see you seem rather agitated. The only replies I removed were about mixing up iOS with macOS. Right now no-one has the lead: it would be great if Apple would fix it soon, but even though we're sort of a large company, its also for us hard to get real traction at Apple. So we are seeing if we can somehow work around the change made by Apple.

I'm well aware about damage - indeed it needs fixing.

For v5.54 crashing on macOS, that was different issue, fixed in the morning of feb 1st, in v5.55.

Thanks for caring - believe me, nobody on our side is unconcerned about VictronConnect not properly working on the latest macOS version.

0 Likes 0 ·
kevinvh avatar image kevinvh mvader (Victron Energy) ♦♦ ·

Thanks for the reply Matthijs. I will be tearing my hair out if Apple takes a year to fix this issue as suggested by enodev. Can I ask what Apple changed in Monterey that caused the issue? Apart from this issue, I have been very happy with Monterey, and I really like VictronConnect - it is simple and easy to use.

In the meantime, I have reverted to using Victron_Grafana with Docker and it still works OK.

0 Likes 0 ·
Thanks everyone for digging in and encouraging Apple to fix the Bluetooth Pairing issue created by Monterey. Sounds like it would have taken a long time for Apple to resolve the issue. With your help it may be resolved soon.

We are not the only ones with Bluetooth issues created by Monterey. Apple obviously changed something that "upset the Apple cart".

0 Likes 0 ·

@mvader (Victron Energy) Do you have an https://openradar.appspot.com/page/1 bug number or https://developer.apple.com/forums/ post about the underlying issue? I am a long term iOS and macOS developer myself and have some developer contacts that may or may not be of help...

0 Likes 0 ·

Hi @enodev , yes that would be great if you could do that.

We have a post on their forum here:

https://developer.apple.com/forums/thread/694377

And submitted a Feedback Support, via the Feedback application that’s in Apple beta software. And we raised a ticket at Apple DTS, ticket number 785847079. They then confirmed this was indeed an issue, would work on it, and closed the ticket.

We haven’t used Open Radar yet.

Let me know what you can do, also happy to continue this on email.

all the best, Matthijs

0 Likes 0 ·
enodev avatar image enodev mvader (Victron Energy) ♦♦ ·
Thanks for the feedback number, will see if I can get an attention of anybody. Been there many times over the past 10 years, know it sucks!


When the DTS closes the request with "it's a bug, we will work on it" I typically wait a around a year before the issue gets resolved... Sad but true :(
0 Likes 0 ·
jonmarinello avatar image jonmarinello mvader (Victron Energy) ♦♦ ·
Gee, that's really nice of apple to close the DTS ticket before deploying a fix ;-)

Would it be possible to reopen the ticket and ask that they keep it open until Apple deploys the fix?

0 Likes 0 ·

It usually does not work like that. The group of people called Apple DTS (Developer Technical Support) is designed to help you - for money - when you have issues with some of the Apple technology - they are not owners of the respective area, just experienced engineers who know the Apple tech better then you. When it turns out that your problem is not your misunderstanding of the Apple technology, but rather Apple bug, they forward the problem to the appropriate team, then refund money and say "Apple will get it fixed, but we can not tell when". I have used DTS many times in the past for many issues in many Apple subsystems and never actually came to a quick solution. It was always a bug someplace else that eventually got fixed but it took super long time.


The Apple engineers I know typically say that when a bug is reported against Beta 1 (For macOS 12 Monterey that was around July 1st 2021) there is a high chance it will get fixed before official release. Anything reported later and not a super important bug will simply get addressed in .1 or .2 or .3 or even new major release next fall.


If you look at developer threads from Victron here: https://developer.apple.com/forums/thread/694377 and from other guy here: https://developer.apple.com/forums/thread/694146 you will see that they were discovered/reported around Dec 2021 which is "after" the official release.


So bringing the fix in now is probably rather risky and will therefore take a lot of time. Not happy about it, but when the software gets big and complex.....

0 Likes 0 ·
Thanks for explaining that aspect of DTS. Shame it can't be more effective. That said this (to me at least) seems like a serious bug. Not at the level of a crash but maybe just below that. How risky the fix is, depends of course on the nature and extent of the coding change to address the root cause and we have no visibility into that.


The only other way I can think of to drive this is by the number of complaints Apple is receiving on the problem.

Maybe I'll give apple support a call and raise the issue there and see what they say. The cost is low and who knows what I might be able to find out. Maybe if enough of us call in with this problem it might get some love.

0 Likes 0 ·
Ok, I called Apple technical support today, worked my way through to a senior MacBook support engineer. She got on my M1 MacBook Air with me and I demonstrated the problem for her and we video recorded the session and also enabled logging during the demonstration. I uploaded all this to Apple to attach to the trouble ticket and she promised to bring this to Engineering and get back to me no later than Tuesday 2/8. She will be my engineering liaison point person on this issue for the duration.


I'm not sure if this will bear any fruit but given things seem to be stuck maybe this will help. I will report back ASAP with her next response.

I will do all I can through this point of contact to drive this to a satisfactory outcome.

0 Likes 0 ·
Nice!
0 Likes 0 ·
frangar avatar image frangar mvader (Victron Energy) ♦♦ ·

Just upgraded to Mac OS 12.2.1 and VictronConnect V5.56.....and still no joy with pairing on bluetooth Im afraid. Have you had any further response from Apple

0 Likes 0 ·

I heard back from Apple yesterday on the ticket I escalated 8 days ago. See my posting above. Apple Engineering wants to gather more detailed logging data from me and I have an appointment with them to do that on Thursday (02/17 - I'm out of town until then). They are sending me a profile to enable that specialized Bluetooth-specific logging. Once I repeat the test and that new Bluetooth-specific profile and the new log is uploaded, they will hopefully know more, and perhaps they can either (1) address the issue directly and deploy a Monterey point release to address this problem, (2) I can get them to buy a Bluetooth device that requires a passcode so they can reproduce this in house and then fix this bug and deploy a Monterey point release to address this problem, (3) they continue sending me logging profiles to run until then get what they need from my logs (this is much less productive and will take a lot longer). In any case, I'm sure we will need to wait for a future Monterey release to get this addressed.

1 Like 1 ·
Thats great progress on your part! As a user thanks for taking the time over this....If you need me to do any logs with the kit I have Im happy to help in any way I can if they want more reports,...Just let me know.
0 Likes 0 ·
Ok Thanks!
0 Likes 0 ·
Hi @jonmarinello@gmail.com , that is really great. Looking forward to hear what comes out. We're happy to help where needed. For example by supplying Apple with a device to test on.
0 Likes 0 ·
jonmarinello avatar image jonmarinello mvader (Victron Energy) ♦♦ ·
Still working on getting the Bluetooth logs completed with the support engineer and uploaded. Thanks!
0 Likes 0 ·
jonmarinello avatar image jonmarinello mvader (Victron Energy) ♦♦ ·
@mvader (Victron Energy) I just finished another session with Apple and uploaded a Bluetooth-specific logging session where I reproduced the problem. I also leaned on them as much as possible to encourage them to allow us to send them a small piece of Victron hardware to allow Engineering to reproduce the problem in-house. I explained that they will need this at some point anyway to validate that they have in fact addressed the root cause. I explained that we can shortcut all this back and forth with logging sessions and help them to diagnose the problem and try a fix using the hardware in-house. Then later QA can validate the fix before deploying it. This made sense to the support engineer but she seemed to think it would be hard to convince Apple engineering of the logic of this approach. Maybe there are some Apple rules that would preclude doing this. In any case, I did my best to convince her and arm her with all the arguments to support this streamlined process to present to Engineering.
0 Likes 0 ·

Hi @jonmarinello@gmail.com , that is great - thank you for all that effort.

We also had a nice discovery this morning: on the latest macOS beta, Bluetooth pairing works again.

This is 12.3 beta 4. We couldn't find any official information about when it is due for release, but in some blogs people mention March.

Also our ticket had an update: a potential fix is identified and will be added into a future OS update.


All the best for now, Matthijs

Ps. I'll also update the status on my first answer.

1 Like 1 ·
Show more comments
I'm really interested in what you are able to find out from Apple on this. Please keep us posted on your progress! Thanks for doing this.
0 Likes 0 ·
I can confirm that it is working in 12.3 release which I updated to last night. This is with VictronConnect 5.57
0 Likes 0 ·

The release candidate is out for beta testers, GA is scheduled for next week.

0 Likes 0 ·
Rob Fijn avatar image
Rob Fijn answered ·

Hi, I had no problem with 15.1 .. Now updating to 15.2 .. let see

Rob


2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

frangar avatar image
frangar answered ·

Thats a result....lets keep everything crossed that it stays working in the official system release. Thanks to all for working on the issue especially @mvader (Victron Energy) & @jonmarinello@gmail.com

2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

raymiller avatar image
raymiller answered ·

Good news everyone MacOS Monteray 12.3.1 on my M1 MacBook Pro has fixed the Bluetooth VictronConnect issue, I just tested on all my devices and they now successfully connect. It has taken Apple quite a while to get around to fixing this software bug.

Cheers


2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.