Closed alexisiglesias1 closed 1 year ago
Without device signature or any other info like pairing logs there's no much that can be done. That is all the pairin log that the device generate?
i was looking for more log this is the only one i could find 2022-10-04 13:27:43.320 INFO (MainThread) [zigpy_znp.zigbee.application] TC device join: ZDO.TCDevInd.Callback(SrcNwk=0x4A8C, SrcIEEE=00:0d:6f:00:02:3a:d9:6b, ParentNwk=0x0000)
this is a post where they describe the process to include them through Xbee http://www.desert-home.com/2015/05/hacking-into-iris-door-sensor-part-3.html this is far complex for my understanding, but i think it has a lot of useful information
And there is some info about getting the info requested:
Thanks @javicalle i will try to get as much info as I can with the debug, im really hoping this can be included I think it's a good device
debug logs:
And the device signature? Any info about the device? What do you expect to have or what is not working? Are these logs related with the device interaction?
Yes these logs are about the device and I can't get the signature device, because I tried to pair to zha, which is able to find it, zha doesn't add it, that's why I was offering send a sample o the device to one of the developers because I don't have enough knowledge, I dm @dmulcahey but I think he hasn't read my mail, I really appreciate ir you are looking on this @javicalle
I see the problem. Have you tried to keep awake the device during the pairing process?. Usually short pushing the button or whatever you do to pair the device will work. Attach all the pairing logs from device.
I tried pushing the buttons on different combinations but nothing still not able to add it this is the complete log:
New device 0x0b34 (00:0d:6f:00:02:3a:d9:6b) joined the network this is the device btw the device is a key fob with two buttons (iris key fob 903). The v2 version is supported with zha with the same functions but less battery, which is this https://zigbee.blakadder.com/Centralite_3450.htm
The KEY903 uses the same proprietary protocol as all of the other Iris V1 stuff. Looking at the main zigpy repo - I see a 2 year old issue where it wasn’t feasible to add support for the custom zigbee clusters those devices use.
https://github.com/zigpy/zigpy/issues/132
I’d love to see a custom quirk for it, as I’ve got a boatload of DWS800 sensors that only work today on Hubitat.
This is a public repo of all of the AlertMe/Irisv1 devices and their groovy formatted handlers.
https://github.com/birdslikewires/hubitat/tree/master/alertme/drivers
I’m unsure if there’s additional support required by the platform for these to work, as I’ve never seen any other platform make use.
this user made some advance https://github.com/zigpy/zigpy/issues/121 but definitely have not idea how to implement it.
This is the iris's source code the published back when they close the platform https://github.com/arcus-smart-home/arcusios
i bought a couple of iris v1 keyfob 903
Is that specific device listed on Zigbee Alliance Certifies Products, Zigbee2MQTT supported devices, or Blakadder's databases?
https://csa-iot.org/csa-iot_products/
https://www.zigbee2mqtt.io/supported-devices/
I only see that Zigbee2MQTT and Blakadder currently list Iris Smart Fob Model 3450-L
https://www.zigbee2mqtt.io/devices/3450-L.html
https://zigbee.blakadder.com/Iris_3450-L.html
Hubitat docs at least looks to have some basic info on how to activate join-mode on IRIS V1 Keyfob KEY903
Is your feature request related to a problem? Please describe. i bought a couple of iris v1 keyfob 903, i was thinking i could add them to zha, but they are not supported i did some research and notice on hubitat forums they managed included them, i can provide a test device to the developers since i already have a few.
Describe the solution you'd like i would like to use this device as an arrival sensor, since the v2 version works like that but with less battery, that's why I really would like this one work
Device signature
since zha only can see but not add the device this is the only info i have: IEEE: 00:0d:6f:00:02:3a:d9:6b NWK: 0x5a34 ```yaml Paste the device signature here. Don't remove the extra line breaks outside the ``` marks. ```Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 9.0 -- | -- update_channel | stable supervisor_version | supervisor-2022.09.1 agent_version | 1.3.0 docker_version | 20.10.17 disk_total | 28.5 GB disk_used | 6.1 GB healthy | true supported | true board | rpi3-64 supervisor_api | ok version_api | ok installed_addons | Z-Wave JS (0.1.74), Studio Code Server (5.4.0), File editor (5.4.1), Samba share (10.0.0), Plex Media Server (3.1.1), Portainer (2022.9.0), Terminal & SSH (9.6.1)Dashboards
dashboards | 1 -- | -- resources | 0 mode | auto-genRecorder
oldest_recorder_run | September 28, 2022 at 2:11 PM -- | -- current_recorder_run | September 30, 2022 at 10:23 AM estimated_db_size | 53.86 MiB database_engine | sqlite database_version | 3.38.5Diagnostic information
```yaml Paste the diagnostic information here. Don't remove the extra line breaks outside the ``` marks. ```Additional logs
``` Device 0x5a34 (00:0d:6f:00:02:3a:d9:6b) joined the network Device 00:0d:6f:00:02:3a:d9:6b changed id (0xa28d => 0x5a34) [0x5a34] Scheduling initialization [0x5a34] Canceling old initialize call Tries remaining: 3 [0x5a34] Requesting 'Node Descriptor' Tries remaining: 2 [0x5a34] Extending timeout for 0xd8 request ```Additional context Add any other context or screenshots about the feature request here.