Whew! If that was anything, it was the work of an aging magician.

Thanks for sticking with it and supplying good info.

OK. Please pull 25310 (aka latest) again. I've patched HassController for this change.

OK. I think I've got it. Pull it once again and restart... this time for sure!!!

It's not mentioned in a substitution somewhere?

Where else are you using that variable, and how?

No errors now?

Yes, please reproduce. Level 4 is fine. You can also set gvar_debug: true in the engine config section -- that will be verbose but a lot less verbose than level 5.

OK... I found the PR in HA's code and the reasoning behind it. They are trying to make their data/responses more compact (performance reasons). I will have an updated build shortly for this change.

Can you show the log starting with "expression alarmTest has changed" (context before the error message)?

OK. I'm on this. See my previous post above yours. HA changes the way the definition of some services is published -- there's now no data/detail where there used to be data/detail. I'm not sure if that's an error they'll correct later, or if that's a new way of saying "just use the default behavior" (which in this case is pretty easy to guess). I will have a workaround update published shortly.

FWIW, specifically, from 2025.10.4:

        "homeassistant": {
            "save_persistent_states": {
                "name": "Save persistent states",
                "description": "Saves the persistent states immediately. Maintains the normal periodic saving interval.",
                "fields": {}
            },
            "turn_off": {
                "name": "Generic turn off",
                "description": "Generic action to turn devices off under any domain.",
                "fields": {},
                "target": {
                    "entity": [
                        {}
                    ]
                }
            },
            "turn_on": {
                "name": "Generic turn on",
                "description": "Generic action to turn devices on under any domain.",
                "fields": {},
                "target": {
                    "entity": [
                        {}
                    ]
                }
            },
            "toggle": {
                "name": "Generic toggle",
                "description": "Generic action to toggle devices on/off under any domain.",
                "fields": {},
                "target": {
                    "entity": [
                        {}
                    ]
                }
            },

Compare this to 2025.11.0:

        "homeassistant": {
            "save_persistent_states": {
                "fields": {}
            },
            "turn_off": {
                "fields": {},
                "target": {}    # <--- where did the detail go???
            },
            "turn_on": {
                "fields": {},
                "target": {}    # <--- where did the detail go???
            },
            "toggle": {
                "fields": {},
                "target": {}    # <--- where did the detail go???
            },

Odd. I'm not able to duplicate this, and there's a message missing from the log that I would expect to see in conjunction with the other messages. Can you re-apply the build and restart, and try again?

I need to see device attributes for those devices (from the Entities list -- use Copy Attributes and paste as fenced code block, no screenshots please). Also would be helpful to see the hass_states.json and hass_services.json from the logs directory, but these are larger. If any of you are willing to upload them, let me know and I will provide you a link.

Edit: it looks like HA 2025.11.0 breaks the homeassistant domain commands (turn_on, turn_off). I'm digging more into that, to see if it's a change to their required parameter structure, or just brokeness, but HA does not reply with an error when those services are attempted, and that's usually what happens when parameters/service definition changes.

Edit 2: ...and a little more info. The service data published by the API in 2025.11.0 now omits the target data detail. That's odd. Maybe they are assuming that when target data is empty, just supply an entity? I need to dig through the release notes. But, easy to work around.

Can you show me an alarm tick message?

Please read the posting guidelines and update your original post with the information that specifies.

Respun again. Give it a try.

Just debug elevated. Next build it will be quiet.

OK. I respun buld 25310. Pull the new zip and give it another go.

Reactor build 25310

IMPORTANT: This build was patched and re-released to address a compatibility issue for Home Assistant 2025.11. If you pulled this release before 1pm Eastern Standard Time (18:00 UTC) on Friday Nov 7, please re-pull/re-install this build to get those fixes.

• Expressions: restore ability (lost in 25304) to define a custom function in a global variable/expression and have it be available to other expressions.
• HassController: Bless HA to 2025.11.0

OK. Build 25310 is up.

I never cease to be amazed at some of the clever angles you all come up with.

Give me a day or two...