Ok, in that case it looks like the querying stopped for some reason way too early. Please try to unpair and pair again the light bulb.
I already committed an xml file for 1b, so it should be available soon.
Hey cnowden,
Ich hab auch den CC2531 am laufen. Das pairing mit dem osram Smart Plug going auch problemlos, nur hab ich seit dem keine Kommunikation mehr. Weder kann ich was steuern noch bekomme ich Signale wenn ich den Schalter Manuel schalte.
Ein paar Fragen zum Aufbau bei dir:
- CC2531 über usb angeschlossen und wenn ja auch noch andere Schnittstellen sticks?
- kannst du mir dein zigbee. Conf Datei vielleicht schicken?
- ist die Grüne LED auf dem Stick bei dir dauerhaft an?
- die Firmware des sticks
Das wäre sehr interessant zu wissen.
Danke
Der Doc
Hi Doc,
zu 1.)
Ich habe einen Homegear Gateway auf einem RPI Zero eingerichtet und daran den CC2531 über USB angeschlossen. Im Admin UI habe ich dann den Gateway eingebunden und danach die Geräte eingerichtet.
zu 2.)
In der zigbee.conf auf meinem RPI 3b - die Homegear Zentrale - ist alles bis auf linkKeyExchange = “no” auskommentiert, da die Config über die Admin UI stattgefunden hat. Es hätte aber auch funktioniert, wenn ich dort den homegear-gateway entsprechend konfiguriert hätte. In einer früheren Testphase war das auch schon mal so.
zu 3.)
Die grüne LED ist nicht ständig an wie bei meiner zigbee2mqtt Instanz (an der Zentrale steckt ebenfalls ein CC2531, der allerdings nur für Z2M da ist), sondern leuchtet nur beim Start des Dienstes - glaube ich.
Der Gateway ist im Grunde genommen eine Spielwiese für mich, da ich meine bestehende Z2M Infrastruktur mit zahlreichen Lampen, Steckdosen und Rollos nicht gefährden wollte. Im Endausbau sollte natürlich der CC2531 in der Zentrale genutzt und damit Z2M abgelöst werden.
VG von,
Carsten
Hey,
hatte auch Z2M im Einsatz und war aber irgendwie nicht richtig zufrieden. War auch mehr erstes Projekt am pi und eventuell ist dabei einiges nicht ganz gut gelaufen. Nun hab ich viel auf Enocean umgebaut.
Nachdem homegear nun zigbee selbst Unterstützt wollte ich mal sehen Ob ich wieder warm werde mit zigbee. Ist ja preislich eigentlich unschlagbar.
Aber bei mir will es nicht. Die led geht nach 30s etwa aus. Danach kann ich zwar munter pairen aber es besteht keine Kommunikation zu den gepairten Modulen. Homegear selbst behauptet aber immer noch in der Admin Ui das die Verbindung besteht.
Wenn du noch ne Idee hast was man machen/ testen kann immer her damit
Kannst du mir noch deine Firmware auf dem Stick nennen? Vielleicht hängt es ja damit zusammen.
Hi @Adrian,
even with updating to the latest nightly and re-pairing the Hue bulb I get the same results when I print the config in Homegear CLI.
Another problem is, that the new XML was not avaible after installation of the latest nightly. This has maybe something to do with my homegear installation on my RPI 3b and has happened also before. After some install/uninstall orgy of the zigbee module via homegear nigthly installation tool, the folder /etc/homegear/devices/26 was empty and I didn’t get it filled regardless how many times I tried to re-install zigbee module… 
I had to install homegear with the zigbee module on my RPI Zero and to copy all XML files to the corresponding folder of my RPI 3b.
If you have a clue what caused this I would be very happy! Else: 
Can you send me the XML or just give me a GIT link where I can download it? Thank you!
Regards,
Carsten
Hi @dr_snuggles,
ich habe aus dem ZIP CC2531_DEFAULT_20190608.zip das File CC2531ZNP-Prod.hex auf den CC2531 geflasht.
Was passiert denn, wenn Du die Steckdose per MQTT ansprichst? Ich nutze dafür MQTT.fx.
Hier ein Beispiel aus meiner Konfiguration:
stateTopic=“homegear/1/plain/40/1/ONOFF”
commandTopic=“homegear/1/set/40/1/ONOFF” mit Payload true oder false (alles andere geht nicht)
PS: Noch was: Wird Dir in der Homegear CLI die komplette Config angezeigt? Die sieht bei mir so aus:
MASTER
{
Channel: 0
{
[ROUTER]: 01
[MAINS_POWERED]: 01
[END_POINT]: 03 00
[SHORT_ADDR]: 60 f4
[LISTENING]: 01
}
}
VALUES
{
Channel: 1
{
[ONOFF]: 01
[ACTIVEPOWER]: 00
}
Channel: 0
{
[UNREACH]: 00
[STICKY_UNREACH]: 00
[CONFIG_PENDING]: 01
[LAST_PACKET_RECEIVED]: 00
}
}
VG von,
Carsten
Let’s stick to english guys, so that Adrian could easier follow allong.
From which directory did you took CC2531_DEFAULT_20190608.zip, @cnowden. It looks like coordinator 1.2.
@Adrian: Did you do some tests with 1.2 or mainly with 3.0.x?
Hi @pmayer,
yes you’re right! Coordinator stack 3.0 seemed too unstable for me when I followed the corresponding discussion thread there. So I decided to use stack 1.2 from 8.6.2019.
But if necessary I can easily switch to stack 3.0 as I have a separated “test environment” with my homegear gateway. 
Regards,
Carsten
AFAIK @Adrian developed against 3.x - but not sure about this.
I only did a small test with 3.x together with homegear and did not have any problems. But only one xiaomi aquara sensor connected…
Only 3.x. 1.2 is rather old and it does not support a lot of things. Maybe that’s why querying the device didn’t work.
Hey cnowden,
my config is way longer than yours.
Family 26 - peer 70> config print
MASTER
{
Channel: 12
{
[ONOFF_REPORTING_CONFIG.ONOFF.MIN_REPORTING_INTERVAL]: 00 00
[ONOFF_REPORTING_CONFIG.ONOFF.MAX_REPORTING_INTERVAL]: 02 58
}
Channel: 9
{
[SCENES.VIEW_SCENE_RESPONSE.TRANSITION_TIME]: 00 00
[SCENES.VIEW_SCENE_RESPONSE.EXTENSION_FIELD_SETS]: 00
[SCENES.STORE_SCENE.SCENE_ID]: 00
[SCENES.STORE_SCENE.GROUP_ID]: 00 00
[SCENES.SCENE_VALID]: 00
[SCENES.GET_SCENE_MEMBERSHIP_RESPONSE.CAPACITY]: 00
[SCENES.VIEW_SCENE.SCENE_ID]: 00
[SCENES.RECALL_SCENE.SCENE_ID]: 00
[SCENES.GET_SCENE_MEMBERSHIP.GROUP_ID]: 00 00
[SCENES.ADD_SCENE.GROUP_ID]: 00 00
[SCENES.CURRENT_GROUP]: 00 00
[SCENES.VIEW_SCENE_RESPONSE.SCENE_NAME]: 00
[SCENES.NAME_SUPPORT]: 00
[SCENES.ADD_SCENE.EXTENSION_FIELD_SETS]: 00
[SCENES.STORE_SCENE_RESPONSE.STATUS]: 00
[SCENES.ADD_SCENE.SCENE_NAME]: 00
[SCENES.ADD_SCENE.SCENE_ID]: 00
[SCENES.GET_SCENE_MEMBERSHIP_RESPONSE.SCENE_LIST]: 00
[SCENES.REMOVE_ALL_SCENES_RESPONSE.STATUS]: 00
[SCENES.VIEW_SCENE.GROUP_ID]: 00 00
[SCENES.GET_SCENE_MEMBERSHIP_RESPONSE.STATUS]: 00
[SCENES.NAME_SUPPORT__SUPPORTED]: 00
[SCENES.RECALL_SCENE.GROUP_ID]: 00 00
[SCENES.SCENE_COUNT]: 00
[SCENES.REMOVE_ALL_SCENES.GROUP_ID]: 00 00
[SCENES.ADD_SCENE.TRANSITION_TIME]: 00 00
[SCENES.REMOVE_SCENE.SCENE_ID]: 00
[SCENES.CURRENT_SCENE]: 00
[SCENES.ADD_SCENE_RESPONSE.STATUS]: 00
[SCENES.REMOVE_SCENE.GROUP_ID]: 00 00
[SCENES.VIEW_SCENE_RESPONSE.STATUS]: 00
[SCENES.REMOVE_SCENE_RESPONSE.STATUS]: 00
}
Channel: 0
{
[SHORT_ADDR]: 90 ed
[END_POINT]: 03 00
[LISTENING]: 01
[MAINS_POWERED]: 01
[ROUTER]: 01
}
Channel: 5
{
[IDENTIFY.IDENTIFY_QUERY_RESPONSE.IDENTIFY_TIME]: 00 00
[IDENTIFY.IDENTIFY_TIME]: 00 00
[IDENTIFY.IDENTIFY_QUERY.ACTION]: 00
[IDENTIFY.IDENTIFY.IDENTIFY_TIME]: 00 00
}
Channel: 3
{
[BASIC.ZCL_VERSION]: 01
[BASIC.SW_BUILD_ID]: 56 31 2e 30 34 2e 31 32
[BASIC.POWER_SOURCE__UNKNOWN]: 01
[BASIC.POWER_SOURCE__SECONDARY_POWER_SOURCE]: 00
[BASIC.POWER_SOURCE__MAINS_3_PHASE]: 00
[BASIC.POWER_SOURCE__EMERGENCY_MAINS_CONSTANTLY_POWERED]: 00
[BASIC.HW_VERSION]: 01
[BASIC.POWER_SOURCE__MAINS_SINGLE_PHASE]: 00
[BASIC.DATE_CODE]: 32 30 31 34 30 33 33 31 44 45 4f 53 2a 2a 2a 2a
[BASIC.DEVICE_ENABLED]: 01
[BASIC.MANUFACTURER_NAME]: 4f 53 52 41 4d
[BASIC.POWER_SOURCE__EMERGENCY_MAINS_AND_TRANSFER_SWITCH]: 00
[BASIC.APPLICATION_VERSION]: 0c
[BASIC.MODEL_IDENTIFIER]: 50 6c 75 67 20 30 31
[BASIC.POWER_SOURCE]: 01
[BASIC.STACK_VERSION]: 02
[BASIC.POWER_SOURCE__BATTERY]: 00
[BASIC.POWER_SOURCE__DC_SOURCE]: 00
}
Channel: 7
{
[GROUPS.VIEW_GROUP_RESPONSE.GROUP_NAME]: 00
[GROUPS.VIEW_GROUP.GROUP_ID]: 00 00
[GROUPS.REMOVE_GROUP_RESPONSE.STATUS]: 00
[GROUPS.ADD_GROUP_IF_IDENTIFYING.GROUP_NAME]: 00
[GROUPS.REMOVE_GROUP.GROUP_ID]: 00 00
[GROUPS.REMOVE_ALL_GROUPS.ACTION]: 00
[GROUPS.ADD_GROUP_IF_IDENTIFYING.GROUP_ID]: 00 00
[GROUPS.ADD_GROUP.GROUP_NAME]: 00
[GROUPS.VIEW_GROUP_RESPONSE.STATUS]: 00
[GROUPS.ADD_GROUP.GROUP_ID]: 00 00
[GROUPS.ADD_GROUP_RESPONSE.STATUS]: 00
[GROUPS.GET_GROUP_MEMBERSHIP_RESPONSE.CAPACITY]: 00
[GROUPS.NAME_SUPPORT__SUPPORTED]: 00
[GROUPS.GET_GROUP_MEMBERSHIP.GROUP_COUNT]: 00
[GROUPS.NAME_SUPPORT]: 00
[GROUPS.GET_GROUP_MEMBERSHIP.GROUP_LIST]: 00
}
}
VALUES
{
Channel: 15
{
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.VERSION]: 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.TOUCHLINK_INFORMATION_RESP__TOUCHLINK_PRIORITY_REQUEST]: 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.TOUCHLINK_INFORMATION_RESP__TOUCHLINK_INITIATOR]: 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.TOUCHLINK_INFORMATION_RESP__ADDRESS_ASSIGNMENT]: 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.TOTAL_GROUP_IDENTIFIERS]: 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.TOUCHLINK_INFORMATION_RESP__FACTORY_NEW]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_START_REQUEST.INTER_PAN_TRANSACTION_ID]: 00 00 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_ROUTER_REQUEST.FREE_GROUP_IDENTIFIER_RANGE_BEGIN]: 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_ROUTER_REQUEST.ENCRYPTED_NETWORK_KEY]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_ROUTER_REQUEST.FREE_NETWORK_ADDRESS_RANGE_END]: 00 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.GROUP_IDENTIFIER_COUNT]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_ROUTER_REQUEST.FREE_NETWORK_ADDRESS_RANGE_BEGIN]: 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_START_REQUEST.GROUP_IDENTIFIERS_END]: 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_ROUTER_REQUEST.EXTENDED_PAN_ID]: 00 00 00 00 00 00 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_END_DEVICE_REQUEST.NETWORK_ADDRESS]: 00 00
[TOUCHLINK_COMMISSIONING.ENDPOINT_INFORMATION.PROFILE_ID]: 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_END_DEVICE_REQUEST.KEY_INDEX]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_END_DEVICE_REQUEST.GROUP_IDENTIFIERS_BEGIN]: 00 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.TOUCHLINK_INFORMATION_RESP]: 00
[TOUCHLINK_COMMISSIONING.DEVICE_INFORMATION_REQUEST.INTER_PAN_TRANSACTION_ID]: 00 00 00 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST.INTER_PAN_TRANSACTION_ID]: 00 00 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_END_DEVICE_REQUEST.FREE_NETWORK_ADDRESS_RANGE_BEGIN]: 00 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.NETWORK_ADDRESS]: 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_END_DEVICE_REQUEST.FREE_GROUP_IDENTIFIER_RANGE_END]: 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_END_DEVICE_REQUEST.FREE_GROUP_IDENTIFIER_RANGE_BEGIN]: 00 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.EXTENDED_PAN_ID]: 00 00 00 00 00 00 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_START_REQUEST.KEY_INDEX]: 00
[TOUCHLINK_COMMISSIONING.ENDPOINT_INFORMATION.IEEE_ADDRESS]: 00 00 00 00 00 00 00 00
[TOUCHLINK_COMMISSIONING.ENDPOINT_INFORMATION.DEVICE_ID]: 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_ROUTER_REQUEST.KEY_INDEX]: 00
[TOUCHLINK_COMMISSIONING.DEVICE_INFORMATION_REQUEST_RESPONSE.SIZE]: 00
[TOUCHLINK_COMMISSIONING.DEVICE_INFORMATION_REQUEST_RESPONSE.DEVICE_INFORMATION_RECORDS]: 00
[TOUCHLINK_COMMISSIONING.ENDPOINT_INFORMATION.ENDPOINT_ID]: 00
[TOUCHLINK_COMMISSIONING.RESET_TO_FACTORY_NEW_REQUEST.INTER_PAN_TRANSACTION_ID]: 00 00 00 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.NETWORK_UPDATE_ID]: 00
[TOUCHLINK_COMMISSIONING.DEVICE_INFORMATION_REQUEST.START_INDEX]: 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.ENDPOINT_ID]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_END_DEVICE_REQUEST.PAN_ID]: 00 00
[TOUCHLINK_COMMISSIONING.GET_GROUP_IDENTIFIERS_REQUEST_RESPONSE.TOTAL]: 00
[TOUCHLINK_COMMISSIONING.IDENTIFY_REQUEST.IDENTIFY_DURATION]: 00 00
[TOUCHLINK_COMMISSIONING.DEVICE_INFORMATION_REQUEST_RESPONSE.NUMBER_OF_SUBDEVICES]: 00
[TOUCHLINK_COMMISSIONING.ENDPOINT_INFORMATION.VERSION]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_ROUTER_REQUEST.GROUP_IDENTIFIERS_END]: 00 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.NUMBER_OF_SUBDEVICES]: 00
[TOUCHLINK_COMMISSIONING.GET_ENDPOINT_LIST_REQUEST.START_INDEX]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_UPDATE_REQUEST.NETWORK_ADDRESS]: 00 00
[TOUCHLINK_COMMISSIONING.GET_ENDPOINT_LIST_REQUEST_RESPONSE.ENDPOINT_INFORMATION_RECORDS]: 00
[TOUCHLINK_COMMISSIONING.GET_ENDPOINT_LIST_REQUEST_RESPONSE.TOTAL]: 00
[TOUCHLINK_COMMISSIONING.GET_GROUP_IDENTIFIERS_REQUEST_RESPONSE.COUNT]: 00
[TOUCHLINK_COMMISSIONING.IDENTIFY_REQUEST.INTER_PAN_TRANSACTION_ID]: 00 00 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_UPDATE_REQUEST.LOGICAL_CHANNEL]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_END_DEVICE_REQUEST.ENCRYPTED_NETWORK_KEY]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_END_DEVICE_REQUEST.INTER_PAN_TRANSACTION_ID]: 00 00 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_UPDATE_REQUEST.NETWORK_UPDATE_ID]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_END_DEVICE_REQUEST.FREE_NETWORK_ADDRESS_RANGE_END]: 00 00
[TOUCHLINK_COMMISSIONING.GET_GROUP_IDENTIFIERS_REQUEST_RESPONSE.GROUP_INFORMATION_RECORDS]: 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.LOGICAL_CHANNEL]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_END_DEVICE_REQUEST.NETWORK_UPDATE_ID]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_ROUTER_REQUEST.LOGICAL_CHANNEL]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_START_REQUEST.FREE_GROUP_IDENTIFIER_RANGE_BEGIN]: 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_ROUTER_REQUEST.GROUP_IDENTIFIERS_BEGIN]: 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_END_DEVICE_REQUEST.GROUP_IDENTIFIERS_END]: 00 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST.TOUCHLINK_INFORMATION_REQ__ADDRESS_ASSIGNMENT]: 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.DEVICE_ID]: 00 00
[TOUCHLINK_COMMISSIONING.GET_ENDPOINT_LIST_REQUEST_RESPONSE.COUNT]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_ROUTER_REQUEST.NETWORK_ADDRESS]: 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_ROUTER_REQUEST.FREE_GROUP_IDENTIFIER_RANGE_END]: 00 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.KEY_BITMASK]: 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_ROUTER_REQUEST.NETWORK_UPDATE_ID]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_ROUTER_REQUEST.PAN_ID]: 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_ROUTER_REQUEST_RESPONSE.STATUS]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_START_REQUEST.ENCRYPTED_NETWORK_KEY]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_START_REQUEST.EXTENDED_PAN_ID]: 00 00 00 00 00 00 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_START_REQUEST.INITIATOR_IEEE_ADDRESS]: 00 00 00 00 00 00 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_START_REQUEST.FREE_GROUP_IDENTIFIER_RANGE_END]: 00 00
[TOUCHLINK_COMMISSIONING.ENDPOINT_INFORMATION.NETWORK_ADDRESS]: 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_START_REQUEST.FREE_NETWORK_ADDRESS_RANGE_BEGIN]: 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_START_REQUEST.FREE_NETWORK_ADDRESS_RANGE_END]: 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_END_DEVICE_REQUEST_RESPONSE.STATUS]: 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST.TOUCHLINK_INFORMATION_REQ__LINK_INITIATOR]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_START_REQUEST.GROUP_IDENTIFIERS_BEGIN]: 00 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST.ZIGBEE_INFORMATION]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_END_DEVICE_REQUEST.EXTENDED_PAN_ID]: 00 00 00 00 00 00 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_START_REQUEST.INITIATOR_NETWORK_ADDRESS]: 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_START_REQUEST_RESPONSE.STATUS]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_START_REQUEST.LOGICAL_CHANNEL]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_ROUTER_REQUEST.INTER_PAN_TRANSACTION_ID]: 00 00 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_UPDATE_REQUEST.INTER_PAN_TRANSACTION_ID]: 00 00 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_START_REQUEST.NETWORK_ADDRESS]: 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_START_REQUEST.PAN_ID]: 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_START_REQUEST_RESPONSE.NETWORK_UPDATE_ID]: 00
[TOUCHLINK_COMMISSIONING.NETWORK_UPDATE_REQUEST.EXTENDED_PAN_ID]: 00 00 00 00 00 00 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_UPDATE_REQUEST.PAN_ID]: 00 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST.TOUCHLINK_INFORMATION_REQ]: 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST.ZIGBEE_INFORMATION__LOGICAL_TYPE]: 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST.ZIGBEE_INFORMATION__RX_ON_WHEN_IDLE]: 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST.TOUCHLINK_INFORMATION_REQ__FACTORY_NEW]: 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.PAN_ID]: 00 00
[TOUCHLINK_COMMISSIONING.GET_GROUP_IDENTIFIERS_REQUEST.START_INDEX]: 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.PROFILE_ID]: 00 00
[TOUCHLINK_COMMISSIONING.NETWORK_JOIN_END_DEVICE_REQUEST.LOGICAL_CHANNEL]: 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.RESPONSE_ID]: 00 00 00 00
[TOUCHLINK_COMMISSIONING.SCAN_REQUEST_RESPONSE.RSSI_CORRECTION]: 00
}
Channel: 1
{
[ONOFF]: 00
[ACTIVEPOWER]: 01 90
}
Channel: 0
{
[UNREACH]: 00
[LAST_PACKET_RECEIVED]: 5e d9 1e 35
[STICKY_UNREACH]: 00
[CONFIG_PENDING]: 00
}
Channel: 11
{
[ONOFF.GLOBAL_SCENE_CONTROL]: 01
[ONOFF.ON_TIME]: 00 00
[ONOFF.ONOFF]: 01
[ONOFF.OFF.ACTION]: 00
[ONOFF.TOGGLE.ACTION]: 00
[ONOFF.OFF_WAIT_TIME]: 00 00
[ONOFF.ON.ACTION]: 00
}
Channel: 13
{
[ELECTRICAL_MEASUREMENT.MEASUREMENT_TYPE__REACTIVE_MEASUREMENT]: 00
[ELECTRICAL_MEASUREMENT.MEASUREMENT_TYPE__ACTIVE_MEASUREMENT]: 00
[ELECTRICAL_MEASUREMENT.MEASUREMENT_TYPE]: 00 00 00 08
[ELECTRICAL_MEASUREMENT.MEASUREMENT_TYPE__DC_MEASUREMENT]: 00
[ELECTRICAL_MEASUREMENT.ACTIVE_POWER]: 01 90
[ELECTRICAL_MEASUREMENT.MEASUREMENT_TYPE__POWER_QUALITY_MEASUREMENT]: 00
[ELECTRICAL_MEASUREMENT.MEASUREMENT_TYPE__HARMONICS_MEASUREMENT]: 00
[ELECTRICAL_MEASUREMENT.MEASUREMENT_TYPE__PHASE_A_MEASUREMENT]: 01
[ELECTRICAL_MEASUREMENT.MEASUREMENT_TYPE__PHASE_B_MEASUREMENT]: 00
[ELECTRICAL_MEASUREMENT.MEASUREMENT_TYPE__APPARENT_MEASUREMENT]: 00
[ELECTRICAL_MEASUREMENT.MEASUREMENT_TYPE__PHASE_C_MEASUREMENT]: 00
}
}
I have firmware 3.0.x installed.
Felix
Hi @Adrian,
I switched to stack 3.0, put the XML file in the corresponding folder and restarted homegear. Now everything works with the Hue bulb. Thanks! 
I’m just a little confused about how to control the color of the bulb. Property XY works with “x,y” values but what values does RGB expect? Values like “r,b,g” or “r g b” are not accepted, also HEX does not work. Instead I see 4 changes in MQTT for properties LEVEL, SATURATION, RGB, RGB after sending a value to RGB. Color temperature works as expected with values in Kelvin (e.g. for HUE from 2000 - 6500 Kelvin).
Also “LEVEL” seems to mean “BRIGHTNESS” but it can’t be set to 0. The bulb always stays at a LEVEL of 15 as minimum (I think).
These are the current channels / properties for my bulb:
MASTER
{
Channel: 0
{
[ROUTER]: 01
[MAINS_POWERED]: 01
[END_POINT]: 0b 00
[SHORT_ADDR]: 39 ac
[LISTENING]: 01
}
}
VALUES
{
Channel: 1
{
[Y]: 00
[XY]: 00
[STATE]: 01
[X]: 00
[COLOR_TEMPERATURE]: a7
[COLORMODE]: 00
[LEVEL]: 00
[SATURATION]: 00
[HUE]: 00
[RGB]: 00 00 00
}
Channel: 0
{
[UNREACH]: 00
[STICKY_UNREACH]: 00
[CONFIG_PENDING]: 01
[LAST_PACKET_RECEIVED]: 00
}
}
Regards,
Carsten
The channels look wrong. It’s like the querying the device failed badly. Could you please try to unpair it and pair it again?
The RGB is supposed to set the color by setting it to a value that contains R, G, B in three bytes. For example 0xFF0000 is full red, 0x0000FF is full blue. I cannot be sure it works on all light bulbs out there, since it actually sets internally some other values which might not be exposed in all of them.
As for LEVEL, indeed in some lightbulbs that can happen, they have it limited to a certain range. If querying the device works, there are some other parameters that allow you to turn it on/off.
HI @Adrian,
I did re-pair the bulb - this time via CLI - but nothing changed. The count of channels as well as their properties stay the same. Also while brigthness, color temperature and state switching are working, rgb values like FF0000 are still not accepted.
Can it be related with my somehow messed up installation of the homegear zigbee module (see post https://forum.homegear.eu/t/zigbee-erste-erfahrungen/3500/28?u=cnowden)?
Also the CLI warned me about the state “pending configuration” of the two zigbee devices when I used command “ron” in order to unpair and to remove them.
Regards,
Carsten
The ‘pending configuration’ is because querying the device did not work until the end:
[CONFIG_PENDING]: 01In fact, it went very badly since there are no channels present at all that are obtained by querying the device. Since those are not present there, I cannot tell why is RGB not working. The RGB parameter is handled in a special manner inside the zigbee module, it’s actually based on three values, LEVEL, SATURATION and HUE. Those also correspond to some zigbee attributes and commands in the zigbee color control cluster. Maybe some of those are not really implemented by the bulb. Some light bulbs might have an issue with the order of settings those params (I had that issue with a Hommie one, I think).
It’s difficult to tell what’s happening in your case without seeing a log with the pairing process with a debug level set to some high value.
Hi,
A couple of more things to be checked:
- please ensure that the
zigbee-clusters.xmlis present in/etc/homegear/families. With that file absent, there would be no attributes and commands identified for clusters, so the channels wouldn’t be generated - please make sure that there isn’t something else accessing the stick.
Hi Adrian,
yes this was the right hint! The file is missing in my installation. I tried to de- and re-install the module, but the file was not written. 
Is there any log where I can see what’s going wrong while the installation process of the zigbee module? I can’t see any errors in the shell.
Can you provide me this xml also? Thanks!
Regards,
Carsten
I’ll send it to you attached to a PM.
After you copy it in /etc/homegear/families, please restart homegear, unpair the device then pair it again.
It would be nice if it would be possible to first delete the homegear.log in /var/log/homegear` then do the pairing. Then perhaps try to set the RGB value, too, then if possible send me the log in a PM…
Thank you!
Adrian Roman