This went long.
The first few times I tried, it failed to unzip.
Thus, the comments you refer to.
Later it did, thus the later comments.
The date/time reflects an old Zip and old contents; nothing has changed.
The SUDO command does not work now or before.
I do know what it does. I have been a developer for 35+ years and a Mac user for well over half of that. I knew what I was doing when I tried and shared technical info with them.
BL are shipping out new versions of the hardware to me after telling me they have no interest in fixing the problem with the application. They say they no longer support them and have no interest in testing, re-zipping, or anything else.
They plan on placing the firmware tools in the desktop apps used to configure the CB projects.
I can only hope they enable cut, copy and paste at the same time.
They said they rushed the software, and they clearly did.
I didn’t take it that way.
I would have loved it to be, but this damn model has been drawn out for issues I did not cause. I really want it out for people to say “nope, not interested.”
I tried everything with the tiny buttons.
I even bought some more cores to keep things moving, as BL is very slow in sending replacements.
I do know my issue is the v1.0.2.51 cores they shared with everyone, which have known bugs, and they refuse to help people resolve those with the firmware tool we have spoken about.
v1.0.2.58 works perfectly.
They shipped the faulty v1.0.2.51 cores with the CyberBrick stuff.
It means if any models use anything other than really basic LED control, it will fail and the users will blame themselves.
For my needs, I wanted to drive 8 LEDs with three colours, which is impossible without code, as you cannot set a single hub to show more than one colour at the same time in the UI.
My model lets users turn on the main lights (white for the front and red for the back) while also having indicators that work left and right.
It is impossible to achieve using the UI.
I can only wonder how many models have been compromised because there is no obvious way, even with V1.0.2.58 and impossible with v1.0.2.51.
Designers will think it is their fault.
The documentation is also incredibly bad. Making getting to the solution even harder.
I tried using the cores from my two time-lapse units; those were also the faulty v1.0.2.51.
The only v1.0.2.58 I had was from a package I purchased after the Kickstarter and from MakerSupply.
That means:
- 2 x time-lapse cores
- 5 x kits via kickstarter
- 2 x review units
All had v1.0.2.51.
The time-lapse kicks can be forgiven as they have a fixed role.
The other 7 - not so much.
Keep in mind, the original review kits were even older and could not be firmware updated, even if that did work. They had to send out the first set of replacements for those because they were incapable of connecting to the desktop and mobile apps.
Again, they knew this and did nothing to inform anyone.
You may remember why they created the config files for all the first CB models. This is why the reviewers were unable to with what they had.
They didn’t tell any of them. They didn’t tell me.
By rights, there should have been a recall if they continue refusing to have a firmware update.
… I did the same just yesterday… it said right there in the instructions to reset the module manually if it wasn’t flashing properly… naturally I didn’t do that and just repeated the same steps multiple times until I did read that! 