u/cyclingroo

First, let me start by thanking the pfSense team.

I have completed my installation of the latest pfSense+ version. And it is working well - thus far. But as anyone who has done this before knows, new versions often lose installed packages. This is the case for the "official" pfSense API. I suspect that

Second, I want to thank those responsible for the pfSense REST API.

I have used this API to manage my router since I deployed 2026.03.1. And the API is great! When coupled with the pfSense Manager app (on my mobile device), I can do almost all management tasks remotely. This is monumental for me.

But as I have now moved onto the bleeding edge support case (i.e., I just installed a new release only a day after its official release. So, as of this moment, I no longer have official / supported API access. And I hope everyone knows that these things take time. I certainly know this. But is anyone aware of when 26.07 will be supported on the latest release? I'm not in a hurry. I can hold my horses. But I was wondering if a tentative date (or set of milestones) has been set.

I have successfully updated my Netgate 420 to the latest firmware (i.e., 26.07). So far, the system is operating nominaally. I did have a hiccup when I turned on the ThreatGate capability. CPU went high - and stayed high for a very long time. But I suspect that this is because ThreatGate uses MaxMind. And my system was probably loading data using my MaxMind API.

After almost twenty minutes, things started settling down.

I get whey the main Nexus controller may have an immense amount of memory. After all, it is keeping data that will be distributed to one or many nodes. But I was utterly shocked when I saw that my overall system memory used had climbed to 60% and that the memory used by the controller had climbed to 91%. Things are operating nominally. But I am having difficulty finding out where I allocate memory to the controller. I'd love to add a bit more memory to the controller. This should not markedly affect anything on the Netgate that is for my household (and acts as the controller). I just get a little nervous when I see a management app using over 90% of its allocated storage.

I've had a Yale Assure 2 (nee August) lock for over four years. And it has started to misbehave. In particular, the Yale WiFi Smart Module has begun to fail. At first, it was a few times a quarter. And over the last year, it has been a few times a month. And in the past few months, it has been a few times a week. The problem is that the device drops off the network. And yes, I've done an RF survey. And it is _not_ a problem with my WiFi infrastructure. Indeed, I have doezens of WiFi devices, and the onloy one with a problem is my Yale lock. And no, it's not coverage drops and/or distance from the AP. I've evaluated that. And I've put other devices within feet of the Yale lock. It is just the lock - and probably its WiFi Smart Module.

SO, what have I done.

I've gone ahead and purchased a Yale Zigbee Smart Module. And that device arrived today. And I've reset (from the app but not the hardware button). And I have a Zigbee infrastructure that includes an ancient Philips Hue hub and A shiny, new Aqara M3 Zigbee / Matter / Thread hub.

But as of this writing, I've tried to get the M3 into scanning mode and then used the <door-code> -> + Gear (icon), followed by "7" + Gear (icon), followed by "1" + Gear (icon). But the device does not appear to be discoverable by my M3. [Note: The M3 is within direct [and unobstructed] line of site and within thirty-to-forty feet of the door lockh.

I can certainly use the lock with Bluetooth. And I do have a Tuya Bluetooth Gateway. But I can't get the Yale lock to be discoverable via Bluetooth.

I can always add a different Zigbee router - including the ordering of a ZBT-2 from Nabu Casa. But I hate to buy more simply to solve something that should be easily resolved.

Do any of you have any thoughts on how I might proceed?

Please and thank you.

Team,

I have been in "the IT industry" for almost fifty-years. And in that time, I've built systems, I've secured systems, and I've monitored (and managed) systems. While all of that has been gratifying, it has also been exhausting.

But now, I am focusing on writing and consulting. I've been working with AI (or its look-alikes) for decades. It started with LISP and Prolog. And it is blossoming during the current AI wave. While I've terrified by AI [due to over a hundred years of media fear], I'm starting to gingerly embrace it. And I think that there is a book that will spring out of my efforts.

In the meantime, I've decided to use lightweight AI to help operate my household. As a Home Assistant user, I've been "lighting up" my household for over eight (8) years. Many spare coins go towards new doodads and thingamabobs. And a lot of time is going to their management. And within the past two weeks, I've started to deploy model context protocol (MCP) services for a good integration backbone. As a Wazuh user, I've been using the wazuh-mcp server. As a Home Assistant user, I've been using the ha-mcp server.

These two MCP servers have been amazing. And their value has sparked additional MCP ideas. This week, I've designed, developed, and deployed two (2) additional MCP servers. One of them is an MCP for container info (i.e., docker-engine-mcp). The other is an MCP for Uptime Kuma. I have almost fifty devices and services that I need to manage. So, I've got a UK dashboard built and deployed. And I've also wired it to my Home Assistant system via webhooks. Now, whenever a critical system (or service) goes offline, I am alerted via native Home Assistant capabilities.

The code is monstrously simple. And its backbone was actually created using Claude Code. [Note: And no, Claude does not have any of my API tokens.] I am thinking about releasing this code under a permissive MIT license. Would anyone else find this useful? At the same time, would you find a Portainer MCP to be valuable as well?

Your thoughts on this matter would be much appreciated.

I am a very seasoned IT systems management professional. And over the last eight years, I've also been on a voyage that is like the voyages experienced by every other person within thsi subreddit: I am using Home Assistant to manage an infrastructure complex infrastructure.

As my envirnoment matures, I need to spend almost as much time with processes as I spend with the technology. Consequently, I've decide to spend additional time on technologies that assist with management processes. And in particular, I want to spend time with monitoring and management.

To that end, I've depoly Uptime Kuma on one of my infrastructure servers. And it is monitoring almost four dozen systems and/or devices. I've put together a good system of tagging these devices. And I've started to use webhooks to as a means of altering me about critical outages. The flow of the webhooks is simple: Uptime Kuma detects a down event. When that event is detected, it is sent via webhook to Home Assistant. And Home Assitant automations are in place to send me relevant notifications. And this works quite well.

Now, I want to up my game a bit. I'd like to get more than the info that a webhook provides. So, I'm looking into using the Uptime Kuma native integration. I've been able to install that itnegration. I've create an API in Uptime Kuma. And I've gotten the integration to provide two entities. One is a version / revision history. The other is a specific event about one of my systems that went down. But it stops at that point.

Here are my questions:

- Should I epxect to see an entity for every monitor in Uptime Kuma?
- Should I expect to see an entity if/when a montor detects a failure?
- At this point, I'm wondering whether it would be better to install the Uptime Kuma addon so that the monitoring instance is on the same same infrastructure as my automation engine?

Your attention to these queries is greatly appreciated.

I went to our bedroom last night. And as I finished my nightime recap on the state of the world [via phone], I called out [to my voice assistant] to turn off the lights. And my voice assistant proclaimed that I couldn't reach the lights. I assumed that this was because of a problem with the Hue lights. [Note: I have both a lot of Matter bulbs as well as a smattering of legacy Hue lights. And it was the Hue lights that seemed to be affected - or so I thought.] But as I jumped onto my phone and checked out the Hue app, I was able to turn off the lights. So, I left the issue until this morning.

Now that I have gotten a few hours of sleep [and a recent infusion of caffeine] it is time to test things out. FWIW, I hate loose ends.

I started by checking out whether it was a problem with my Hue bridge. I restarted the bridge - just to be safe. Unfortunately, there was "no joy" on that. I guess that I'm glad. I'd prefer to know that I had a problem [with a specific device] rather than just doing the three-finger salute equivalent (i..e., just restarting the system). And FWIW, I did restart my Home Assistant system as well.

So, it was time to log into HA and check things out. I logged in with the local URL - from my phone. And things were working. In fact, I could go to the pages that I've set up for each room and I could toggle the lights on and off. Apparently, it was only the voice assistant that was affected. [Note: I must admit to using "Madame A" for voice control. Yes, I block the telemetry out of the house. But my spouse is so accustomed to the voice peculiarities of "Madame A" that I really want to get this integration back online.]

I looked at the status of the HA cloud. And it was not logged in. That was unsettling. But I've seen it before. My firewall / router sometimes blocks my access to their public IP. To be precise, Snort tags the public IP for abuse. And then suspends access. So, I clear out the snort cache and things usually work. Well, not this time.

Basically, I can reliably connect to Nabu Casa. At first, I didn't have an active connection. So, I forced a signout. And I logged back into Nabu Casa. This time, I saw a valid remote URL. So, I figured that I finally found the root cause. But I am not so fortunate.

As of this moment, I can connect to Nabu Casa (via a direct login using my browser). And I have restarted things - a few times. But I can't get "Madame A" to mange the in home devices. I've validated a good connection to Nabu Casa. And I've double-checked the 'Voice Assistants' menu in Home Assistant. I've flipped the assistants off and then on. And I've disabled and then re-enabled the remote management access. So far, I'm still experiencing "no joy" on this issue.

Any ideas, team?