New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remontée batterie sensor presence Xiaomi #141

Closed
KiwiHC16 opened this Issue Feb 28, 2018 · 7 comments

Comments

Projects
None yet
4 participants
@KiwiHC16
Owner

KiwiHC16 commented Feb 28, 2018

No description provided.

KiwiHC16 pushed a commit that referenced this issue Mar 1, 2018

KiwiHC16
Code Parser pour battery capteur presence Xiaomi V1
Remontée batterie sensor presence Xiaomi #141
@KiwiHC16

This comment has been minimized.

Owner

KiwiHC16 commented Mar 1, 2018

lumi.sensor_motion ne semble pas remonter l info battery...
I don't know how to trigger it.

edgd1er added a commit to edgd1er/Abeille that referenced this issue Mar 2, 2018

Code Parser pour battery capteur presence Xiaomi V1
Remontée batterie sensor presence Xiaomi KiwiHC16#141
@KiwiHC16

This comment has been minimized.

Owner

KiwiHC16 commented Mar 2, 2018

capture d ecran 2018-03-01 a 18 31 45

Le capteur IR de présence Xiaomi envoie le fameuse trames ff02.
La ZiGate ne semble pas transparente car je ne trouve pas ce message dans les logs.

@lukebr91

This comment has been minimized.

Contributor

lukebr91 commented Mar 4, 2018

Mon soucis a l'air lié :
Sur mon lumi.sensor_motion.aq2 je reçois cette trame ff01 (sans mouvement) avec des caractères bizarres dans Data byte
Du coup Jeedom ne m'affiche plus le log AbeilleParser... - et en téléchargeant et l'ouvrant en local j'obtiens ça :

AbeilleParser 2018-03-04 12:41:03[DEBUG]-------------- 2018-03-04 12:41:03: protocolData size(102) message > 12 char
AbeilleParser 2018-03-04 12:41:03[DEBUG]Type: 8102 quality: 54
AbeilleParser 2018-03-04 12:41:03[DEBUG] Type: 8102 (Attribut Report)(Processed->MQTT)
AbeilleParser 2018-03-04 12:41:03[DEBUG][2018-03-04 12:41:03]
AbeilleParser 2018-03-04 12:41:03[DEBUG]SQN: e8
AbeilleParser 2018-03-04 12:41:03[DEBUG]Src Addr : e837
AbeilleParser 2018-03-04 12:41:03[DEBUG]End Point : 01
AbeilleParser 2018-03-04 12:41:03[DEBUG]Cluster ID : 0000
AbeilleParser 2018-03-04 12:41:03[DEBUG]Attr ID : ff01
AbeilleParser 2018-03-04 12:41:03[DEBUG]Attr Status : 00
AbeilleParser 2018-03-04 12:41:03[DEBUG]Attr Data Type : 42
AbeilleParser 2018-03-04 12:41:03[DEBUG]Attr Size : 0021
AbeilleParser 2018-03-04 12:41:03[DEBUG]Data byte list : 0121e50B0328130421a81305210800062401000000000A2100006410000B217f01
AbeilleParser 2018-03-04 12:41:03[DEBUG**]Data byte: �!å��(��!¨��!��$�
!d��!��**
AbeilleParser 2018-03-04 12:41:03[DEBUG]mqttPublish with Qos: 0
@edgd1er

This comment has been minimized.

Collaborator

edgd1er commented Mar 4, 2018

oui, j'ai la même chose sur un interrupteur simple Xiaomi, ff01 est un champ privée a décoder, pour l'instant indécodable. cf #170

@fairecasoimeme

This comment has been minimized.

fairecasoimeme commented Mar 10, 2018

Fixed in next version (3.0e) . packet 0xFF02 OK

@KiwiHC16

This comment has been minimized.

Owner

KiwiHC16 commented Sep 3, 2018

0xFF02 remonte bien maintenant en V30E. Example d association de IR V1:

AbeilleParser 2018-09-03 17:09:15[DEBUG];Type: 8102 (Attribut Report)(Processed->MQTT); SQN: 00; Src Addr : 6e72; End Point : 01; Cluster ID : 0000; Attr ID : 0005; Attr Status : 00; Attr Data Type : 42; Attr Size : 0012; Data byte list : ->lumi.sensor_motion<-
AbeilleParser 2018-09-03 17:09:15[DEBUG];Type: 8102 (Attribut Report)(Processed->MQTT); SQN: 01; Src Addr : 6e72; End Point : 01; Cluster ID : 0000; Attr ID : 0001; Attr Status : 00; Attr Data Type : 20; Attr Size : 0001; Data byte list : 0B
AbeilleParser 2018-09-03 17:09:16[DEBUG];Type: 8102 (Attribut Report)(Processed->MQTT); SQN: 02; Src Addr : 6e72; End Point : 01; Cluster ID : 0000; Attr ID : ff02; Attr Status : 00; Attr Data Type : 42; Attr Size : 0013; Data byte list : 100121bd0B21a801240000000000210E002059
AbeilleParser 2018-09-03 17:09:16[DEBUG]Champ 0xFF02 non decode a ce stade
@KiwiHC16

This comment has been minimized.

Owner

KiwiHC16 commented Sep 3, 2018

Done and pushed in the master. Only for battery information. If more data is reverse engineered then will need to include.

@KiwiHC16 KiwiHC16 closed this Sep 3, 2018

KiwiHC16 pushed a commit that referenced this issue Sep 3, 2018

KiwiHC16
Remontée batterie sensor presence Xiaomi #141
Inclus FF02 battery data analysis
Xiaomi door sensor V1
Xiaomi IR V1

@llaumgui llaumgui referenced this issue Nov 7, 2018

Open

Support du firmware 3.0e #83

2 of 3 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment