Yes, okay now (two top records). It gave me also the opportunity to iron 
out a bug in my own weewx-service. Hadnt caught the situation that rain 
might be NULL :)

mysql> select datetime,from_unixtime(datetime),outtemp,extratemp1,rain,ET 
from archive order by datetime desc limit 10;
+------------+-------------------------+--------------------+--------------------+------+-----------------------+
| datetime   | from_unixtime(datetime) | outtemp            | 
extratemp1         | rain | ET                    |
+------------+-------------------------+--------------------+--------------------+------+-----------------------+
| 1593711420 | 2020-07-02 19:37:00     | 18.916666666666664 |  
19.47222222222222 |    0 |  0.003361470627628734 |
| 1593711360 | 2020-07-02 19:36:00     |  18.88888888888889 | 
19.388888888888893 |    0 | 0.0034129711072366695 |
| 1593711060 | 2020-07-02 19:31:00     |  18.77777777777778 | 
19.055555555555557 | NULL |  0.003440203244074394 |
| 1593711000 | 2020-07-02 19:30:00     |  18.77777777777778 | 
18.930555555555554 | NULL | 0.0034680891688093356 |
| 1593710940 | 2020-07-02 19:29:00     |  18.72222222222222 |  
18.88888888888889 | NULL |                  NULL |
| 1593695820 | 2020-07-02 15:17:00     |  19.61111111111111 | 
20.370370370370367 | NULL | 0.0031779497530594037 |
| 1593695760 | 2020-07-02 15:16:00     |  19.61111111111111 | 
20.444444444444443 | NULL |  0.003190712625375343 |
| 1593695700 | 2020-07-02 15:15:00     | 19.555555555555557 | 
20.444444444444443 | NULL |  0.003232360174501971 |
| 1593695640 | 2020-07-02 15:14:00     | 19.555555555555557 | 
20.444444444444443 | NULL | 0.0032646454867943896 |
| 1593695580 | 2020-07-02 15:13:00     | 19.555555555555557 | 
20.444444444444443 | NULL |  0.003283176153447136 |
+------------+-------------------------+--------------------+--------------------+------+-----------------------+
10 rows in set (0.00 sec)


Op donderdag 2 juli 2020 15:06:20 UTC+2 schreef Bastiaan Meelberg:
>
> Sorry about that. I was surprised as well. I accidentally comment out the 
> rain to get in the Loop, during debugging.
>
> It should be good in the current master build:
>
> https://github.com/grebleem/weewx-weatherlinkliveudp/archive/master.zip
>
>
> I'm also working on a weatherlink import, at this moment the program will 
> produce a .cvs and wee_import can import this file. Keep you posted!
>
>
> On Thursday, July 2, 2020 at 2:50:13 PM UTC+2, Maarten van der Hoeven 
> wrote:
>>
>> A question. Is 'rain' still work in progress? I notice a repeating 
>> NULL-value (no worries, testing against a test-database within a virtual 
>> machine. fully seperated from my 'production'-site)
>>
>> mysql> select datetime,from_unixtime(datetime),outtemp,extratemp1,rain,ET 
>> from archive order by datetime desc limit 10;
>>
>> +------------+-------------------------+--------------------+--------------------+------+-----------------------+
>> | datetime   | from_unixtime(datetime) | outtemp            | 
>> extratemp1         | rain | ET                    |
>>
>> +------------+-------------------------+--------------------+--------------------+------+-----------------------+
>> | 1593693840 | 2020-07-02 14:44:00     |                 20 |  
>> 21.64814814814815 | NULL |  0.004293896657547285 |
>> | 1593693780 | 2020-07-02 14:43:00     |                 20 | 
>> 21.833333333333332 | NULL |  0.004304368552713827 |
>> | 1593693720 | 2020-07-02 14:42:00     |                 20 | 
>> 21.833333333333332 | NULL |  0.004311294113859122 |
>> | 1593693660 | 2020-07-02 14:41:00     |                 20 | 
>> 21.833333333333332 | NULL |  0.004316451537816886 |
>> | 1593693600 | 2020-07-02 14:40:00     | 20.041666666666664 | 
>> 21.930555555555554 | NULL |  0.004321999760490444 |
>> | 1593693540 | 2020-07-02 14:39:00     | 20.055555555555554 | 
>> 22.074074074074073 | NULL |  0.004325689825000265 |
>> | 1593693480 | 2020-07-02 14:38:00     | 20.083333333333332 | 
>> 22.166666666666664 | NULL |  0.004326424995698886 |
>> | 1593693300 | 2020-07-02 14:35:00     |  20.09259259259259 | 
>> 22.277777777777775 | NULL | 0.0042999357683097044 |
>> | 1593693240 | 2020-07-02 14:34:00     |  20.11111111111111 |   
>> 22.2037037037037 | NULL |   0.00429406704665147 |
>> | 1593693180 | 2020-07-02 14:33:00     |  20.12962962962963 |  
>> 22.11111111111111 | NULL |  0.004320916570420523 |
>>
>> +------------+-------------------------+--------------------+--------------------+------+-----------------------+
>> 10 rows in set (0.01 sec)
>>
>>
>> Op donderdag 2 juli 2020 om 13:44:43 UTC+2 schreef Maarten van der Hoeven:
>>
>>> Yes, that makes a difference! Also showing okay on the website!
>>>
>>> mysql> select 
>>> datetime,from_unixtime(datetime),outtemp,extratemp1,extratemp2,extratemp3 
>>> from archive order by datetime desc limit 10;
>>>
>>> +------------+-------------------------+--------------------+--------------------+------------+------------+
>>>
>>> | datetime   | from_unixtime(datetime) | outtemp            | 
>>> extratemp1         | extratemp2 | extratemp3 |
>>>
>>> +------------+-------------------------+--------------------+--------------------+------------+------------+
>>> | 1593690180 | 2020-07-02 13:43:00     | 19.444444444444443 |  
>>> 20.24074074074074 |       NULL |       NULL |
>>> | 1593690120 | 2020-07-02 13:42:00     | 19.388888888888893 |  
>>> 20.12962962962963 |       NULL |       NULL |
>>> | 1593690060 | 2020-07-02 13:41:00     |  19.34722222222222 | 
>>> 19.916666666666668 |       NULL |       NULL |
>>> | 1593690000 | 2020-07-02 13:40:00     | 19.333333333333332 | 
>>> 19.833333333333332 |       NULL |       NULL |
>>> | 1593689940 | 2020-07-02 13:39:00     | 19.333333333333332 | 
>>> 19.740740740740737 |       NULL |       NULL |
>>> | 1593689820 | 2020-07-02 13:37:00     | 19.333333333333332 
>>> |               NULL |       NULL |       NULL |
>>> | 1593689760 | 2020-07-02 13:36:00     | 19.333333333333332 
>>> |               NULL |       NULL |       NULL |
>>> | 1593689700 | 2020-07-02 13:35:00     | 19.333333333333332 
>>> |               NULL |       NULL |       NULL |
>>> | 1593676680 | 2020-07-02 09:58:00     |  16.72222222222222 
>>> |               NULL |       NULL |       NULL |
>>> | 1593676620 | 2020-07-02 09:57:00     |  16.72222222222222 
>>> |               NULL |       NULL |       NULL |
>>>
>>> +------------+-------------------------+--------------------+--------------------+------------+------------+
>>>
>>> 10 rows in set (0.00 sec)
>>>
>>>
>>>
>>> Op donderdag 2 juli 2020 om 12:10:15 UTC+2 schreef Bastiaan Meelberg:
>>>
>>>> Very helpful! 
>>>> Just found out that the extra_id from the .conf file is a str type. 
>>>> Comparing this to an int will never match. 
>>>> Try this build please:
>>>> https://github.com/grebleem/weewx-weatherlinkliveudp/archive/Debug1.zip
>>>>
>>>>
>>>> On Thursday, July 2, 2020 at 9:57:25 AM UTC+2, Maarten van der Hoeven 
>>>> wrote:
>>>>>
>>>>> No data in whatever extratemp. I got the external sensor on channel id 
>>>>> = 3 (hence extra_id=3), but I suspect the data comes into extratemp1. I d 
>>>>> not have any preference on that. Mysql-output, and three json files of 
>>>>> current conditions
>>>>>
>>>>>
>>>>>>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/d0a12fc0-a9c0-4276-8716-6c62ba61e0e4o%40googlegroups.com.

Reply via email to