Indigo Domotics

What are your data sources?
If these are the indigoplotd sql files they are the results from straight sql statements plus a filter that removes none numbers
Interesting is that there are gaps in the sequential numbers
Every time the number goes up there are some numbers missing after that

Could you run sql utilities sql report on these to see if you get the same results?


Sent from my iPhone using Tapatalk

The source are the indigoplotd sql-files as you guessed. One is the temperature reading from a multisensor and the other is from the adapter plugin based on the same multisensor. And I thought the gaps were a bit strange as well.
I'm not sure how to run the sql utilities sql report. What is that?

Install Plugin indigo utilities
Then at the bottom of the menu you find sql ....
in the selection window select the device and the state and starting # of records. And execute.


Sent from my iPhone using Tapatalk

The gaps could come from the plugin rejecting the entries as not a valid number. I.e. Not 123 but e.g. " "


Sent from my iPhone using Tapatalk

These are values from an adaptor-device (not the same device I had in the last post).


SQL-OUTPUT:
id strftime('%Y-%m-%d-%H:%M:%S',ts,'localtime') sensorvalue
---------- -------------------------------------------- -----------
1416 2016-12-20-10:49:02 21.9
1417 2016-12-20-10:53:21 19.7
1418 2016-12-20-10:53:21 17.1
1419 2016-12-20-11:01:05 22.4
1420 2016-12-20-11:13:17 22.5
1421 2016-12-20-11:25:17 22.2
1422 2016-12-20-11:37:18 22.1
1423 2016-12-20-11:49:18 22.0
1424 2016-12-20-11:52:59 19.7
1425 2016-12-20-11:52:59 17.1
1426 2016-12-20-12:01:18 21.9
1427 2016-12-20-12:13:29 22.0
1428 2016-12-20-12:51:20 19.7
1429 2016-12-20-12:51:20 17.1
1430 2016-12-20-13:01:21 22.0
1431 2016-12-20-13:25:21 22.1
1432 2016-12-20-13:50:20 19.7
1433 2016-12-20-13:50:20 17.1
1434 2016-12-20-14:01:24 22.1
1435 2016-12-20-14:13:24 22.0
1436 2016-12-20-14:25:24 22.1
1437 2016-12-20-14:49:21 19.7
1438 2016-12-20-14:49:21 17.1
1439 2016-12-20-14:49:25 22.1
1440 2016-12-20-15:13:24 22.0
1441 2016-12-20-15:48:20 19.7
1442 2016-12-20-15:48:20 17.1
1443 2016-12-20-15:49:24 21.9
1444 2016-12-20-16:25:24 21.8
1445 2016-12-20-16:47:22 19.7
1446 2016-12-20-16:47:22 17.1
1447 2016-12-20-16:47:22 19.7
1448 2016-12-20-16:47:22 17.1
1449 2016-12-20-16:49:34 21.8
1450 2016-12-20-17:01:28 21.7
1451 2016-12-20-17:46:20 19.7
1452 2016-12-20-17:46:20 17.1
1453 2016-12-20-17:50:12 21.7
1454 2016-12-20-18:01:28 21.6
1455 2016-12-20-18:45:20 19.7
1456 2016-12-20-18:45:20 17.1
1457 2016-12-20-18:49:32 21.6
1458 2016-12-20-19:25:42 21.5
1459 2016-12-20-19:44:20 19.7
1460 2016-12-20-19:44:20 17.1
1461 2016-12-20-19:49:28 21.5
1462 2016-12-20-20:43:21 19.7
1463 2016-12-20-20:43:21 17.1
1464 2016-12-20-20:49:29 21.5
1465 2016-12-20-21:37:43 21.6

and here's from the corresponding multisensor device.
SQL-OUTPUT:
id strftime('%Y-%m-%d-%H:%M:%S',ts,'localtime') sensorvalue
---------- -------------------------------------------- -----------
19934 2016-12-19-14:12:16 22
19935 2016-12-19-14:24:16 22.1
19936 2016-12-19-17:12:22 22.2
19937 2016-12-19-17:24:26 22.1
19938 2016-12-19-17:36:58 22
19939 2016-12-19-17:48:27 21.9
19940 2016-12-19-18:00:27 21.8
19941 2016-12-19-18:48:28 21.9
19942 2016-12-19-19:48:28 22
19943 2016-12-19-22:12:29 22.1
19944 2016-12-19-22:48:42 22.2
19945 2016-12-19-23:12:49 22.3
19946 2016-12-19-23:24:49 22.4
19947 2016-12-19-23:36:49 22.3
19948 2016-12-19-23:48:49 22.4
19949 2016-12-20-00:00:49 22.3
19950 2016-12-20-01:12:49 22.2
19951 2016-12-20-02:36:50 22.1
19952 2016-12-20-06:24:54 22.2
19953 2016-12-20-06:36:56 22.4
19954 2016-12-20-06:49:00 23.6
19955 2016-12-20-07:01:01 22.9
19956 2016-12-20-07:13:01 22.5
19957 2016-12-20-07:25:01 22.4
19958 2016-12-20-07:37:01 22.3
19959 2016-12-20-07:49:02 22.2
19960 2016-12-20-08:01:01 22.1
19961 2016-12-20-08:25:01 22
19962 2016-12-20-08:49:18 21.9
19963 2016-12-20-09:25:01 21.8
19964 2016-12-20-09:49:01 21.9
19965 2016-12-20-10:37:01 22
19966 2016-12-20-10:49:02 21.9
19967 2016-12-20-11:01:05 22.4
19968 2016-12-20-11:13:17 22.5
19969 2016-12-20-11:25:17 22.2
19970 2016-12-20-11:37:18 22.1
19971 2016-12-20-11:49:18 22
19972 2016-12-20-12:01:18 21.9
19973 2016-12-20-12:13:29 22
19974 2016-12-20-13:25:21 22.1
19975 2016-12-20-14:13:24 22
19976 2016-12-20-14:25:24 22.1
19977 2016-12-20-15:13:24 22
19978 2016-12-20-15:49:24 21.9
19979 2016-12-20-16:25:24 21.8
19980 2016-12-20-17:01:28 21.7
19981 2016-12-20-18:01:28 21.6
19982 2016-12-20-19:25:42 21.5
19983 2016-12-20-21:37:43 21.6

And this is from the same sensor, but cut from the indigoplotd sql file.


19922;20161219102359;22.0
19923;20161219103606;22.3
19924;20161219104814;22.7
19925;20161219110015;22.4
19926;20161219111240;22.2
19927;20161219112415;22.1
19928;20161219113627;22.0
19929;20161219114814;21.9
19930;20161219120015;21.8
19931;20161219123616;21.9
19932;20161219124816;22.0
19933;20161219133615;22.1
19934;20161219141216;22.0
19935;20161219142416;22.1
19936;20161219171222;22.2
19937;20161219172426;22.1
19938;20161219173658;22.0
19939;20161219174827;21.9
19940;20161219180027;21.8
19941;20161219184828;21.9
19942;20161219194828;22.0
19943;20161219221229;22.1
19944;20161219224842;22.2
19945;20161219231249;22.3
19946;20161219232449;22.4
19947;20161219233649;22.3
19948;20161219234849;22.4
19949;20161220000049;22.3

It seems that the adaptor has sometimes 2 entries at the same time.

In this case indigoplotd takes the last entry, not the average. I believe ... but I need to double check. When I have access to a computer.

It might be that the adapter plugin needs to look at the timing of when values get updated.


Sent from my iPhone using Tapatalk

This is to confirm: if there are 2 entries for the same value with the same date stamp indigoplotd will use the last one ( id > last one) and ignore the one before

it looks as if the adapter plugin creates these double entries once in a while:

Code: Select all

1462 2016-12-20-20:43:21 19.7
1463 2016-12-20-20:43:21 17.1


in between the "real" values.

Karl

It looks like you found the problem.
@dustysparkle: do you think the adaptor plugin can cause this?

Well, I can't imagine how it might be doing that, but if years of programming have taught me anything it's that things will fail in the most devious ways possible.

Do you by any chance have multiple adapters "attached" to the same underlying sensor? Shot in the dark.

It's strange, i agree. The previous attached figures comes from a aeotec multisensor, and it shows both humidity and temperature. There are adaptors for both.

Could you do an sql print for all the states of that sensor not just the temp. May be the states get co mingled as they arrive in indigo at the same time.


Sent from my iPhone using Tapatalk

I'm away a couple of days, so it'll be early next week. Yesterday, i did disable the humidity-adaptor, but that didn't change any for the temp-adaptor

I have 6 multisensors, each with an Adaptor-temp-device connected. I've attached the sensor values (50last) of 3+3 of the sensors ('real' value + adaptor value). They don't match in time (don't know why), and the Adaptor values look very strange (several values registered on the same date-time). I extracted the data with the 'utilities' plug in (attached).