Hi @Peter_Bittner,
I believe if the diameter of the pipe is big enough and the sensor is mounted absolutely horizontal it should work.
And thx for the donation 

Hi @Peter_Bittner,
I believe if the diameter of the pipe is big enough and the sensor is mounted absolutely horizontal it should work.
And thx for the donation 

No, the sensor and the app work with whole centimeters, no decimals. The decimals are a result from the way Homey stores the data in the Insights database because it averages data for long term storage.
Thank you, no worries, itās not important, just was surprised by that 
Yes, I saw that video. I will work on getting it perfectly level.
Is it possible to get the App to show the water fill in litres rather than cubes metres?
Iām using m3 because I can then make use of a default watermeter that is available in Homey. Making a liters meter is extra work for me, and also doesnāt match with international standards how large volumes are measured.
By the way: just move the decimal point 3 places to the right in your mind, and m3 magically turn into liters ![]()
Good point. Thanks.
Peter
[Mod break, removed (possible) phone number]
| Gruijter Regular
March 26 |
- | - |
Peter_Bittner:
App to show the water fill in litres rather than cubes metres
Iām using m3 because I can then make use of a default watermeter that is available in Homey. Making a liters meter is extra work for me, and also doesnāt match with international standards how large volumes are measured.
By the way: just move the decimal point 3 places to the right in your mind, and m3 magically turn into liters ![]()
Hmm, just 1st time happened values were not updated on Homey for 4 hours (the LCD was updated thought). It happened 1st time since I have installed it. Anyone else has got similar experience? Reboot didnāt help now after 4 hours it got updating again, without me doing anythingā¦
That probably means temporary bad reception or interference. In the app logs you can see why the app is disregarding received data.
Wow, I didnāt know you included LOGs !
Pity though yesterday āno receptionā time log is gone already (maybe due to the restart, not sure). Even the bad reception/temporary interference is strange - everything was/is located as it was⦠Anyway, I see plenty of errors but seems to be working just fine now. Attaching just part of logs, where even CRC checksum error occurred.
2021-03-29 00:39:55 [err] invalid message length received
2021-03-29 00:36:55 [err] invalid message length received
2021-03-29 00:36:55 [err] invalid message length received
2021-03-29 00:36:55 [err] invalid message length received
2021-03-29 00:33:55 [err] invalid message length received
2021-03-29 00:33:55 [err] invalid message length received
2021-03-29 00:24:55 [err] CRC failed
2021-03-28 23:51:55 [err] invalid message length received
2021-03-28 23:51:55 [err] invalid message length received
2021-03-28 23:51:55 [err] invalid message length received
2021-03-28 23:42:55 [err] invalid message length received
2021-03-28 23:21:55 [err] invalid message length received
2021-03-28 23:18:55 [err] invalid message length received
Just not sure if it would help, today after I just installed v6 rc4 and after I tried to restart app ā¦diag. code b8d12186-3837-425c-9d0a-c0617b8b094f - currently hour without update. Hopefully it will be again temporary only. update 30 min later and itās working againā¦nothing new in the logs though
Btw, time seems to be shifted according to the reality about 2 hours.
[err] 2021-04-07 14:09:57 [Driver:ts_ft002] invalid message length received
[err] 2021-04-07 14:09:57 [Driver:ts_ft002] invalid message length received
[log] 2021-04-07 14:09:57 [Driver:ts_ft002] First data received from device: { data: āafb3116068e0d10034ā, sof: 175, randomID: 179, msgType: 17, airGap: 102, temp: 7.8, batState: 8, interval: 0, rain: 0, crc: 52 }
[log] 2021-04-07 14:09:31 [Driver:ts_ft002] [Device:0088fe05-5b55-44e4-bb3a-bbe252ffe69f] device ready: TS_FT002
[log] 2021-04-07 14:09:31 [Driver:ts_ft002] Driver has been initialized
[log] 2021-04-07 14:09:31 Wireless Tank Level Meter app is runningā¦
[log] 2021-04-07 14:09:31 capturing stderr
[log] 2021-04-07 14:09:31 capturing stdout
[log] 2021-04-07 14:09:27 app unload called
[err] 2021-04-07 14:03:57 [Driver:ts_ft002] invalid message length received
[err] 2021-04-07 14:03:57 [Driver:ts_ft002] invalid message length received
[err] 2021-04-07 14:00:57 [Driver:ts_ft002] invalid message length received
[err] 2021-04-07 14:00:57 [Driver:ts_ft002] invalid message length received
[err] 2021-04-07 13:45:57 [Driver:ts_ft002] invalid message length received
[err] 2021-04-07 13:45:57 [Driver:ts_ft002] invalid message length received
[log] 2021-04-07 13:42:57 [Driver:ts_ft002] First data received from device: { data: āafb3116068e0d10034ā, sof: 175, randomID: 179, msgType: 17, airGap: 102, temp: 7.8, batState: 8, interval: 0, rain: 0, crc: 52 }
[log] 2021-04-07 13:41:23 [Driver:ts_ft002] [Device:0088fe05-5b55-44e4-bb3a-bbe252ffe69f] device ready: TS_FT002
[log] 2021-04-07 13:41:23 [Driver:ts_ft002] Driver has been initialized
[log] 2021-04-07 13:41:22 Wireless Tank Level Meter app is runningā¦
[log] 2021-04-07 13:41:22 capturing stderr
[log] 2021-04-07 13:41:22 capturing stdout
2021-04-07 13:37:19 [log] app unload called
Minimum distance the sensor can detect reliably is around 40 cm. That is your issue. So place the sensor higher, or accept that you will not be able to see reliably if the barrel is more then half full.
Can we than make a pvc pipe its that okƩ? For the working
thank you for the help I am going to work with it I am already very happy and certainly done well with the app develo