It looks like you will need to upgrade to the latest firmware (R309C) as this command is only available in this version. I’m not 100% sure where the Telegesis firmware is available on the web - maybe you can have a look around to see if you can find it - if so, then upgrading shouldn’t be too hard as it is possible to do it through the binding.
@chris Thanks for taking a look, especially at this busy (and wonderful) time of year.
I was fearing that the firmware might be the issue. I had already been and still am searching for the R309C firmware to download. None of the links on Silabs sites or provided by suppliers etc. lead to anything useful.
If anyone out there knows where I can get a copy of the TeleGesis ETRX3 R309C firmware, I would greatly appreciate your help.
Thanks.
I will check with Silabs in the new year - I believe they should be available somewhere.
Hi @chris, Played around with my ETRX3 today to try and get it to replace my HUE bridge, I’m on R309C firmware but the binding doesn’t recognise it:
I’ve unpaired one of the hue bulbs using the touchlink command on the Hue bridge, but still can’t get the binding to find anything. The debug logs for the binding as soon as I add the coordinator as a thing are:
https://gist.github.com/BClark09/f4b0b87f6884fb81df1040acc4a5a350
Any ideas where to start looking?
It shows ONLINE in your image - I think the binding does recognise it.
I’ll take a look at the log when I get a chance…
1 Like
Thanks Chris, sorry I haven’t filtered anything specific, not sure what I’m looking for. I’ve just tried on a Windows machine with a free osram lightify bulb I had and unable to find anything there too.
Everything looks ok - the initialisation of the dongle is fine - its communicating, downloading the routing table etc - all good.
I don’t see any join command being sent though - are you putting the binding into join mode? I normally put the binding into join (which it will only stay in for 30 seconds) then reset or power on the device - all the devices I’ve tried have quickly joined at that point (a Hue bulb, 4 different types of Osram bulbs, ST plugs and sensors…).
When you say join mode, that’s done by searching for things right? I’ve set “Allow All Joins” and still no dice. I’m a little baffled at why zigbee_permitjoining is always false too.
I see this in the log each time, which starts with Permit join to 65532/0 for 60 seconds:
Does the touchlink command from the Hue bridge automatically join it to the hub again? The bulb flashes, which I thought indicated a reset.
Correct.
Ignore this - it’s a status feedback from the beacons that is only updated during the mesh update.
Ok, that looks fine. I didn’t see this in the earlier log.
I’ve no idea really what the Hue bridge does - I don’t know if it always wants to use touchlink joining, or if it can also use standard joining. The Hue bridge might automatically rejoin the bulb after the reset - I just don’t know.
Correct - but I guess it might then do a rejoin to the bridge?
I think this might be the case, that’s frustrating. The Lutron Remote seems to be no longer sold which would have been able to reset them so I’m a little stuck for now. It’s not very likely that I’d be able to find some touchlink app for the etrx3 either.
Thanks for looking at it anyhow!
I was playing around with touchlink the other day with a view to adding the touchlink reset command. I’m not 100% sure how it works though - ie if it will only reset a device that’s in close proximity (probably), and it it will only reset a bulb that was included into it’s ZLL network (maybe), or if I need to encrypt the reset with the “secret” ZLL key (which I found on the web, but not sure if I can use in the ETRX)…
It’s not something I’ll look at in the next day or two, but I might have a quick play at some point soon.
1 Like
Thanks again. For now I’ve bought a hue dimmer as I’ve seen reports of that working for hue lights will arrive on Wednesday so will let you know the results.
Hi @Benjy, you mention you are using R309C firmware on your ETRX3. Did it come with that firmware, or did you get the firmware from somewhere else? If so, please can you share with us?
All new devices come with R309C - I’m not aware of a public download of this at the moment but I’m trying to get one.
That’s right, the device came with R309C
Progress report:
The Hue dimmer switch arrived and I was able to reset each bulb to factory default. I added each bulb one at a time and tested and all worked fine, up until my 5th bulb. Now nothing responds, not even the bulbs that were previously working. Not sure where to go from here.
13:35:55.281 [DEBUG] [gbee.internal.ZigBeeNetworkDiscoverer] - 0/1: Simple Descriptor returned null
13:35:55.302 [DEBUG] [gbee.internal.ZigBeeNetworkDiscoverer] - 0/1: Endpoint discovery request failed. Wait before retry.
13:35:55.328 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - TX CMD: SimpleDescriptorRequest [0/0 -> 0/0, cluster=0004, TID=CF, nwkAddrOfInterest=0, endpoint=1]
13:35:55.357 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=0/0, profile=0000, cluster=4, addressMode=DEVICE, radius=31, sequence=207, payload=00 00 00 01]
13:35:55.385 [DEBUG] [ongle.telegesis.ZigBeeDongleTelegesis] - Telegesis send: TelegesisSendUnicastCommand [address=0, sourceEp=0, destEp=0, profileId=0, clusterId=4, messageData=00 00 00 01, messageId=null]
13:35:55.405 [DEBUG] [egesis.internal.TelegesisFrameHandler] - TX Telegesis queue: 8
13:35:55.419 [DEBUG] [egesis.internal.TelegesisFrameHandler] - TELEGESIS TX: Data 41 54 2B 53 45 4E 44 55 43 41 53 54 42 3A 30 34 2C 30 30 30 30 2C 30 30 2C 30 30 2C 30 30 30 30 2C 30 30 30 34 0D 00 00 00 01 0D 0A
13:37:54.225 [INFO ] [smarthome.event.ItemCommandEvent ] - Item 'Kitchen_Light_Switch' received command OFF
13:37:54.228 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 001788011029F4B8: Command for channel zigbee:device:88b392d3:001788011029f4b8:001788011029F4B8_11_switch_level --> OFF
13:37:54.253 [INFO ] [smarthome.event.ItemStateChangedEvent] - Kitchen_Light_Switch changed from ON to OFF
13:37:57.916 [DEBUG] [gbee.internal.ZigBeeNetworkDiscoverer] - 0/1: Simple Descriptor returned null
13:37:57.952 [DEBUG] [gbee.internal.ZigBeeNetworkDiscoverer] - 0/1: Endpoint discovery request failed. Wait before retry.
13:37:57.997 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - TX CMD: SimpleDescriptorRequest [0/0 -> 0/0, cluster=0004, TID=DB, nwkAddrOfInterest=0, endpoint=1]
13:37:58.048 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=0/0, profile=0000, cluster=4, addressMode=DEVICE, radius=31, sequence=219, payload=00 00 00 01]
13:37:58.091 [DEBUG] [ongle.telegesis.ZigBeeDongleTelegesis] - Telegesis send: TelegesisSendUnicastCommand [address=0, sourceEp=0, destEp=0, profileId=0, clusterId=4, messageData=00 00 00 01, messageId=null]
13:37:58.124 [DEBUG] [egesis.internal.TelegesisFrameHandler] - TX Telegesis queue: 8
13:37:58.144 [DEBUG] [egesis.internal.TelegesisFrameHandler] - TELEGESIS TX: Data 41 54 2B 53 45 4E 44 55 43 41 53 54 42 3A 30 34 2C 30 30 30 30 2C 30 30 2C 30 30 2C 30 30 30 30 2C 30 30 30 34 0D 00 00 00 01 0D 0A
I’ve received the R309C firmware so will look at providing this in a format that you can use in a few days.
@chris just to save you some effort and let people know, you can get a copy of the R309C firmware if you directly contact the Silabs support team using their contact details on the slabs website.
I got sent a file with docs yesterday. Haven’t had time to try it yet.
Ok, cool - if you don’t need this then that’s fine. If it’s needed then I can simply package it up so the binding can update the firmware…
1 Like
Hey @chris, sorry to trouble you once again. I’ve failed at trying to get this working. Nothing responds if I try to include all my bulbs at the same time.
I’ve been able to add each and every light individually and they work fine on their own. As soon as I turn multiple bulbs on, they start responding very slowly and then stop responding at all. My process for adding the bulbs are:
- Turn off all lights
- Turn on one, reset to factory default using Hue dimmer.
- Start Join process, binding finds the new Thing immediately.
- Link the channels to the relevant items.
- Test on BasicUI.
- If working, turn off and go to step 2.
- When all lights are working individually, turn all on and wait a bit.
I have the logs of the last three minutes whilst only 5 bulbs are on at a time and none of them responding, and I think this includes the last inclusion. Please let me know if there’s anything specific that would help you, or if I’ve done something wrong along the way.
Just to test, I’ve also reset the EXRX3 to factory default.