All 4 of my cyberbrick cores arent connecting to the cyberbrick macos app through bluetooth or even a cable. Is this a software issue or a hardware issue.
Also the light is green on the esp32 and white on the core board.
The CyberBrick remotes are the ones that connect first; you can put the receivers to one side for testing.
Are you able to connect using the mobile apps?
If so, you may need to enable Bluetooth discoverability on your macOS or enable any permission requirements.
If this also fails, then the following is unlikely, but worth ruling out.
There have been two versions of the receiver/transmitters; the originals were WiFi, and the new ones are Bluetooth.
It is important to note that the WiFi ones should have only been sent out to reviewers (like me). They also had handwritten numbers on stickers, which may have been only on some boards, though.
So, this test is purely to rule things out.
To rule this unlikely situation out:
Use your mobile phone
Navigate to the WiFi section
Locate the pairing page (this is where you see a list of available WiFi transmitters).
Turn on the Transmitter on your CyberBrick.
Do you see a new entry appearing in the WiFi list?
Hey,
Quick question… what does your core show up as when you search for it over Bluetooth? Is it named BBL_Shutter or RC_module?
Also, just a heads-up: make sure your phone and computer aren’t both trying to connect to it at the same time. It can cause issues, so try turning off Bluetooth on your phone or removing the device from the paired list before you connect with your computer.
I never said they were. They are not hidden; that is where they are located.
The word or separates two different things.
Bluetooth discoverability is one thing, permission requirements are another.
This is why we use the word ‘or’ in sentences.
I suggested you try the mobile apps, which you hadn’t, and they did work when you tried them.
Assuming that was the case, you were to check the Bluetooth discoverability (which you said showed them).
I again pointed out it was a connectivity issue with macOS, which needed to be investigated.
It turned out it was the permissions suggestion.
Restricting, you say, that is another word for permissions, right?
Amazing, you stated a problem, I gave the answer, the solution was that answer, yet weirdly, you arrived at the stated solution without any assistance.