Thanks for the reply however I’m still having problems getting this working again. As I’ve mentioned I’ve updated the dns on my router so the requests/posts all reach my pi but I can’t seem to get my pi to accept the requests and or send the expected reply. As mentioned in my first post all the received data mentions something with firmware. Almost like it’s trying to do a firmware check or something. And when trying to use the methods mentioned in the article you mentioned my Apache logs all show a 404 when trying to post to /messages/. Any help would be greatly appreciated.
On Fri, Apr 5, 2019 at 5:14 PM rich T <[email protected]> wrote: > No it is not bricked, my hub stopped reporting yesterday. > https://www.wxforum.net/index.php?topic=36552.msg375667;topicseen#msg375667 > > > On Friday, April 5, 2019 at 5:46:51 PM UTC-4, Jamie Borget wrote: >> >> I noticed yesterday morning my Pi stopped reporting, upon further >> inspection I could see that acurite updated their zone file so that >> hubapi.myacurite.com had an a-record of 127.0.0.1. Well sure I expected >> this back in March but for some reason my Pi has been working and sending >> data up until yesterday. Since I was running the weewx interceptor in >> sniff mode I figured this isn't going to work anymore. I went ahead and >> updated my DNS mapping on my router to send hubapi.myacurite.com >> requests directly to my Pi. However things still aren't working and when >> running the interceptor with the following values I'm getting data but no >> specific data from my actual 5n1 weather station. See output below: >> >> root@raspberrypi:~/weewx-interceptor-master# sudo >> PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/interceptor.py >> --device=acurite-bridge --mode=listen --port 80 --debug >> identifiers: {'bridge_id': '24C86E077FC', 'sensor_type': 'firmware', >> 'sensor_id': None} >> raw data: id=24C86E077FC&mt=firmware&line=0&count=1 >> raw packet: {'usUnits..24C86E077FC': 17, 'sensor_type..24C86E077FC': >> 'firmware', 'dateTime': 1554499979, 'dateTime..24C86E077FC': 1554499979, >> 'bridge_id..24C86E077FC': '24C86E077FC', 'usUnits': 17} >> mapped packet: {'usUnits': 17, 'dateTime': 1554499979} >> identifiers: {'bridge_id': '24C86E077FC', 'sensor_type': 'firmware', >> 'sensor_id': None} >> raw data: id=24C86E077FC&mt=firmware&line=0&count=1 >> raw packet: {'usUnits..24C86E077FC': 17, 'sensor_type..24C86E077FC': >> 'firmware', 'dateTime': 1554500022, 'dateTime..24C86E077FC': 1554500022, >> 'bridge_id..24C86E077FC': '24C86E077FC', 'usUnits': 17} >> mapped packet: {'usUnits': 17, 'dateTime': 1554500022} >> identifiers: {'bridge_id': '24C86E077FC', 'sensor_type': 'firmware', >> 'sensor_id': None} >> raw data: id=24C86E077FC&mt=firmware&line=0&count=1 >> raw packet: {'usUnits..24C86E077FC': 17, 'sensor_type..24C86E077FC': >> 'firmware', 'dateTime': 1554500066, 'dateTime..24C86E077FC': 1554500066, >> 'bridge_id..24C86E077FC': '24C86E077FC', 'usUnits': 17} >> >> I'm hoping I'm just missing something simple, and my bridge didn't >> actually get bricked by some update acurite sent out to existing users of >> the old bridge. Thanks in advance. >> >> >> >> >> -- > You received this message because you are subscribed to a topic in the > Google Groups "weewx-user" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/weewx-user/0e2E3F7EG7Y/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
