Topic: Meteobridge temperature

[arrowspace90]

I moved my Pro upstairs so that it sits right under the roof where the station is mounted.

I was going to begin to reconfigure it wireless mode so I could resume reporting with it, but noticed that it is displaying data from my station when plugged into power.  OK, that's good, right? 

But, it is not in perfect agreement with my Davis console downstairs on my desk that is likewise receiving station data.  For example, my console says the pressure is 29.90 inches.  The Pro says its 29.86.

What could cause the discrepancy?  I am hesitant to hook it up to the internet when the 2 do not agree.

[galfert]

Well you moved the Meteobridge Pro up to a different level. You have to calibrate the barometer for the elevation of the second floor. You can't just move the Meteobridge Pro without adjusting for its new higher elevation.

[arrowspace90]

I didn't know that.

Doesn't it just read what the actual station is reporting?

[galfert]

The VP2 outdoor ISS module does not contain a barometric sensor and therefore does not send that information. The barometric sensor is contained in the Meteobridge Pro and you have another barometric sensor in the display console. They each report what each one of those is measuring.

The discrepancy you are noticing of 0.04 inHg difference corresponds to about somewhere around 30 feet difference between the 1st and 2nd floor. There is rounding so the difference may really be less than 0.04 inHg as it may be just 0.035 inHg.  So the discrepancy you are noticing makes sense.

Also I recommend switching to hpa to calibrate. Change both the console and the Meteobridge Pro to use hpa. Calibrate using hpa and then switch back to inHg and you'll get better results.

[arrowspace90]

I can't believe I didn't realize that. 

Obviously, I should watch a youtube video or something.  I have had a Vue and then the Pro for some years!  I use the Vue console.

[arrowspace90]

Nothing with Meteobridge comes easily for me.

I am struggling to set up my Pro in WiFi instead of LAN.  I used "these" instructions..

REBOOT WIFI AP reboots Meteobridge PRO as a WiFi access point. When the reboot is done Meteobridge PRO will show the SSID on the display and will ask you to connect with your mobile device to this WLAN and to browse to 192.168.1.1 where you will find the network configuration page of Meteobridge pro. Being there you can do needed network settings of your Meteobridge PRO to have it operational. „WiFi access point“ setting is just a temporary measure to allow you to reach network configuration without having the Meteobridge PRO connected to a wired LAN.

I pushed the button and selected the Wifi.  I connected my phone to the Pro access point.  But now what?  I tried to browse to the router ID and then to the IP address shown by the wifi access point, but I go nowhere.  Am I supposed to see the blue Meteobridge set up pages?  What step am I not doing?

[galfert]

Sounds like you are almost there.

Yes the phone should be able to see the Meteobridge configuration pages by using the phones browser and going to 192.168.1.1. That is after the phone has connected to the Meteobridge temporary wireless SSID. You phine seems to have connected as it shows unsecured connection established. So the next step is to open the phone's browser to 192.168.1.1 for the Meteobridge setup.

There is another way of doing it. You could do the setup as above but with a laptop. May be easier than a phone. I also recommend first telling the phone to forget your real WiFi SSID as the phine may decide to switch back the the home WiFi network and not stay connected to the temporary Meteobridge WiFi. Do the set and tell the computer to forget (or to not connect automatically) to the home WiFi. After setting everything up then you can tell your phone or laptop to again remember or automatically connect to the home WiFi network.

And there is a third way.... Connect the Meteobridge back to Ethernet as you had it before on your network. Then use your computer to configure the Meteobridge to the WiFi network (yes while it is still connected to Ethernet). This is the setup procedure for the standard Meteobridge that has no display. Then unplug the Ethernet and move the Meteobridge upstairs. It will connect to WiFi automatically as that was saved while on Ethernet. This is probably the easiest option.

[arrowspace90]

Thank you again, that's what I did.  Something didn't work correctly.  I think it's a good idea to try it with the laptop, and failing that attempt, I will go back to ethernet downstairs and configure it there for wireless.

When I had the Pro connected to ethernet previously, it showed signals no worse than 70db, which while "not great" seemed to work fine for a year.  It's a shame I had to mess with something that had been working.

[arrowspace90]

The laptop worked on the first try!  So, some progress.

However I only have the tab for the network page.  I only hit "Save", not "Save and reboot".
Do I need to manually fill in the IP address, etc?  Or should it have done that?

[galfert]

Looks good. Save button is all you need. No need to enter in static IP. You can now power off, take it upstairs and it should connect to Wifi. That is if that WiFi SSID is a good signal upstairs. I see the SSID ends in EXT which leads me to believe that you are using WiFi extenders. I'm not a fan of WiFi extenders. But if it works then fine.

When you power it on upstairs you need to find out what IP address the router assigns to it because it won't stay as 192.168.1.1. You can probably find what IP it gets through the LCD (I think...remember I only have a regular Meteobridge). Or you can find out what IP it gets by logging into your router and checking the DHCP lease table (cross reference by matching MAC address printed on Meteobridge).

UPDATE Wait I just remembered. You don't need to find the IP address. There is a special URL that finds it. Just use this in your browser:
magicip.meteobridge.com
That will redirect you automatically to the IP it gets. Then write it down for next time.

[arrowspace90]

I have to use extenders upstairs because the router (a new one) has weak coverage.  Another reason I didn't want to move the Pro away from Ethernet.  We have Frontier Internet, and they make sure you cannot use a powerful 3rd party router on their network.

I am still missing a step somehow.  When I go back to the WiFi network in the house, the Pro is not accessable from the laptop and it doesn't show on the router network (It shows the old ethernet connection).  So something isn't set up right.  The Pro shows the iP address on the front, same one it had as ethernet connected.  When i type it in, the address is not reachable. 

[Mattk]

I have to use extenders upstairs because the router (a new one) has weak coverage.  Another reason I didn't want to move the Pro away from Ethernet.  We have Frontier Internet, and they make sure you cannot use a powerful 3rd party router on their network.

Nobody can stop you connecting a third party AP beyond any router

[arrowspace90]

I have to express my gratitude and thanks to Mr. "Galfert" for his great help and amazing networking expertise in helping a non IT person like me reconfigure my Meteobridge Pro to wireless in a new location.  Without him, I don't know, it would have at best taken me days or longer to figure out what to do.
The menus and settings on Meteobridge are numerous and challenging enough that even he had to think about them for seconds at a time.
He also discovered weaknesses in my clunky home network that should be fixed.  I am now going to address those.
I hope not too many people call him for help because then I can't monopolize his expertise.
If you have a network and need to hire someone to manage it, he is the man.
Now that I have moved my Pro closer to the wireless station, I will closely monitor it's temp reports to ensure I have no more sudden, high spikes over 100 degrees.  If I do, then I know it's not my station and not a situation where I have multiple inputs to WU, and not a lack of signal to my Pro box.

[galfert]

No problem. You are welcome! I'm an IT network guy so it was a fun challenge to figure out the nuances of your network and get more acquainted with the Meteobridge Pro as I just have a regular Meteobridge. Now I want a Pro.

As Mattk said, nobody can stop you from connecting your own router/WiFi access point, and I'm glad to have helped you get rid of those WiFi extenders, to gain wireless performance and range, and getting a better firewall/router instead of the junk that all cable companies hand out.

[arrowspace90]

Temperature spike retuned quickly.  Fault in Pro box.

[Mattk]

Temperature spike retuned quickly.  Fault in Pro box.

?? I would have some reservation about that, it may, it might, it could but for some reason I believe there are some other factors involved with this????

[galfert]

I think the Meteobridge Pro is broken. There are some very wrong and strange packets being received by CWOP. The latitude and longitude should be static and not be something that changes in the Meteobridge Pro. Your latitude/longitude are showing strange numbers. Every time this occurs the Meteobridge Pro is also changing its software version to eMP50 instead of the correct eMB38, this is another parameter than should not be changing in the Meteobridge Pro.

My recommendation is to do a factory reset of the Meteobridge Pro. Then see how it performs after a factory reset. You'll have to fully reconfigure everything. You may want to make sure you have all your settings copied down on paper.

We know that a different software/device is not sending these bad packets because we turned the Meteobridge Pro off for some time and waited for a moment of silence (gap) in the CWOP data. Then we turned it on.

Here is the the strange CWOP data that I'm seeing:

DW8828>APRS,TCPXX*,qAX,CWOP-4:@012231z3305.53N/09703.86W_018/001g011t061r000p000P000b10132h49eMB38
Dw8828>APRS,TCPXX*,qAX,CWOP-3:@012232z-1-1.-2N/-01-1.-2E_000/001g010t101r000p000P000b09925h24eMP50
DW8828>APRS,TCPXX*,qAX,CWOP-7:@012236z3305.53N/09703.86W_018/001g011t061r000p000P000b10132h49eMB38
DW8828>APRS,TCPXX*,qAX,CWOP-1:@012241z3305.53N/09703.86W_039/002g009t061r000p000P000b10133h48eMB38
Dw8828>APRS,TCPXX*,qAX,CWOP-7:@012242z-1-1.-2N/-01-1.-2E_000/002g011t101r000p000P000b09928h24eMP50
DW8828>APRS,TCPXX*,qAX,CWOP-4:@012246z3305.53N/09703.86W_000/002g009t060r000p000P000b10133h49eMB38
DW8828>APRS,TCPXX*,qAX,CWOP-7:@012251z3305.53N/09703.86W_000/002g009t060r000p000P000b10134h49eMB38
Dw8828>APRS,TCPXX*,qAX,CWOP-3:@012253z-1-1.-2N/-01-1.-2E_000/001g009t101r000p000P000b09929h25eMP50
DW8828>APRS,TCPXX*,qAX,CWOP-3:@012256z3305.53N/09703.86W_000/000g009t060r000p000P000b10134h49eMB38
DW8828>APRS,TCPXX*,qAX,CWOP-6:@012301z3305.53N/09703.86W_000/000g003t060r000p000P000b10136h50eMB38
DW8828>APRS,TCPXX*,qAX,CWOP-4:@012306z3305.53N/09703.86W_039/000g003t060r000p000P000b10137h51eMB38
DW8828>APRS,TCPXX*,qAX,CWOP-7:@012311z3305.53N/09703.86W_021/001g004t060r000p000P000b10136h50eMB38
Dw8828>APRS,TCPXX*,qAX,CWOP-5:@012314z-1-1.-2N/-01-1.-2E_000/000g003t101r000p000P000b09931h25eMP50
DW8828>APRS,TCPXX*,qAX,CWOP-3:@012316z3305.53N/09703.86W_008/000g004t060r000p000P000b10138h51eMB38
DW8828>APRS,TCPXX*,qAX,CWOP-1:@012321z3305.53N/09703.86W_011/000g003t059r000p000P000b10137h52eMB38
Dw8828>APRS,TCPXX*,qAX,CWOP-5:@012324z-1-1.-2N/-01-1.-2E_023/000g004t101r000p000P000b09933h25eMP50
DW8828>APRS,TCPXX*,qAX,CWOP-5:@012326z3305.53N/09703.86W_017/000g005t059r000p000P000b10138h52eMB38
DW8828>APRS,TCPXX*,qAX,CWOP-7:@012331z3305.53N/09703.86W_000/000g002t059r000p000P000b10139h53eMB38

[arrowspace90]

Temperature spike retuned quickly.  Fault in Pro box.

?? I would have some reservation about that, it may, it might, it could but for some reason I believe there are some other factors involved with this????

I have not considered myself an expert and have only been attempting to do reasonable things to test where the problem lies.
It's not my station; when the station was only connected to VWS software, the spikes stopped.
It's not from trying to report to WU from more than one source.  That was tested and was not the case.
It's not from a weak signal to the Meteobridge Pro; that was tested by moving the Pro higher and closer to the station and the signal was measuring in the -50db range.
So I agree reluctantly that a full reset is the next thing to try.  That will have to wait till tomorrow.

[galfert]

I do have some other thoughts....

Since now Virtual Weather Station is running via the console USB logger, are you seeing the spikes in Virtual Weather Station also? Virtual Weather Station is running but reporting is turned off, so it now serves as a control to see if the ISS is sending bad data. Virtual Weather Station is only doing local data logging and shouldn't affect the Meteobridge Pro. The Meteobridge Pro gets data over RF directly from the ISS. As my thinking here is that if the ISS is sending bad data it could cause an unexpected software glitch in the Meteobridge Pro.

On the other hand if the data looks good on Virtual Weather Station then definitely the problem is with the Meteobridge Pro.

[arrowspace90]

I had checked that previously and again just now.

There are no spikes on VWS.  There have been none.  So I was already confident that the Davis ISS was not the issue.

The temp data reported by the Pro has already spiked again twice since midnight.  There's no doubt in my mind that, for whatever reason, the Pro box is malfunctioning.

I will revert again to VWS reporting of my station data, while I prepare for a full reset of my Pro Box. 

[galfert]

Before you reset it reach out to Boris. He has the ability to remote into the Meteobridge Pro. He may be able to look at internal logs or do other troubleshooting. All he needs is your Meteobridge Pro MAC address and he remotes in I think. Along with ensuring that under the Meteobridge Pro system tab the checkbox to, "allow remote access" is turned on. I've read other posts where he has done that.

Your Meteobridge Pro is definitely acting up also because I noticed the CWOP uploads are occurring more frequently than every 5 minutes. It's all those strange ones that don't fall in line with the normal 5 minute increment.

Boris may use this opportunity to perhaps improve the Meteobridge to have some sort of internal diagnostic to alert the user that it needs a factory reset or to indicate that the unit is damaged.

[arrowspace90]

When the MB PRO picks up tons of RF noise there might be a false packet here and there that has a valid CRC by accident.
What is your average sensor signal strength (live data tab tells, might be in the between 60 and 70)?
What is the percentage of fine packets (indoor sensor tells a percentage)?
what is the RF threshold you defined on "station" tab?

Having that data one can optimize your reception and by doing so make the occurrence of false reading much less probable.

Mr Docbee, I have done this and was now getting sensor signal strength in the -60db range.  If there is some way to receive more help in dealing with this issue of spiking temps, ( I believe that I have, with some pretty good help, tested other possibilities short of a factory reset), please advise me?  I would like to do whatever is necessary to get this resolved.