Topic: [SOLVED] Data Issue On Meteobridge after Reboot

[A1cntrler]

My Meteobridge has been running flawlessly for a couple years now on a DIR-505.  I hadn't looked at it in quite a while as everything had been running great.  I noticed on Sunday that the SW version was out of date and I'd need to pay for new updates.  No problem, as I don't mind being a supporter for something I use every day.  Here's when the problem started though.  As soon as I paid and the license was updated, my data has been strange.  I've included screenshots of my WU logs from the day prior to the upgrade to now. 

I checked the data on the Acurite servers and the data is transmitting normal through the Acurite Bridge (or whatever they're calling it now..) but when the data passes through the Meteobridge for upload to WU it has the issues.

I tried posing on the actual Meteobridge forums, but I've forgotten my password and requesting a new one, the board says it has sent me a link several times, but nothing has been received in my inbox or spam folders..

Here are the logs:

This is the log from the day prior to upgrading to the updates.  They look like this one every day for the past couple years.

 [ You are not allowed to view attachments ]

Here I did the purchase just after 12pm local time.

 [ You are not allowed to view attachments ]

I let it run to see if it would settle down

 [ You are not allowed to view attachments ]

And today it's still wonky.

 [ You are not allowed to view attachments ]


Platform:   DIR-505   (no USB hub)
RAM:   61556 kB total, 24184 kB free (60% used)
SW Version:   Meteobridge 3.2 (May 29 2017, build 11222), FW 1.3
Uptime:   2 days, 1 hours, 29 minutes    Buffer: 0 items (0%)

[Mattk]

Just for the record there was no need to pay for future license updates for the version (3.2 May 29, 2017) that you updated to, however anything from 3.3 on you are now covered for the next 2 years.

My take on software updates is if it's not broken then don't fix it. I am still running some MB's with 2.5, which still do exactly what I require. Maybe your software version was not up to date (as in current version) but not necessarily out of date as it was apparently doing everything you required it to do. New updates can induce other issues that are totally un-associated to what the actual changes/release were all about or meant to fix.       

[A1cntrler]

Just for the record there was no need to pay for future license updates for the version (3.2 May 29, 2017) that you updated to, however anything from 3.3 on you are now covered for the next 2 years.

My take on software updates is if it's not broken then don't fix it. I am still running some MB's with 2.5, which still do exactly what I require. Maybe your software version was not up to date (as in current version) but not necessarily out of date as it was apparently doing everything you required it to do. New updates can induce other issues that are totally un-associated to what the actual changes/release were all about or meant to fix.     

My System page had a red header on it saying updates were expired (or something to that effect) and I'd need to subscribe for updates.  When I bought the license I had assumed it was a forever license including updates.  While it may have continued to work, if Acurite had changed something on their end in the Smarthub that no longer let it communicate with the MB, I'd probably have to subscribe anyways to make it work again if the fix was in a update.

If I recall the last firmware that was on it was dated February or March?  When I started the new "subscription" it gave the May 29th one.  Maybe I should try rolling it back to see if that corrects it.  Could just be in the 29th update not playing well with the Acurite stuff...

[A1cntrler]

So I looked at the other data I'm reporting to other sites, not just WU.

I checked for today, June 6th from the time period of 2:15am to 2:45am. 

At this time WU showed I reported going from 66 degrees (F) to 61 degrees a few minutes later.

NOAA had this data from my station:

06 Jun 2:46 am   61   56   83   NNW   1        29.19   1013.0   29.92   0.00   0.00
06 Jun 2:36 am   61   56   83      CALM       29.19   1013.0   29.92   0.00   0.00
06 Jun 2:30 am   61   56   83      CALM       29.19   1013.0   29.92   0.00   0.00
06 Jun 2:25 am   61   56   85      CALM       29.19   1013.0   29.92   0.00   0.00
06 Jun 2:20 am   61   56   85      CALM       29.19   1013.0   29.92   0.00   0.00
06 Jun 2:15 am   61   56   85      CALM       29.19   1013.0   29.92   0.00   0.00

I also upload to PWS.  Here is that data:

02:45 AM   61.3°F   56.1°F   83%   0.7 mph NNW   2.0 mph   29.91 in   0.00 in   0.00 in   0.00 in
02:44 AM   61.3°F   56.1°F   83%   0.4 mph WNW   2.0 mph   29.91 in   0.00 in   0.00 in   0.00 in
02:43 AM   61.3°F   56.1°F   83%   0.4 mph NNW   2.0 mph   29.91 in   0.00 in   0.00 in   0.00 in
02:42 AM   61.3°F   56.1°F   83%   0.2 mph NW   0.9 mph   29.91 in   0.00 in   0.00 in   0.00 in
02:41 AM   61.5°F   56.3°F   83%   Calm   0.9 mph   29.91 in   0.00 in   0.00 in   0.00 in
02:40 AM   61.5°F   56.3°F   83%   Calm   -   29.91 in   0.00 in   0.00 in   0.00 in
02:39 AM   61.5°F   56.3°F   83%   Calm   -   29.91 in   0.00 in   0.00 in   0.00 in
02:38 AM   61.5°F   56.3°F   83%   Calm   -   29.91 in   0.00 in   0.00 in   0.00 in
02:37 AM   61.5°F   56.3°F   83%   Calm   -   29.91 in   0.00 in   0.00 in   0.00 in
02:35 AM   61.3°F   56.1°F   83%   0.4 mph SSW   -   29.91 in   0.00 in   0.00 in   0.00 in
02:34 AM   61.3°F   56.1°F   83%   0.7 mph SSE   -   29.91 in   0.00 in   0.00 in   0.00 in
02:33 AM   61.3°F   56.1°F   83%   0.7 mph SW   -   29.91 in   0.00 in   0.00 in   0.00 in
02:32 AM   61.3°F   56.1°F   83%   0.7 mph NNW   0.9 mph   29.91 in   0.00 in   0.00 in   0.00 in
02:31 AM   61.3°F   56.1°F   83%   0.4 mph S   2.0 mph   29.91 in   0.00 in   0.00 in   0.00 in
02:30 AM   61.3°F   56.1°F   83%   0.2 mph SSW   0.9 mph   29.91 in   0.00 in   0.00 in   0.00 in
02:29 AM   61.3°F   56.1°F   83%   0.2 mph S   -   29.91 in   0.00 in   0.00 in   0.00 in
02:28 AM   61.3°F   56.1°F   83%   0.2 mph S   -   29.91 in   0.00 in   0.00 in   0.00 in
02:27 AM   61.2°F   55.9°F   83%   0.2 mph S   -   29.91 in   0.00 in   0.00 in   0.00 in
02:26 AM   61.2°F   56.7°F   85%   0.2 mph S   0.9 mph   29.91 in   0.00 in   0.00 in   0.00 in
02:25 AM   61.2°F   56.7°F   85%   Calm   0.9 mph   29.91 in   0.00 in   0.00 in   0.00 in
02:23 AM   61.2°F   56.7°F   85%   Calm   -   29.91 in   0.00 in   0.00 in   0.00 in
02:22 AM   61.2°F   56.7°F   85%   Calm   -   29.91 in   0.00 in   0.00 in   0.00 in
02:21 AM   61.2°F   56.7°F   85%   Calm   -   29.91 in   0.00 in   0.00 in   0.00 in
02:20 AM   61.2°F   56.7°F   85%   Calm   -   29.91 in   0.00 in   0.00 in   0.00 in
02:19 AM   61.2°F   56.7°F   85%   Calm   0.9 mph   29.91 in   0.00 in   0.00 in   0.00 in
02:18 AM   61.2°F   56.7°F   85%   Calm   0.9 mph   29.91 in   0.00 in   0.00 in   0.00 in
02:17 AM   61.2°F   56.7°F   85%   Calm   -   29.91 in   0.00 in   0.00 in   0.00 in
02:16 AM   61.2°F   56.7°F   85%   0.2 mph ENE   -   29.91 in   0.00 in   0.00 in   0.00 in




So it looks like maybe I can just chalk it up to some way that WU is seeing the data?  I checked other local stations and also 2 other stations I have set up across the country (One in AZ and one in VA at family members homes) and the WU data appeared normal.  One uses the Acurite SmartHub to send data to WU and the other in an Ambient station that uploads it to WU directly.  So not sure if it was a problem on the WU end or not since it only affected mine.

[A1cntrler]

Rolled back to version 3.1 and still getting erroneous data on WU.  Scrolled back through my history a month and all data looks good up until I renewed the license.  Not a clue what changed other than that...

[docbee]

Nothing to the Acurite code has changed in the last months, so no SW update problems are involved here. Your self-investigation also turned out that older version 3.1 does behave the same.

The purchase process does initiate a reboot and I think the problem is located to this. To get data from the Acurite bridge it needs to channel data through the Meteobridge. Rebooting the Meteobridge will interrupt the Internet connectivity of the Aculink bridge and it will need to request a new IP through Meteobridge, something where a lot can go wrong. Once you reboot the Meteobridge, doing a power cycle of the Acurite bridge should solve this.

Are you fine when I change your Subject to "Data Issue On Meteobridge after Reboot", which is much more factual?

[A1cntrler]

Nothing to the Acurite code has changed in the last months, so no SW update problems are involved here. Your self-investigation also turned out that older version 3.1 does behave the same.

The purchase process does initiate a reboot and I think the problem is located to this. To get data from the Acurite bridge it needs to channel data through the Meteobridge. Rebooting the Meteobridge will interrupt the Internet connectivity of the Aculink bridge and it will need to request a new IP through Meteobridge, something where a lot can go wrong. Once you reboot the Meteobridge, doing a power cycle of the Acurite bridge should solve this.

Are you fine when I change your Subject to "Data Issue On Meteobridge after Reboot", which is much more factual?

Thank you for the input.  I've changed the title of the post as requested.

Also I seem to have solved the issue.  I had also sent a message to Weather Underground asking about the issue and sending the data to them in my message about it sending correct to other sites and not WU.

It took a few days but I did get a reply and they told me that the problems seemed to be coming from switching between SmartThings upload and Meteobridge upload.  I was perplexed by this as I hadn't changed anything in the configuration of my Samsung SmartThings in quite a while.  I had a module on there to pull the data from my PWS for display in the app on my phone.  It had somehow started pulling in data from my smart thermostat (inside my house) and sending that temperature and humidity to my WU page.  This also is why the pressure, wind and rainfall were missing from the graphs during the times of the temperature spikes.  It's possible it was always trying to send this data to WU but Meteobridge just always overrode it, but when it was down for the reboot it started pulling that data and then they were playing tug-of-war.

I deleted all interaction between SmartThings Hub and WU and from that moment on it has been smooth sailing. 

So it was never an issue on your end or WU end, but I guess something in SmartThings triggered during a moment of weakness and refused to let go...

I can either leave to post for reference for others, or delete it.  Let em know what you'd like to do with it.