IotConnectionCheck is append-only without @Immutable (every link failed with a 500)
Hibernate 6.5 reads the database-generated checked_at back after the INSERT and then sets a lock mode on the entry; an immutable entry refuses it **************...
The /features metadata names IoT Devices only once it is announced (SP14)
Share devices from the device page and the Devices list through SP04's dialog; one sharing client
Keep @kamo/realtime at its range — chat-core pins 0.1.2 and IoT topics come from @kamo/iot-core
The sharing and SI settings tabs carry their tour anchors as literal attributes
The /settings/iot page - tabs, help, settings-menu topic and landing section
Settings, alarms - maintenance and design suppression, quality figures, and the tab
Settings, alarms - rules with preview and backtest, and escalation policies
Record the SP10 plan deviations and execution decisions in master section 10 [skip ci]
/iot/shared - outgoing shares with keyset paging and safe row actions, the details drawer, and shares received
See-also links for the IoT Devices area (SP14)
Every IoT page gets 3 to 6 links. Eleven existing pages' links change because the new category exists (listed in **************** for import --relations-only). ...
IoT Devices voice, phone, SI, administration and health articles (SP14)
Amazon Alexa (linked from the Alexa app; the skill's own name is the only brand word allowed), what Alexa can and cannot do, KamoMobile, how SI members use devi...
IoT Devices access, sharing, automation and alarm articles (SP14)
Access grants and who-can-do-what, sharing with a named person or a link, revoking, opening a share, one-time codes; automations, backtests, site modes (Occupie...
IoT Devices connection articles (SP14)
One How to Connect article for each of the sixteen services that link with an account or a key, linking Google Home or Apple Home from a phone, what a connectio...
IoT Devices getting-started articles (SP14)
Six hand-authored articles: what it is and is not, turning it on (Settings → My Account → Apps & Features), sites and spaces, which services can connect (no ven...
The IoT Devices area: category, seven sections, the roster, the claims rules and their tests (SP14)
The category iot-devices is appended after Cameras (sort order 18), so no existing category moves. The manifest keeps every existing entry exactly as committed ...
The Advanced tab marks the simulator as a test tool that cannot be enabled (SP14)
The view gains testOnly; visibleActions never offers ENABLE for a test-only connector (the server already omits it); TEST_ONLY_PROVIDER and the four simulator t...
The automation builder - actions, save-time confirmation, webhook secrets, test and backtest
DRAFT FOR COUNSEL - list the connected-device clauses on the Terms and Privacy pages (IoT SP14, T-31)
Material change under Terms section 15: effective 30 days after this goes live. Branch iot/sp14-legal-draft only; never push before the owner says counsel appro...
DRAFT FOR COUNSEL - list the connected-device clauses on the Terms and Privacy pages (IoT SP14, T-31)
Material change under Terms section 15: effective 30 days after this goes live. Branch iot/sp14-legal-draft only; never push before the owner says counsel appro...
Guard that the Terms and Privacy pages and their dictionary text land together (SP14)
The generated device-compatibility page and its copy guard, closed until announced (SP14)
The list is the live feed; the words are dictionary copy; a gap fails the next build.
IOT_ANNOUNCED flag, the unheld-claims guard, the /features category and the capabilities group (SP14)
Nothing is announced: the flag defaults false. The guard scans only the new IoT copy.
GET /api/public/iot/providers, the device-compatibility feed (IoT SP14 D2)
IoT Devices on every paid KamoUniverse rung and no free one (IoT SP14 D3)
KAMO_SIMULATOR, the 22nd provider type (test-only; SP14)
Appended last; the client catalogue JSON keeps the 21 program types (@kamo/iot-core is unchanged).
Remove a committed diagnostic log that carries the database password and the password pepper
k8s/diagnose-output.txt (2025-11-03) is a startup log captured with com.zaxxer.hikari at DEBUG. Nothing reads it. Removing it does not clear history; the values...
Stop logging the database password at startup
com.zaxxer.hikari at DEBUG makes HikariConfig print its whole configuration on every start, including dataSourceProperties {password=...} and password......; Pr...
Stop logging the database password at startup
com.zaxxer.hikari at DEBUG makes HikariConfig print its whole configuration on every start, including dataSourceProperties {password=...} and password......; Pr...
Stop logging the database password at startup
com.zaxxer.hikari at DEBUG makes HikariConfig print its whole configuration on every start, including dataSourceProperties {password=...} and password......; Pr...
Stop logging the database password at startup
com.zaxxer.hikari at DEBUG makes HikariConfig print its whole configuration on every start, including dataSourceProperties {password=...} and password......; Pr...
Stop logging the database password at startup
com.zaxxer.hikari at DEBUG makes HikariConfig print its whole configuration on every start, including dataSourceProperties {password=...} and password......; Pr...
Stop logging the database password at startup
com.zaxxer.hikari at DEBUG makes HikariConfig print its whole configuration on every start, including dataSourceProperties {password=...} and password......; Pr...
Stop logging the database password at startup
com.zaxxer.hikari at DEBUG makes HikariConfig print its whole configuration on every start, including dataSourceProperties {password=...} and password......; Pr...
Stop logging the database password at startup
com.zaxxer.hikari at DEBUG makes HikariConfig print its whole configuration on every start, including dataSourceProperties {password=...} and password......; Pr...
Stop logging the database password at startup
com.zaxxer.hikari at DEBUG makes HikariConfig print its whole configuration on every start, including dataSourceProperties {password=...} and password......; Pr...
Stop logging the database password at startup
com.zaxxer.hikari at DEBUG makes HikariConfig print its whole configuration on every start, including dataSourceProperties {password=...} and password......; Pr...
Like what you see shipping?
All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.