Eglo / AwoX led driver

[taugusti]

I have finally found a way to make the Eglo / AwoX zigbee lights work properly.
Their customer support advised me to use another app - not the one listed in the documentation online and with the product :-(
"AwoX HomeControl" is the correct app. It included a more recent firmware version for the lamps - and it works without blocking the newwork and generating the infamous NWK_TABLE_FULL errors.
The new fw version is 2.5.0_999.
But... they report themselves with a new zigbee id, so a new converter is required.

I looked at the "old" eglo/awox driver - and it just does an extend of light_onoff_brightness_colortemp:
"extend: extend.light_onoff_brightness_colortemp({colorTempRange: [153, 370]})"
So - I did the same in a custom converter and it works fine.
on/off, brightness, color_temp and color_temp_startup, power_on_behavior works fine.
The effects also does "something" - not sure if it is as expected. I have never used that feature before so I do not know what to expect...

But - the question is if that is the right extend to use? When I go to the "exposes" tab in zigbee2mqtt, there is a block called color_xy - but it is not a color LED lamp...

Do I misunderstand the color_xy?
Can someone help me ensure the converter is correct?
What information do you need?

Here the list of zigbee endpoints as reported by zigbee2mqtt:

Endpoint 1
Output clusters
genOnOff
Input clusters
genBasic
genIdentify
genGroups
genScenes
genOnOff
genLevelCtrl
lightingColorCtrl
touchlink
64599
genTime
Endpoint 3
Output clusters
65360
65361
Input clusters
65360
65361
genGroups
Endpoint 242
Output clusters
greenPower

Thanks!

[Koenkk]

That's great news!

Can you provide the data/database.db entry of this device and as which model it should be recognized?

[Koenkk]

Given the modelId, I would expect the device to be detected as a 99847 which only supports color temp (at least in z2m 1.32.1), isn't this the case?

[taugusti]

ha ha - apparently someone added it while I was messing around - it is detected correctly now
And the color option has gone
All good now - thanks!

[Diaoul]

@taugusti do you confirm the network instabilities are gone following the upgrade? 🙏

I just bought a bunch of those Eglo lights so I never saw what was wrong first hand, I'd rather give them back if they still cause issues 😬

[taugusti]

Hi @Diaoul
The lamps works much better with the upgrade. No network errors and issues like that.
But they still suffer from not always responding when they have not been operated for extended periods of time...
Honestly I would not buy them again.
best of luck
/th

[d3relict]

i have an awox 33955 in my network that was firmware upgraded to 2.7.x. before the upgrade, the unit sent frequent updates, like every 10-30 seconds or so. after the upgrade, the updates are sent every few hours, which seems reasonable, and also seems more responsive (but still a bit slow every now and then). strange thing is, that zigbee2mqtt still reports the device with firmware version 2.3.12_250, but the awox app shows another (and no further option to upgrade).

[87insane]

Hey guys,
I also have an EGLO LED (https://www.amazon.de/dp/B09FSY66SH?psc=1&ref=ppx_yo2ov_dt_b_product_details). I noticed that a set off does not switch off the LED but sets the brightness to 1. The LED can be switched on/off completely via the app (HomeControl).

Info: My light is an RGBCCT

{"id":12,"type":"Router","ieeeAddr":"0xa4c1384e1fbf357a","nwkAddr":61468,"manufId":4417,"manufName":"AwoX","powerSource":"Mains (single phase)","modelId":"EGLO_ZM_RGB_TW","epList":[1,3,242],"endpoints":{"1":{"profId":260,"epId":1,"devId":269,"inClusterList":[0,3,4,5,6,8,768,4096,64599,10],"outClusterList":[6],"clusters":{"genBasic":{"attributes":{"swBuildId":"2.5.0_999","zclVersion":3}},"lightingColorCtrl":{"attributes":{"colorCapabilities":25,"colorTempPhysicalMin":153,"colorTempPhysicalMax":370,"colorMode":2,"currentX":9122,"currentY":3559,"colorTemperature":304,"startUpColorTemperature":370}},"genLevelCtrl":{"attributes":{"currentLevel":1}},"genOnOff":{"attributes":{"onOff":1,"startUpOnOff":1}}},"binds":[],"configuredReportings":[],"meta":{"onLevelSupported":false}},"3":{"profId":4751,"epId":3,"devId":269,"inClusterList":[65360,65361,4],"outClusterList":[65360,65361],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}},"242":{"profId":41440,"epId":242,"devId":97,"inClusterList":[],"outClusterList":[33],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":2,"stackVersion":1,"hwVersion":60,"swBuildId":"2.5.0_999","zclVersion":3,"interviewCompleted":true,"meta":{"configured":88764544},"lastSeen":1690809250174,"defaultSendRequestWhen":"immediate"}

[jeroenvansch]

Hi, same behaviour here for a eglo downlights that identify as Awox 33957.
Since updating to 2.7.0 the turn on/off doesnt work correctly. A remote that has been bound to the light does work as expected.
so I think there is something wrong with the converter.

[Diaoul]

I have the same issue. How can I help get this solve? I can contribute code if needed but pointers would be appreciated 🙏

[taugusti]

I think you should create a ned issue and link to this one. This one is closed so the right people might not see it...
/Th

[Diaoul]

🎉 I've managed to fix this issue (it seems) by emptying the Transition in the Setting (specific) tab.

It was previously at 1 as I wanted transitions on every change. I even tried to set it back to 0 which is supposed to be the default but it did not work either. I imagine 0 and empty have different meanings 🤷

Edit: I think it's still actually a bit broken when trying to use transitions.

[87insane]

I created a ticket: #19007