1st gen Hue bulbs with 67.91.1 firmware not working

Emil · June 19, 2022, 3:47pm

Hi,

In my pursue to remove my HUE bridge and go all in on Deconz I have discovered something unfortunate.

My good old Hue Color 1st gen does not work in my setup. With some proper “negotiation” I get them to join and they will stay in the network for 2-30 mins, then they are gone or non responsive. None of my other devices have issues. I can reset them, get them back online and after a random short time, gone again.

I thought they had a bad chip or something. I fired up the old hue bridge, paired them and no problem they work like a charm. I did a lot of research and a lot of people seems to have this issue. Some have solved it by reverting the Deconz firmware to:

The issue came with the 67.91.1 firmware update from Philips (security fix or “planned obsolesce”?) . Bulbs with 67.88.1 (non upgraded) seems to work fine. Is there a work around or do I have to say, thanks for this time guys, it is time for you to retire (what a pitty)?

BR,

Emil

Emil · June 19, 2022, 9:12pm

Some have mentioned that certain fw does not send / support reporting, could that be an issue?

Could we have the same problem / issue here?

manup · June 20, 2022, 10:12am

All hue lights (unfortunately) don’t support reporting and are polled, but usually otherwise are very stable.

The signal quality between the light and the other devices seems rather weak. I need to find my old Hue color light to check if the updated firmware also causes problems.

Emil · June 20, 2022, 8:24pm

Thanks for the feedback. Yes the signal is not the best and the conditions is the same for the hue setup.
If you could test with an old bulb that would mean a lot! It seems I have some other philips fixtures with the same issue. Lets focus on the first one and it may solve the rest.
Let me know if you need any kind of logs.

BR,

Emil

Emil · June 21, 2022, 8:31pm

Actually most of my philips bulbs has dropped off now and are not connecting again, dimmer switches are ok. Very strange. All other devices, Ikea Trådfri lights, sockets and some Aqara devices are good.

Emil · June 22, 2022, 6:40pm

Don’t know if it is related.

After this, highlighted the device goes in zombie mode and looses all connections but one very weak one.

Emil · June 22, 2022, 6:49pm

After it is deleted it pops up again with the old nwk

Emil · June 22, 2022, 8:59pm

Looks like the similar issue here:

github.com/Koenkk/zigbee2mqtt

Lights go unresponsive from time to time

opened 12:13PM - 08 Nov 21 UTC

closed 12:02AM - 05 Jun 22 UTC

hmorkemo

problem stale

Many of my lights (Ikea and Philips) go unavailable from time to time (several times pr. week), and can't be contolled. After a while, sometimes, they come back online again. Sometimes a refresh in the z2m device panel brings the light back to life. But usually that doesn't help. Often I have to delete / add it. It seems like the lights farthest away from the controller suffer the most. All lights are quite evenly distributed in and around the house. The farthest distance from the ConBee is 20 meters. They are uncontrollable both from HA and from the Zigbee2mqtt UI. The same problem occurs with my Ikea Fyrtur blinds from time to time. Typical error message in the zigbee2mqtt log: "Publish 'set' 'state' to 'Utebod Lys2' failed: 'Error: Command 0x5c0272fffe840e54/1 genOnOff.off({}, {"sendWhenActive":false,"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received)'" I have 55 mains powered devices (Ikea and Philips lights, wall plugs). 48 battery powered devices (Sensors, fyrtur blinds, switches). What could be the reason for this behaviour, and what can I do to make it stable? My config file: ``` data_path: /config/zigbee2mqtt external_converters: [] devices: devices.yaml groups: groups.yaml homeassistant: true permit_join: false mqtt: base_topic: zigbee2mqtt user: xxxxxx password: xxxxxxx serial: port: >- /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2434862-if00 adapter: deconz advanced: log_level: warn pan_id: 62369 channel: 25 network_key: - x - x availability_blocklist: [] availability_passlist: [] device_options: {} blocklist: [] passlist: [] queue: {} frontend: port: 8099 experimental: {} socat: enabled: false master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777 slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5 options: '-d -d' log: false ``` ## What happened Lights stop responding to Zigbee2Mqtt. ## What did you expect to happen Normal lights on/off for all lights. ## How to reproduce it (minimal and precise) This happens spontaneoulsy, it seems, with no prior action ## Debug info Zigbee2MQTT version: 1.22.0-2, Zigbee channel 25. Far away from any local WiFi channels (1, 6 and 8). Adapter hardware: Conbee II Adapter firmware version: 26720700, updated 7.nov. HA Core 2021.11.1, Supervisor 2021.10.8

github.com/Koenkk/zigbee2mqtt

Device offline but can still control via zigbee group

opened 01:48PM - 28 Feb 22 UTC

closed 12:03AM - 16 Apr 22 UTC

millionsofjeffries

problem stale

### What happened? I have a few devices that randomly start to show as offline …and can't be controlled. For example, an offline bulb is part of a zigbee group of 3 identical bulbs and doesn't respond to any issued commands. It works just fine if I control the group instead. However, this doesn't bring it back to online and it still can't be controlled individually. After a random period of hours, it will come back online on its own and be reachable individually again for a while, but will go offline again at some point. Here is an example of the debug log for a state request and it doesn't seem to receive a response from the bulb: `zigbee2mqtt | Zigbee2MQTT:error 2022-02-28 13:18:20: Publish 'get' 'state' to 'Bulb_BarSpot2' failed: 'Error: Read 0x84fd27fffe92a61a/11 genOnOff(["onOff"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received)' zigbee2mqtt | Zigbee2MQTT:debug 2022-02-28 13:18:20: Error: Read 0x84fd27fffe92a61a/11 genOnOff(["onOff"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received) zigbee2mqtt | at DeconzAdapter.sendZclFrameToEndpoint (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:649:23) zigbee2mqtt | at runMicrotasks (<anonymous>) zigbee2mqtt | at runNextTicks (internal/process/task_queues.js:60:5) zigbee2mqtt | at processTimers (internal/timers.js:497:9) zigbee2mqtt | at Endpoint.sendRequest (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:299:20) zigbee2mqtt | at Endpoint.read (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:472:28) zigbee2mqtt | at Object.convertGet (/app/node_modules/zigbee-herdsman-converters/converters/toZigbee.js:293:13) zigbee2mqtt | at Object.convertGet (/app/node_modules/zigbee-herdsman-converters/converters/toZigbee.js:898:17) zigbee2mqtt | at Publish.onMQTTMessage (/app/lib/extension/publish.ts:272:21) ` And here is an example of a successful group command that completed successfully (notice the last seen for the problem bulb 'Bulb_BarSpot2' is when it went offline): ` zigbee2mqtt | Zigbee2MQTT:debug 2022-02-28 13:24:13: Received MQTT message on 'zigbee2mqtt/BarSpots/set' with data '{"state": "ON", "color_temp": 352}' zigbee2mqtt | Zigbee2MQTT:debug 2022-02-28 13:24:13: Skipping state because of Home Assistant zigbee2mqtt | Zigbee2MQTT:debug 2022-02-28 13:24:13: Publishing 'set' 'color_temp' to 'BarSpots' zigbee2mqtt | Zigbee2MQTT:debug 2022-02-28 13:24:13: Received Zigbee message from 'Coordinator', type 'commandMoveToColorTemp', cluster 'lightingColorCtrl', data '{"colortemp":352,"transtime":0}' from endpoint 1 with groupID 1, ignoring since it is from coordinator zigbee2mqtt | Zigbee2MQTT:info 2022-02-28 13:24:13: MQTT publish: topic 'zigbee2mqtt/Bulb_BarSpot1', payload '{"brightness":254,"color":{"h":33,"hue":33,"s":79,"saturation":79,"x":0.4488,"y":0.4078},"color_mode":"color_temp","color_temp":352,"color_temp_startup":65535,"last_seen":"2022-02-28T13:23:03+00:00","linkquality":255,"state":"ON"}' zigbee2mqtt | Zigbee2MQTT:info 2022-02-28 13:24:13: MQTT publish: topic 'zigbee2mqtt/BarSpots', payload '{"brightness":254,"color":{"h":33,"hue":33,"s":79,"saturation":79,"x":0.4488,"y":0.4078},"color_mode":"color_temp","color_temp":352,"state":"ON"}' zigbee2mqtt | Zigbee2MQTT:info 2022-02-28 13:24:13: MQTT publish: topic 'zigbee2mqtt/Bulb_BarSpot2', payload '{"brightness":254,"color":{"h":33,"hue":33,"s":79,"saturation":79,"x":0.4488,"y":0.4078},"color_mode":"color_temp","color_temp":352,"color_temp_startup":65535,"last_seen":"2022-02-28T09:38:34+00:00","linkquality":240,"state":"ON"}' zigbee2mqtt | Zigbee2MQTT:info 2022-02-28 13:24:13: MQTT publish: topic 'zigbee2mqtt/Bulb_BarSpot3', payload '{"brightness":254,"color":{"h":33,"hue":33,"s":79,"saturation":79,"x":0.4488,"y":0.4078},"color_mode":"color_temp","color_temp":352,"color_temp_startup":65535,"last_seen":"2022-02-28T13:21:49+00:00","linkquality":240,"state":"ON"}' ` Bulbs are Ajax Online Ltd AJ_ZB120_GU10. However, I've had the same thing happen occasionally with Ikea control outlets. Mesh is good (48 routers) and the 3 bulbs in the group are only 30 cm away from each other. Have tried the latest dev version but results are the same. zigbee2mqtt is running on a rpi4 in a docker container with a conbee2 usb on an extension cord. All devices are on the latest firmware I could find available. Thanks in advance for your assistance! ### What did you expect to happen? If bulb can be controlled as part of a group it should be reachable individually too ### How to reproduce it (minimal and precise) Via the zigbee2mqtt frontend, try to control a bulb that is showing as offline and there is no response from the bulb and eventually a timeout message is logged. Try to control the same bulb as part of a group and the bulb responds as instructed. ### Zigbee2MQTT version 1.23.0-dev commit: afe94a7 ### Adapter firmware version 266e0700 ### Adapter Conbee 2 ### Debug log _No response_

Emil · June 22, 2022, 10:43pm

Might have found a work around.

After the bulb has been paired, when it goes zombie, reset it with a hue dimmer, it will get back online again automatically, if not try for a second time and it seems to kick it back in to place. Will monitor how long they will stay online.

Mimiix · June 23, 2022, 5:52am

Asked manup to check

Emil · June 23, 2022, 5:52am

After a power cycle of the bulbs they are back into zombie mode.

1 came alive after reqesting simple discriptors. All my other devices except of HUE works nicely.

Sometimes the Hue lamps seems to respond to commands, but shows no connections in deconz.

Emil · June 27, 2022, 3:03pm

Any luck finding a bulb? I have now tried with all possible settings and to reproduce the error/issue.

Just power cycle a hue bulb and it is not connecting again. I can change channel etc while online but as soon as the power is gone it needs to be re-paird.

Any useful logs i can provide?

BR,

Emil

Mimiix · June 27, 2022, 5:12pm

Can you please open an bug report on the github to properly track the issue?

manup · June 27, 2022, 6:15pm

Hi sorry for the delay, I checked my boxes, somehow the bulb is missing I’ll check if we have an older one in the company.

Emil · June 28, 2022, 8:14am

I will do a github issue. Some clues, I played with making a DDF for one of the bulbs. 1 issue I had to overcome, based on the autogenerated one. 1. Manufacturer name has changed to ‘Signify Netherlands B.V.’ nothing happened before doing a read of the basic cluster, to get the manuf. name.

“manufId”:4107

henwi · May 16, 2023, 3:53pm

Hi, are there any news on this topic?

I have the same problem. All of the 1st gen HUE Lights from firmware 67.91.1 to 67.101.2 on do not work and show the same behavior as described here. Shortly after discovery, not reachable but groups still work
The lamps that do not work are (LLC010, LLC011, LCT001, LST001, LLC011, LCT001)

When I go back to firmware 5.127.1.26581 via OTAU, everything works as expected.

I have no problem with other lights, switches or sensors. Even newer HUE lights with firmware 67.101.2 work.

I am running the latest stable deCONZ (2.21.2 and RaspbeeII FW 26780700)

henwi · January 24, 2024, 4:38pm

Hi, just to let you know.
I have changed my setup from RaspBeeII to ConBeeIII at the beginning of this year. After that, the 1st Gen Hue lights worked again with the latest firmware.

LCT001 - Bulb, FW: 67.101.2
LLC010 - Iris, FW: 67.93.11
LLC011 - Bloom, FW: 67.93.11
LST001 - Lightstrip, FW: 67.93.11

For me, the problem is solved.

(deCONZ: 2.24.3, ConBee III FW: 264F0900)

mtressl · February 29, 2024, 10:19am

hello @henwi
I found your post here and I am in the same boat as you were before. I have two LST001 - Lightstrip and 2 LLC011 - Bloom lights, latest firmware (since they were running on a Hue bridge before).

with deConz and a RaspBeeII these lights do not work, same issues as you discovered.

if I get your post, I have two options: upgrade to a ConBeeIII (don’t want to), or downgrade the firmware of the lights mentioned to FW version 5.127.1.26581 via OTAU.

is that correct?
if the FW downgrade is possible (through OTAU), may I ask you where you got the FW images for the lights?

thanks in advance!

mtressl · February 29, 2024, 10:21am

hi @manup , @Mimiix
is this still a known issue or is it my problem I am facing.
seems like the ConBeeIII works with these lights, but the RaspBeeII is not.
any chance you bring whatever makes them work into a FW update for the RaspBeeII?

thanks, Markus

henwi · March 1, 2024, 9:58am

Hi @mtressl,
iI I remember correctly, I have the firmware images from the githup page. (GitHub - dresden-elektronik/deconz-ota-plugin: Server side implementation of the standard Zigbee OTA protocol.) However, it has been updated. I have cleaned up my system in the meantime and unfortunately no longer have the old images.
Maybe someone still has?