Well, unfortunately the distance is really quite similar, given our locations and tank locations (eg. like triangle…). I’m most probably screwed then ;-( He just like the device so he just purchased it 
…
I guess there is no way eg. how to filter values or pair them, eg. if previous value differs significantly, it takes the one which is closer…or something similar if you understand what I mean.
Or is it possible device include in the signal serial number as well ?
According to the https://forum.arduino.cc/uploads/short-url/yfLuiII9NMPXKER50xa6ifxTkKA.xls ?
Wow, I didnt think this would happen unless someone would buy multiple units.
Yes, the signal includes a random ID. Problem is that this ID changes to some other random ID when you replace the batteries.
Manually setting an ID in the app is far from userfriendly. I have to think if it is possible to pair / repair in a user friendly way…
1 Like
Thank you, so if he is using just the display, it will work him during first pairing, because the LCD screen will probably associate to that random ID of “stronger” signal…good to know.
Well, if you would be able to decode the ID, then simply after exchanging batteries, pairing new device and copy pasting the newly generated ID & deleting newly paired device might work eventually ? Not ideal but might be working… for me it would be fine even to repair it after each pairing / battery replacement honestly. I wonder if there would be even higher benefits, like avoiding errors of “invalid message length received” I’m getting each 3 minutes… other option might be setting in the app to “ignore” paired ID…
Just ideas, if I’m talking nonsense, no need to explain how wrong I’m 
Note - I was wondering if I get anything out of https://developer.athom.com/tools/signals and it seems I’m able to record “some” 433MHz signal, no idea which are those however Just in case it would be useful for anything.
https://pastebin.com/aM8dcHi7
https://pastebin.com/T0s5twx1
I dont know how the display pairs with a specific sensor. Maybe it just matches the first ID it sees.
that is not ‘simple’ for the average Homey user. I want to keep the pairing process monkey proof for people who only have 1 device in range. (That is everyone in the world except you and your neighbour). I think I know how to do that, but I would have to make changes in the app. If I have spare time I will do that.
Nope, these will stay and probably double once your neighbour activates his device.
The TFFT002 only breefly transmits every 3 minutes. So if you are recording this at any given time it is noise or some other 433MHz devices transmitting.
Yep I meant by default no changes necessary (ID would be ignored unless especially verification enabled), unless someone would purchase eg. two devices of this kind (which may happen actually thanks to your app and thanks to how unique and quite cheap this device is) 
But if you know how to obey that and keep it simple, great.
I know that one or two beers will not really help you to find time - so just when you will be thinking about that, enjoy
Beers received. Many thx! 
1 Like
Btw, randomID is really such a short ID ? I was realy hoping something more sophisticated…
Also noticed the “invalid message length received” the same time it receives also first update, I assume this is also normal. I’m just wondering, btw my neighbor didn’t install his level meter yet…I’m not using any other 468MHz device. Interesting.
[log] 2021-05-02 10:13:44 [MyApp] Wireless Tank Level Meter app is running...
[log] 2021-05-02 10:13:45 [ManagerDrivers] [Driver:ts_ft002] Driver has been initialized
[log] 2021-05-02 10:13:45 [ManagerDrivers] [Driver:ts_ft002] [Device:0a03ecb1-ccb6-4f43-b030-cbc0a0022125] device ready: TS_FT002
[log] 2021-05-02 10:14:33 [ManagerDrivers] [Driver:ts_ft002] First data received from device: {
data: 'afb31160a8201200f7',
sof: 175,
randomID: 179,
msgType: 17,
airGap: 106,
temp: 13,
batState: 8,
interval: 0,
rain: 0,
crc: 247
}
[err] 2021-05-02 10:14:33 [ManagerDrivers] [Driver:ts_ft002] invalid message length received
[err] 2021-05-02 10:14:33 [ManagerDrivers] [Driver:ts_ft002] invalid message length received
[err] 2021-05-02 10:23:33 [ManagerDrivers] [Driver:ts_ft002] invalid message length received
[err] 2021-05-02 10:23:33 [ManagerDrivers] [Driver:ts_ft002] invalid message length receivedyes, it is just 1 byte. So a chance of 1 in 256 that two sensors have the same id 
This can happen. It means on first reception the first message was decoded ok, but the second was broken up apparently in two corrupt messages.
1 Like
Ok, @Sharkys incentive did help to find time today 
v1.1.0 brings many improvements:
- Added multiple device support.
- Added option to ignore out-of-range air gap.
- Improved log.
- Removed ‘invalid message length received’ messages.
- Show sensor ID in settings.
- Make device unavailable if not updated for over 3 hours.
- Fixed invalid_device_by_appid after device delete.
Available here as test version https://homey.app/a/com.gruijter.wtlm/test/
1 Like
Wow, wait, I thought you will be able to find time in new weeks, not today…you are awesome ! Thank you, going to test it and will report in case of some findings. THANK YOU SO MUCH !
Funny story - I told myself to my neighbor story about searching for wireless level meter, how I was happy to find possibility to integrate with Homey, how fantastic it really is etc. …and recently I learned he purchased it…naturally saying : Hey, can you help me to install it…and I was like … Sure, Happy to ! … and 3 hours later I start to think…
update installation went smooth, the new settings is great…now I need to wait till it will be raining again. It’s cold outside, what a spring is this…
1 Like
Hi @Gruijter , so far temperature got updated even with set “Ignore sensor ID = No”, hours gap as well… according to the logs migration seems to be performed well.
However first time ever I see errors of “CRC failed”… just mentioning it in case it should cause something, otherwise seems to be working just fine.
[err] 2021-05-03 04:20:33 [ts_ft002] CRC failed
[err] 2021-05-03 02:44:33 [ts_ft002] CRC failed
[err] 2021-05-03 01:47:33 [ts_ft002] CRC failed
[err] 2021-05-03 01:05:33 [ts_ft002] CRC failed
[err] 2021-05-02 22:08:33 [ts_ft002] CRC failed
[log] 2021-05-02 20:48:46 [ts_ft002] [dev] Device was renamed: Tank meter TS_FT002
[log] 2021-05-02 20:46:18 [ts_ft002] [dev] MyDevice settings where changed
[log] 2021-05-02 20:44:33 [ts_ft002] First data received from device: { data: 'afb31160a8b0f10084', sof: 175, randomID: 179, msgType: 17, airGap: 106, temp: 10.7, batState: 8, interval: 0, rain: 0, crc: 132 }
[log] 2021-05-02 20:41:40 [ts_ft002] [dev] device TS_FT002 migrated to version 1.1.0
[log] 2021-05-02 20:41:40 [ts_ft002] [dev] device ready: TS_FT002
[log] 2021-05-02 20:41:40 [ts_ft002] Driver has been initializedYes, the CRC fails were always there, but were flooded in the ‘invalid message length’ errors. For me it is comforting to see them though, because it at least shows that on a very regular basis Homey receives messages from the sensor
1 Like
I can confirm check for “hostile” ID works as well 
[log] 2021-05-12 20:45:09 [ts_ft002] Anomaly: { data: 'af7b113010202200e7', sof: 175, randomID: 123, msgType: 17, airGap: 49, temp: 14.6, batState: 0, interval: 0, rain: 0, crc: 231 }
[log] 2021-05-12 20:45:09 [ts_ft002] Anomaly: { data: 'af7b113010202200e7', sof: 175, randomID: 123, msgType: 17, airGap: 49, temp: 14.6, batState: 0, interval: 0, rain: 0, crc: 231 }
[log] 2021-05-12 20:33:09 [ts_ft002] Anomaly: { data: 'af7b113010202200e7', sof: 175, randomID: 123, msgType: 17, airGap: 49, temp: 14.6, batState: 0, interval: 0, rain: 0, crc: 231 }
[log] 2021-05-12 20:30:09 [ts_ft002] Anomaly: { data: 'af7b113010202200e7', sof: 175, randomID: 123, msgType: 17, airGap: 49, temp: 14.6, batState: 0, interval: 0, rain: 0, crc: 231 }
[log] 2021-05-12 20:27:09 [ts_ft002] Anomaly: { data: 'af7b113010202200e7', sof: 175, randomID: 123, msgType: 17, airGap: 49, temp: 14.6, batState: 0, interval: 0, rain: 0, crc: 231 }
[log] 2021-05-12 20:27:09 [ts_ft002] Anomaly: { data: 'af7b113010202200e7', sof: 175, randomID: 123, msgType: 17, airGap: 49, temp: 14.6, batState: 0, interval: 0, rain: 0, crc: 231 }
[log] 2021-05-12 20:21:09 [ts_ft002] Anomaly: { data: 'af7b113010202200e7', sof: 175, randomID: 123, msgType: 17, airGap: 49, temp: 14.6, batState: 0, interval: 0, rain: 0, crc: 231 }
[log] 2021-05-12 20:18:09 [ts_ft002] Anomaly: { data: 'af7b113010202200e7', sof: 175, randomID: 123, msgType: 17, airGap: 49, temp: 14.6, batState: 0, interval: 0, rain: 0, crc: 231 }
[log] 2021-05-12 20:18:09 [ts_ft002] Anomaly: { data: 'af7b113010202200e7', sof: 175, randomID: 123, msgType: 17, airGap: 49, temp: 14.6, batState: 0, interval: 0, rain: 0, crc: 231 }
1 Like
LOL.
Did you already find out you can add your neighbors device to your Homey? Not saying you should, because that would be eavesdropping
And did you find out how the displays know which sensor to show?
Yes, added without problem…
…testing purposes only…
No idea but mine luckily report correct values True is it’s also much closer to it then homey, so maybe it takes stronger signal. But I hope it takes ID as well… However reading the manual, who knows maybe it really consider ID as well.
Insert 6 x AAA batteries into the wireless transmitter, and then insert 2 x AA batteries immediately into the LCD monitor.
A lot of conversations have been had since I last connected this device to Homey. Just thought I would let people know that I had two faulty devices before I got the third one which is now working perfectly. The first device seemed to have a faulty sonar, always showed the tank as empty. I thought it was a faulty install. The second one had a good sonar and showed the correct water level but continually gave me a low battery alarm. The third one fixed that and all is good. They are a very nifty sensor, but they do have quality problems.
2 Likes
@Gruijter Robin, really there is nothing that can be done? It’s hard to believe all of those are real errors, I guess there is no parity in the code or something like this which would allow some code repair, right?
2021-06-22 11:15:20 [ts_ft002] CRC failed
[err] 2021-06-22 11:12:20 [ts_ft002] CRC failed
[err] 2021-06-22 11:01:44 [ts_ft002] CRC failed
[err] 2021-06-22 10:58:44 [ts_ft002] CRC failed
[err] 2021-06-22 10:57:21 [ts_ft002] CRC failed
[err] 2021-06-22 10:55:44 [ts_ft002] CRC failed
[err] 2021-06-22 10:49:44 [ts_ft002] CRC failed
[err] 2021-06-22 10:49:44 [ts_ft002] CRC failed
[err] 2021-06-22 10:46:44 [ts_ft002] CRC failed
[err] 2021-06-22 10:43:44 [ts_ft002] CRC failed
[err] 2021-06-22 10:42:20 [ts_ft002] CRC failed
[err] 2021-06-22 10:40:44 [ts_ft002] CRC failed
[err] 2021-06-22 10:37:44 [ts_ft002] CRC failed
[err] 2021-06-22 10:34:44 [ts_ft002] CRC failed
[err] 2021-06-22 10:33:20 [ts_ft002] CRC failed
[err] 2021-06-22 10:30:20 [ts_ft002] CRC failed
[err] 2021-06-22 10:25:44 [ts_ft002] CRC failed
[err] 2021-06-22 10:22:44 [ts_ft002] CRC failed
[err] 2021-06-22 10:13:44 [ts_ft002] CRC failed
[err] 2021-06-22 10:07:44 [ts_ft002] CRC failed
[err] 2021-06-22 09:58:44 [ts_ft002] CRC failed
[err] 2021-06-22 09:51:21 [ts_ft002] CRC failed
[err] 2021-06-22 09:40:44 [ts_ft002] CRC failed
[err] 2021-06-22 09:31:44 [ts_ft002] CRC failed
[err] 2021-06-22 09:25:43 [ts_ft002] CRC failed
[err] 2021-06-22 09:19:44 [ts_ft002] CRC failed
[err] 2021-06-22 09:18:21 [ts_ft002] CRC failed
[err] 2021-06-22 09:15:21 [ts_ft002] CRC failed
[err] 2021-06-22 09:10:44 [ts_ft002] CRC failed
[err] 2021-06-22 09:07:44 [ts_ft002] CRC failed
[err] 2021-06-22 09:03:21 [ts_ft002] CRC failed
[err] 2021-06-22 08:58:44 [ts_ft002] CRC failed
[err] 2021-06-22 08:58:43 [ts_ft002] CRC failed
[err] 2021-06-22 08:52:44 [ts_ft002] CRC failed
[err] 2021-06-22 08:49:43 [ts_ft002] CRC failed
[err] 2021-06-22 08:25:43 [ts_ft002] CRC failed
[err] 2021-06-22 08:07:43 [ts_ft002] CRC failed
[err] 2021-06-22 07:46:43 [ts_ft002] CRC failed
[err] 2021-06-22 07:43:43 [ts_ft002] CRC failed
It is what it is. A checksum. No way to do code repair.
What I could do is not log these anymore…
Easyer would be if you just didn’t look at it…
If you want to have less CRC errors only thing you can do is move Homey closer to the transmitter. But are you experiencing real world issues? It looks like you are getting enough correct receptions to get an update at least every 15 minutes or so.
1 Like
I’m not concerned about cosmetic reports, actually sometimes I’m getting dropouts for half a day (randomly, eg one time a week)… That’s why I was wondering if really nothing can be done. But you are expert, so if nothing can be done, nothing can be done
