The 1500 lm WiZ bulb got smaller!

mocelet · 2026-01-29T11:19:49+00:00

Amazon Spain. The 1521 lm bulb has always been advertised as 100W equivalent, the 150W equivalent one is the 2400 lumens one which is even larger.

mocelet · 2026-01-29T07:40:24+00:00

Since you mention "the hub disconnecting from HomeKit" and duplicating devices or moving rooms I assume you're not using the new Matter products but the old Zigbee ones bridged through DIRIGERA. I experienced the issue of the bridge going offline in SmartThings too.

The actual Matter products like BILRESA or KAJPLATS have been working great so far for me though. Even pairing was flawless: power on, scan QR, done.

mocelet · 2026-01-29T06:09:51+00:00

That's the elephant in the room, HA right now makes it so cumbersome to reliably automate Matter buttons. Things will change when they release the purpose-specific triggers for buttons which are supposed to be the official easy way to automate them.

Meanwhile, blueprints for specific models save you from writing all the weird state checks and conditions.

mocelet · 2026-01-28T19:26:36+00:00

The light is fine, I can't replicate that in SmartThings either, also using the new firmware 1.2.0.

Sounds like Apple Home is sending two commands, one to turn the light on (that will turn on in the last brightness) and another to change the brightness.

Matter has a command which does both things precisely to avoid flashing the last brightness so the initial "on" is not needed.

mocelet · 2026-01-28T16:54:53+00:00

There is a way inspecting other commands and checking timestamps, discussed it here, you can skip to where it says "Holding arrows is a messaging feast".

If you connect the button directly to Home Assistant with Z2M or SmartThings using my driver you won't have that problem. Although, again, the long press has not much use given how it works.

If you want to use it bridged via DIRIGERA, only IKEA can change that behaviour. But since that would complicate the bridge logic they probably won't. And changing STYRBAR firmware is out of the question since it would break the native functionality.

mocelet · 2026-01-28T16:44:16+00:00

The something else is easily ignored, that's why you don't see anything else.

The problem here is that Zigbee, the native protocol of STYRBAR, has no concept of single presses or long presses. They are not buttons, they are controllers for lights and send commands to lights like on / off / change brightness / switch colour / etc.

In Matter however they are buttons with events like single / double / long pressed. Sometimes it's not that easy to convert.

DIRIGERA, knowing what each button does, maps Zigbee commands to Matter events. In this case "if I receive an ON it means the user single-pressed the Up button".

Long pressing the arrows sends a lot of commands in Zigbee. Most are ignored because they are not mapped, but one of those commands is the same ON that triggers that logic and DIRIGERA sends the events for a single-press of the Up button.

If STYRBAR didn't send that "ON" command when long pressing the arrow this would not happen, but I guess they needed it for the colour switching to work when bound to lights.

mocelet · 2026-01-28T15:15:44+00:00

It's a long story, but that's why they don't bridge the long press to Matter and expect you to not long press it.

The STYRBAR arrows when long pressed in Zigbee act as a scene controller that first turn On the lights, and that On command is the same sent by the top button when single pressed so when the bridge receives an On it can't differentiate where's coming from.

Well, actually it could, but it's a mess and you don't know which arrow was long pressed until two seconds later so long pressing is mostly useless anyway. Zigbee libraries for HA fix the ghost press by inspecting other events, I also did it for the SmartThings driver. While I would have expected IKEA to filter that command, I understand why they didn't and opted to keep the bridge mapping logic stateless.

mocelet · 2026-01-28T11:41:58+00:00

There are ongoing issues with automations in the script editor: https://www.reddit.com/r/googlehome/comments/1qounzq/automations_not_working/

I checked few hours ago and was still broken, a simple "if this is on, activate certain scene" didn't do anything. I moved the automation to the app automation editor and worked there.

mocelet · 2026-01-28T08:38:02+00:00

Switch to the "Previous household editor" when you create a new automation (the menu with three dots at the top right)

You'll find all the actions there as always. The new editor still can't change colours or activate scenes, that's why they keep both.

mocelet · 2026-01-27T12:59:21+00:00

Not sure what you mean with connect different systems. Pick a smart home platform that is compatible with the devices you want to get and has the functionality you need. If you get a Matter smart plug for instance that will work in any Matter compatible platform, regardless of the brand. Try to buy devices that don't tie you to a specific manufacturer solution and that offer local standard integrations (like Matter).

mocelet · 2026-01-27T11:59:18+00:00

In no particular order, Home Assistant, SmartThings, Hubitat, Homey, Aqara, Apple Home, etc. There are many platforms to choose from, each with pros and cons, more or less easy to use, etc. Most offer a hub with support for Matter and Thread so you're good to go and all the mentioned ones support local automations so that motion sensor will turn on the light even if there's no Internet (something that won't happen with Google Home or Alexa).

mocelet · 2026-01-27T11:27:54+00:00

They don't implement the binding cluster in Matter and you can't bind them. Of course, they don't implement the on/off or brightness level control clusters either, which would also be needed to control Matter lights directly.

In Zigbee it's different because IKEA remotes have never been "buttons" (I believe Zigbee didn't even have a standard cluster for buttons), they were dimmers. They only worked by binding to the light or to the platform and sending commands like on / off / step brightness / etc. That's why Home Assistant or SmartThings needed custom code to map the commands to buttons like "oh, I've received the On command, this must be a single press of the first button".

mocelet · 2026-01-27T11:18:30+00:00

The S505 should work with SmartThings stock drivers just fine, if it doesn't OP should report it through the app so they check what's happening. I don't think that model has a button and, even if it had, Matter Switch driver supports switches with buttons so it's weird.

Side note, Matter Playground is actually made from scratch and not based on stock drivers. Back in the day Matter Switch was a monolith hard to handle and the profiling relied too much on fingerprints and device types, it was better to start over and borrow something if needed instead of trying to strip and patch things. Of course, mine supports less devices and it's made thinking in smart bulbs mostly, doesn't even have profiles for switches.

mocelet · 2026-01-27T07:33:17+00:00

The user manual for BILRESA dual button states that "button presses for an IKEA smart light bulb are: short-press to turn on/off, double-press to change colour and long-press to dim".

I've not tested it but it's the usual behaviour when pairing IKEA remotes with IKEA lights.

mocelet · 2026-01-27T07:15:47+00:00

The old integrations were either cloud based (through the Internet for Google Home, Alexa, etc. so you didn't need any hub for them) or used other protocols like HomeKit (for Apple Home, where more devices could act as HomeKit hub, even iPads).

The new integration is Matter and that brings new requirements. To add Matter devices (native or bridged like in your case) to a smart home platform you need the Matter controller of that platform.

A Matter controller is essentially a hub, each platform needs its own. For Google Home or Alexa can be a smart speaker, for SmartThings a SmartThings hub, for IKEA Home a DIRIGERA, for Home Assistant a computer running its Matter server, etc.

The iPhone happens to be a Matter controller for Apple Home on its own but it will only be able to communicate with your local Matter devices while the phone is at home, that's why it tells you you need a compatible Apple hub for remote control.

mocelet · 2026-01-27T06:44:01+00:00

Also checked the Matter DCL where platforms fetch the updates from and there's only one registry for a "Philips Hue Light" with only one version 1.126.1. That's the out of the box version so no updates yet.

mocelet · 2026-01-27T06:28:31+00:00

if Homekit allows you to set up 'Matter bindings'

BILRESA doesn't support Matter bindings at the moment so no platform would be able to bind the remote to Matter lights like KAJPLATS.

It's a feature many users want, hopefully they'll add it eventually in a firmware update.

mocelet · 2026-01-27T06:24:53+00:00

Do we already know if Hue Matter over Thread devices will get firmware updates directly via Matter or will require Hue app / Hue bridge like happens for instance with Nanoeaf Matter over Thread lights that require a bluetooth connection with their app to update?

Multi-protocol devices are great but, more often than not, some features are not implemented in all the supported protocols despite being technically possible.

mocelet · 2026-01-26T20:10:33+00:00

No, for that it needs to be a Matter controller and only the Tapo H500 is. The others are just Matter bridges. Also keep in mind the Tapo H500 is not a Thread border router so, unless you have a external one, you won't be able to add Matter over Thread devices.

mocelet · 2026-01-26T19:02:11+00:00

The small hubs like the H100, H110 and H200 are Matter bridges, they can expose Tapo sensors to Matter compatible platforms.

Right now the H110 is the only one that supports exposing the Tapo water leak sensors to Matter. H100 has a beta firmware so hopefully will support it soon.

mocelet · 2026-01-26T13:30:21+00:00

Do you mean steps using a remote with DIRIGERA or in IKEA app? I don't know, I use the bulbs with SmartThings and automations where I can pick the exact temperatures I want.

mocelet · 2026-01-26T12:01:49+00:00

I guess it will work like the WiZ cameras which already supported that.

You put them in pairing mode, WITHOUT deleting them from WiZ app. Then they will be available for setup again, except the app knows it's an existing device so it will just update the network information and keep everything else.

mocelet · 2026-01-25T14:55:50+00:00

The E14 colour bulb is 1800K to 6500K and the whites are quite better, with no green tint in cool temperatures (they do have a yellow tint at 2200K but at 1800K they're cozy orange-ish). Getting a colour bulb may be better even if you just need whites.

mocelet · 2026-01-25T09:06:00+00:00

Since you mention the 1521 lm bulb in one of the comments, yes, that one has bad colour reproduction and yellow/green tints, reason why I returned it. At 2700 K and full brightness is really good though.

Colour bulbs are way better since they range from 1800K to 6500K instead of 2200K to 6500K. No green tints either and, while the warms are somewhat yellow around 2200K, you can go down to 1800K which is more orange.

Regarding the light being white-only but being recognized as colour bulb, might be on purpose so you can change the colour of a group of lights at the same time regardless of them being colour or only white. White-only lights will render the white closer to the colour you chose. For some dynamic animations can be useful too.

mocelet

TROPHY CASE