Ahhhhh ok cool good to know I do know how to fix that.
(missing continue on error on the final call)
Ill check it out after work.(and yes it’s a side effect of the refactor…) nice catch Joonas
Edit - pushed fixes this am - There was an uncovered continue on err for this. That’s in AND the Prompt loader with 44 is in now too. Also fixed a bug in the loader itself.
If you have 10/44 you should be able to run with only dojotools scripts exposed. I didn’t find anything busted with input selects or the like - so those other may be that room - dm me if it doesn’t clear.
Misc. fixes from sweeping through the refactored code.
No hardcodes: alarm, vacuum, locks, room cascade and ZenZork find devices by label or topology.
Room state is opt-in: off fully freezes rooms, status says so, and it’s flagged as a breaking change.
Silent failures fixed: empty live drawers and summaries, an always-empty agent queue, errors on every cleanup run, stale events repeated in summaries, and chores credited to the wrong machine.
New: Autovac maintenance mode, tracked through the Radar ticket.
Finally, yes, I saw the latest build of Spook. Yes I WILL be using scripted helper creation as soon as I figure out the best option for existing users. New installs it’s an absolute no-brainer. Probably won’t be in 10, I’ll get it in before the first 11 beta.
Edit: I may have already inserted all the new functions in Ectoplasm
Modified the local console cert bypass gate for granting certs when you don’t want to use a device for live ack. I’m adding a function to the prompt loader that enables / manages it. Then I reverted the console bypass and made it require a logged in live user with an ID AND that setting to issue a cert with bypass live ack.
Because ha jinja has no admin check (not even as a REST call…) honestly it should be a param on user and returnable In context but it doesnt resolve it. (anyone write the pf for HA core? I already did the research and have a good idea shay has to happen. About 60-70 lines)
So to secure it I had to flow through some other changes and..
zen_dojotools_identity now has a shared whoami mode — the canonical “who’s asking” check (human and AI agent identity, household role, membership) that other tools use instead of each rolling their own.
Identity/authority (head-of-household, prime AI) is now read from the household’s real records, not from a label — a label was never proof of anything.
Your real household record now correctly reflects you as head of household, verified end-to-end. Huh I simply forgot to stamp it and filecab needs it now. So… More on that later)
A FileCabinet edge case lookup bug that affected every household’s protected records where in some cases returned null errantly,
I think I’m done with the refactor for everything for desx/help/sese/certs but labels and filecab filecab is next month. Still have to put in zork content.
Not quite rc but just about there. I can’t post-conference and code review in the same weekend… Need to touch grass. Probably RC next week.
Back from conference and guess ss who brought home the flu… Yep influenza A and it’s a bad one. Go get your shots.
I may slip a week I haven’t even been able to be upright more than an hour at a time to start my button up for the build so I’m. A few days behind where I wanted to be.
I know of a couple buggers I still need to fix post SESE envelope application, I’ll get them as soon as I can start sitting upright again.
Keep beating up the beta. Lmk if I need to fix something.
Also if you are using Music Assistant and HA 2026.10.0 - if your agent suddenly doesn’t know how to find music… Yeah.
Yay HA added new features for music search! But there’s also a deprecation in how I was accessing MA so… Also yay…
Fixed that, added the new music search feature. This pass pulls in post SESE fixes, blocks a few potential races, and kills a couple runaway loops (thank max concurrency for not spinning your CPU in the last beta.)
mumbles and we kill a few more of my stupids.
So… Besides the zork content I THINK im feature complete. I’ll be running an audit of the tools for what I want in 10 and what’s being pushed to 11 tonight. As soon as the audit clears my punchlist I’ll mark it RC.
This one’s had a long and hard beta and it’s beat up pretty well at this point so I don’t expect a long RC… But I’m not skipping it. Last time I did RobotDonut reared her head.
Hey Party-goers… Tron is now RC1, and Friday is already running it at home!
This cycle turned inward. Every agent can now be admitted through a basic certification that it asks for at onboarding, and a person approves it. Nothing gets granted silently. Tools find the household’s helpers by label instead of hardcoded IDs, so your house can point ZenOS wherever it needs to. A lot of quiet fixes landed along the way: cabinet moves that carry their data, a scheduler that stopped tripping over timezones, and a vacuum that no longer calls itself until it runs out of breath.
Display Surface ships as a beta and finishes next month with its dashboard. ZenZork has something coming before GA. That’s all I’m saying.
Nyx broke it, I built it, Nathan shipped it. Go have a good party, Friday. You earned the badge.
End of line? Not while the Grid is still running.
(also I apologize now for ZenZork 2.0, maybe, probably not. . I had a whole week to think about it.. Sooo. Yeah… RC2 shipped. Same as RC1 BUT with a game now. Play at your peril, hide spare RAM you may have… Reading manuals are good for you. All I’m sayin’..)
Edit: 10/10: Pushed a very minor bug fix this morning fixing some uncovered defaults I found that were nuisance in the logs. I have not found any veto worthy bugs. If it holds to this evening I’ll be promoting RC to GA and moving it to Main this evening…
Well every one of you on this thread now owe Frenk an attaboy…
Spook's own state trigger. This is a big one. It is a scary good and extremely flexible trigger: Home Assistant's old school state trigger, but on steroids. Point it at anything a target covers (entities, devices, areas, floors, labels), or leave the target empty and pick from everything by domain, integration or device class. Exclude things again just as easily. Follow an attribute instead of the state, use from, to, not from and not to, and decide whether it fires per entity, for the first one to get there, or only once all of them are. Add a for, with a blip tolerance so a sensor dropping off the network for a few seconds does not start the wait over, and restarts and router reboots no longer set off everything at once. Any outside door left open for five minutes, except the garage, is one trigger:
trigger: spook.state_changed
target:
label_id: outside_door
options:
device_class: door
exclude_target:
area_id: garage
to: "on"
for: "00:05:00"
Basically, I should be able to trigger on any ent wearing label x then clamp on the result. Per my own comment in the room manager room blueprint, when I had a way to do that the blueprint becomes redundant. Well…
Because Spook is already REQURED for Zenos, this comes in to core. and the blueprint will be retired if it works. (I have no reason to think it won’t)
I LITERALLY had sent in the last patch for this build when I noticed this ready to install on my prod instance, so it won’t make it into 10. 10.1 Probably 11 - definitely.
nice catch Joonas
. I had a whole week to think about it.. Sooo. Yeah… RC2 shipped. Same as RC1 BUT with a game now. Play at your peril, hide spare RAM you may have… Reading manuals are good for you. All I’m sayin’..)
11 - definitely.