Alright. I started again from scratch, with a brand new weex.conf. This time I managed to get this working correctly with the dummy data service (not sure what was wrong before though). But as soon as I configured the real data service, I again ran into the same problem.
After some investigation and testing, I came up with the following hypothesis to explain the problem, but since I don't know how the StdArchive is working, I am not sure if this really makes sense: I have 2 stations configured: the Vantage one, which is my main station. I also have a WS3000 with 8 temperature sensors, and I am adding the data coming from the WS3000 to the records from the Vantage station. This is all working fine (except for the augmentation done by StdArchive of course). But the sequence of event is the following: 1. The Vantage is producing LOOP packets as expected (containing consBatteryVoltage). 2. When a record is generated, my data service is invoked. 3. The data service pulls the information from the WS3000 station, and adds it to the record. 4. Then StdArchive if supposed to augment the record as usual. The packet from the WS3000 station has a slightly different timestamp than the record from the Vantage. And when merging the data, I was simply looping all the keys from the WS3000 packet, and was overwritting the dateTime value from the Vantage. If I skip the dateTime key when doing the merge, everything is then working fine and the StdArchive is able to augment the record with the consBatteryVoltage and all the other values. So, it looks like the dateTime value from the record is critical for the augmentation to work. In any case, thanks a lot for your help in resolving this! -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/weewx-user/4206dd70-1307-4c70-804c-0522db7a80fen%40googlegroups.com.
