Miboxer FUT03xZ devices seem to have problems with state command

[Jordo-o]

What happened?

The devices (in my case FUT036Z and FUT037Z) seem to have problems with the ON state command. After being turned off for a while, the devices respond in a strange way to the ON command.

After turning it on, they immediately go off again. Although, according to the device state they are still turned on to the set brightness. You have to send a brightness value again or even turn it off first before it turns on again. After reviewing the log, it seems that the MQTT topic is also triggered twice, once ON and once OFF.

It looks like the light stays on when sending only the brightness and not the state ON command. But I am not completely sure about the fix yet.

What did you expect to happen?

The light should stay on after the first command.

How to reproduce it (minimal and precise)

1. Wait for a few hours... unfortunately, the device doesn't show this problem shortly after successfully turning it on.
2. Send on command via the zigbee2mqtt frontend or for example GoogleHome via OpenHAb or HomeAsisstant.
3. See the light turning off again.

Zigbee2MQTT version

1.33.1-1

Adapter firmware version

20221226

Adapter

Slaesh's CC2652RB Stick

Debug log

debug 2023-10-19 09:56:08: Received MQTT message on 'zigbee2mqtt/RGB/set' with data '{"state":"ON"}' debug 2023-10-19 09:56:08: Publishing 'set' 'state' to 'RGB' info 2023-10-19 09:56:08: MQTT publish: topic 'zigbee2mqtt/RGB', payload '{"brightness":206,"color":{"x":0.422,"y":0.52},"color_mode":"xy","color_power_on_behavior":"previous","do_not_disturb":true,"last_seen":"2023-10-19T07:56:08.986Z","linkquality":98,"state":"OFF"}' info 2023-10-19 09:56:08: MQTT publish: topic 'zigbee2mqtt/RGB', payload '{"brightness":206,"color":{"x":0.422,"y":0.52},"color_mode":"xy","color_power_on_behavior":"previous","do_not_disturb":true,"last_seen":"2023-10-19T07:56:08.986Z","linkquality":98,"state":"ON"}'

[lux73]

i can second this - few Month before i buy FUT039Z RGB+CCT LED Controller

i have some serious Problems with it - state Command leave untrue as you mentoined

BUT this Device also blocks my whole Zigbee Network after few Weeks - so no Commands to other Zigbee Devices could made

in my opinion these Miboxer Devices are crap, sorry... they are cheap but unreliable

[Jordo-o]

I indeed noticed that it doesn't matter to leave the state command away. Although, it looks a bit better without then with the state command.

But I have 4 of them and the don't block my network. But maybe that's because all the devices can take another route to the controller.

But indeed, they are cheap and a bit crappy.... For now I will send the command twice then 🤷🏽

[emandtf]

I'm using 6 FUT036Z from 2 years without any issue (beside the "do_not_disturb" feature that not always works leaving the dimmer ON after an AC power outage)

[Jordo-o]

Okay, that's weird I think. Maybe different firmware or something? Only, I can't see the version of these devices.... :/

[emandtf]

Maybe different firmware or something? Only, I can't see the version of these devices.... :/

If you are referring to multiple device types, I doubt firmware is the cause. Are you sure to not have some Homeassistant (or whichever smart software) Automation that does that?

[Jordo-o]

There you have a good point 😅 I also ruled out a power problem.

I have had it with different platforms, homeassistant, OpenHAB and even with the Z2M UI. So I really can't find the problem. But it only happens after the lights being off for a longer while.

Solution is pressing the on button twice, but it is kinda annoying 😅

(I also couldn't find anything about firmware in the miboxer website)

[joconcepts]

I have the same issues with them which already caused me to order another LED dimmer model (which is not yet here). But it is very annoying, I'm using it with a motiondetector and another one with homekit using homebridge and both show the same weird behavior (turning on, then instantly turning off, etc).

If the new dimmer will fix the issue I will replace them, however I'm very interested in knowing the reason for that behavior.

[alexsahka]

The devices (in my case FUT036Z and FUT037Z) seem to have problems with the ON state command.

I recently purchased a FUT037Z device, but it is not compatible with Z2M. Where can I find an external converter?

[Jordo-o]

I recently purchased a FUT037Z device, but it is not compatible with Z2M. Where can I find an external converter?

The controller should be supported. Maybe you can reset the controller (button on top) and try to connect it again.

[alexsahka]

The controller should be supported. Maybe you can reset the controller (button on top) and try to connect it again.

I bought three FUT037Z devices, and they all behave identically.

[Jordo-o]

Well, then its probably not the device. Can you maybe check your router firmware version and Z2M version?

[alexsahka]

All of my devices are working correctly on the Z2M hub except for the FUT037Z.

Zigbee2MQTT version 1.33.2-dev commit: ef00a64

Coordinator type zStack3x0

Coordinator revision 20220103

[alexsahka]

Does yours look like this?

[alexsahka]

The controller should be supported. Maybe you can reset the controller (button on top) and try to connect it again.

I don't see the FUT037Z on the supported list of devices

[paranoiq1]

I have similar problem with my two FUT039Z. I turn them on, then they immediately go off. State remains 'on'. Neither brightness change, nor turning them on once more will help, but yesterday they both started to work after few hours of not touching. I run zigbee2mqtt 1.35.0-1

[Jordo-o]

Does yours look like this?

Sorry, for the late reply 😅

But no, mine was without WW and CW. Note that you have de FUT037Z+. Mine is without +. That's probably the problem.

I'm afraid that you need to make converter yourself.

[Jordo-o]

I have similar problem with my two FUT039Z. I turn them on, then they immediately go off. State remains 'on'. Neither brightness change, nor turning them on once more will help, but yesterday they both started to work after few hours of not touching. I run zigbee2mqtt 1.35.0-1

I have fixed it by sending the on command twice. First one without a color/temperature. Second one with color and correct brightness (Few ms delay).

Isn't great, but it works.

[paranoiq1]

I have fixed it by sending the on command twice.

Have you tried turning off DND mode? I read that this actually should help, because those devices have this "functionality" that after power outage you need to click twice to turn them on

[Jordo-o]

I have fixed it by sending the on command twice.

Have you tried turning off DND mode? I read that this actually should help, because those devices have this "functionality" that after power outage you need to click twice to turn them on

Yes, DND mode has been off for a while now. Still doesn't help :(

[Jordo-o]

Currently I have requested support from MiBoxer. There are not so fast with a solution, but hopefully, it's on its way :)

[paranoiq1]

Ok, so in my case turning light on twice did not help, but turning it on and then setting new brightness did the trick or at least I hope it did

[Jordo-o]

Ok, so in my case turning light on twice did not help, but turning it on and then setting new brightness did the trick or at least I hope it did

That should also work indeed. It looks like there is some bug with the device not handling a ON command and brightness/color together. So, sending with a few milliseconds delay should do the trick, although it's not so nice.

I'm afraid they won't come with a solution. But if they do, I will let you all know :)

[Jordo-o]

I have had a lot of email contact with MiBoxer. They have tested some things on their side and I have tested some things with my controllers. But unfortunately, they conclude that the problem is in the gateway :(. Soo, I'm afraid they can't help us any further.

Edit: They said that they possibly have firmware updates, but only via the MiBoxer gateway. I've requested the OTA url, but no reply yet...

[xeroski]

Hi. I've probably found a reason why this is happening. If Miboxer is turned off and I send the turn-off command again, it turns off immediately after turning it on. This may happen if we send a global command to turn off all lights and Moboxer is already turned off

[Jordo-o]

So, it will sort of remember that it was turned off, while being off? Sounds like a useless feature to me haha, but if that's the case, it should be possible to fix.

[Jordo-o]

I have tested some of my devices and can confirm that this is indeed can be the problem. When I turned off my lights once, the light turned on normally. When I turned it off twice (or more) it went off directly after receiving the ON command...

Hope MiBoxer can help us witht he problem...

Edit: MiBoxer support keeps telling me that our gateway is not compatible and that they won't give us any firmware updates. The only advice I get is buying a MiBoxer gateway....

[keteflips]

I have tested some of my devices and can confirm that this is indeed can be the problem. When I turned off my lights once, the light turned on normally. When I turned it off twice (or more) it went off directly after receiving the ON command...

Hope MiBoxer can help us witht he problem...

Edit: MiBoxer support keeps telling me that our gateway is not compatible and that they won't give us any firmware updates. The only advice I get is buying a MiBoxer gateway....

Any news?

I thinks my problem its firmware related https://github.com/Koenkk/zigbee2mqtt/issues/23793

[Jordo-o]

Any news?

I thinks my problem its firmware related #23793

No news, unfortunately. MiBoxer won't help us and tells us to buy an MiBoxer gateway to "fix" the problem. They say it doesn't happen with their test setup.

You have to make a workaround outside zigbee2mqtt to fix the problem... It looks like the problem is in the firmware of the controller.

[xeroski]

That's why I won't buy anything from Miboxer again. Let them live in their own closed world

[0BanZai0]

Oh no, I'm stuck with a Miboxer controller that I can't change... I have the exact same problem.

Isn't there a way to "ping" the device frequently from z2m to receive the correct state?

I might also be willing to buy the Gateway for the FW update to solve this...