[Zigbee] Erste Erfahrungen

Bei mir ist der Sensor eher komisch. Es scheint so, als wenn der Sensor Zahlen anstatt true/false für Motion liefert. Hatte aber noch keine Zeit mir das genauer anzusehen.

Ist das bei dir auch so?

Family 26> ls
  ID │ Name                            │      Serial Number │ Type │ Type String
─────┼─────────────────────────────────┼────────────────────┼──────┼────────────
     │                                 │                    │      │
 279 │ Plug 01 0x3                     │ ZG037cb03eaa00a... │ 0008 │ bbaaPlug...
 280 │ lumi.sensor_motion.aq2 0x1      │ ZG0100158d00023... │ 0009 │ 1037lumi...
─────┴─────────────────────────────────┴────────────────────┴──────┴────────────

Family 26 - peer 280> config print
MASTER
{
    Channel: 10
    {
            [OCCUPANCY_SENSING_REPORTING_CONFIG.OCCUPANCY.MIN_REPORTING_INTERVAL]: 00 00
            [OCCUPANCY_SENSING_REPORTING_CONFIG.OCCUPANCY.MAX_REPORTING_INTERVAL]: 00 00
    }
    Channel: 5
    {
            [IDENTIFY.IDENTIFY_QUERY_RESPONSE.IDENTIFY_TIME]: 00 00
            [IDENTIFY.IDENTIFY.IDENTIFY_TIME]: 00 00
            [IDENTIFY.IDENTIFY_TIME]: 00 00
            [IDENTIFY.IDENTIFY_QUERY.ACTION]: 00
    }
    Channel: 0
    {
            [ROUTER]: 00
            [MAINS_POWERED]: 00
            [END_POINT]: 01 00
            [SHORT_ADDR]: 55 44
            [LISTENING]: 00
    }
    Channel: 8
    {
            [ILLUMINANCE_MEASUREMENT_REPORTING_CONFIG.MEASURED_VALUE.REPORTABLE_CHANGE]: 00 00
            [ILLUMINANCE_MEASUREMENT_REPORTING_CONFIG.MEASURED_VALUE.MAX_REPORTING_INTERVAL]: 00 00
            [ILLUMINANCE_MEASUREMENT_REPORTING_CONFIG.MEASURED_VALUE.MIN_REPORTING_INTERVAL]: 00 00
    }
    Channel: 1
    {
            [BASIC.POWER_SOURCE__SECONDARY_POWER_SOURCE]: 00
            [BASIC.ZCL_VERSION]: 00
            [BASIC.POWER_SOURCE__MAINS_3_PHASE]: 00
            [BASIC.POWER_SOURCE]: 00
            [BASIC.POWER_SOURCE__BATTERY]: 00
            [BASIC.POWER_SOURCE__DC_SOURCE]: 00
            [BASIC.POWER_SOURCE__MAINS_SINGLE_PHASE]: 00
            [BASIC.MODEL_IDENTIFIER]: 6c 75 6d 69 2e 73 65 6e 73 6f 72 5f 6d 6f 74 69 6f 6e 2e 61 71 32
            [BASIC.POWER_SOURCE__UNKNOWN]: 00
            [BASIC.POWER_SOURCE__EMERGENCY_MAINS_AND_TRANSFER_SWITCH]: 00
            [BASIC.POWER_SOURCE__EMERGENCY_MAINS_CONSTANTLY_POWERED]: 00
    }
}

VALUES
{
    Channel: 11
    {
            [IAS_ZONE.ZONE_TYPE]: 00 00
            [IAS_ZONE.ZONE_ID]: 00
            [IAS_ZONE.ZONE_STATUS__BATTERY]: 00
            [IAS_ZONE.ZONE_ENROLL_RESPONSE.ZONE_ID]: 00
            [IAS_ZONE.ZONE_STATUS__TROUBLE]: 00
            [IAS_ZONE.ZONE_ENROLL_RESPONSE.ENROLL_RESPONSE_CODE]: 00
            [IAS_ZONE.IAS_CIE_ADDRESS]: 00 00 00 00 00 00 00 00
            [IAS_ZONE.ZONE_ENROLL.ZONE_TYPE]: 00 00
            [IAS_ZONE.ZONE_STATUS__RESTORE_REPORTS]: 00
            [IAS_ZONE.ZONE_ENROLL.MANUFACTURER_CODE]: 00 00
            [IAS_ZONE.ZONE_STATE]: 00
            [IAS_ZONE.ZONE_STATUS__TEST]: 00
            [IAS_ZONE.ZONE_STATUS__AC_MAINS]: 00
            [IAS_ZONE.ZONE_STATUS]: 00 00
            [IAS_ZONE.ZONE_STATUS__ALARM1]: 00
            [IAS_ZONE.ZONE_STATUS__SUPERVISION_REPORTS]: 00
            [IAS_ZONE.ZONE_STATUS__ALARM2]: 00
            [IAS_ZONE.ZONE_STATUS__BATTERY_DEFECT]: 00
            [IAS_ZONE.ZONE_STATUS__TAMPER]: 00
    }
    Channel: 9
    {
            [OCCUPANCY_SENSING.OCCUPANCY__OCCUPIED]: 01
            [OCCUPANCY_SENSING.OCCUPANCY]: 01
            [OCCUPANCY_SENSING.OCCUPANCY_SENSOR_TYPE]: 00
    }
    Channel: 0
    {
            [UNREACH]: 00
            [LOWBAT]: 00
            [STICKY_UNREACH]: 00
            [CONFIG_PENDING]: 01
            [LAST_PACKET_RECEIVED]: 5e a7 22 a1
    }
    Channel: 7
    {
            [ILLUMINANCE_MEASUREMENT.MIN_MEASURED_VALUE]: 00 00
            [ILLUMINANCE_MEASUREMENT.MAX_MEASURED_VALUE]: 00 00
            [ILLUMINANCE_MEASUREMENT.MEASURED_VALUE]: 00 01
    }
}

Oder ist der einfach nur schlecht angelernt? Ich weiss ja, dass die Xiaomi Sensoren mitunter zickig sind. :wink:

Hi @job,

also bei mir sendet er immer true bei erkannter Bewegung (leider ein false nach Zeit XY ohne Bewegung, aber gut … irgendwo muss der Preis ja herkommen :wink: ).

Die Helligkeit ist bei dem Teil eigentlich nur ein nettes Gimmik, laesst sich aber nicht wirklich grossartig verwenden … die wird naemlich nur gesendet, wenn auch Motion erkannt wurde :wink:

– Micha

1 Like

One problem with zigbee battery devices is that they tend to go to sleep before finishing querying them.

There is nothing one can do about it in code, pressing the button on the device once each 6-10 seconds might help to keep it awake, but it’s not a warranty. Pressing too fast prevents querying it, as the device sends notifications instead of replying to queries, pressing too seldom will not prevent it going to sleep. It can be quite hard of getting it right. In your case, querying did not finish (notice the CONFIG_PENDING still 1).

Now, as for your concern of the notification, what you have there are generic values, dynamically generated by the zigbee module from info obtained while querying the device. The occupancy is one byte (OCCUPANCY_SENSING.OCCUPANCY) which is basically a number. There is also a bitmask (OCCUPANCY_SENSING.OCCUPANCY__OCCUPIED) which in this case it’s only a bit (if I recall correctly) and in this particular case it could be interpreted as a boolean. For bitmasks this is not always the case and you get numbers because of the generic handling.

Now, I think I already provided a device xml file for that particular device (still work in progress, I’m trying to see if I could add battery voltage info in there from a manufacturer specific report). With that file in place (in the 26 devices directory) you’ll get OCCUPANCY as a boolean variable in the channel 1 (also the ILLUMINATION variable will be there).
You’ll need to unpair and pair the device again, because the info for the devices changes with the addition of the one from the device xml file.

I attach it here if you want to just drop it into the 26 directory.1037lumi.sensor_motion.aq21.xml (10.9 KB)

This might suffer changes in the future, as already mentioned I’m trying to add battery voltage info.

3 Likes

Ich habe einige der Sensoren mit Zigbee2mqtt am laufen. Nach einem vernünftigen Einbinden funktionieren die eigentlich ganz gut.

Hmm. Das sehe ich bei zigbee2mqtt nicht so. Ich bekomme regelmäßig Helligkeitsmeldungen, unabhängig ob Bewegung da ist oder nicht. OCCUPANCY true/false kommt dann entsprechend mit. Ich meine sogar, es wird jede “merkliche” Helligkeitsveränderungen mitgeteilt, also irgendein Schwellenwert der Veränderung.

Das entspricht auch dem Verhalten des Aqara Temperatursensors. Ich habe so einen an meinem Heizkessel und messe damit die Heiz- bzw. Abkühlphase. Zur Zeit, sendet er so gut wie gar nicht, da die Heizung aus ist. Ist der Kessel an, teilweise sekündlich.

Habe das gestern mal getestet, nachdem der Micha das geschrieben hatte. Als ich in einem abgedunkelten Raum das Licht für 10s eingeschaltet habe, wurde das nicht direkt übermittelt, erst mit dem Bewegungsereignis. Vielliecht ist das Intervall bei Helligkeit größer als bei der Temperatur, da sind Sprünge ja eher möglich. :thinking:

1 Like

Hmm. Ich beobachte das mal bei zigbee2mqtt mit dem mqttexplorer. Vielleicht erinnere ich mich ja auch falsch.

Edit:

Ich erinnere mich nicht falsch. Hier mal ein Bewegungsmelder:

Occupancy:

Illuminance:

Der Zeitraum ist aber nicht allzu kurz. :wink:
Ich lass das mal mitlaufen, mal schauen, wie oft die Dinger senden.

Es könnte sein, das 90s nach Bewegung und sonst alle 30m eine Nachricht gesendet wird.

2 Likes

Reporting values is typically configurable. The zigbee module tries to configure them in a reasonable manner (or if provided, with values from a configuration file), but for battery devices where config pending remains to 1, that might not succeed, so the device stays with default settings, which depend on the device.

If configuring succeeds, the default is to report a value change and also send the value at a time interval (one hour for sleeping devices, 10 minutes for online).

In principle the configuration can be changed later by items exposed in config channels (those with REPORTING_CONFIG in the name), but for battery devices it might not work, since they are sleeping (perhaps by repeatedly sending the packet and waking up the device from the button?).

3 Likes

Schön, dass ich nicht der einzige bin, der nun mit Zigbee over Homegear loslegt.

Ich habe ZIGBEE installiert und auch recht schnell den Xiaomi / Aqara Zweifach-Wandschalter über die admin-ui angelernt. Aber von den angeblich vorhandenen 19 Channels sehr ich im MQTT-Explorer nur 9, und ein Schaltvorgang wird nicht übermittelt:

Family 26 - peer 6> channel count
Peer has 19 channels.
Family 26 - peer 6> config print
MASTER
{
Channel: 14
{
[ONOFF_REPORTING_CONFIG.ONOFF.MIN_REPORTING_INTERVAL]: 00 00
[ONOFF_REPORTING_CONFIG.ONOFF.MAX_REPORTING_INTERVAL]: 00 00
}
Channel: 11
{
[SCENES.VIEW_SCENE_RESPONSE.TRANSITION_TIME]: 00 00
[SCENES.VIEW_SCENE.GROUP_ID]: 00 00
[SCENES.STORE_SCENE_RESPONSE.STATUS]: 00
[SCENES.REMOVE_SCENE_RESPONSE.STATUS]: 00
[SCENES.VIEW_SCENE_RESPONSE.EXTENSION_FIELD_SETS]: 00
[SCENES.VIEW_SCENE.SCENE_ID]: 00
[SCENES.SCENE_COUNT]: 00
[SCENES.REMOVE_ALL_SCENES_RESPONSE.STATUS]: 00
[SCENES.REMOVE_SCENE.GROUP_ID]: 00 00
[SCENES.ADD_SCENE_RESPONSE.STATUS]: 00
[SCENES.VIEW_SCENE_RESPONSE.SCENE_NAME]: 00
[SCENES.RECALL_SCENE.SCENE_ID]: 00
[SCENES.ADD_SCENE.TRANSITION_TIME]: 00 00
[SCENES.VIEW_SCENE_RESPONSE.STATUS]: 00
[SCENES.ADD_SCENE.SCENE_NAME]: 00
[SCENES.ADD_SCENE.GROUP_ID]: 00 00
[SCENES.STORE_SCENE.SCENE_ID]: 00
[SCENES.ADD_SCENE.EXTENSION_FIELD_SETS]: 00
[SCENES.CURRENT_GROUP]: 00 00
[SCENES.GET_SCENE_MEMBERSHIP_RESPONSE.STATUS]: 00
[SCENES.CURRENT_SCENE]: 00
[SCENES.GET_SCENE_MEMBERSHIP.GROUP_ID]: 00 00
[SCENES.REMOVE_ALL_SCENES.GROUP_ID]: 00 00
[SCENES.GET_SCENE_MEMBERSHIP_RESPONSE.CAPACITY]: 00
[SCENES.STORE_SCENE.GROUP_ID]: 00 00
[SCENES.GET_SCENE_MEMBERSHIP_RESPONSE.SCENE_LIST]: 00
[SCENES.LAST_CONFIGURED_BY]: 00 00 00 00 00 00 00 00
[SCENES.SCENE_VALID]: 00
[SCENES.ADD_SCENE.SCENE_ID]: 00
[SCENES.NAME_SUPPORT]: 00
[SCENES.NAME_SUPPORT__SUPPORTED]: 00
[SCENES.REMOVE_SCENE.SCENE_ID]: 00
[SCENES.RECALL_SCENE.GROUP_ID]: 00 00
}
Channel: 18
{
[BINARY_OUTPUT_REPORTING_CONFIG.STATUS_FLAGS.MIN_REPORTING_INTERVAL]: 00 00
[BINARY_OUTPUT_REPORTING_CONFIG.STATUS_FLAGS.MAX_REPORTING_INTERVAL]: 00 00
[BINARY_OUTPUT_REPORTING_CONFIG.PRESENT_VALUE.MAX_REPORTING_INTERVAL]: 00 00
[BINARY_OUTPUT_REPORTING_CONFIG.PRESENT_VALUE.MIN_REPORTING_INTERVAL]: 00 00
}
Channel: 1
{
[BASIC.POWER_SOURCE__SECONDARY_POWER_SOURCE]: 00
[BASIC.ZCL_VERSION]: 01
[BASIC.POWER_SOURCE__MAINS_3_PHASE]: 00
[BASIC.POWER_SOURCE__EMERGENCY_MAINS_CONSTANTLY_POWERED]: 00
[BASIC.POWER_SOURCE__DC_SOURCE]: 00
[BASIC.POWER_SOURCE__BATTERY]: 00
[BASIC.DATE_CODE]: 30 36 2d 32 35 2d 32 30 31 38
[BASIC.POWER_SOURCE__UNKNOWN]: 01
[BASIC.POWER_SOURCE__EMERGENCY_MAINS_AND_TRANSFER_SWITCH]: 00
[BASIC.HW_VERSION]: 12
[BASIC.POWER_SOURCE]: 01
[BASIC.STACK_VERSION]: 02
[BASIC.MANUFACTURER_NAME]: 4c 55 4d 49
[BASIC.POWER_SOURCE__MAINS_SINGLE_PHASE]: 00
[BASIC.APPLICATION_VERSION]: 21
[BASIC.MODEL_IDENTIFIER]: 6c 75 6d 69 2e 63 74 72 6c 5f 6c 6e 32 2e 61 71 31
}
Channel: 0
{
[ROUTER]: 01
[MAINS_POWERED]: 01
[END_POINT]: 01 00
[SHORT_ADDR]: a1 7a
[LISTENING]: 01
}
Channel: 7
{
[IDENTIFY.IDENTIFY_QUERY_RESPONSE.IDENTIFY_TIME]: 00 00
[IDENTIFY.IDENTIFY.IDENTIFY_TIME]: 00 00
[IDENTIFY.IDENTIFY_TIME]: 00 00
[IDENTIFY.IDENTIFY_QUERY.ACTION]: 00
}
Channel: 3
{
[POWER_CONFIGURATION.MAINS_VOLTAGE]: 08 c0
}
Channel: 5
{
[DEVICE_TEMPERATURE_CONFIGURATION.CURRENT_TEMPERATURE]: 00 1a
}
Channel: 9
{
[GROUPS.VIEW_GROUP.GROUP_ID]: 00 00
[GROUPS.REMOVE_GROUP_RESPONSE.STATUS]: 00
[GROUPS.REMOVE_GROUP.GROUP_ID]: 00 00
[GROUPS.NAME_SUPPORT__SUPPORTED]: 01
[GROUPS.GET_GROUP_MEMBERSHIP_RESPONSE.CAPACITY]: 00
[GROUPS.REMOVE_ALL_GROUPS.ACTION]: 00
[GROUPS.GET_GROUP_MEMBERSHIP.GROUP_LIST]: 00
[GROUPS.VIEW_GROUP_RESPONSE.STATUS]: 00
[GROUPS.ADD_GROUP.GROUP_NAME]: 00
[GROUPS.ADD_GROUP.GROUP_ID]: 00 00
[GROUPS.ADD_GROUP_IF_IDENTIFYING.GROUP_NAME]: 00
[GROUPS.ADD_GROUP_RESPONSE.STATUS]: 00
[GROUPS.VIEW_GROUP_RESPONSE.GROUP_NAME]: 00
[GROUPS.NAME_SUPPORT]: 80
[GROUPS.ADD_GROUP_IF_IDENTIFYING.GROUP_ID]: 00 00
[GROUPS.GET_GROUP_MEMBERSHIP.GROUP_COUNT]: 00
}
}

VALUES
{
Channel: 13
{
[ONOFF.TOGGLE.ACTION]: 00
[ONOFF.ONOFF]: 00
[ONOFF.OFF.ACTION]: 00
[ONOFF.ON.ACTION]: 00
}
Channel: 17
{
[BINARY_OUTPUT.STATUS_FLAGS__OVERRIDDEN]: 00
[BINARY_OUTPUT.PRESENT_VALUE]: 00
[BINARY_OUTPUT.OUT_OF_SERVICE]: 00
[BINARY_OUTPUT.STATUS_FLAGS]: 00
[BINARY_OUTPUT.STATUS_FLAGS__OUT_OF_SERVICE]: 00
[BINARY_OUTPUT.STATUS_FLAGS__FAULT]: 00
[BINARY_OUTPUT.STATUS_FLAGS__IN_ALARM]: 00
}
Channel: 0
{
[UNREACH]: 00
[STICKY_UNREACH]: 00
[CONFIG_PENDING]: 00
[LAST_PACKET_RECEIVED]: 5e a9 ae 65
}
Channel: 15
{
[TIME.TIME_STATUS__SUPERSEDING]: 00
[TIME.TIME_STATUS__MASTER_ZONE_DST]: 00
[TIME.TIME]: 00 00 00 00
[TIME.TIME_STATUS]: 00
[TIME.TIME_STATUS__SYNCHRONIZED]: 00
[TIME.TIME_STATUS__MASTER]: 00
}
}

Soll man fehlende Kanäle manuell ergänzen? Beim Anlernen über die admin-ui werde ich bei ‘select devices’ nach secure oder insecure gefragt - was ist damit gemeint?

I’m not sure I understand this correctly (I’m using google translate).

If reports are sent from the device, you should see the change in ON/OFF in the channel 13, ONOFF.ONOFF value.

On the other hand, if you want to switch it ON or OFF, you have the option of either setting ONOFF.OFF.ACTION to turn it off and ONOFF.ON.ACTION to turn in on, or if you want to toggle it no matter of its state, you could use ONOFF.TOGGLE.ACTION.

I could probably provide an xml file for that device that should expose an ONOFF value in channel 1 in VALUES, which is both readable and writable.

The reason you see this

[ONOFF.TOGGLE.ACTION]: 00
[ONOFF.ONOFF]: 00
[ONOFF.OFF.ACTION]: 00
[ONOFF.ON.ACTION]: 00

in the channel 13 is because of the ZigBee specs: there is an ONOFF attribute that is read only and the ACTION ones actually come from separate command packets definitions.

I am so happy to reduce the amount of programmes running on my RasPi (actual, only Mosquitto, Homegear, NodeRED and NGrok are installed) and I could eliminate Zigbee2MQTT. Quite funny, the readings from Zigbee2MQTT were different if I remember correctly. I would be very happy if you can submit that XML-file.
BTW, did you try to connect IKEA’s lamps within Homegear?

I’ll try to make one tomorrow. I might ask you for more info about that device.

As for the lamps, I personally tested Philips Hue and Hommie. Others should work, too, as long as they respect ZigBee specs.

Now I think I see one of the issues you have: why there are missing channels.

It’s hard to be certain without seeing the log while the device is paired, but probably the device reports as supported some clusters, but then when queried about them it reports that it doesn’t actually support attributes/commands. As such, those channels remain empty and are not displayed.

I reinstalled again. Now, I can switch ONOFF on channel 13. But only the left switch, no chance for the right one (I’m using the double key version). Maybe doubling the XML-entry can help?
The IKEA-lamp (LED1737R5 or LED1739R5) I still couldn’t install. Had no probs with Zigbee2MQTT. Is linkkeyexchange = “no” correct?

linkKeyExchange = “no” should be set, because otherwise a lot of devices won’t join the network, a lot of them are ‘legacy’.

You might need to reset the lamps in order to make them join the network.

As for the ONOFF, it might be the case that you have a device that exposes two end points, one for each switch. If that’s the case, the ZigBee module should create two peers, one for each end point.
As I didn’t have available such a device (with multiple end points like that) to test, I cannot be sure that it works as expected.
Of course, I cannot be sure that is the case with your device, I would need a log with the device pairing to figure it out, with debug level turned to something like 7.

I changed to debug mode 7, and this a extract for my trial to pair with IKEA’s 1537-lamp:

05/02/20 13:12:01.309 Script Engine Server: Info: Client number 1 is calling RPC method: getPairingState
(Integer) 26
05/02/20 13:12:01.310 Script Engine Server: Response:
(Struct length=3)
{
[general] (Array length=1)
[
(Struct length=2)
{
[messageId] (String) l10n.zigbee.pairing.pairOnStart
[variables] (Array length=0)
[
]
}
]
[pairingModeEnabled] (Boolean) 0
[pairingModeEndTime] (Integer64) 1588417921
}
05/02/20 13:12:01.321 Script Engine Server: Info: Client number 1 is calling RPC method: scriptHeaders
(Struct length=5)
{
[Cache-Control] (Array length=1)
[
(String) max-age=0, must-revalidate, private
]
[Content-Type] (Array length=1)
[
(String) application/json
]
[Date] (Array length=1)
[
(String) Sat, 02 May 2020 11:12:01 GMT
]
[RESPONSE_CODE] (Integer) 200
[X-Powered-By] (Array length=1)
[
(String) PHP/7.4.4
]
}
05/02/20 13:12:01.321 Script Engine Server: Response:
(void)
05/02/20 13:12:01.323 Script Engine Server: Info: Client number 1 is calling RPC method: scriptOutput
(String) {“status”:“success”,“message”:“0”}
(Boolean) 0
05/02/20 13:12:01.323 Script Engine Server: Response:
(void)
05/02/20 13:12:01.328 Info: Script with id 54 finished with exit code 0
05/02/20 13:12:01.328 RPC Server (Port 2001): Debug: Connection to client number 104 closed.
05/02/20 13:12:01.328 RPC Server (Port 2001): Debug: Connection to client number 104 closed (1).
05/02/20 13:12:08.012 UPnP Server: Debug: Sending notify packets.
05/02/20 13:12:08.033 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.1.32:64932 accepted. Client number: 105
05/02/20 13:12:08.034 RPC Server (Port 2001): Info: RPC server client id for client number 105 is: 91
05/02/20 13:12:08.035 RPC Server (Port 2001): Listening for incoming packets from client number 105.
05/02/20 13:12:08.035 RPC Server (Port 2001): Debug: Packet received: 474554202F6465736372697074696F6E2E786D6C20485454502F312E310D0A557365722D4167656E743A2050616E61736F6E6963204D494C20444C4E412043502055506E502F312E3020444C4E41444F432F312E35300D0A486F73743A203139322E3136382E312E33343A323030310D0A582D50414E41534F4E49432D526567697374726174696F6E3A204E546845574463344D4639545A584A705A584D410D0A582D50414E41534F4E49432D444D502D50726F66696C653A204D5045475F50535F50414C204A5045475F534D2050565F444956585F444956332050565F444956585F444956342050565F444956585F444956582050565F444956585F445835302050565F44524D5F444956585F444956332050565F44524D5F444956585F444956342050565F44524D5F444956585F444956582050565F44524D5F444956585F445835300D0A0D0A
05/02/20 13:12:08.058 RPC Server (Port 2001): Debug: Connection to client number 105 closed.
05/02/20 13:12:08.058 RPC Server (Port 2001): Debug: Connection to client number 105 closed (1).
05/02/20 13:12:08.254 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.1.31:48038 accepted. Client number: 106
05/02/20 13:12:08.255 RPC Server (Port 2001): Info: RPC server client id for client number 106 is: 92
05/02/20 13:12:08.256 RPC Server (Port 2001): Listening for incoming packets from client number 106.
05/02/20 13:12:08.256 RPC Server (Port 2001): Debug: Packet received: 474554202F6465736372697074696F6E2E786D6C20485454502F312E310D0A4163636570743A202A2F2A0D0A486F73743A203139322E3136382E312E33343A323030310D0A557365722D4167656E743A2054776F6E6B792D4E4D432F382E322E3120284C696E757820332E342E363B2061726D763574656C2920444C4E41444F432F312E35300D0A436F6E6E656374696F6E3A20636C6F73650D0A0D0A
05/02/20 13:12:08.279 RPC Server (Port 2001): Debug: Connection to client number 106 closed.
05/02/20 13:12:08.279 RPC Server (Port 2001): Debug: Connection to client number 106 closed (1).
05/02/20 13:12:08.362 MQTT Client: Debug: MQTT packet received: D000
05/02/20 13:12:08.362 MQTT Client: Debug: Packet received: D000
05/02/20 13:12:08.362 MQTT Client: Debug: Received ping response.
05/02/20 13:12:08.646 IPC Server: Info: Client number 0 is calling RPC method: lifetick Parameters:
05/02/20 13:12:08.647 IPC Server: Response:
(Boolean) 1
05/02/20 13:12:13.952 Module Zigbee: Zigbee serial module “Serial1”: Info: Received packet FE19448100000A00BBB50101005900CCDFC3000005109F000000BBB51DC8
05/02/20 13:12:13.953 Module Zigbee: Zigbee serial module “Serial1”: Info: Received packet FE19448100000A00BBB50101005900CCDFC3000005109F000000BBB51DC8 is MT frame, type: AREQ subsys: AF cmd: 0x81 len: 25
05/02/20 13:12:13.953 Module Zigbee: Zigbee serial module “Serial1”: Info: Received AF incoming MSG notification: 0xFE19448100000A00BBB50101005900CCDFC3000005109F000000BBB51DC8 for src addr: 0xB5BB src endpoint: 0x1 cluster: 0xA
05/02/20 13:12:13.953 Module Zigbee: Zigbee serial module “Serial1”: Info: It’s a ZCL frame: 0x109F000000 for src addr: 0xB5BB src endpoint: 0x1 cluster: 0xA
05/02/20 13:12:13.953 Module Zigbee: Zigbee serial module “Serial1”: Info: ZCL frame type: Global command: read attr
05/02/20 13:12:13.953 05/02/20 13:12:13.953 Zigbee packet received by the central - Sender address: 0x0001B5BB
05/02/20 13:12:13.953 Module Zigbee: Entering packet received
05/02/20 13:12:13.953 Module Zigbee: getValuesFromPacket, packet type: 0xA00
05/02/20 13:12:13.953 Module Zigbee: Entering ParsePacketDynamic
05/02/20 13:12:23.856 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.1.20:62631 accepted. Client number: 107
05/02/20 13:12:23.857 RPC Server (Port 2001): Info: RPC server client id for client number 107 is: 93
05/02/20 13:12:23.858 RPC Server (Port 2001): Listening for incoming packets from client number 107.
05/02/20 13:12:23.858 RPC Server (Port 2001): Debug: Packet received: 474554202F61646D696E2F696E76656E746F72792F6465766963657320485454502F312E310D0A486F73743A203139322E3136382E312E33343A323030310D0A557365722D4167656E743A204D6F7A696C6C612F352E30202857696E646F7773204E542031302E303B20574F5736343B2072763A36382E3029204765636B6F2F32303130303130312046697265666F782F36382E300D0A4163636570743A20746578742F68746D6C2C6170706C69636174696F6E2F7868746D6C2B786D6C2C6170706C69636174696F6E2F786D6C3B713D302E392C2A2F2A3B713D302E380D0A4163636570742D4C616E67756167653A2064652C656E2D55533B713D302E372C656E3B713D302E330D0A4163636570742D456E636F64696E673A20677A69702C206465666C6174650D0A526566657265723A20687474703A2F2F3139322E3136382E312E33343A323030312F61646D696E2F696E76656E746F72792F646576696365732F6164640D0A436F6E6E656374696F6E3A206B6565702D616C6976650D0A436F6F6B69653A2050485053455353494441444D494E3D61663937313866623465393131613663336365343731336539626139366539653B20696F3D323464594F4A4458687246674730302D414141440D0A557067726164652D496E7365637572652D52657175657374733A20310D0A0D0A
05/02/20 13:12:23.859 Web server (Port 2001): Client is requesting: /admin/inventory/devices (translated to /var/lib/homegear/www/rpc/admin/inventory/devices, method: GET)

Can you please have a look why I fail pairing it? I remember I read that IKEA uses a different/older ZIGBEE-version than XIAOMI.

Is it actually going into pairing mode?

I don’t see any packets that switch into network admin mode.

All I see here that might be relevant is an incoming packet that appears to be an ‘attr read’ request (which is quite odd). Looks as being for ‘time’ cluster. homegear won’t reply for such request (yet, now that I’m seeing that I might consider implementing it).

Anyway, that packet, if it’s incoming from the device you are trying to add, shows that’s already in the ZigBee network, just it’s not paired into homegear. The way of solving this is to reset the device and pair it again.

Hey,

mal ne generelle Frage.

hab aktuell noch Zigbee2mqtt am laufen aber da es bei mir nicht sauber funktioniert würde ich gern auf den internen Zigbee von homegear switchen.

Frage Zigbee2mqtt erstmal deinstallieren und wenn ja wie?

Doku ist ja schon online. Muss man was anderes beachten?

Falls es sinnvoller wäre einen eigenen Thread zu machen sagt Bescheid! Dachte nur mit das es nicht hunderte threads mit „Ersten Erfahrungen“ gibt.

Gruß
Der Doc

Brauchst nur den Dienst auszumachen, damit dein „Device“ frei wird.
Steht glaube in der Installationsdoku, da wo auch das Einrichten als Dienst beschrieben ist. :+1:t2:

8 posts were split to a new topic: CC2531 USB-Stick mit Homegear