Global Moderators group | Smart Home

CatmanV2

Today marks another milestone in my Home Automation journey.

After tripping the main breaker once, and shedding more blood than is normally recommended, the underfloor heating (which was the last Z-wave device on my system) has been replaced with a Zigbee one.

Edited reactor.conf
Disabled z-way-server
Disabled Openluup

Z-wave is no more....

C

toggledbits

I'll see what can be done later, but this comes from a package I use, not code of my own creation. Despite the bug discovered, if I abandon the external package, I lose years of testing against myriad servers in the wild, so it's a potentially costly trade-off that makes a lot of future work (and frustration, potentially).

toggledbits

Reactor build 26143

If you are upgrading to this build from 26011 or earlier, please read the cautions for build 26116!

Reaction Editor: fix an issue where non-group actions could not be cloned.
Docker images: add ping command to underlying minimal OS packages.
HTTP Request Action: a bug in an underlying package dependency caused digest authentication to ignore a server's suggested/supported digest algorithm. A workaround has been put in place and tested successfully against servers requiring SHA-256 and SHA-512-256, in addition to the now disfavored MD5.
HassController: Bless HA to 2026.5.4

toggledbits

Got it. Next build... tomorrow, or Sunday at the latest.

toggledbits

OK. I've respun 26140 docker images with some additions to the underlying minimal OS. Grab the updated image for your container and you should have ping back.

toggledbits

Well... isn't this interesting... I tried to find a reliable SHA-256 endpoint to test against. Pretty much everything I tried went to MD5. So I wrote my own that I could restrict to a specific hash algorithm, and lo! and behold! I found a bug in the digest-fetch package... if it attempts auth with an algorithm and the server responds with a different algorithm (i.e. what it supports/prefers), it simply re-issues the same request with the prior algorithm rather than trying the server's suggested algorithm. Mind you, this package has been like this for years (like maybe 2019?), and the last big check-in for the package was three years ago and not about this.

So quick and dirty, I wrote a wrapper around it to do the right thing, and it should properly support SHA-256, SHA-512-256, and MD5 (in that order of preference for now). That will be in the next build (soon).

Edit: the fix for this issue was made in build 26143.

toggledbits

Have you tried it?

toggledbits

What architecture are you running the container on?

toggledbits

Easiest/quickest is to just change the name of the integration entity.

Or, you can filter out the entity in your HassController config:

  - id: hass
    implementation: HassController
    enabled: true
    name: Home Assistant
    config:
      # ...other stuff...
      filter_entity:
        "integration_01J9VP...etc": true  # filter out integration with specified ID
        "/^integration_/i": true  # filter out all integration entities

Global Moderators

Posts

Reactor build 26143

Member List