Eglo Zigbee Remote - any suggestions for a start point

⚙️ Custom Apps and Drivers Custom Drivers
1

Anyone got any ideas as to where I can start trying to make a custom driver for one of these:

EGLO REMOTE 2.0

It will pair OK with Hubitat with the following information but just as device:

2023-07-12 05:46:51.663 PMinfofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0003,0004,1000", outClusters:"0000,0003,0004,0005,0006,0008,0300,1000", model:"ERCU_3groups_Zm", manufacturer:"AwoX"
dev:1492023-07-12 05:46:51.463 PMtraceZCL version:03
dev:1492023-07-12 05:46:51.458 PMtraceSoftware Build Id:2.3.12_250
dev:1492023-07-12 05:46:51.456 PMtraceModel:ERCU_3groups_Zm
dev:1492023-07-12 05:46:51.452 PMtraceManufacturer:AwoX
dev:1492023-07-12 05:46:51.410 PMinfoZigbee parsed:[raw:catchall: 0104 0000 01 01 0040 00 719B 01 00 0000 01 01 00030004000F000A, profileId:0104, clusterId:0000, clusterInt:0, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:719B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, 03, 00, 04, 00, 0F, 00, 0A]]
dev:1492023-07-12 05:46:37.399 PMdebuggetting info for unknown Zigbee device...

Any suggestions for a driver that might be a starting point, or any other ideas gratefully received?

Thanks

2

Do you see anything in the live logs when you press the buttons?

3

No. Nothing in live logs unfortunately.

4

This is the device data.

  • endpointId: 01
  • application: 02
  • inClusters: 0000,0003,0004,1000
  • manufacturer: AwoX
  • model: ERCU_3groups_Zm
  • outClusters: 0000,0003,0004,0005,0006,0008,0300,1000
  • softwareBuild: 2.3.12_250
5

This device seems to be similar to MiBoxer remote - it will not work with Hubitat.
It uses Zigbee Inbound Groups Messaging, which are filtered by Hubitat.

6

OK, thanks for your help.

I've been away from using Hubitat for a while using Zigbee2MQTT exclusively for my Zigbee stuff, but I've just came across my old Hubitat hub, so I thought I'd fire it up, update it to the latest firmware and give it a try again. I was a bit fed up with Z2M as in doing recent Z2M update I somehow managed to end up back to an old database which lost some devices and added some I'd deleted ages ago. I don't like having to delve deeply into Linux to just to do an update, so thought I'd give Hubitat another try. Plus I think the Hubitat community is one of the best and have always kept checking in on these pages even when I haven't been using Hubitat.

There do seem to have been a lot of improvements since i last used it, but it's disappointing that the device compatibility is still way below that of Z2M. I use Ikea Styrbar remotes and that needs a community driver that doesn't yet report battery levels and now this device which apparantly wont work at all. Both of these work perfectly on Z2M so it looks like ill have to stick with that. I get that the EGLO is a bit niche, but I would have expected the Styrbar to be a standard compatible device.