Plus de Zigbee (et plus de lampes Philips)

XabiX · Juillet 1, 2021, 2:31

Bonjour,

Je ne comprends plus pourquoi je n’arrive plus a piloter mes lampes ni en ajouter des nouvelles. Du coup, j’ai installé l’appli Hue Android et j’ai réussi a reprendre la main en BE sur les lampes et a les mettre a jour (fw).

Par contre j’ai l’impression que je n’ai tjs pas de communication avec ma ConBee II (dernier fw stable). A l’époque j’utilisais Deconz, et j’avais migré au plugin zigbee en beta puis je suis repassé en stable quand cela a été disponible.

En mode inclusion, je vois:


[2021-07-01 16:21:03][DEBUG] : http://127.0.0.1:8089/device/command type : PUT
[2021-07-01 16:21:03][DEBUG] : {"ieee":"00:17:88:01:06:1c:ed:91","cmd":[{"endpoint":11,"cluster":"light_color","command":"move_to_color","await":1,"args":[29523,26681,0]}],"allowQueue":false}
[2021-07-01 16:21:03][DEBUG] : http://127.0.0.1:8089/device/command type : PUT
[2021-07-01 16:21:03][DEBUG] : {"ieee":"00:17:88:01:06:1e:a8:56","cmd":[{"endpoint":11,"cluster":"light_color","command":"move_to_color","await":1,"args":[0,0,0]}],"allowQueue":false}
[2021-07-01 16:21:03][DEBUG] : http://127.0.0.1:8089/device/command type : PUT
[2021-07-01 16:21:03][DEBUG] : {"ieee":"00:17:88:01:06:1c:b7:1a","cmd":[{"endpoint":11,"cluster":"light_color","command":"move_to_color","await":1,"args":[29523,26681,70]}],"allowQueue":false}
[2021-07-01 16:21:04][ERROR] : Erreur exécution de la commande [Chambre Papa][Papa][Couleur] : Erreur lors de la requete : http://127.0.0.1:8089/device/command(PUT), data : {"ieee":"00:17:88:01:06:1c:b7:1a","cmd":[{"endpoint":11,"cluster":"light_color","command":"move_to_color","await":1,"args":[29523,26681,70]}],"allowQueue":false} erreur : {"state":"error","result":"[0x004d:11:0x0300]: Message send failure","code":0}
[2021-07-01 16:21:06][ERROR] : Erreur exécution de la commande [Cuisine][Table][Couleur] : Erreur lors de la requete : http://127.0.0.1:8089/device/command(PUT), data : {"ieee":"00:17:88:01:06:1c:ed:91","cmd":[{"endpoint":11,"cluster":"light_color","command":"move_to_color","await":1,"args":[29523,26681,0]}],"allowQueue":false} erreur : {"state":"error","result":"[0x1882:11:0x0300]: Message send failure","code":0}
[2021-07-01 16:21:06][DEBUG] : http://127.0.0.1:8089/application/include type : PUT
[2021-07-01 16:21:06][DEBUG] : {"duration":180}
[2021-07-01 16:21:06][DEBUG] : ""
[2021-07-01 16:21:15][ERROR] : Erreur exécution de la commande [Chambres Jossua][Couloir Haut][Couleur] : Erreur lors de la requete : http://127.0.0.1:8089/device/command(PUT), data : {"ieee":"00:17:88:01:06:1e:a8:56","cmd":[{"endpoint":11,"cluster":"light_color","command":"move_to_color","await":1,"args":[0,0,0]}],"allowQueue":false} erreur : {"state":"error","result":"[0x0529:11:0x0300]: Message send failure","code":0}

Quand j’execute une aciton sur une lampe, je vois:

[2021-07-01 16:29:11][DEBUG] : http://127.0.0.1:8089/group/command type : PUT
[2021-07-01 16:29:11][DEBUG] : {"ieee":"2","cmd":[{"endpoint":0,"cluster":"on_off","command":"on","await":1}],"allowQueue":false}
[2021-07-01 16:29:11][ERROR] : Erreur exécution de la commande [Cuisine][Cuisine][On] : Erreur lors de la requete : http://127.0.0.1:8089/group/command(PUT), data : {"ieee":"2","cmd":[{"endpoint":0,"cluster":"on_off","command":"on","await":1}],"allowQueue":false} erreur : {"state":"error","result":"Group not found","code":0}

J’avoue être perdu et ne plus savoir que faire (si ce n’est de craquer et d’acheter un pont Hue).

Avez vous des idées, merci à tous?

XabiX

HugoVal11 · Juillet 1, 2021, 3:02

Tu avais des soucis avec Deconz ?

XabiX · Juillet 1, 2021, 3:07

Pas spécialement mais j’appréciais la base de devices reconnue automatiquement par le plugin officiel Zigbee de la team.

J’ai aussi de maj le fw de la clé:

jeedom@Jeedom:~$ md5sum deCONZ_RaspBeeII_0x266e0700.bin.GCF 
6069ad1562b84c292149b5f7c826b046  deCONZ_RaspBeeII_0x266e0700.bin.GCF
jeedom@Jeedom:~$ sudo /usr/bin/GCFFlasher_internal -d /dev/ttyACM1 -t 60 -x 3 -f deCONZ_RaspBeeII_0x266e0700.bin.GCF 
[sudo] Mot de passe de jeedomÂ :Â 
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
17:11:48:745 using firmware file: deCONZ_RaspBeeII_0x266e0700.bin.GCF 
17:11:48:764 ls dev: /dev/ttyACM0 (0x0658/0x0200) sn: 
17:11:48:764 ls dev: /dev/ttyACM1 (0x1CF1/0x0030) sn: DE2256325
17:11:48:764 pin serialno: DE2256325
17:11:48:765 search FTDI device: no.1
Reboot device /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2256325-if00 (ConBee II)
17:11:48:773 query bootloader v1 ID after 5 ms
17:11:49:273 close serial after 505
17:11:50:296 query bootloader v3 ID after 1528 ms
17:11:50:296 TX c081027dffc0
17:11:50:797 close serial after 2029
17:11:50:818 query deCONZ firmware version
17:11:50:820 SLIP RX frame length: 9
deCONZ firmware version 26580700
17:11:50:820 send watchdog reset 2 seconds
17:11:50:820 TX c00b02000c0005002602000000baffc0
17:11:50:822 set watchdog ttl status: 0x00
17:11:50:841 wait reboot: 2100 ms
17:11:55:250 query bootloader v1 ID after 2308 ms
17:11:55:251 close serial after 2308
17:11:57:211 query bootloader v3 ID after 4269 ms
17:11:57:211 TX c081027dffc0
17:11:57:711 close serial after 4769
17:11:58:724 query bootloader v3 ID after 5781 ms
17:11:58:724 TX c081027dffc0
17:11:59:224 close serial after 6282
17:12:00:233 query bootloader v3 ID after 7291 ms
17:12:00:233 TX c081027dffc0
17:12:00:734 close serial after 7791
17:12:01:129 query bootloader v3 ID after 8187 ms
17:12:01:129 TX c081027dffc0
17:12:01:129 close serial after 8187
17:12:04:870 query bootloader v3 ID after 11928 ms
17:12:04:870 TX c081027dffc0
17:12:05:371 close serial after 12429
17:12:06:382 query bootloader v3 ID after 13440 ms
17:12:06:382 TX c081027dffc0
17:12:06:883 close serial after 13940
17:12:07:892 query bootloader v3 ID after 14950 ms
17:12:07:893 TX c081027dffc0
17:12:08:393 close serial after 15451
failed reset 19628
17:12:08:396 retry, elapsed 19 seconds
17:12:08:501 parse commands: /usr/bin/GCFFlasher_internal.bin -d /dev/ttyACM1 -t 60 -x 3 -f deCONZ_RaspBeeII_0x266e0700.bin.GCF

17:12:08:501 using firmware file: deCONZ_RaspBeeII_0x266e0700.bin.GCF 
17:12:08:520 ls dev: /dev/ttyACM0 (0x0658/0x0200) sn: 
17:12:08:521 ls dev: /dev/ttyACM1 (0x1CF1/0x0030) sn: DE2256325
17:12:08:521 search FTDI device: no.1
Reboot device /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2256325-if00 (ConBee II)
17:12:08:530 query bootloader v1 ID after 5 ms
17:12:09:031 close serial after 505
17:12:10:040 query bootloader v3 ID after 1514 ms
17:12:10:040 TX c081027dffc0
17:12:10:541 close serial after 2015
17:12:10:549 query deCONZ firmware version
17:12:12:053 SLIP RX frame length: 9
deCONZ firmware version 26580700
17:12:12:053 send watchdog reset 2 seconds
17:12:12:053 TX c00b03000c0005002602000000b9ffc0
17:12:12:055 set watchdog ttl status: 0x00
17:12:12:058 wait reboot: 2100 ms
17:12:22:432 query bootloader v3 ID after 8273 ms
17:12:22:432 TX c081027dffc0
17:12:22:933 close serial after 8774
17:12:23:943 query bootloader v3 ID after 9784 ms
17:12:23:943 TX c081027dffc0
17:12:24:443 close serial after 10284
17:12:25:452 query bootloader v3 ID after 11293 ms
17:12:25:452 TX c081027dffc0
17:12:25:953 close serial after 11794
17:12:26:962 query bootloader v3 ID after 12803 ms
17:12:26:962 TX c081027dffc0
17:12:27:462 close serial after 13303
17:12:28:471 query bootloader v3 ID after 14312 ms
17:12:28:471 TX c081027dffc0
17:12:28:972 close serial after 14813
17:12:29:982 query bootloader v3 ID after 15823 ms
17:12:29:982 TX c081027dffc0
17:12:30:483 close serial after 16324
failed reset 21959
17:12:30:485 retry, elapsed 41 seconds
17:12:30:590 parse commands: /usr/bin/GCFFlasher_internal.bin -d /dev/ttyACM1 -t 60 -x 3 -f deCONZ_RaspBeeII_0x266e0700.bin.GCF

17:12:30:590 using firmware file: deCONZ_RaspBeeII_0x266e0700.bin.GCF 
17:12:30:609 ls dev: /dev/ttyACM0 (0x0658/0x0200) sn: 
17:12:30:609 ls dev: /dev/ttyACM1 (0x1CF1/0x0030) sn: DE2256325
17:12:30:609 search FTDI device: no.1
Reboot device /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2256325-if00 (ConBee II)
17:12:30:620 query bootloader v1 ID after 5 ms
17:12:31:120 close serial after 505
17:12:32:130 query bootloader v3 ID after 1515 ms
17:12:32:130 TX c081027dffc0
17:12:32:631 close serial after 2016
17:12:32:638 query deCONZ firmware version
17:12:34:643 retry, elapsed 45 seconds
17:12:34:738 parse commands: /usr/bin/GCFFlasher_internal.bin -d /dev/ttyACM1 -t 60 -x 3 -f deCONZ_RaspBeeII_0x266e0700.bin.GCF

17:12:34:738 using firmware file: deCONZ_RaspBeeII_0x266e0700.bin.GCF 
17:12:34:753 ls dev: /dev/ttyACM0 (0x0658/0x0200) sn: 
17:12:34:753 ls dev: /dev/ttyACM1 (0x1CF1/0x0030) sn: DE2256325
17:12:34:753 search FTDI device: no.1
Reboot device /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2256325-if00 (ConBee II)
17:12:34:763 query bootloader v1 ID after 5 ms
17:12:35:263 close serial after 505
17:12:36:273 query bootloader v3 ID after 1514 ms
17:12:36:273 TX c081027dffc0
17:12:36:773 close serial after 2015
17:12:36:781 query deCONZ firmware version
17:12:38:786 retry, elapsed 50 seconds
17:12:38:892 parse commands: /usr/bin/GCFFlasher_internal.bin -d /dev/ttyACM1 -t 60 -x 3 -f deCONZ_RaspBeeII_0x266e0700.bin.GCF

17:12:38:892 using firmware file: deCONZ_RaspBeeII_0x266e0700.bin.GCF 
17:12:38:911 ls dev: /dev/ttyACM0 (0x0658/0x0200) sn: 
17:12:38:911 ls dev: /dev/ttyACM1 (0x1CF1/0x0030) sn: DE2256325
17:12:38:911 search FTDI device: no.1
Reboot device /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2256325-if00 (ConBee II)
17:12:38:921 query bootloader v1 ID after 5 ms
17:12:39:422 close serial after 505
17:12:40:450 query bootloader v3 ID after 1534 ms
17:12:40:450 TX c081027dffc0
17:12:40:951 close serial after 2034
17:12:40:978 query deCONZ firmware version
17:12:40:980 SLIP RX frame length: 9
deCONZ firmware version 26580700
17:12:40:980 send watchdog reset 2 seconds
17:12:40:980 TX c00b04000c0005002602000000b8ffc0
17:12:40:983 set watchdog ttl status: 0x00
17:12:41:005 wait reboot: 2100 ms
17:12:45:413 query bootloader v1 ID after 2307 ms
17:12:45:413 close serial after 2308
17:12:47:365 query bootloader v3 ID after 4259 ms
17:12:47:365 TX c081027dffc0
17:12:47:865 close serial after 4760
17:12:48:876 query bootloader v3 ID after 5771 ms
17:12:48:876 TX c081027dffc0
17:12:49:377 close serial after 6271
17:12:50:386 query bootloader v3 ID after 7280 ms
17:12:50:386 TX c081027dffc0
17:12:50:887 close serial after 7781
17:12:51:896 query bootloader v3 ID after 8790 ms
17:12:51:896 TX c081027dffc0
17:12:52:217 close serial after 9111
17:12:56:069 query bootloader v3 ID after 12963 ms
17:12:56:069 TX c081027dffc0
17:12:56:569 close serial after 13464
17:12:57:580 query bootloader v3 ID after 14474 ms
17:12:57:580 TX c081027dffc0
17:12:58:081 close serial after 14975
17:12:59:090 query bootloader v3 ID after 15984 ms
17:12:59:090 TX c081027dffc0
17:12:59:591 close serial after 16485
failed reset 20677
retry, failed

2408: Error: uart reset failed, check retry

XabiX · Juillet 2, 2021, 5:52

Je confirme que j ai lu les docs sur les potentiels pbs de Message failed to sent, autour du maillage et interférences wifi etc…

J ai déplacé mon wifi sur le canal 11 et mon zigbee sur le 15. Avant cela marché et j ai aussi essayé avec des lampes a 1m. Donc j ai des doutes que cela vienne du signal.

Merci

Yves19 · Juillet 2, 2021, 6:24

Au vu de tes logs le flashage du firmware a échoué car la clef Conbee2 n’est pas visible depuis ta box.

As tu essayé de passer ta ConBee2 sur un PC win10 et d’y lancer deCONZ ?

XabiX · Juillet 5, 2021, 12:14

Bonjour,

Je suis passé par Windows et le flash 266e0700 a marché mais cela ne change rien au pb initial. J’appuie 10s sur la télécommande pour reset la lampe, je l’eteins, je lance l’inclusion, je rallume la lampe et rien ne se passe.

Que puis je faire? reset de la clé? changer de clé? acheter un pont?

Merci
XabiX

XabiX · Juillet 5, 2021, 12:22

Est ce qu’il peut y avoir un pb de données de la base Zigbee dans le plugin?

[2021-07-05 14:11:48][WARNING] : [00:15:8d:00:06:3d:cb:5a][map.scan] neighbour 00:15:8d:00:06:3d:cb:5a is not in 'zigbee.db'
[2021-07-05 14:11:48][WARNING] : [00:15:8d:00:06:36:d6:05][map.scan] neighbour 00:15:8d:00:06:36:d6:05 is not in 'zigbee.db'
[2021-07-05 14:11:48][WARNING] : [00:15:8d:00:02:5e:d9:21][map.scan] neighbour 00:15:8d:00:02:5e:d9:21 is not in 'zigbee.db'
[2021-07-05 14:11:48][WARNING] : [00:15:8d:00:03:c7:74:c0][map.scan] neighbour 00:15:8d:00:03:c7:74:c0 is not in 'zigbee.db'
[2021-07-05 14:11:48][WARNING] : [00:15:8d:00:02:5c:95:b6][map.scan] neighbour 00:15:8d:00:02:5c:95:b6 is not in 'zigbee.db'
[2021-07-05 14:11:48][WARNING] : [00:15:8d:00:02:e3:32:f5][map.scan] neighbour 00:15:8d:00:02:e3:32:f5 is not in 'zigbee.db'
[2021-07-05 14:11:48][WARNING] : [00:15:8d:00:02:5c:95:b6][map.scan] neighbour 00:15:8d:00:02:5c:95:b6 is not in 'zigbee.db'
[2021-07-05 14:11:48][WARNING] : [00:15:8d:00:06:39:2d:a4][map.scan] neighbour 00:15:8d:00:06:39:2d:a4 is not in 'zigbee.db'
[2021-07-05 14:11:48][WARNING] : [00:15:8d:00:02:e3:33:35][map.scan] neighbour 00:15:8d:00:02:e3:33:35 is not in 'zigbee.db'
[2021-07-05 14:11:48][WARNING] : [00:15:8d:00:02:5c:96:3a][map.scan] neighbour 00:15:8d:00:02:5c:96:3a is not in 'zigbee.db'
[2021-07-05 14:11:48][WARNING] : [00:15:8d:00:02:e3:32:f5][map.scan] neighbour 00:15:8d:00:02:e3:32:f5 is not in 'zigbee.db'

[2021-07-05 15:08:24][DEBUG] : Frame received: 0x17140021001a002201fcff010200000000003600030001b40000afdd5e742c001e
[2021-07-05 15:08:24][DEBUG] : APS data indication response: [26, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.GROUP address=0xfffc>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 0, 0, 54, b'\x01\xb4\x00', 0, 175, 221, 94, 116, 44, 0, 30]
[2021-07-05 15:08:24][DEBUG] : [0x0000:zdo] ZDO request ZDOCmd.Mgmt_Permit_Joining_req: [180, <Bool.false: 0>]
[2021-07-05 15:08:24][DEBUG] : 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, ep: 0, profile: 0x0000, cluster_id: 0x0036, data: b'01b400'
[2021-07-05 15:08:25][DEBUG] : Frame received: 0x0e15000700a600
[2021-07-05 15:08:25][DEBUG] : Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_CONFIRM|2: 166>, 0]
[2021-07-05 15:08:25][DEBUG] : Command Command.aps_data_confirm (0,)
[2021-07-05 15:08:25][DEBUG] : Send: 0x04150007000000
[2021-07-05 15:08:25][DEBUG] : Frame received: 0x04150012000b00220201fcff00e100000000
[2021-07-05 15:08:25][DEBUG] : APS data confirm response for request with id 2: e1
[2021-07-05 15:08:25][DEBUG] : Request id: 0x02 'aps_data_confirm' for <DeconzAddressEndpoint address_mode=ADDRESS_MODE.GROUP address=0xfffc endpoint=None>, status: 0xe1
[2021-07-05 15:08:25][DEBUG] : Error while sending 2 req id broadcast: TXStatus.MAC_CHANNEL_ACCESS_FAILURE
[2021-07-05 15:08:25][DEBUG] : Command Command.write_parameter (2, <NetworkParameter.permit_join: 33>, b'\xb4')
[2021-07-05 15:08:25][DEBUG] : Send: 0x0b16000900020021b4
[2021-07-05 15:08:25][DEBUG] : Frame received: 0x0b16000800010021
[2021-07-05 15:08:25][DEBUG] : Write parameter permit_join: SUCCESS
[2021-07-05 15:08:25][DEBUG] : [zgp.permit] Permit green power pairing for 180 s
[2021-07-05 15:08:25][INFO] : 200 PUT /application/include (127.0.0.1) 145.28ms

Yves19 · Juillet 5, 2021, 12:25

Si la Conbee2 fonctionnait avec le plug in Deconz alors elle n’est pas à mettre en cause (tu peux aussi le vérifier en l’utilisant sur un PC et en essayant les appairages/actions avec l’application deCONZ.exe)

XabiX · Juillet 5, 2021, 1:10

Mercy Yves19! Meme si je ne comprends pas pourquoi je ne peux plus communiquer avec les appareils déjà inclus.

En mode debug, qd je lance l’inclusion pour un nouvel appareil je ne vois rien…

[2021-07-05 15:08:24][DEBUG] : Frame received: 0x17140021001a002201fcff010200000000003600030001b40000afdd5e742c001e
[2021-07-05 15:08:24][DEBUG] : APS data indication response: [26, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.GROUP address=0xfffc>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 0, 0, 54, b'\x01\xb4\x00', 0, 175, 221, 94, 116, 44, 0, 30]
[2021-07-05 15:08:24][DEBUG] : [0x0000:zdo] ZDO request ZDOCmd.Mgmt_Permit_Joining_req: [180, <Bool.false: 0>]
[2021-07-05 15:08:24][DEBUG] : 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, ep: 0, profile: 0x0000, cluster_id: 0x0036, data: b'01b400'
[2021-07-05 15:08:25][DEBUG] : Frame received: 0x0e15000700a600
[2021-07-05 15:08:25][DEBUG] : Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_CONFIRM|2: 166>, 0]
[2021-07-05 15:08:25][DEBUG] : Command Command.aps_data_confirm (0,)
[2021-07-05 15:08:25][DEBUG] : Send: 0x04150007000000
[2021-07-05 15:08:25][DEBUG] : Frame received: 0x04150012000b00220201fcff00e100000000
[2021-07-05 15:08:25][DEBUG] : APS data confirm response for request with id 2: e1
[2021-07-05 15:08:25][DEBUG] : Request id: 0x02 'aps_data_confirm' for <DeconzAddressEndpoint address_mode=ADDRESS_MODE.GROUP address=0xfffc endpoint=None>, status: 0xe1

[2021-07-05 15:08:25][DEBUG] : Error while sending 2 req id broadcast: TXStatus.MAC_CHANNEL_ACCESS_FAILURE

[2021-07-05 15:08:25][DEBUG] : Command Command.write_parameter (2, <NetworkParameter.permit_join: 33>, b'\xb4')
[2021-07-05 15:08:25][DEBUG] : Send: 0x0b16000900020021b4
[2021-07-05 15:08:25][DEBUG] : Frame received: 0x0b16000800010021
[2021-07-05 15:08:25][DEBUG] : Write parameter permit_join: SUCCESS
[2021-07-05 15:08:25][DEBUG] : [zgp.permit] Permit green power pairing for 180 s
[2021-07-05 15:08:25][INFO] : 200 PUT /application/include (127.0.0.1) 145.28ms

L’inclusion marche en bluetooh ou avec la telecommande 5s sur le bouton ON mais pas avec la clé

J’ai testé sous DeConz par la partie Web et cela a marché, ma lampe est directement reconnue. Par contre quand je remets la clé dans Jeedom, relance & sync rien n’apparait. Du coup, dois je remettre la clé sous DeConz et la supprimer pour ressayer?

A mon avis il faudrait déjà comprendre pq je ne peux piloter les lampes déjà ajoutées par le passé avant d’en ajouter des nouvelles

[2021-07-05 15:21:56][DEBUG] : {"ieee":"00:17:88:01:06:1c:ed:91","cmd":[{"endpoint":11,"cluster":"on_off","command":"off","await":1}],"allowQueue":false}
[2021-07-05 15:21:59][ERROR] : Erreur exécution de la commande [Cuisine][Table][Off] : Erreur lors de la requete : http://127.0.0.1:8089/device/command(PUT), data : {"ieee":"00:17:88:01:06:1c:ed:91","cmd":[{"endpoint":11,"cluster":"on_off","command":"off","await":1}],"allowQueue":false} erreur : {"state":"error","result":"[0x1882:11:0x0006]: Message send failure","code":0}

zigpy.exceptions.DeliveryError: [0x1882:11:0x0006]: Message send failure
[2021-07-05 15:21:59][INFO] : 200 PUT /device/command (127.0.0.1) 3114.04ms
[2021-07-05 15:22:03][DEBUG] : Frame received: 0x0e22000700aa00
[2021-07-05 15:22:03][DEBUG] : Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0]
[2021-07-05 15:22:03][DEBUG] : Command Command.aps_data_indication (1, 1)
[2021-07-05 15:22:03][DEBUG] : Send: 0x1722000800010001
[2021-07-05 15:22:03][DEBUG] : Frame received: 0x1722002a00230022020000010283990b040119000c00010901000b1014010814000100afff797b2c00e1
[2021-07-05 15:22:03][DEBUG] : APS data indication response: [35, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x9983>, 11, 260, 25, b'\x01	\x01\x00\x0b\x10\x14\x01\x08\x14\x00\x01', 0, 175, 255, 121, 123, 44, 0, -31]
[2021-07-05 15:22:03][DEBUG] : Received frame from unknown device: 0x9983
[2021-07-05 15:22:03][DEBUG] : 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x9983>, ep: 11, profile: 0x0104, cluster_id: 0x0019, data: b'010901000b10140108140001'
[2021-07-05 15:22:13][DEBUG] : Frame received: 0x0e23000700aa00
[2021-07-05 15:22:13][DEBUG] : Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0]
[2021-07-05 15:22:13][DEBUG] : Command Command.aps_data_indication (1, 1)
[2021-07-05 15:22:13][DEBUG] : Send: 0x1723000800010001
[2021-07-05 15:22:13][DEBUG] : Frame received: 0x1723002a00230022020000010283990b040119000c00010a01000b1014010814000100afff7a7b2c00e1
[2021-07-05 15:22:13][DEBUG] : APS data indication response: [35, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x9983>, 11, 260, 25, b'\x01
\x01\x00\x0b\x10\x14\x01\x08\x14\x00\x01', 0, 175, 255, 122, 123, 44, 0, -31]
[2021-07-05 15:22:13][DEBUG] : Received frame from unknown device: 0x9983
[2021-07-05 15:22:13][DEBUG] : 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x9983>, ep: 11, profile: 0x0104, cluster_id: 0x0019, data: b'010a01000b10140108140001'
[2021-07-05 15:22:23][DEBUG] : Frame received: 0x0e24000700aa00
[2021-07-05 15:22:23][DEBUG] : Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0]
[2021-07-05 15:22:23][DEBUG] : Command Command.aps_data_indication (1, 1)
[2021-07-05 15:22:23][DEBUG] : Send: 0x1724000800010001
[2021-07-05 15:22:23][DEBUG] : Frame received: 0x1724002a00230022020000010283990b040119000c00010b01000b1014010814000100afff7b7b2c00e1
[2021-07-05 15:22:23][DEBUG] : APS data indication response: [35, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x9983>, 11, 260, 25, b'\x01\x0b\x01\x00\x0b\x10\x14\x01\x08\x14\x00\x01', 0, 175, 255, 123, 123, 44, 0, -31]
[2021-07-05 15:22:23][DEBUG] : Received frame from unknown device: 0x9983
[2021-07-05 15:22:23][DEBUG] : 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x9983>, ep: 11, profile: 0x0104, cluster_id: 0x0019, data: b'010b01000b10140108140001'
[2021-07-05 15:22:33][DEBUG] : Frame received: 0x0e25000700aa00
[2021-07-05 15:22:33][DEBUG] : Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0]
[2021-07-05 15:22:33][DEBUG] : Command Command.aps_data_indication (1, 1)
[2021-07-05 15:22:33][DEBUG] : Send: 0x1725000800010001
[2021-07-05 15:22:33][DEBUG] : Frame received: 0x1725002a00230022020000010283990b040119000c00010c01000b1014010814000100afff7b7b2c00e1
[2021-07-05 15:22:33][DEBUG] : APS data indication response: [35, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x9983>, 11, 260, 25, b'\x01\x0c\x01\x00\x0b\x10\x14\x01\x08\x14\x00\x01', 0, 175, 255, 123, 123, 44, 0, -31]
[2021-07-05 15:22:33][DEBUG] : Received frame from unknown device: 0x9983
[2021-07-05 15:22:33][DEBUG] : 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x9983>, ep: 11, profile: 0x0104, cluster_id: 0x0019, data: b'010c01000b10140108140001'

Yves19 · Juillet 5, 2021, 2:26

Pour rappel au cas où : pour un coupleur (coordinateur) donné il ne peut y avoir qu’un seul plug in actif à la fois. Donc si tu utilises zigbee avec la ConBe2 il faut arrêter le plug ind Deconz (démon) et ré appairer l’ensemble des équipements avec zigbee puis transférer leurs configurations vers zigbee.
Le ré-appairage des équipements peut nécessiter un reset de ces derniers au préalable, C’est au cas par cas.

XabiX · Juillet 5, 2021, 3:34

En faisaint un reset de la passerelle (aka la clé), l’inclusion a fonctionné dans Jeedom.

Par contre, je n’arrive tjs pas piloter les équipements existants. Je pense que je vais devoir tout recréer

Cela fait longtemps que j’ai supprimé le plugin deconz et que je suis uniquement en zigbee. J esperai qu’il n’y ait plus de démon deconz qui tourne. D’ailleurs tous mes équipements sont configurés dans le plugin zigbee, et qd je plug la clé dans Deconz sur Windows je ne vois aucun équipement dessus.

Qd j’avais migré de deconz a zigbee j’avais refait les inclusions et depuis deconz n’est plus censé etre installé et présent dans mon image Jeedom…

Yves19 · Juillet 5, 2021, 5:32

Attention un reset de la clef sans en restaurer la configuration par la suite… change le réseau Zigbee. Donc il faut effectivement ensuite tout ré appairer puisque le set-up réseau a été modifié.

system · Juillet 7, 2021, 7:11

Ce sujet a été automatiquement fermé après 24 heures suivant le dernier commentaire. Aucune réponse n’est permise dorénavant.