I could add an option to also display results that have a bad crc. But you would most likely get random spikes in your data for temperature and/or fill ratio.
1 Like
Well, happy to test it 
I have two sensors on which I can test it eventually, mine and neighborsâŚ
I wonder if nobody else has such problems, or yourself - you get no dropouts / no CRC errors ?
I have crc errors. But nothing that lasts for a very long time. It depends on the weather I guess. Humid weather gives more errors.
InterestingâŚ
[err] 2021-06-23 08:43:44 [ts_ft002] CRC failed
[err] 2021-06-23 08:31:44 [ts_ft002] CRC failed
[err] 2021-06-23 08:28:20 [ts_ft002] CRC failed
[err] 2021-06-23 08:16:44 [ts_ft002] CRC failed
[err] 2021-06-23 08:07:20 [ts_ft002] [dev] No valid data received for a long time.
[err] 2021-06-23 08:04:44 [ts_ft002] CRC failed
[err] 2021-06-23 07:19:44 [ts_ft002] CRC failed
[err] 2021-06-23 07:16:44 [ts_ft002] CRC failed
âŚand my device is marked as unavailable, yet when trying to add new device, it offers the one with ID 179âŚso now I have two.
Anything particular you would see in LOGs?
2b74f019-dbc3-4369-bdc4-ad35ad6798c8
Thank you.
that is probably because you migrated from the previous version app. If you try again it shouldnât be added again.
No, it just means no valid data was received for more then 3 hours. It will automatically be enabled again when a valid message is received.
Testing in progres⌠installation went smoothly, I see in the log info about devices migration. Now waiting for CRC errors
If you switched on ignore CRC in the device settings you will not get any CRC errors since the CRC is ignoredâŚ
1 Like
Yes, sure - I didnât enable CRC ignore.
So far, seems to be indeed a lot of noise only, letâs see if there will be any usable patternâŚ
actual / full log below
Update after a day (Anomalies are actually not really anomalies, there is crazy weather aroundâŚ), not sure what means "Error: CRC failed at MyDevice.handleInfo "âŚ
[log] 2021-06-25 02:25:45 [ts_ft002] First data received from device: { data: 'afff632400131a4004', sof: 175, randomID: 255, msgType: 99, airGap: 1056, temp: 217.7, batState: 0, interval: 3, rain: 64, crc: 4 }
[err] 2021-06-25 02:24:50 [ts_ft002] [dev] No valid data received for a long time.
[log] 2021-06-25 00:46:45 [ts_ft002] First data received from device: { data: 'affbd801044482108d', sof: 175, randomID: 251, msgType: 216, airGap: 256, temp: 24.4, batState: 4, interval: 4, rain: 16, crc: 141 }
[log] 2021-06-24 23:02:50 [ts_ft002] Anomaly: { data: 'afb3115008f86200cf', sof: 175, randomID: 179, msgType: 17, airGap: 80, temp: 22.3, batState: 8, interval: 8, rain: 0, crc: 207 }
[log] 2021-06-24 23:02:20 [ts_ft002] Anomaly: { data: 'afb3115068f86200af', sof: 175, randomID: 179, msgType: 17, airGap: 86, temp: 22.3, batState: 8, interval: 8, rain: 0, crc: 175 }
[log] 2021-06-24 23:02:19 [ts_ft002] Anomaly: { data: 'afb3115068f86200af', sof: 175, randomID: 179, msgType: 17, airGap: 86, temp: 22.3, batState: 8, interval: 8, rain: 0, crc: 175 }
[log] 2021-06-24 23:01:49 [ts_ft002] Anomaly: { data: 'afb31160080872001f', sof: 175, randomID: 179, msgType: 17, airGap: 96, temp: 22.4, batState: 8, interval: 8, rain: 0, crc: 31 }
[log] 2021-06-24 17:25:50 [ts_ft002] First data received from device: { data: 'affe4481c163c900ce', sof: 175, randomID: 254, msgType: 68, airGap: 396, temp: 210.2, batState: 1, interval: 3, rain: 0, crc: 206 }
[log] 2021-06-24 17:13:45 [ts_ft002] First data received from device: { data: 'aff632400110e4002e', sof: 175, randomID: 246, msgType: 50, airGap: 64, temp: 84.9, batState: 1, interval: 0, rain: 0, crc: 46 }
[log] 2021-06-24 16:55:45 [ts_ft002] First data received from device: { data: 'affd648002e0c9008c', sof: 175, randomID: 253, msgType: 100, airGap: 128, temp: 211, batState: 2, interval: 0, rain: 0, crc: 140 }
[log] 2021-06-24 16:52:50 [ts_ft002] First data received from device: { data: 'af7722c0e01005002f', sof: 175, randomID: 119, msgType: 34, airGap: 206, temp: 88.1, batState: 0, interval: 0, rain: 0, crc: 47 }
[log] 2021-06-24 16:25:50 [ts_ft002] First data received from device: { data: 'afb3116068408200c7', sof: 175, randomID: 179, msgType: 17, airGap: 102, temp: 24.4, batState: 8, interval: 0, rain: 0, crc: 199 }
[log] 2021-06-24 16:25:45 [ts_ft002] First data received from device: { data: 'af7b1120889072008f', sof: 175, randomID: 123, msgType: 17, airGap: 40, temp: 23.3, batState: 8, interval: 0, rain: 0, crc: 143 }
[log] 2021-06-24 16:20:03 [ts_ft002] [dev] device TS_FT002_179 migrated to version 1.2.0
[log] 2021-06-24 16:20:03 [ts_ft002] [dev] device TS_FT002_123 migrated to version 1.2.0
[log] 2021-06-24 16:20:03 [ts_ft002] [dev] device ready: TS_FT002_179
[log] 2021-06-24 16:20:03 [ts_ft002] [dev] device ready: TS_FT002_123
[log] 2021-06-24 16:20:03 [ts_ft002] Driver has been initialized
[log] 2021-06-24 16:20:03 [App] Wireless Tank Level Meter app is running...
[log] 2021-06-24 16:20:03 logfile retrieved
[log] 2021-06-24 13:29:29 saving logfile...
[log] 2021-06-24 13:29:28 [App] app unload called
[err] 2021-06-24 09:40:45 [ts_ft002] [dev] No valid data received for a long time.
[log] 2021-06-24 06:19:33 [ts_ft002] [dev] Device was renamed: TS_FT002_179
[log] 2021-06-24 05:40:50 [ts_ft002] First data received from device: { data: 'aff7722a081b1c4004', sof: 175, randomID: 247, msgType: 114, airGap: 2592, temp: 268.9, batState: 8, interval: 11, rain: 64, crc: 4 }
[log] 2021-06-24 01:16:44 [ts_ft002] First data received from device: { data: 'affbd80104c582100c', sof: 175, randomID: 251, msgType: 216, airGap: 256, temp: 25.2, batState: 4, interval: 5, rain: 16, crc: 12 }
[log] 2021-06-23 23:55:20 [ts_ft002] Anomaly: { data: 'afb3115098c862006f', sof: 175, randomID: 179, msgType: 17, airGap: 89, temp: 22, batState: 8, interval: 8, rain: 0, crc: 111 }
[err] 2021-06-23 21:58:44 [ts_ft002] [dev] Error: CRC failed at MyDevice.handleInfo (/drivers/ts_ft002/device.js:142:50) at Homey.eventListener (/drivers/ts_ft002/device.js:65:9) at Homey.emit (events.js:323:22) at Signal433. (/drivers/ts_ft002/driver.js:156:26) at processTicksAndRejections (internal/process/task_queues.js:97:5)
[log] 2021-06-23 20:40:20 [ts_ft002] First data received from device: { data: 'affd980300c703108f', sof: 175, randomID: 253, msgType: 152, airGap: 768, temp: 38, batState: 0, interval: 7, rain: 16, crc: 143 }
[log] 2021-06-23 20:28:20 [ts_ft002] First data received from device: { data: 'affe448100e38900cf', sof: 175, randomID: 254, msgType: 68, airGap: 384, temp: 204.6, batState: 0, interval: 3, rain: 0, crc: 207 }
[log] 2021-06-23 20:22:44 [ts_ft002] First data received from device: { data: 'aff632400150c4004e', sof: 175, randomID: 246, msgType: 50, airGap: 64, temp: 82.1, batState: 1, interval: 0, rain: 0, crc: 78 }
[log] 2021-06-23 20:16:44 [ts_ft002] First data received from device: { data: 'af7b1120882062002f', sof: 175, randomID: 123, msgType: 17, airGap: 40, temp: 21, batState: 8, interval: 0, rain: 0, crc: 47 }
[log] 2021-06-23 20:13:20 [ts_ft002] First data received from device: { data: 'afb311600800720017', sof: 175, randomID: 179, msgType: 17, airGap: 96, temp: 22.4, batState: 8, interval: 0, rain: 0, crc: 23 }
[log] 2021-06-23 20:07:20 [ts_ft002] First data received from device: { data: 'af7722c00010e40026', sof: 175, randomID: 119, msgType: 34, airGap: 192, temp: 84.9, batState: 0, interval: 0, rain: 0, crc: 38 }
[log] 2021-06-23 20:05:11 [ts_ft002] [dev] device TS_FT002_179 migrated to version 1.2.0
[log] 2021-06-23 20:05:11 [ts_ft002] [dev] device TS_FT002_123 migrated to version 1.2.0
[log] 2021-06-23 20:05:11 [ts_ft002] [dev] device ready: TS_FT002_179
[log] 2021-06-23 20:05:11 [ts_ft002] [dev] device ready: TS_FT002_123
[log] 2021-06-23 20:05:11 [ts_ft002] Driver has been initialized
[log] 2021-06-23 20:05:10 [App] Wireless Tank Level Meter app is running...
[log] 2021-06-23 20:05:10 logfile not found
[log] 2021-06-23 20:05:10 capturing stderr
[log] 2021-06-23 20:05:10 capturing stdout
Well, it is clear to me that ignoring CRC is totally useless. It just results in random data and ghost devices. I will remove this option again from the app.
Seems to be - just a pity I have those random dropoutsâŚobviously there is nothing which can be done. Thank you for your effort and still trying to improve your app.
Maybe just keep the option to log / not log CRC errors, so itâs at least visible that signal is weak yet some sensor still is alive and trying to send out data. Btw, previously I got CRC errors like every 10min but Iâm getting ânoiseâ now less frequentlyâŚany idea about that ?
New app version v1.3.0 is coming up.
- Removed option to ignore CRC.
- Added auto fix for shifted payload.
- Removed anomaly check.
- Increased log buffer.
This version is able to correct certain CRC failures @Sharkys
1 Like
I knew it, you can do it !! 
Even 5% improvement, is a improvement.
Thank you, testing now, unfortunately waiting now for my device again to pickup signal after a break. (vice versa)
1 Like
@Gruijter
Love what you have done with this app! I have installed my tank level meter in the well about 10 meters from Homey. I get frequent temperature updates but no updates from the rest of the parameters. Am I doing something wrong?
You can check the advanced device settings. If the min/max levels are not filled in correctly you can get an âout of rangeâ and it will ignore the measurement. If so it would show out of range messages in the app logs.
If the min/max is correctly set it could be that the sensor itself is not working properly. Does the sensor display show the correct level?
Edit: and I forgot about another possibility: the level actually hasnât changed. Did the level change in the well?
I have not used the sensor display, only Homey. I now opened the well and âyankedâ the sensor a bit. About a minute later; the parameters updated in Homey. I guess it could be a range-related problem. Seems strange, however, that the temperature updates frequently.
If the sensor is not getting a good distance reading (e.g. because it is not mounted exactly horizontal) it will keep transmitting the last valid value. Hence Homey will not update the air gap and related values.
Ok. It keeps updating now, so I guess the problem was the sensor not beeing completley in level. Thank you for your effort with the app!
