Page 2 of 2

Re: GW1000 connectivity issues **closed**

Posted: Sat Aug 10, 2019 4:13 am
by xannor
why would it connect and then drop if it could not resolve the ip. false issue. I have used the IP as well and I still had the issue, that is in fact the first thing I tried.

Code: Select all

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 BARRIER BREAKER (Bleeding Edge, r34065)
  * 1/2 oz Galliano         Pour all ingredients into
  * 4 oz cold Coffee        an irish coffee mug filled
  * 1 1/2 oz Dark Rum       with crushed ice. Stir.
  * 2 tsp. Creme de Cacao
root@MeteoBridge:~# ping gw1000
PING gw1000 ( 56 data bytes
64 bytes from seq=0 ttl=255 time=155.404 ms
64 bytes from seq=1 ttl=255 time=77.009 ms
--- gw1000 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 77.009/116.206/155.404 ms

Re: GW1000 connectivity issues **closed**

Posted: Sat Aug 10, 2019 4:27 am
by xannor
And to humor you, used IP, no dice, same issue, try again.

Re: GW1000 connectivity issues **not resolved**

Posted: Sat Aug 10, 2019 11:57 am
by admin
I had a second look as providing the IP does not fix the issue and I discovered that this GW1000 is returning an unexpected record type 0x51. This is not part of the docs I have been provided and Meteobridge quits reading data when bumping into the unknown. I changed behavior to the more clever option to stop reading data from this chunk but to make use of the so far received record types. In parallel I reached out to FineOffset to get an understanding what this record type stands for. I guess it is about a newly introduced air quality sensor... but just guessing.

Just release update should handle this fine. Sorry, for being too sure that the problem is not in my code ;-)

@xannor: I changed topic top closed again, as your meteobridge is now receiving data.

Re: GW1000 connectivity issues **resolved**

Posted: Sat Aug 10, 2019 2:52 pm
by xannor
Thank you for looking into it, since it is an unknown/unusual situation, and not one that many others seem to have, I will leave the password as I mailed you, for a time. If you need to research or test this unknown sensor feel free to test with mine. If you feel this issue is done and final I will go ahead and change my password.

Thank you again for the quick resolution.

Re: GW1000 connectivity issues **resolved**

Posted: Sat Aug 10, 2019 3:19 pm
by xannor
Also, I do own ecowitts air quality sensor, and have since I had the GW1000, so maybe they did update when this issue presented its self to add that sensor to the API you use, or maybe they expanded/changed it. I have a history of Air PM so it is something that was seen in the past, and interestingly enough not seen now. The sensors the GW1000 should be providing are ID:57 - my ambient weather WS1900, ID:58 - my AQ sensor, ID:b6 and outdoor T&H and ID:99 another outdoor T&H, and whetever ID it uses for its internal T&H (This is from the info that ws live shows me)

Re: GW1000 connectivity issues **resolved**

Posted: Sat Aug 10, 2019 4:36 pm
by admin
I got some more details on the new record types and added support for up to 4 air quality sensors of the GW1000.

Re: GW1000 connectivity issues **solved**

Posted: Sat Aug 10, 2019 6:34 pm
by xannor
Now that you mention it, i did notice that my AQ sensor moved to slot #2 in ws view,though nothing is on #1 so I don't know why it did that. Well at least the issue is solved. Thanks again.