Pods for SkySpark 3.1.12 and 4.0.6 (legacy 3.1.6, 3.1.8, 3.1.9, 3.1.10, 3.1.11 too): download them here, or keep servers up to date with bassgReleaseClient.
SkySpark licenses next to the modules. The licensing view (Settings > BASSG Licenses) shows two tables in the top row: the BASSG modules on the left, and the Sk…
SkySpark licenses next to the modules. The licensing view (Settings > BASSG Licenses) shows two tables in the top row: the BASSG modules on the left, and the Sk…
SkySpark licenses next to the modules. The licensing view (Settings > BASSG Licenses) shows two tables in the top row: the BASSG modules on the left, and the Sk…
SkySpark licenses next to the modules. The licensing view (Settings > BASSG Licenses) shows two tables in the top row: the BASSG modules on the left, and the Sk…
SkySpark licenses next to the modules. The licensing view (Settings > BASSG Licenses) shows two tables in the top row: the BASSG modules on the left, and the Sk…
SkySpark licenses next to the modules. The licensing view (Settings > BASSG Licenses) shows two tables in the top row: the BASSG modules on the left, and the Sk…
Faster relay. Calls to the relay on lic.bas.co reuse one keep-alive connection and a saved session token, so a restart or a new Connect with the same login no l…
Faster relay. Calls to the relay on lic.bas.co reuse one keep-alive connection and a saved session token, so a restart or a new Connect with the same login no l…
Restart from the page. "Install selected and restart" installs the chosen pods and restarts SkySpark; "Restart SkySpark" restarts it alone. The page waits for t…
Restart from the page. "Install selected and restart" installs the chosen pods and restarts SkySpark; "Restart SkySpark" restarts it alone. The page waits for t…
One version per module per zip. The zip holds the .pod files and MANIFEST.txt with SHA-256.
bassgCommon
3.1.12.2.2
Highlights
SkySpark licenses next to the modules. The licensing view (Settings > BASSG Licenses) shows two tables in the top row: the BASSG modules on the left, and the SkySpark license files of the server (lics()) on the right, with SkySpark's "used N of M" line as heading.
Module counts. The modules table has the heading "BASSG modules · N exts · M licensed · P licensed projects".
Point capacity. Above the projects table, the selected module shows "Capacity 1,000 points · used 349 · left 651", or "over by N" when the limit is exceeded.
Also
Same API level (2) and functions as 2.1. Only the licensing view changed.
bassgCommon
3.1.6.2.2
Highlights
SkySpark licenses next to the modules. The licensing view (Settings > BASSG Licenses) shows two tables in the top row: the BASSG modules on the left, and the SkySpark license files of the server (lics()) on the right, with SkySpark's "used N of M" line as heading.
Module counts. The modules table has the heading "BASSG modules · N exts · M licensed · P licensed projects".
Point capacity. Above the projects table, the selected module shows "Capacity 1,000 points · used 349 · left 651", or "over by N" when the limit is exceeded.
Also
Same API level (2) and functions as 2.1. Only the licensing view changed.
bassgCommon
3.1.8.2.2
Highlights
SkySpark licenses next to the modules. The licensing view (Settings > BASSG Licenses) shows two tables in the top row: the BASSG modules on the left, and the SkySpark license files of the server (lics()) on the right, with SkySpark's "used N of M" line as heading.
Module counts. The modules table has the heading "BASSG modules · N exts · M licensed · P licensed projects".
Point capacity. Above the projects table, the selected module shows "Capacity 1,000 points · used 349 · left 651", or "over by N" when the limit is exceeded.
Also
Same API level (2) and functions as 2.1. Only the licensing view changed.
bassgCommon
3.1.9.2.2
Highlights
SkySpark licenses next to the modules. The licensing view (Settings > BASSG Licenses) shows two tables in the top row: the BASSG modules on the left, and the SkySpark license files of the server (lics()) on the right, with SkySpark's "used N of M" line as heading.
Module counts. The modules table has the heading "BASSG modules · N exts · M licensed · P licensed projects".
Point capacity. Above the projects table, the selected module shows "Capacity 1,000 points · used 349 · left 651", or "over by N" when the limit is exceeded.
Also
Same API level (2) and functions as 2.1. Only the licensing view changed.
bassgCommon
3.1.10.2.2
Highlights
SkySpark licenses next to the modules. The licensing view (Settings > BASSG Licenses) shows two tables in the top row: the BASSG modules on the left, and the SkySpark license files of the server (lics()) on the right, with SkySpark's "used N of M" line as heading.
Module counts. The modules table has the heading "BASSG modules · N exts · M licensed · P licensed projects".
Point capacity. Above the projects table, the selected module shows "Capacity 1,000 points · used 349 · left 651", or "over by N" when the limit is exceeded.
Also
Same API level (2) and functions as 2.1. Only the licensing view changed.
bassgCommon
3.1.11.2.2
Highlights
SkySpark licenses next to the modules. The licensing view (Settings > BASSG Licenses) shows two tables in the top row: the BASSG modules on the left, and the SkySpark license files of the server (lics()) on the right, with SkySpark's "used N of M" line as heading.
Module counts. The modules table has the heading "BASSG modules · N exts · M licensed · P licensed projects".
Point capacity. Above the projects table, the selected module shows "Capacity 1,000 points · used 349 · left 651", or "over by N" when the limit is exceeded.
Also
Same API level (2) and functions as 2.1. Only the licensing view changed.
bassgMobilytik
3.1.12.5.8
Highlights
Faster relay. Calls to the relay on lic.bas.co reuse one keep-alive connection and a saved session token, so a restart or a new Connect with the same login no longer logs in again. The 10-minute sync and the sync after Connect are one request. Measured on lic.bas.co: 3 classes / 2 phones went from 822 ms to 208 ms, 30 classes / 10 phones from 1248 ms to 421 ms.
BASSG account portal at lic.bas.co/account/: a shop cart with every app, one checkout for several apps, public prices per product, and the customer changes the portal and relay passwords there. Ordering moves to lic.bas.co/apps.
Company tools for the owner. Create, delete and fix companies on the relay Companies page and in the Mobilytik Accounts view. A new company gets its account, relay company and SkySpark user, with the password shown once; Delete removes everything attached; Fix permissions repairs the user and the links.
Relay
A request that hit a dropped connection is sent once more, a POST too, with its body (a retried POST used to wait 5 s and fail).
The token from a relay-login answer is kept, so the first restart after a Connect with an e-mail account no longer logs in.
Relay setup accepts the relay password the owner saw when creating the company, besides the portal password of a verified account.
The relay writes only what changed, one commit per call; a phone's last-seen time moves at most every 5 minutes.
Readable relay errors on the account page.
Account and e-mail
The relay login is e-mailed for a new company and for a new or set password; "E-mail password" sends the current one.
Enable Portal / Disable Portal follow the SkySpark user: disabling stops the relay logins of that customer's servers. Verify E-mail button for unconfirmed accounts.
E-mails use the BASSG wording and link the website from the new setting websiteUrl (Host > Settings > SysMods > mobilytik).
A failed company create removes the half-made SkySpark user; a failed relay mail shows as a warning.
Install
Same API level 5 and functions as 3.1.12.5.5. Needs bassgCommon 3.1.12. Customer servers get the faster relay and the account page changes; the portal and company tools run on lic.bas.co. Built and tested for SkySpark 3.1.12 (2718 checks); the relay session lock is plain Fantom, so 3.1.6 and 3.1.8 build too. The same build is released as 3.1.9.5.6 for SkySpark 3.1.9.
bassgMobilytik
3.1.9.5.6
Highlights
Faster relay. Calls to the relay on lic.bas.co reuse one keep-alive connection and a saved session token, so a restart or a new Connect with the same login no longer logs in again. The 10-minute sync and the sync after Connect are one request. Measured on lic.bas.co: 3 classes / 2 phones went from 822 ms to 208 ms, 30 classes / 10 phones from 1248 ms to 421 ms.
BASSG account portal at lic.bas.co/account/: a shop cart with every app, one checkout for several apps, public prices per product, and the customer changes the portal and relay passwords there. Ordering moves to lic.bas.co/apps.
Company tools for the owner. Create, delete and fix companies on the relay Companies page and in the Mobilytik Accounts view. A new company gets its account, relay company and SkySpark user, with the password shown once; Delete removes everything attached; Fix permissions repairs the user and the links.
Relay
A request that hit a dropped connection is sent once more, a POST too, with its body (a retried POST used to wait 5 s and fail).
The token from a relay-login answer is kept, so the first restart after a Connect with an e-mail account no longer logs in.
Relay setup accepts the relay password the owner saw when creating the company, besides the portal password of a verified account.
The relay writes only what changed, one commit per call; a phone's last-seen time moves at most every 5 minutes.
Readable relay errors on the account page.
Account and e-mail
The relay login is e-mailed for a new company and for a new or set password; "E-mail password" sends the current one.
Enable Portal / Disable Portal follow the SkySpark user: disabling stops the relay logins of that customer's servers. Verify E-mail button for unconfirmed accounts.
E-mails use the BASSG wording and link the website from the new setting websiteUrl (Host > Settings > SysMods > mobilytik).
A failed company create removes the half-made SkySpark user; a failed relay mail shows as a warning.
Install
Same API level 5 and functions as 3.1.9.5.3. Needs bassgCommon 3.1.9. Customer servers get the faster relay and the account page changes; the portal and company tools run on lic.bas.co. Built and tested for SkySpark 3.1.9 (2718 checks). The same build is released as 3.1.12.5.8 for SkySpark 3.1.12.
bassgReleaseClient
3.1.12.1.8
Highlights
Restart from the page. "Install selected and restart" installs the chosen pods and restarts SkySpark; "Restart SkySpark" restarts it alone. The page waits for the new boot, then shows the install result in the history.
Settings tab. Channel (stable / beta), repository, check interval, host key, operating system (Linux / Windows / Mac, detected) and the restart command with a default per OS. "Restart automatically after an install" is off by default.
Channel in the header. Switch between stable and beta on the updates page; the repository is checked right away.
New pods. Pods of the repository that are not installed yet are listed as "new" and install like updates.
How the restart works
SkySpark runs the restart command itself two seconds after answering. No script files are written to the server.
Defaults: Linux sudo -n /bin/systemctl restart skyspark, Windows powershell -NoProfile -NonInteractive -Command "Restart-Service -Name SkySpark", Mac sudo -n launchctl kickstart -k system/skyspark. Change the command under Settings if the service has another name.
On Linux the SkySpark service user needs a sudoers rule for that exact command, unless SkySpark runs as root: <user> ALL=(root) NOPASSWD: /bin/systemctl restart skyspark.
A command that returns without restarting SkySpark is reported with its exit code and output; the last attempt is shown under Settings.
Also
Axon (su only): podRepoClientInstall(pods, restart: false), podRepoClientRollback(restart: false) and the new podRepoClientRestart().
Settings are tags on the podRepoClient ext record: podRepoChannel, podRepoUri, podRepoCheckHours, podRepoHostKey, podRepoOs, podRepoRestartCmd, podRepoAutoRestart. A value equal to its default removes the tag.
Install
Install from the Pod Updates page, then restart SkySpark once by hand: the previous client cannot restart it. Same API level 1. Needs bassgCommon 3.1.12. Built and tested for SkySpark 3.1.12 (87 checks); the same build is released as 3.1.9.1.2 for SkySpark 3.1.9.
bassgReleaseClient
3.1.9.1.2
Highlights
Restart from the page. "Install selected and restart" installs the chosen pods and restarts SkySpark; "Restart SkySpark" restarts it alone. The page waits for the new boot, then shows the install result in the history.
Settings tab. Channel (stable / beta), repository, check interval, host key, operating system (Linux / Windows / Mac, detected) and the restart command with a default per OS. "Restart automatically after an install" is off by default.
Channel in the header. Switch between stable and beta on the updates page; the repository is checked right away.
New pods. Pods of the repository that are not installed yet are listed as "new" and install like updates.
How the restart works
SkySpark runs the restart command itself two seconds after answering. No script files are written to the server.
Defaults: Linux sudo -n /bin/systemctl restart skyspark, Windows powershell -NoProfile -NonInteractive -Command "Restart-Service -Name SkySpark", Mac sudo -n launchctl kickstart -k system/skyspark. Change the command under Settings if the service has another name.
On Linux the SkySpark service user needs a sudoers rule for that exact command, unless SkySpark runs as root: <user> ALL=(root) NOPASSWD: /bin/systemctl restart skyspark.
A command that returns without restarting SkySpark is reported with its exit code and output; the last attempt is shown under Settings.
Also
Axon (su only): podRepoClientInstall(pods, restart: false), podRepoClientRollback(restart: false) and the new podRepoClientRestart().
Settings are tags on the podRepoClient ext record: podRepoChannel, podRepoUri, podRepoCheckHours, podRepoHostKey, podRepoOs, podRepoRestartCmd, podRepoAutoRestart. A value equal to its default removes the tag.
Install
Install from the Pod Updates page, then restart SkySpark once by hand: the previous client cannot restart it. Same API level 1. Needs bassgCommon 3.1.9. Built and tested for SkySpark 3.1.9 (87 checks); the same build is released as 3.1.12.1.8 for SkySpark 3.1.12.
bassgCommon
3.1.12.2.1
Highlights
Online subscription check. Licenses are checked against lic.bas.co; subscriptions follow the billing state, and every license now has an expiry date. Offline mode keeps a server running without internet.
Warn mode for BASSG extensions. An unlicensed extension that opts in keeps running and shows "Not Licensed" instead of stopping.
No restart for license changes. New or renewed licenses are picked up while SkySpark runs.
Licensing
License requests now send the instance id, fingerprints, points and current licenses, so renewals match the right server.
Enabled projects follow the module's extension.
A "No internet" banner in the licensing view.
The no-license allowance applies only to the Anka Labs organisation, up to 10 points.
Fixes
Licenses load even when the host database is missing; the host database is written atomically.
License records of enabled modules are kept when bassgCommon starts.
cryptoTrustUri is called with the SkySpark 3.1 signature.
A trust entry added by another project is no longer reported as an error.
The module's own project always counts toward the license.
Install
First release through the pod repository. API level 2. Built and tested for SkySpark 3.1.12 (558 checks).
bassgMobilytik
3.1.6.5.3
Highlights
Chart details under the chart. Tapping a bar, line, pie, radar, heatmap, candlestick or coloured history chart lists its values (time, value, unit, band, open/high/low/close) under the chart instead of in a popup that hid the lines on phones.
Heatmap. Tap, summary and colour scale; long spans become an average week.
Web dashboard on SkySpark 3.1.6–3.1.10 no longer opens blank; the backup list no longer errors when it is empty.
Fixes
PointWatch opens a new watch after the old one closed.
Bar charts: colours per series, unit on each value, interval "all" survives the dashboard span; table cards fill the card width; history threshold bands stay inside the chart.
Also
Same API level (5) and functions as the previous build.
bassgMobilytik
3.1.8.5.3
Highlights
Chart details under the chart. Tapping a bar, line, pie, radar, heatmap, candlestick or coloured history chart lists its values (time, value, unit, band, open/high/low/close) under the chart instead of in a popup that hid the lines on phones.
Heatmap. Tap, summary and colour scale; long spans become an average week.
Web dashboard on SkySpark 3.1.6–3.1.10 no longer opens blank; the backup list no longer errors when it is empty.
Fixes
PointWatch opens a new watch after the old one closed.
Bar charts: colours per series, unit on each value, interval "all" survives the dashboard span; table cards fill the card width; history threshold bands stay inside the chart.
Also
Same API level (5) and functions as the previous build.
bassgMobilytik
3.1.9.5.3
Highlights
Chart details under the chart. Tapping a bar, line, pie, radar, heatmap, candlestick or coloured history chart lists its values (time, value, unit, band, open/high/low/close) under the chart instead of in a popup that hid the lines on phones.
Heatmap. Tap, summary and colour scale; long spans become an average week.
Web dashboard on SkySpark 3.1.6–3.1.10 no longer opens blank; the backup list no longer errors when it is empty.
Fixes
PointWatch opens a new watch after the old one closed.
Bar charts: colours per series, unit on each value, interval "all" survives the dashboard span; table cards fill the card width; history threshold bands stay inside the chart.
Also
Same API level (5) and functions as the previous build.
bassgMobilytik
3.1.10.5.3
Highlights
Chart details under the chart. Tapping a bar, line, pie, radar, heatmap, candlestick or coloured history chart lists its values (time, value, unit, band, open/high/low/close) under the chart instead of in a popup that hid the lines on phones.
Heatmap. Tap, summary and colour scale; long spans become an average week.
Web dashboard on SkySpark 3.1.6–3.1.10 no longer opens blank; the backup list no longer errors when it is empty.
Fixes
PointWatch opens a new watch after the old one closed.
Bar charts: colours per series, unit on each value, interval "all" survives the dashboard span; table cards fill the card width; history threshold bands stay inside the chart.
Also
Same API level (5) and functions as the previous build.
bassgMobilytik
3.1.11.5.3
Highlights
Chart details under the chart. Tapping a bar, line, pie, radar, heatmap, candlestick or coloured history chart lists its values (time, value, unit, band, open/high/low/close) under the chart instead of in a popup that hid the lines on phones.
Heatmap. Tap, summary and colour scale; long spans become an average week.
Web dashboard on SkySpark 3.1.6–3.1.10 no longer opens blank; the backup list no longer errors when it is empty.
Fixes
PointWatch opens a new watch after the old one closed.
Bar charts: colours per series, unit on each value, interval "all" survives the dashboard span; table cards fill the card width; history threshold bands stay inside the chart.
Also
Same API level (5) and functions as the previous build.
bassgMobilytik
3.1.12.5.5
Highlights
Chart details under the chart. Tapping a bar, line, pie, radar, heatmap, candlestick or coloured history chart lists its values (time, value, unit, band, open/high/low/close) under the chart instead of in a popup that hid the lines on phones.
Heatmap. Tap, summary and colour scale; long spans become an average week.
Web dashboard on SkySpark 3.1.6–3.1.10 no longer opens blank; the backup list no longer errors when it is empty.
Fixes
PointWatch opens a new watch after the old one closed.
Bar charts: colours per series, unit on each value, interval "all" survives the dashboard span; table cards fill the card width; history threshold bands stay inside the chart.
Also
Same API level (5) and functions as the previous build.
bassgMobilytik
3.1.12.5.4
Highlights
Clean account links. Mobilytik Notify opens the Mobilytik account portal at its new addresses: https://lic.bas.co/mobilytik/register, /forgot and /topics (no #). Older links keep working.
Also
Same API level (5) and functions as 3.1.12.5.3, including the 7-day license grace period.
bassgMobilytik
3.1.12.5.3
Highlights
7-day grace for a lapsed license. When the Mobilytik license lapses, everything keeps working for 7 days and Notify, the web dashboard and the app show when push notifications stop. After 7 days the server stops sending push notifications until the license is renewed; receiving, acknowledging and the inbox keep working. Renewal restarts pushes within a minute.
License checks. Each Mobilytik function has a license policy: most keep working without a license and show a warning; configuration changes and manual sends in Notify need a license.
Clear history. A push that was not sent because of the license shows as skipped, with the reason, in the notification history.
License state for BAS. The server reports a lapsed license to the Mobilytik relay, so BAS can contact you before pushes stop.
Also
mEntitlement() returns licenseLapsedSince, graceEnds and pushStopped.
Works with Mobilytik app 1.0.68, which shows a "Features missing" notice on servers below API level 5.
bassgMobilytik
3.1.12.5.2
Highlights
Mobilytik Notify connectors. Group hand-picked devices and points into a connector class; the console shows when a connector goes down and when it recovers.
Escalation. Device owners, escalation policies and a staging job: a push that is not acknowledged moves on to the next stage.
Staging and Devices views in SkySpark, and a stage column in the console and graphs.
License gate. Mobilytik functions check the bassgCommon license, and the extension opts into warn mode (see "Before you promote").
Notify
Topics carry the kind conn and a stage suffix .s<n>.
Stage rows go only to a relay that accepts them.
Console: acknowledge, resend and tasks work for connector alarms; recovered state.
Stage 1 members always get the push.
Fixes
A connector watch re-reads its records before it removes them.
Closing a connector class deleted elsewhere closes its open event.
A delivery's stage comes from its own topic only.
Only the phone's owner can take over an install id.
Before you promote
This build includes the license gate (5366f891). Promote only after the open questions on trio functions, the web dashboard, scheduled pushes and the deny list are answered.
Install
API level 5. Built and tested for SkySpark 3.1.12 (2246 checks). Needs bassgCommon 3.1.12.
bassgReleaseClient
3.1.12.1.7
Highlights
Pod Updates app. One SkySpark app on each customer server that keeps the BASSG pods up to date from lic.bas.co, with its own icon. It opens with the SkySpark login, so no second password.
Safe installs. Every download is checked before it is written: SHA-256, size, pod name, version and SkySpark line. If one pod fails, nothing is installed.
Backup and roll back. The current pod files are kept for each install; "Roll back last install" puts them back.
SHA-256 against the server. Each installed pod is compared with the repository's record of its version: match, differs, or not in the repository.
The page
Search where every word must match, and filters: updates only, up to date, SHA-256 differs, channel and sort.
Built for 30+ pods: the list lives in IndexedDB and a background worker runs search and filters.
Release date, size and notes for installed pods too, and release notes in a side panel.
Check now asks lic.bas.co for updates; Refresh reloads the page.
How it works
Pods are written to var/lib/fan/ and load at the next SkySpark restart. The client never restarts SkySpark itself.
After the restart the client reports ok or failed per pod to lic.bas.co.
Checks every 6 hours by default. Settings are tags on the podRepoClient ext record: podRepoChannel (stable / beta), podRepoCheckHours, podRepoUri, podRepoHostKey.
su only: the page, its API and its Axon functions podRepoClientCheck, podRepoClientInstall and podRepoClientRollback.
Install
First release. Copy the pod to var/lib/fan/, restart SkySpark, then run extAdd("podRepoClient") in one project. Needs bassgCommon 3.1.12. API level 1. Built and tested for SkySpark 3.1.12.
bassgReleaseClient
3.1.12.1.6
Highlights
Pod Updates app. One SkySpark app on each customer server that keeps the BASSG pods up to date from lic.bas.co, with its own icon. It opens with the SkySpark login, so no second password.
Safe installs. Every download is checked before it is written: SHA-256, size, pod name, version and SkySpark line. If one pod fails, nothing is installed.
Backup and roll back. The current pod files are kept for each install; "Roll back last install" puts them back.
SHA-256 against the server. Each installed pod is compared with the repository's record of its version: match, differs, or not in the repository.
The page
Search where every word must match, and filters: updates only, up to date, SHA-256 differs, channel and sort.
Built for 30+ pods: the list lives in IndexedDB and a background worker runs search and filters.
Release date, size and notes for installed pods too, and release notes in a side panel.
Check now asks lic.bas.co for updates; Refresh reloads the page.
How it works
Pods are written to var/lib/fan/ and load at the next SkySpark restart. The client never restarts SkySpark itself.
After the restart the client reports ok or failed per pod to lic.bas.co.
Checks every 6 hours by default. Settings are tags on the podRepoClient ext record: podRepoChannel (stable / beta), podRepoCheckHours, podRepoUri, podRepoHostKey.
su only: the page, its API and its Axon functions podRepoClientCheck, podRepoClientInstall and podRepoClientRollback.
Install
First release. Copy the pod to var/lib/fan/, restart SkySpark, then run extAdd("podRepoClient") in one project. Needs bassgCommon 3.1.12. API level 1. Built and tested for SkySpark 3.1.12.
Feed for SkySpark servers: https://lic.bas.co/podRepo/api/feed?line=<line>. Every download carries its SHA-256 in the X-Pod-Sha256 header.
