vmario/Nukiana
0
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

„README.md“ ändern

Browse Source
This commit is contained in:
Mario Voigt 2018-12-11 14:55:44 +01:00
parent 0604743be3
commit bfafee43ee
1 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -567,12 +567,10 @@ https://grafana.com/dashboards/7628/ or https://leyghis.fablabchemnitz.de:8444/M
* to implement: * to implement:
* make us of fields `keypadPaired` `lastAction` `doorState` `homekitState` `timezoneId` `accountUserId` * make us of fields `keypadPaired` `lastAction` `doorState` `homekitState` `timezoneId` `accountUserId`
* build up some check script to make proof of correct count of columns and column order of the csv files * build up some check script to make proof of correct count of columns and column order of the csv files
* collect data with time history: * collect data with time history (maybe with triggers):
* history of firmware changes * BridgeFirmwareHistory: BridgeId, date, BridgeFirmware, BridgeWifiFirmware,BridgeAppVersion
* SmartlockFirmwareHistory: SmartlockId,date,SmartlockFirmware
* history of rssi values * history of rssi values
* history of state changes: locking states, pairing state * history of state changes: locking states, pairing state
* to test: this project was never tested with more than one Smartlock and more than one Bridge. We only have one! I also did not test what data output FOB will produce * to test: this project was never tested with more than one Smartlock and more than one Bridge. We only have one! I also did not test what data output FOB will produce
* Maybe give a try to send the JSON output files directly to JQ/Filebeat → Elasticsearch → Grafana Datasource for Elasticsearch ↔ possible? * Maybe give a try to send the JSON output files directly to JQ/Filebeat → Elasticsearch → Grafana Datasource for Elasticsearch ↔ possible?
* Write some data collector tables like "BridgeFirmwareHistory" and "SmartlockFirmwareHistory" for tracking firmware changes utilizing some trigger
* BridgeFirmwareHistory: BridgeId, date, BridgeFirmware, BridgeWifiFirmware,BridgeAppVersion
* SmartlockFirmwareHistory: SmartlockId,date,SmartlockFirmware