I add a Nuki Keypad 2 NFC to my Smart Lock Ultra

📘🔐 Special file: Nuki Smart Lock Ultra

This article is part of my complete file from installation to accessories to home automation.

When I installed the Nuki Smart Lock Ultra At home, I immediately felt that I had reached a milestone.

Here is the direct link to the previous article: I replace my Danalock V3 with a Nuki Smart Lock Ultra

The lock is faster, more discreet, more pleasant to use on a daily basis, and I finally feel like I have a modern solution.

But after a few days, I realised that I was still missing a link: a simple, immediate and universal way to enter the home, without systematically depending on a smartphone or a physical key.

That's exactly why I added the Nuki Keypad 2 NFC to my installation.

On paper, it is “just” a remote keyboard with fingerprint reader and NFC.

In practice, it is this small accessory that transforms a very successful connected lock into a real family solution, immediately adopted by everyone at home.

🤔 Why I added a Keypad 2 NFC

With the Smart Lock Ultra alone, the experience was already excellent.

I could open with the app, automate scenarios, manage my access and integrate the lock into my home automation installation.

But in real life, there were always the same questions: How does my wife do if she doesn't want to take out her phone? How do my daughters do it? How can I give someone simple access without explaining my home automation? And above all, how can the opening of the door be made as natural as a gesture of everyday life?

The Keypad 2 NFC responds precisely to this need.

Nuki offers several access modes on a single product: code, fingerprint and ‘Tap to Unlock’ via NFC with a compatible smartphone or watch.

👨‍👩‍👧‍👧 A real product designed for the family

The product can handle up to 200 codes, 20 unique fingerprints and 35 NFC keys.

In other words, we are not facing a geek gadget, but rather a system designed for a family, guests, relatives or temporary access.

✨ What this product actually does

What I like about Nuki Keypad 2 NFC, it does not replace the lock: He completes it intelligently.

Installed outdoors, it becomes the easiest entry point for everyone.

You can type a code, put your finger on the fingerprint reader, or approach your phone as you would with a contactless payment.

Apple Home Key or Samsung Digital Home Key can also be used.

And even without a Matter hub, the Nuki app mode already allows NFC to be opened with a compatible smartphone, but with certain usage limits.

📱 Several opening methods

  • Opening by code.
  • Fingerprint opening.
  • NFC opening with compatible smartphone.
  • NFC opening with compatible watch depending on the ecosystem used.
  • Access management directly from the Nuki application.

It is this mixture that makes the product interesting.

Not everyone has the same habits. My wife prefers what is immediate and obvious. My daughters immediately understand the principle of a code or a fingerprint.

For my part, I especially appreciate having several ways to get into the house without ever being dependent on a single method.

🛠 A really simple installation

As is often the case with Nuki, installation is probably the most reassuring thing.

The manufacturer announces a installation in a few minutes, without tools, with a fixation designed for the outside and a guided configuration in the application.

This is exactly the impression I had: the location is chosen, the keypad is fixed, the association is launched in the app, and then the access configuration is set up directly.

📍 The choice of location

I took the time to choose a convenient, visible but discreet location at your fingertips when you arrive in front of the door.

I wanted the use to be obvious from day one, without having to aim for a specific place or make an unnatural gesture.

Once in place, the Keypad 2 NFC integrates very well visually. It remains compact and does not give the impression of a cumbersome technical housing.

⚙ The association with the Smart Lock Ultra

The association with the Smart Lock Ultra was uncomplicated.

The application guides the steps, followed by the creation of access codes, the registration of fingerprints and the setting of rights.

Nuki also provides temporary and individualized access, which allows you to reason quickly in real use.

👨‍👩‍👧‍👧 The test of everyday life at home

The real test was not technical. The real test was the house.

This is always where a connected product reveals its real value: Does it simplify life or add complexity?

On this point, the Keypad 2 NFC clearly surprised me in the right direction.

Acceptance was immediate, and this is probably the best indicator.

💡 An excellent WAF

My wife immediately understood the operation, without explanation. My daughters found the principle obvious, almost playful.

You put your finger down, type a code, approach a phone, and the door opens.

There is no learning curve, no complicated interface, no dependency on an application.

The product disappears behind its use.

🚪 The Uses That Really Change Life

🔢 The Code

The code remains perfect for occasional access or for people who do not want to use an app.

Important point: this is the basis of the operation. You can't configure anything without creating at least one code.

In the Nuki app, I go to Keypad and use:

then

Once the 6-digit code is set, it works immediately.

🧩 Temporary Codes

Nuki makes it possible to create up to 200 codes with precise rules:
– opening hours,
– days,
– repetitions,
– Limited duration.

This is extremely convenient for managing ad hoc access.

Just check "Limited time access" when adding the code.

You can define an hour, a day of the week, a repetition, it is really well thought out.

👆 Fingerprint

This is the simplest method on a daily basis.

For my youngest daughter, who has neither a smartphone nor a connected watch, it is ideal: more key, more risk of forgetting.

With regard to the elderly (grandparents), I have not been able to register certain fingerprints.

👴 Why fingerprints can be a problem?

With age:
– the skin becomes drier (less conductive),
– the reliefs of the footprints are less marked,
– the sensor captures information less well.

Result: the registration may fail.

In this case, the code remains the most reliable solution.

📲 The NFC

NFC is the most “spectacular” feature: We approach his phone as if to pay contactless.

Nuki calls it Tap to Unlock.

📲 The two modes proposed by Nuki

The official documentation is clear: You have to choose a mode.

Nuki app mode Connected Home Mode
It's just a phone call. Smartwatch or phone. 
It must support either the Apple Home key or Samsung Home digital keys.
Unlock your phone first. 
Unlock your phone, then tap it on the Keypad. On iOS, you also need to type a notification. The Nuki app will then unlock your door. No need to open the app manually.
Tap to Unlock instantly.
Unlock using the Home digital key in your wallet. In Express mode, your phone can stay locked.
Nuki app required. Home automation system required. 
You need a Matter-compatible home automation hub. It works with Apple Home and Samsung SmartThings.
Adjust settings and manage users via the Nuki app. Adapt settings and manage users via the Connected Home and Wallet app.
For all users of the Nuki app. For users of the Connected House. 
Must be added via your Connected Home app. iOS users can only add other iOS users, and Samsung users can only add other Samsung users.

NFC 📲 in Nuki Application Mode

I have configured this option: it worked … then non… then again … then more.

This mode requires unlocking the phone, which breaks the experience.

Conclusion: Inconvenient, I give up, especially since it is random.

📲 NFC in Connected Home Mode

When switching to this mode, the Nuki application gives us these indications:

When I click on Open SmartThings, this switches me to the application SmartThings which was already installed on my smartphone.

And now I'm looking for what I have to do … I can't find, I'm going back to look the Nuki Documentation.

I am told to check that:

  • my lock is compatible, it is ok, it is a Smart Lock Ultra ✅
  • my smartphone must be an Apple, that is not my case, or a mobile device Samsung with Samsung Wallet and SmartThings App. I discover this and I am finally lucky, my Samsung is compatible And I have Samsung Wallet and SmartThings App ✅.
  • I also need a Samsung Matter/Thread hub, This is the ⛔ 😰 cold shower.

I don’t have any of the 4 hubs on offer and the link is failing.

While I had read everywhere, on all Nuki’s publications, the information Matter Hub (see image below), for the first time I am being told about SmartThings Hub. I am concerned about that.

I review the documentation and understand that I have confused two things : Hub Matter and Tap to Unlock compatibility, two very different things.

Now I'm a little lost. I have a Nabucasa hub configured in Matter and at this point I do not know if it will be compatible.

The Nuki Help Page is no longer of much help to me.

During my search, I come across this Declaration : "One of Nuki's core principles is to make the new features accessible to all users, regardless of manufacturer," said Jürgen Pansy, co-founder and Chief Innovation Officer.

At this point, this is at odds with what I just discovered because I understand that Apple and Samsung share the cake together.

The last 3 are the modes I have already tested. But here the technique used is precise. It is therefore necessary to Samsung Digital Home Key.

📲 Samsung Digital Home Key – what is it?

Recently, Samsung launched a feature that really transforms the experience: the Samsung Digital Home Key. This is the Samsung equivalent of Apple Home Key on iPhone.

In practice, it is revolutionary: Imagine the typical situation where you arrive at your door, with your hands full:

– Phone locked : no need to unlock it
– Without application : No need to open the Nuki app
– NFC : you're just approaching your phone from the keyboard
– Fast : 1-2 seconds

This is automatic, invisible, and that really feels like a digital key.

The Samsung Digital Home Key is based on the standard Aliro 1.0.

Security is maximum :
– The keys are stored in the Samsung Knox Safe Box
– Protection by biometrics or PIN
– We can Disable remote key
– The key is limited to your lock

🔒 Samsung Digital Home Key with Nabu Casa Matter?

Short answer: NO, I can't. ⛔

Without SmartThings app + SmartThings Hub → Digital Home Key IMPOSSIBLE.

🛑 Conclusion on Tap to Unlock

It's time to close on this Tap to Unlock mode, finally, I finish these essays by disabling it.

In the end, I understand Nuki's logic quite well. By relying on the security mechanisms of Apple and Samsung, the brand clearly seeks to provide a smoother, more modern and arguably more reassuring experience.

It is regrettable, however, that moving in this direction is a step away from the idea of digital sovereignty.

In my case, I did not test further, so I do not know if the information remains only on the equipment, or if some data also transits through cloud services.

And it is precisely this point that, in my view, deserves clarification.

🔒 What opening methods do I finally choose?

Finally, on the Keypad, I will use two modes of opening the lock:

✅ The Code, it is in any case essential, I give a permanent 6-digit code.

✅ The fingerprints, two or three fingers per person in my household, we can add 20.

These two modes are mostly used by my daughters when they come home from middle school or high school.

As far as I am concerned, I have activated Auto Lock mode, which automatically unlocks when I arrive close to home. This mode does not use the Keypad.

🛡 Security: the point I didn't want to neglect

On this type of product, the issue of safety is central.

The Keypad 2 NFC is not a simple generic NFC reader or a basic keyboard.

Nuki says it applies end-to-end encryption for every NFC interaction, fingerprint, and code.

🔐 Why it is not just a clonable badge

Concretely, this means that one does not follow the logic of a rudimentary badge that one would easily copy.

👤 The case of fingerprints

Fingerprints are managed locally on the equipment.

⚠ What you need to know before you crack

📵 The question of compatibility

The Keypad 2 NFC is very convincing, but we must keep in mind that if we do not want to sign an exclusivity agreement with Apple or Samsung, we will be really very limited.

🛍 Finally which model of Keypad to choose at Nuki?

  • Between the Keypad and Keypad 2, there is no photo: If I want the opening with the fingerprints, it is imperative to take the Keypad 2.
  • Between Keypad 2 and Keypad 2 NFC, the NFC functionality appeared. The price difference is ‘only’ €20. Which can make you hesitate.

✅ My Feeling After Installation

On a daily basis, the Nuki Keypad 2 NFC brings exactly what was missing from the Smart Lock Ultra : Simplicity of immediate access, without dependence on the smartphone.

It is clearly this small element that transforms a high-performance connected lock into a truly family-friendly solution.

In my use, the code + fingerprint duo is more than enough and covers 100 % needs. The NFC, although very promising on paper, remains today too dependent on closed ecosystems.

On the security side, Nuki’s approach is reassuring and consistent, although some areas would deserve more transparency.

In the end, the Keypad is not a gadget accessory, it is almost an indispensable element.

Without him, the Smart Lock Ultra remains an excellent technological solution. With him, it becomes simply obvious.

💭 What I would have liked with this product

Despite its high quality, it lacks some features that would make the Keypad 2 NFC even more successful:

🔓 A universal NFC aperture, without being forced to choose between Apple or Samsung. Ideally, a fully Matter/Aliro-compatible implementation with any Matter hub (such as Nabu Casa), without a locked ecosystem. This is probably not a matter for Nuki, but rather for Samsung or Apple, which I am asking to open their doors to ….

📊 A more detailed usage history: know who opened the door, at what time, and with what method (code, fingerprint, NFC). This would be very useful for tracking college feedback, managing speakers, or simply having more traceability.

🔔 Real-time notifications when a fingerprint or code is used, with the ability to receive an alert if temporary access expires or if a fingerprint is attempted multiple times without success.

⚙ Finally, I would have just loved to be able to use the Keypad 2 to open the portal for example. It is ideally placed on my porch, a particular code could trigger a home automation action!!

These developments would make the product not only more universal, but also more suitable for users who want to remain independent of large ecosystems.

I cut my last Tuya from the cloud to keep it local

This is the last Tuya equipment I have left in my entire home automation ecosystem, and it is not just any: It feeds the grip of the straightener and the hairdresser of my wife. In other words, I never took it lightly.

I don’t like Tuya, and I say it bluntly: too many unpredictable behaviours, too many small malfunctions that happen without warning, and, on some Zigbee equipment, a way of doing things that often leads me to think that they are interpreting the protocol a bit to their liking.

For years, this switch has done its job without flinching.

Then one day, nothing on the Home Assistant side. Smart Life, on the other hand, continued to drive it without worry. No clear error, no big alert message, just a device that seemed to ignore me in the wrong place.

🔎 I see the concern

The first clue is that the Smart Life app was still working. I could turn on, turn off, test, check: Everything answered. On the other hand, in Home Assistant, nothing. No obvious mistake, no clear message, just a switch that seemed to go on vacation while the rest of the house continued to live.

I tried the classics: reload the integration, delete and repair, start over cleanly. Nothing was done about it.

On Tuya’s Dev platform, the equipment was offline while it was online on my smartphone.

The most frustrating thing is that you feel like you are dealing with a blurred bug, when in reality the problem was elsewhere.

🧠 I understand why it's blocking

When I looked more closely, I came to understand why. I had just reorganised my local network and split my IP ranges: one party could go out on the internet, the other could not.

The switch had just landed in the blocked slice. Result: more connection to the Tuya cloud, and therefore more correct visibility in Home Assistant.

The decisive test was simple. From my smartphone, while I was on Wi‑Fi, I could still control the switch. As soon as I cut Wi‑Fi and switched to 4G, it became inaccessible.

There, I had the click: Local piloting worked well, but cloud addiction sabotaged everything else.

🔌 I switch to Tuya Local

From then on, the decision was immediate: This last Tuya device was going to come out of the cloud. I no longer wanted to rely on an external service for such sensitive equipment in the house, especially when it directly touches my wife’s hairdresser and straightener.

When a device is used every day, we want it to be simple, stable and, above all, predictable.

So I decided to move permanently out of the traditional Tuya integration to move on to Tuya Local, so that Home Assistant speaks directly to the switch, without going through the Tuya servers for each order.

⚙ I configure the integration

I have installed Tuya Local in Home Assistant, then I launched the Add wizard. And this is where I found the approach rather pleasant: the integration offers a configuration supported by the Smart Life cloud, or manual input if you prefer to control everything yourself.

Installation is very simple, the custom repository of https://github.com/make-all/tuya-local is added via HACS

I then chose Tuya Local integration and let the assistant guide me. I took the first choice that does the job for me.

For my model, Home Assistant automatically proposed a type profile Dual switch with timers, which fit perfectly with the functions of the device.

Just that reassured me: we were not facing a mysterious device, but a double switch with a timer, well understood by the integration.

Next, the technical information had to be checked: the device ID, l’IP address, the local key and the Protocol version.

The assistant did everything, he recovered everything and it took me 2 minutes. I went step by step, and once the fields were filled in, all that remained was to validate.

✅ I turn the switch back on

The result was immediate: the device is reassembled correctly in Home Assistant. The two switches are there, the timers too, and the whole thing finally responds as I expected.

I must say that it feels good to see Tuya equipment finally live its life in my local network, without having to ask for permission from an external cloud for each action.

This is even more satisfying when we know that the latter device was also the most sensitive in the house, the one that we do not want to see become capricious at the wrong time.

Obviously, I am removing the Tuya integration which no longer serves any purpose.

🧩 I learn from history

In essence, this story confirmed to me what I have been thinking for a while: I prefer by far local, simple and predictable solutions.

With Tuya, I have always been wary, because too often I have seen integrations that fail, states that go wrong, or Zigbee devices that load the network instead of serving it.

I am not saying that everything is bad at Tuya, but in my house I have clearly made my choice.

This last switch is now in Home Assistant, locally, under control, and especially far from the whims of the cloud. It was the last Tuya in the house. He held on, but he ended up losing the cloud battle but stays alive locally.

I replace my Danalock V3 with a Nuki Smart Lock Ultra

📘🔐 Special file: Nuki Smart Lock Ultra

This article is part of my complete file from installation to accessories to home automation.

📌 Why this change of home automation lock?

For several years I have been using a Danalock V3 Zigbee on my front door. It had itself replaced an old Danalock in Z-Wave, when I switched my home automation installation from Z-Wave to Zigbee.

She is still doing the job very well, but I wanted to move to a more modern solution and above all better suited to my current installation, especially with Matter in mind. I also wanted to forget the physical keys without multiplying the modules for it. And, quite honestly, I also wanted to get rid of 😇 battery management.

With the Nuki Smart Lock Ultra, What immediately interested me was the promise of a more mature package: Built-in Wi‑Fi, Matter over Thread compatibility, rechargeable battery, universal cylinder supplied and guided installation.

Looking through the official documentation, I also understood that Nuki had not simply sought to make a lock look prettier or smaller. The Ultra introduces a brushless motor, presented as more efficient and sustainable, with a technological approach that the brand brings closer to what is already known in other sectors such as electric vehicles.

In this article, I tell how I went from my Danalock V3, installed in 2023, to the Nuki Smart Lock Ultra, from the removal of the old connected lock to the first tests in the application. I will document in other articles the different modes of home automation connection as well as the interface in Home Assistant.

To tell you the truth, I discovered the Nuki Lock thanks to an opportunity to loan the equipment, I did not know the Smart Lock Ultra, I only knew the Smart Lock Go, the one with a white case under the lock. It was never compatible with my front door, because of the relief/reinforcement on the leaf between the lock and the edge of the door. Read More

I connect an Ethernet camera to Wi‑Fi with a TL-WR902AC

By 2020, I had already achieved this Assembly with a TL-WR802N to add Wi‑Fi to an Ethernet camera.

At the time, the solution met my needs, but over time I noticed regular disconnections, frequent enough that I finally decided to change equipment.

So I took over the installation completely with a TL-WR902AC, with the aim of achieving a more stable and flexible set-up.

My objective remained the same: connect a camera with only one Ethernet port to my Wi‑Fi network, without pulling an additional network cable to the box.

The TL-WR902AC acts here as a bridge: it connects to the Wi‑Fi of the house, then transmits this connection to the camera through its RJ45 port in Client mode.

🔁 I replace my old TL-WR802N

My first montage is from 2020. At that time, I had used a TL-WR802N to give Wi‑Fi access to this Ethernet camera. In principle, this worked, but the installation was not sufficiently reliable over time.

So I chose to start from scratch with a newer model.

The TL-WR902AC I was interested for a simple reason: it also allows the use of 5 GHz, whereas my previous assembly with the TL-WR802N did not give me this possibility in this context.

Read More

I turned my SkyConnect Zigbee into a Thread for Matter

In Home Assistant, a Nabucasa coordinator (SkyConnect, ZBT-1, ZBT-2, …) can either Zigbee, or Thread, but not as a universal radio to do everything at once. In this test, a first key remained dedicated to the Zigbee in production, and a second key was reconfigured for Thread to prepare a Matter over Thread network without breaking the existing one.
Here is the full HTML code of the article, already written in the first person and with the descriptive titles:

📌 Context

My goal was simple: check if a second SkyConnect could become a Thread adapter directly from Home Assistant, without plugging the key into a PC and without touching the already operational Zigbee. I chose this cautious approach because my home automation installation was already working properly, and I did not want to shake everything up.

To avoid any risk, I left the Zigbee key intact. The new key served as a test bed for me, which allowed me to clearly document the behaviour of Home Assistant and to keep my own feedback.

💡 Difference Between Thread and Matter

Thread and Matter They don't mean the same thing. Thread is the radio network used by some low-power devices, while Matter is the standard that allows these devices to speak the same language in Home Assistant. SkyConnect therefore does not “do” Matter on its own: it provides the Thread radio layer, and Home Assistant then manages the Matter integration.

🚦 I start from a SkyConnect already in production

Initially, a SkyConnect was already in service for the Zigbee. I had a second, new key that had never been used before. It was this second key that I plugged into my Home Assistant machine for the experiment.

The choice to separate roles allowed me to clearly compare behaviours: on the one hand the production Zigbee, on the other a radio dedicated to Thread. It was also, in my view, the safest way to test a protocol change without a service interruption.

🔎 I let Home Assistant detect the new key

Once plugged in, Home Assistant detected my new SkyConnect in the Integrations page, in the Discoveries section. The card displayed “Home Assistant SkyConnect / Home Assistant Connect ZBT-1” with a button Add.

At the same time, the other SkyConnect remained present in the configured integrations. This confirmed to me that production was not impacted and that Home Assistant already managed the two instances as two separate devices.

🖱 I start adding from the dashboard

The new map appeared in the ‘Discoveries’ area. I clicked on Add to launch the configuration wizard for this second key.

We can see with this simplicity invented by Nabucasa, I did not need to go through a manual flash or an external tool. The configuration started directly from the Home Assistant web interface.

🧭 I choose the protocol of the key

After clicking on Add, Home Assistant asked me to choose the protocol of the key. Two options were proposed: Use as Zigbee Adapter and Use as Thread Adapter.

This choice confirmed an important point for me: The SkyConnect is assigned to a specific role. I had to choose either Zigbee for a classic network or Thread to prepare Matter over Thread.

🧵 Why I choose Thread

I chose Thread to test the Matter over Thread use case. My objective was not to replace the existing Zigbee, but to validate the creation of a dedicated Thread radio in Home Assistant.

It is also, in my view, the right logic if we want to maintain a stable installation: one dongle keeps the Zigbee in production, the other serves as the basis for Thread.

⚙ I let Home Assistant install OpenThread

Once Thread was selected, Home Assistant launched the adapter update.

At this point, my key was being transformed into a Thread adapter. The procedure advanced in Home Assistant without outside intervention.

 

📈 I monitor the progress of the flash

The progress bar showed the progress of the installation, in particular at 5 %. This confirmed to me that the key was indeed being flashed with the OpenThread firmware.

 

🛠 I complete the configuration of Thread

After the flash, Home Assistant went to the “Configuration of Thread” step.

I then saw messages like “Installing app” and then “Starting app”, signs that the Thread stack was being deployed.

This is when Home Assistant orchestrates the OpenThread Border Router service. In practice, my key becomes the system’s Thread radio, and Home Assistant takes care of the associated network layer.

The Thread network is not just a cosmetic setting. This is a real network setup, with a radio adapter that becomes able to play the role of border router for Matter-enabled Thread devices.

At the end of the procedure, I add the MATTER information so as not to confuse the keys.

My new key appeared with the firmware OpenThread RCP 2.7.2.0. This confirmed that the Thread reconfiguration was successful.

Home Assistant then displayed two separate devices in the Devices tab: a classic ‘Home Assistant SkyConnect’ and a ‘Home Assistant SkyConnect MATTER’. The integration map also indicated “2 devices”.

🧠 I read what it teaches me

This separation is convenient because it visually shows both roles. One key remains associated with historical use, the other becomes the radio dedicated to Thread/Matter.

For feedback, this is a strong point: The reader immediately understands that the migration created a second logical instance in Home Assistant, without breaking the first use.

🔬 What this test proves to me

This experience has shown me that it is possible to convert a second SkyConnect to a Thread adapter directly from Home Assistant. The procedure is integrated, guided, and does not require complex manipulations outside the interface.

She also showed me that Home Assistant knows how to manage the separation between Zigbee and Thread in a clear way. This is particularly reassuring when a Zigbee plant is already in production.

⚠ I keep a limit in mind

However, it should be borne in mind that a SkyConnect does not become a stand-alone hub Matter. Matter remains managed by the Matter integration of Home Assistant; The key here provides Thread connectivity, not all Matter logic alone.

In other words, SkyConnect fulfils for Thread the role that a coordinator fulfils for Zigbee: It opens and connects the network to Home Assistant. The difference is that Zigbee talks about a coordinator, while Thread relies on a border router, and Home Assistant then manages Matter above.

📝 Review and conclusion

Perhaps the most interesting thing about this test is the simplicity of the flow. I kept a key in Zigbee for stability, added the second one as a discovery, then reconfigured it into Thread with just a few clicks.

For someone who wants to test Matter over Thread without touching their existing installation, it is a clean and reassuring method. It avoids disassembly, manual flash and the risk of shutdown on the main Zigbee network.

In the end, the transformation worked as expected. Home Assistant detected my new SkyConnect, offered me the choice of Zigbee or Thread, installed OpenThread, and then showed me a key switched to MATTER/Thread mode with OpenThread RCP firmware.

Above all, this feedback shows me that it is possible to organise your radio roles properly in Home Assistant: one key for Zigbee production, another for experimenting with Thread and preparing Matter over Thread.

I monitor my home network with Home Security Assistant

The security of home networks has become a real concern.

Between connected objects, voice assistants, IP cameras, NAS, smartphones and home automation equipment, our local networks increasingly resemble small corporate networks.

And we will not escape mass attacks by cybercriminals.

After several years of upgrading my home automation system, I wanted to add a passive network monitoring layer:

  • without impacting performance;
  • without changing traffic;
  • and without turning the grid into a gas plant.

Read More

I monitor the reputation of my public IP in Home Assistant

I spend a lot of time monitoring, securing and understanding what is happening on my home network. Between the internet box, the unintentionally exposed equipment and the permanent scans from the internet, I once wondered one simple thing: Is my public IP known as “noisy” or suspicious on the internet?

That is, malicious tools use my network (pc, NAS, router, HA, …) ??

That’s how I came across GreyNoise, a really interesting service that makes it possible to know whether an IP address is part of the “noise” of the Internet, i.e. whether it is observed in scanning, polling or malicious traffic activities.

GreyNoise rightly describes its approach as a way to qualify the background noise of the Internet and contextualise an observed IP.

And as often with me, after a few tests, I thought: “Well, it would still be convenient to have this directly in Home Assistant”.

Initially, I thought I would do something very simple with a classic HTTP request. On paper, it seemed trivial. In practice, the most obvious method did not work for me as I had hoped. So I changed my approach and finally switched to a command line sensor. In this article, I tell you all this step by step, as I actually set it up at home, with the Lovelace cards for the final display.

Read More

I'm testing the Voice & Music Assistant Dev Edition by Third Reality

When we think of voice assistant for the house, we still think very quickly about Alexa, Google Home or, on the open home automation side, at Home Assistant Voice Preview Edition from Nabu Casa.

That is precisely why the THIRDREALITY Voice & Music Assistant Dev Edition intrigued me. It promises both voice, home assistant integration and a real audio role with Music Assistant.

I therefore did not want to test it only as a voice satellite. What I wanted to know was whether it could really become a useful little audio player in a Home Assistant installation, able to play a local MP3, broadcast an internet radio and drive cleanly from Home Assistant. In short, check whether it is a simple curious product or a device that really deserves a place in the current home automation ecosystem.

In this article, I take the whole route, from unpacking to commissioning, then to the first concrete audio uses with Music Assistant, RadioBrowser and a station launch in YAML. This test is also an opportunity to replace this box in front of the official product of Nabu Casa, but also in the face of wider public solutions such as Alexa and Google Home.

Read More

Néo reviews the sealing of its external siren Zigbee NAS-AB06B2

I still remember this early December 2025, my siren Zigbee outdoor NEO NAS-AB06B2, star of my initial test and my Zigbee siren comparison, had gone offline.

I climb the ladder, I dismantle … and there, disaster: full of water, the circuit soaks. I try an emergency resuscitation, nothing to do, the battery works perfectly, it is full, it is the electronic card that does not leave. Rip the mermaid!

More than a year of impeccable service reduced to nothing by inadequate sealing. I was disgusted because it was the only real good outdoor siren Zigbee.

My doubt at its reception was the ability of the solar collector to hold over time, its ability to provide more energy than the siren consumes, it worked perfectly, the fault of the siren was its tightness.

Once the mourning has been done and I admit to many requests from visitors to my blog who asked me for news of my mermaid, as it also came to them to make their souls determined, I order a new one. NAS-AB06B2 to autopsie the problem and offer my loyal readers a tutorial to tweak with putty. And there, total surprise! When I open it, I discover that NEO has reviewed its copy: the manufacturer had to receive tons of returns like mine and upgraded the model without changing the reference. Without indicating anything on the box, but by making some modifications that I will present to you.

Read More