I have connected the D-Link DIR-505 running the lastest version of MeteoBridge to the LAN with a static IP. The Ambient Observer-IP also has a static IP. MeteoBridge sees the IP address of the Observer IP, but it does not see the data. The logger shows: Seems to be trying to connect via USB.
logger (17.03.2015 08:34:04): connect station 0 (Observer-IP via USB HID).
logger (17.03.2015 08:34:04): unexpected 0 bytes.
logger (17.03.2015 08:34:04): disconnect station 0 (Observer-IP): response without data
logger (17.03.2015 08:34:34): connect station 0 (Observer-IP via USB HID).
logger (17.03.2015 08:34:34): unexpected 0 bytes.
logger (17.03.2015 08:34:34): disconnect station 0 (Observer-IP): response without data
Thanks,
Chuck
D-Link DIR-505 sees Observer-IP but no Data **solved**
Moderator: Mattk
- prestwickwx
- Platinum Boarder
- Posts: 510
- Joined: Sat Aug 23, 2014 3:28 pm
- Location: Myrtle Beach, SC USA
- Contact:
Re: D-Link DIR-505 sees Observer-IP but no Data
as written per PM, easiest way would be to have me login and check what fails with your rig.
- prestwickwx
- Platinum Boarder
- Posts: 510
- Joined: Sat Aug 23, 2014 3:28 pm
- Location: Myrtle Beach, SC USA
- Contact:
Re: D-Link DIR-505 sees Observer-IP but no Data
Thanks. I sent you an email with more information.
Re: D-Link DIR-505 sees Observer-IP but no Data
Doing some inspections on the impacted system I discovered that there is a station specific bug in the data extraction code for D-Link and Asus Meteobridges. This is fixed with just uploaded update. Therefore, a reboot should fix the issue.
- prestwickwx
- Platinum Boarder
- Posts: 510
- Joined: Sat Aug 23, 2014 3:28 pm
- Location: Myrtle Beach, SC USA
- Contact:
Re: D-Link DIR-505 sees Observer-IP but no Data **solved**
Was working fine until a reboot. It picked up the March 18 update and now does not see the live data.
- prestwickwx
- Platinum Boarder
- Posts: 510
- Joined: Sat Aug 23, 2014 3:28 pm
- Location: Myrtle Beach, SC USA
- Contact:
Re: D-Link DIR-505 sees Observer-IP but no Data **solved**
The latest update fixed the problem. Thanks.