bonjour @Loic
juste une petite demande de confirmation
avec ma clef CC2531 en configue ZNP dans le plugin, j’avais mon boitier blitzwolf BW-SS7 de reconnu en routeur et plusieurs capteur s’accrochaient dessus
par contre avec la clef combe2 le meme produit est reconnu en inconnu, est ce normal pour toi ?
merci
Ca peut etre du au firmware de la clef qui a des soucis de demande d’identifiant du materiel. Malheureusement ca ya rien a y faire c’est un peu le soucis du zigbee qui depend a plus de 50% du firmware de la clef
ok merci.
si je regarde et fait la mise a jour si il y a une, je vais tout perdre les capteurs qui sont en synchro avec celle ci ou pas
Bonjour
je ne sais pas si quelqu’un a déjà posté pour ce détecteur de mouvement, je n’ai pas trouvé
{
"ieee": "5c:02:72:ff:fe:ca:b8:1b",
"nwk": 41991,
"status": 2,
"lqi": "191",
"rssi": "-70",
"last_seen": "1613146644.2673297",
"node_descriptor": "02:40:80:02:10:52:52:00:00:2c:52:00:00",
"endpoints": [
{
"id": 1,
"status": 1,
"device_type": 1026,
"profile_id": 260,
"manufacturer": "TUYATEC-zn9wyqtr",
"model": "RH3040",
"output_clusters": [
{
"id": 25,
"name": "Ota",
"attributes": []
},
{
"id": 10,
"name": "Time",
"attributes": []
}
],
"input_clusters": [
{
"id": 0,
"name": "Basic",
"attributes": [
{
"id": 0,
"name": "zcl_version",
"value": 3
},
{
"id": 1,
"name": "app_version",
"value": 69
},
{
"id": 2,
"name": "stack_version",
"value": 0
},
{
"id": 3,
"name": "hw_version",
"value": 1
},
{
"id": 4,
"name": "manufacturer",
"value": "TUYATEC-zn9wyqtr"
},
{
"id": 5,
"name": "model",
"value": "RH3040"
},
{
"id": 6,
"name": "date_code",
"value": ""
},
{
"id": 7,
"name": "power_source",
"value": 3
}
]
},
{
"id": 1,
"name": "Power Configuration",
"attributes": []
},
{
"id": 1280,
"name": "IAS Zone",
"attributes": [
{
"id": 16,
"name": "cie_addr",
"value": [
119,
132,
4,
255,
255,
46,
33,
0
]
}
]
}
]
}
],
"signature": {
"manufacturer_name": "TUYATEC-zn9wyqtr",
"model": "RH3040",
"node_descriptor": {
"byte1": 2,
"byte2": 64,
"mac_capability_flags": 128,
"manufacturer_code": 4098,
"maximum_buffer_size": 82,
"maximum_incoming_transfer_size": 82,
"server_mask": 11264,
"maximum_outgoing_transfer_size": 82,
"descriptor_capability_field": 0
},
"1": {
"profileid": 260,
"deviceid": 1026,
"in_clusters": [
0,
1,
1280
],
"out_clusters": [
25,
10
]
}
},
"class": "zigpy.device"
}
finalement après avoir refait l’association c’est good
LUMI.lumi.sens V1
pile bouton CR2032
{
"ieee": "00:15:8d:00:01:56:a8:a9",
"nwk": 498,
"status": 2,
"lqi": "255",
"rssi": "-28",
"last_seen": "1613159880.6061218",
"node_descriptor": "02:40:80:37:10:7f:64:00:00:00:64:00:00",
"endpoints": [
{
"id": 1,
"status": 1,
"device_type": 24322,
"profile_id": 260,
"manufacturer": "LUMI",
"model": "lumi.sens",
"output_clusters": [
{
"id": 0,
"name": "Basic",
"attributes": []
},
{
"id": 4,
"name": "Groups",
"attributes": []
},
{
"id": 3,
"name": "Identify",
"attributes": []
},
{
"id": 5,
"name": "Scenes",
"attributes": []
},
{
"id": 25,
"name": "Ota",
"attributes": []
},
{
"id": 65535,
"name": "Manufacturer Specific",
"attributes": []
},
{
"id": 18,
"name": "MultistateInput",
"attributes": []
}
],
"input_clusters": [
{
"id": 0,
"name": "BasicCluster",
"attributes": [
{
"id": 0,
"name": "zcl_version",
"value": 1
},
{
"id": 1,
"name": "app_version",
"value": 2
},
{
"id": 2,
"name": "stack_version",
"value": 2
},
{
"id": 3,
"name": "hw_version",
"value": 30
},
{
"id": 4,
"name": "manufacturer",
"value": "LUMI"
},
{
"id": 5,
"name": "model",
"value": "lumi.sens"
},
{
"id": 6,
"name": "date_code",
"value": "20160516"
},
{
"id": 7,
"name": "power_source",
"value": 3
},
{
"id": 16384,
"name": "sw_build_id",
"value": "3000-0001"
}
]
},
{
"id": 1,
"name": "Power Configuration",
"attributes": []
},
{
"id": 3,
"name": "Identify",
"attributes": []
},
{
"id": 1026,
"name": "Temperature Measurement",
"attributes": [
{
"id": 0,
"name": "measured_value",
"value": 2274
}
]
},
{
"id": 1029,
"name": "Relative Humidity Measurement",
"attributes": [
{
"id": 0,
"name": "measured_value",
"value": 4061
}
]
},
{
"id": 65535,
"name": "Manufacturer Specific",
"attributes": []
},
{
"id": 25,
"name": "Ota",
"attributes": []
}
]
},
{
"id": 2,
"status": 1,
"device_type": 24322,
"profile_id": 260,
"manufacturer": null,
"model": null,
"output_clusters": [
{
"id": 4,
"name": "Groups",
"attributes": []
},
{
"id": 3,
"name": "Identify",
"attributes": []
},
{
"id": 5,
"name": "Scenes",
"attributes": []
},
{
"id": 18,
"name": "MultistateInput",
"attributes": []
}
],
"input_clusters": [
{
"id": 3,
"name": "Identify",
"attributes": []
}
]
},
{
"id": 3,
"status": 1,
"device_type": 24323,
"profile_id": 260,
"manufacturer": null,
"model": null,
"output_clusters": [
{
"id": 4,
"name": "Groups",
"attributes": []
},
{
"id": 3,
"name": "Identify",
"attributes": []
},
{
"id": 5,
"name": "Scenes",
"attributes": []
},
{
"id": 12,
"name": "AnalogInput",
"attributes": []
}
],
"input_clusters": [
{
"id": 3,
"name": "Identify",
"attributes": []
}
]
}
],
"signature": {
"manufacturer": "LUMI",
"model": "lumi.sens",
"node_desc": {
"byte1": 2,
"byte2": 64,
"mac_capability_flags": 128,
"manufacturer_code": 4151,
"maximum_buffer_size": 127,
"maximum_incoming_transfer_size": 100,
"server_mask": 0,
"maximum_outgoing_transfer_size": 100,
"descriptor_capability_field": 0
},
"endpoints": {
"1": {
"profile_id": 260,
"device_type": 24322,
"input_clusters": [
0,
1,
3,
1026,
1029,
65535,
25
],
"output_clusters": [
0,
4,
3,
5,
25,
65535,
18
]
},
"2": {
"profile_id": 260,
"device_type": 24322,
"input_clusters": [
3
],
"output_clusters": [
4,
3,
5,
18
]
},
"3": {
"profile_id": 260,
"device_type": 24323,
"input_clusters": [
3
],
"output_clusters": [
4,
3,
5,
12
]
}
}
},
"class": "zhaquirks.xiaomi.mija.sensor_ht"
}
Bonjour Loic,
Merci pour l’intégration. Il me semble cependant qu’il manque une paire de commandes : en effet, les ports USB peuvent être commandés indépendamment de la prise elle-même (c’est le cas en commande manuelle via le bouton de la prise, mais aussi sur le modèle que j’ai sur mon autre instance Jeedom via Deconz).
Est-il possible de rajouter ces commandes ?
Merci d’avance.
Bonjour @Loic
J’ai bien reçu l’update avec l’ajout de la siréne dans la marque Tuya mais les commandes sont toujours les meme que les siniphy meme le nom de la sirene de la sirene est pas bon ( TS0601 )
Je sais pas si c’est normal
Merci
Salutations,
Bonjour @Loic,
C’est ma première demande, j’espère avoir bien compris ce qui est attendu 
Dénomination: Aqara Wall Switch D1 (with Neutral, double Rocker)
Référence: QBKG12LM
Il s’agit du double bouton « filaire » en version avec neutre
Image:
Ci-joint le contenu de l’onglet [Informations brutes] dans Configuration
{
"ieee": "00:15:8d:00:04:90:a1:ea",
"nwk": 35902,
"status": 2,
"lqi": "255",
"rssi": "-40",
"last_seen": "1613214144.9567916",
"node_descriptor": "01:40:8e:5f:11:7f:64:00:00:00:64:00:00",
"endpoints": [
{
"id": 1,
"status": 1,
"device_type": 81,
"profile_id": 260,
"manufacturer": "LUMI",
"model": "lumi.ctrl_ln2.aq1",
"output_clusters": [
{
"id": 10,
"name": "Time",
"attributes": []
},
{
"id": 25,
"name": "Ota",
"attributes": []
}
],
"input_clusters": [
{
"id": 0,
"name": "BasicCluster",
"attributes": [
{
"id": 0,
"name": "zcl_version",
"value": 1
},
{
"id": 1,
"name": "app_version",
"value": 92
},
{
"id": 2,
"name": "stack_version",
"value": 2
},
{
"id": 3,
"name": "hw_version",
"value": 18
},
{
"id": 4,
"name": "manufacturer",
"value": "LUMI"
},
{
"id": 5,
"name": "model",
"value": "lumi.ctrl_ln2.aq1"
},
{
"id": 6,
"name": "date_code",
"value": "06-11-2020"
},
{
"id": 7,
"name": "power_source",
"value": 1
}
]
},
{
"id": 1,
"name": "Power Configuration",
"attributes": []
},
{
"id": 2,
"name": "Device Temperature",
"attributes": []
},
{
"id": 3,
"name": "Identify",
"attributes": []
},
{
"id": 4,
"name": "Groups",
"attributes": []
},
{
"id": 5,
"name": "Scenes",
"attributes": []
},
{
"id": 6,
"name": "On\/Off",
"attributes": [
{
"id": 0,
"name": "on_off",
"value": 0
}
]
},
{
"id": 10,
"name": "Time",
"attributes": []
},
{
"id": 16,
"name": "BinaryOutput",
"attributes": []
}
]
},
{
"id": 2,
"status": 1,
"device_type": 81,
"profile_id": 260,
"manufacturer": null,
"model": null,
"output_clusters": [],
"input_clusters": [
{
"id": 6,
"name": "On\/Off",
"attributes": [
{
"id": 0,
"name": "on_off",
"value": 0
}
]
},
{
"id": 16,
"name": "BinaryOutput",
"attributes": []
}
]
},
{
"id": 3,
"status": 1,
"device_type": 9,
"profile_id": 260,
"manufacturer": null,
"model": null,
"output_clusters": [
{
"id": 4,
"name": "Groups",
"attributes": []
},
{
"id": 12,
"name": "AnalogInput",
"attributes": []
}
],
"input_clusters": [
{
"id": 12,
"name": "AnalogInputCluster",
"attributes": [
{
"id": 85,
"name": "present_value",
"value": 0
}
]
}
]
}
],
"signature": {
"manufacturer": "LUMI",
"model": "lumi.ctrl_ln2.aq1",
"node_desc": {
"byte1": 1,
"byte2": 64,
"mac_capability_flags": 142,
"manufacturer_code": 4447,
"maximum_buffer_size": 127,
"maximum_incoming_transfer_size": 100,
"server_mask": 0,
"maximum_outgoing_transfer_size": 100,
"descriptor_capability_field": 0
},
"endpoints": {
"1": {
"profile_id": 260,
"device_type": 81,
"input_clusters": [
0,
1,
2,
3,
4,
5,
6,
10,
16
],
"output_clusters": [
10,
25
]
},
"2": {
"profile_id": 260,
"device_type": 81,
"input_clusters": [
6,
16
],
"output_clusters": []
},
"3": {
"profile_id": 260,
"device_type": 9,
"input_clusters": [
12
],
"output_clusters": [
4,
12
]
}
}
},
"class": "zhaquirks.xiaomi.aqara.ctrl_ln"
}
Par avance merci
Gilles
Bonjour, Loïc
Je reviens sur le sujet de l’équipement TZ3000_40zcsvfv.TS0502A.
Le mien gère un spot « Swing » de marque ASLED.
Quand je fait l’intégration de ce module, il apparaît avec le logo ZigBee vert standard, bref, il n’est pas reconnu.
Pourtant, il existe dans le répertoire /var/www/html/plugins/zigbee/core/config/devices/tuya un fichier nommé _TZ3000_40zcsvfv.TS0502A qui pourrait correspondre aux données brutes de mon appareil ci-dessous :
{
"ieee": "ec:1b:bd:ff:fe:8a:19:7d",
"nwk": 54633,
"status": 2,
"lqi": "195",
"rssi": "0",
"last_seen": "1613224377.2143657",
"node_descriptor": "01:40:8e:02:10:52:52:00:00:2c:52:00:00",
"endpoints": [
{
"id": 1,
"status": 1,
"device_type": 257,
"profile_id": 260,
"manufacturer": "_TZ3000_40zcsvfv",
"model": "TS0502A",
"output_clusters": [
{
"id": 25,
"name": "Ota",
"attributes": []
}
],
"input_clusters": [
{
"id": 0,
"name": "Basic",
"attributes": [
{
"id": 0,
"name": "zcl_version",
"value": 3
},
{
"id": 1,
"name": "app_version",
"value": 65
},
{
"id": 2,
"name": "stack_version",
"value": 0
},
{
"id": 3,
"name": "hw_version",
"value": 1
},
{
"id": 4,
"name": "manufacturer",
"value": "_TZ3000_40zcsvfv"
},
{
"id": 5,
"name": "model",
"value": "TS0502A"
},
{
"id": 6,
"name": "date_code",
"value": ""
},
{
"id": 7,
"name": "power_source",
"value": 1
}
]
},
{
"id": 10,
"name": "Time",
"attributes": []
},
{
"id": 4,
"name": "Groups",
"attributes": []
},
{
"id": 5,
"name": "Scenes",
"attributes": []
},
{
"id": 6,
"name": "On\/Off",
"attributes": [
{
"id": 0,
"name": "on_off",
"value": 1
},
{
"id": 16386,
"name": "off_wait_time",
"value": 0
}
]
},
{
"id": 8,
"name": "Level control",
"attributes": [
{
"id": 0,
"name": "current_level",
"value": 255
}
]
},
{
"id": 768,
"name": "Color Control",
"attributes": [
{
"id": 7,
"name": "color_temperature",
"value": 255
}
]
}
]
}
],
"signature": {
"manufacturer": "_TZ3000_40zcsvfv",
"model": "TS0502A",
"node_desc": {
"byte1": 1,
"byte2": 64,
"mac_capability_flags": 142,
"manufacturer_code": 4098,
"maximum_buffer_size": 82,
"maximum_incoming_transfer_size": 82,
"server_mask": 11264,
"maximum_outgoing_transfer_size": 82,
"descriptor_capability_field": 0
},
"endpoints": {
"1": {
"profile_id": 260,
"device_type": 257,
"input_clusters": [
0,
10,
4,
5,
6,
8,
768
],
"output_clusters": [
25
]
}
}
},
"class": "zigpy.device"
}
Malheureusement, d’une part, ce fichier json n’est pas reconnu et d’autre part, il est incomplet.
Il ne contient qu’une instruction ON/OFF, alors que cet équipement est supposé être contrôlable en plus, en intensité lumineuse et en température de blanc.
Peux-tu me dire s’il y a un souci particulier avec ce module pour intégrer les commandes ?
Sinon, pourrais-tu compléter sa définition en ajoutant les données et actions manquantes ?
Merci d’avance.
Pour compléter :
si j’applique manuellement le profils Tuya [_TZ3000_40zcsvfv…
J’obtiens une commande ON/OFF fonctionnelle.
Si j’applique les profils Lidl GU10 ou E14, j’obtiens la commande ON/OFF et la commande de luminosité fonctionnelle, mais la commande de la température du blanc ne fonctionne pas.
Re-bonjour, Loïc
Je viens de refaire quelques tests.
Finalement, mon module fonctionne correctement si on lui applique le profil Lidl GU10 LED LIVARNOLUX.
Le seul bémol qui m’a fait croire que l’action de mise à jour de la température de blanc ne fonctionnait pas vient de la valeur max de cette action.
Elle est de 500 et devrait être 254.
Bon week-end.
Bonjour @Loic
Est-il possible d’intégrer les lampes RGBW JunYu ?
{
"ieee": "00:12:4b:00:22:6d:4d:95",
"nwk": 26802,
"status": 2,
"lqi": "132",
"rssi": "-62",
"last_seen": "1613314740.741065",
"node_descriptor": "01:40:8e:00:00:50:a0:00:00:00:a0:00:00",
"endpoints": [
{
"id": 1,
"status": 1,
"device_type": 528,
"profile_id": 49246,
"manufacturer": "JunYu",
"model": "ZB-RGBCW",
"output_clusters": [],
"input_clusters": [
{
"id": 0,
"name": "Basic",
"attributes": [
{
"id": 0,
"name": "zcl_version",
"value": 1
},
{
"id": 1,
"name": "app_version",
"value": 13
},
{
"id": 2,
"name": "stack_version",
"value": 2
},
{
"id": 3,
"name": "hw_version",
"value": 1
},
{
"id": 4,
"name": "manufacturer",
"value": "JunYu"
},
{
"id": 5,
"name": "model",
"value": "ZB-RGBCW"
},
{
"id": 6,
"name": "date_code",
"value": "20201216"
},
{
"id": 7,
"name": "power_source",
"value": 1
},
{
"id": 16384,
"name": "sw_build_id",
"value": "2.0.1"
}
]
},
{
"id": 3,
"name": "Identify",
"attributes": []
},
{
"id": 4,
"name": "Groups",
"attributes": []
},
{
"id": 5,
"name": "Scenes",
"attributes": []
},
{
"id": 6,
"name": "On\/Off",
"attributes": [
{
"id": 0,
"name": "on_off",
"value": 1
}
]
},
{
"id": 8,
"name": "Level control",
"attributes": [
{
"id": 0,
"name": "current_level",
"value": 254
}
]
},
{
"id": 768,
"name": "Color Control",
"attributes": [
{
"id": 3,
"name": "current_x",
"value": 24939
},
{
"id": 4,
"name": "current_y",
"value": 24701
},
{
"id": 7,
"name": "color_temperature",
"value": 333
}
]
}
]
},
{
"id": 13,
"status": 1,
"device_type": 57694,
"profile_id": 49246,
"manufacturer": null,
"model": null,
"output_clusters": [
{
"id": 4096,
"name": "LightLink",
"attributes": []
}
],
"input_clusters": [
{
"id": 4096,
"name": "LightLink",
"attributes": []
}
]
}
],
"signature": {
"manufacturer": "JunYu",
"model": "ZB-RGBCW",
"node_desc": {
"byte1": 1,
"byte2": 64,
"mac_capability_flags": 142,
"manufacturer_code": 0,
"maximum_buffer_size": 80,
"maximum_incoming_transfer_size": 160,
"server_mask": 0,
"maximum_outgoing_transfer_size": 160,
"descriptor_capability_field": 0
},
"endpoints": {
"1": {
"profile_id": 49246,
"device_type": 528,
"input_clusters": [
0,
3,
4,
5,
6,
8,
768
],
"output_clusters": []
},
"13": {
"profile_id": 49246,
"device_type": 57694,
"input_clusters": [
4096
],
"output_clusters": [
4096
]
}
}
},
"class": "zigpy.device"
}
Merci
Bonjour,
Il faut me remettre la configuration alors trop de message pour que je la retrouve
Bonjour,
Merci de repréciser A CHAQUE FOIS le module dont vous parlez avec si possible la conf ou un lieu vers votre post précèdent je n’ai malheureusement pas le temps de rechercher a chaque fois
Bonjour,
J’ai traité toute les demandes d’ajout/correction de configuration. Ca sera tout dans la beta de demain
Bonjour,
Pour information dans la version de demain il y aura possibilité de faire un backup pour les type ezsp et znp. Pour l’instant je n’ai rien tester, Pour znp je ne pourrais pas testé. Pour ezsp je pourrais mais pas avant quelques semaine… Si des personnes pouvait tester juste la partie backup (ca risque de merdé vu que j’ai rien pu tester mais je pense d’ici la fin de la semaine ca pourrait etre ok).
Pour la partie restore c’est plus compliqué… Sur znp aucun soucis pour ceux qui ont une 2eme clef. Pour ezsp c’est du one shot : une fois un backup restoré sur une clef il est impossible d’en restorer un autre…
Autre nouveauté pour demain la prise en charge des mise à jour OTA des modules pour les fabricants jouant le jeux (ikea, ledavance officiellement et d’autre officieusement).
Idem la je peux pas tester j’ai aucun module ou le fabricant fournis la maj OTA.
Il me reste encore a prendre en charge les firmware fournis par dresden (je sais pas comment ils font pour les avoir d’ailleurs…)
Pas de soucis,
Il faut supprimer Tuya LCA 001 sirene, rien ne va .
Et créer :
manufacturer TZE200 ( Tuya )
Model : TS0601 sirene
{
"ieee": "5c:02:72:ff:fe:ce:a2:1f",
"nwk": 55671,
"status": 2,
"lqi": "255",
"rssi": "-57",
"last_seen": "1613393045.5880005",
"node_descriptor": "02:40:80:02:10:52:52:00:00:2c:52:00:00",
"endpoints": [
{
"id": 1,
"status": 1,
"device_type": 1027,
"profile_id": 260,
"manufacturer": "_TZE200_d0yu2xgi",
"model": "TS0601",
"output_clusters": [
{
"id": 3,
"name": "Identify",
"attributes": []
},
{
"id": 25,
"name": "Ota",
"attributes": []
}
],
"input_clusters": [
{
"id": 0,
"name": "Basic",
"attributes": [
{
"id": 0,
"name": "zcl_version",
"value": 3
},
{
"id": 1,
"name": "app_version",
"value": 83
},
{
"id": 2,
"name": "stack_version",
"value": 0
},
{
"id": 3,
"name": "hw_version",
"value": 1
},
{
"id": 4,
"name": "manufacturer",
"value": "_TZE200_d0yu2xgi"
},
{
"id": 5,
"name": "model",
"value": "TS0601"
},
{
"id": 6,
"name": "date_code",
"value": ""
},
{
"id": 7,
"name": "power_source",
"value": 3
}
]
},
{
"id": 3,
"name": "Identify",
"attributes": []
},
{
"id": 61184,
"name": "Tuya Manufacturer Specicific",
"attributes": [
{
"id": 617,
"name": "temperature",
"value": 277
},
{
"id": 618,
"name": "humidity",
"value": 21
}
]
},
{
"id": 1026,
"name": "Temperature Measurement",
"attributes": [
{
"id": 0,
"name": "measured_value",
"value": 2770
}
]
},
{
"id": 1029,
"name": "Relative Humidity Measurement",
"attributes": [
{
"id": 0,
"name": "measured_value",
"value": 2100
}
]
},
{
"id": 6,
"name": "On\/Off",
"attributes": []
}
]
}
],
"signature": {
"manufacturer": "_TZE200_d0yu2xgi",
"model": "TS0601",
"node_desc": {
"byte1": 2,
"byte2": 64,
"mac_capability_flags": 128,
"manufacturer_code": 4098,
"maximum_buffer_size": 82,
"maximum_incoming_transfer_size": 82,
"server_mask": 11264,
"maximum_outgoing_transfer_size": 82,
"descriptor_capability_field": 0
},
"endpoints": {
"1": {
"profile_id": 260,
"device_type": 1027,
"input_clusters": [
0,
3,
61184,
1026,
1029,
6
],
"output_clusters": [
3,
25
]
}
}
},
"class": "zhaquirks.tuya.siren"
}
Tu es sur du json ca c’est un module lidl pour moi (la prise).