Hey all, over the past few days I’ve made a couple incremental releases. Here’re the changes between v2.6.32 and v2.6.42, which I released today.
For all Bond bridges
Persist device state after a reboot
Fix issue where upgrades were not cancelling properly
For Bond bridges with serials starting in A or B: Note: the features below were already present in Bond bridges with serials starting in Z
Support non-ASCII SSIDs
Add support for static IP and custom DNS configurations, via the local API or web GUI
(for the web GUI, visit 10.7.42.1 while associated with the Bond’s Config AP… an in-app interface will come soon)
Fix issue where transmissions would stop working after a while, despite returning 204 statuses
Fix issue where the Bond would think its database was full, causing all kinds of problems
Jacob, Should I be getting an email with an invitation to have TestFlight install the beta? If so, I never got one for 2.6.32 or 42. My email address is bryan@visual-av.com. Could you check my account and let me know if it’s setup correctly. Thanks. Bryan
To bring cloud devices offline, our approach is to embed signal-generating Lua scripts on the Bond. The idea of “BondScript” is to make this feature available to our users, to enable them to create and share custom scripted devices. We’ve got a proof-of-concept running, and we’re working out the supporting libraries and the API now.
Should both A/B and Z revision Bridges have 2.6.42 as most recent firmware?
My B updated to 2.6.42, and my Z updated to 2.6.36; both are saying most recent firmwares / up to date.
I’ve been away for a while and just tried to upgrade to the latest firmware. I have the latest beta ios app (1.142.2 (2)), but my Bond firmware is stuck at 2.6.21. I have had to upgrade manually via the api in the past, but in those cases the app would at least see the firmware but fail to upgrade.