I modified two lines in wxMesh.py and it works fine with Python 3.
changed
#!/usr/bin/python
to
#!/user/bin/python3
and
changed
except ValueError, e:
to
except ValueError as e:
> On Jun 24, 2020, at 8:59 AM, 'Christian Peters' via weewx-user
> wrote:
>
> Hi,
>
> I ran a weewx 3.9.
That did it.
Thank you, Thank you, Thank you.
> On Jun 15, 2020, at 12:43 PM, Garry A Lockyer wrote:
>
> Try setting websockets topic to frogs/loop.
>
> Regards,
>
> Garry Lockyer
> C: +1.250.689.0686
> H: +1.250.495.5343
> E: Garry.Lockyer.ca
>
>>
eafWet4": "0.0", "insideAlarm": "0.0", "rainAlarm":
> "0.0","outsideAlarm1": "0.0", "outsideAlarm2": "0.0", "extraAlarm1":
> "0.0","extraAlarm2": "0.0", &q
ntrols publishing one variable at a time, or
> publishing them all in a single connection (an aggregate).
>
> Regards,
>
> Garry
>
>
> From: weewx-user@googlegroups.com On Behalf Of
> Ken Walker
> Sent: June 14, 2020 5:11 PM
> To: weewx-user@googlegroups.com
;
> Regards,
>
> Garry Lockyer
> C: +1.250.689.0686
> E: ga...@lockyer.ca
>
>
>> On Jun 14, 2020, at 16:43, Ken Walker wrote:
>>
>>
>> I'm getting my data from an internal MQTT server using the wxMesh driver and
>> all is working well.
>
:47 PM, Garry A Lockyer wrote:
>
> The websockets port probably should be 9001. 1883 is usually the MQTT broker.
>
> Regards,
>
> Garry Lockyer
> C: +1.250.689.0686
> E: ga...@lockyer.ca
>
>
>> On Jun 14, 2020, at 16:43, Ken Walker wrote:
>>
>
I'm getting my data from an internal MQTT server using the wxMesh driver
and all is working well.
I would like to enable the MQTT updates, but cannot get them to work.
I get a failed to connect message. All items are on my internal network.
I have no trouble connecting from my weewx
Works great.
On Sunday, June 14, 2020 at 3:43:43 PM UTC-4, Ken Walker wrote:
>
> I have installed the development version of the Belchertown skin and it
> looks terrific!
>
> Thanks Pat
>
> I'm just wondering if you've found an free version of the Aeris api that
>
data.
>
> On Sunday, June 14, 2020 at 3:43:43 PM UTC-4, Ken Walker wrote:
> I have installed the development version of the Belchertown skin and it looks
> terrific!
>
> Thanks Pat
>
> I'm just wondering if you've found an free version of the Aeris api that
> doesn'
I have installed the development version of the Belchertown skin and it
looks terrific!
Thanks Pat
I'm just wondering if you've found an free version of the Aeris api that
doesn't expire after 30 days. Or does the development account still keep
working?
Thanks.
Ken
--
You received this
Pat,
That did the trick. Thanks for the quick response and for the great
skin
Ken
> On Jun 9, 2020, at 2:28 PM, Pat wrote:
>
> You need to restart weewx after any changes to belchertown.py
>
> On Tuesday, June 9, 2020 at 1:13:18 PM UTC-4, Ken Walker wrote:
> Fo
somewhere else?
On Tuesday, June 9, 2020 at 1:05:54 PM UTC-4, Ken Walker wrote:
>
> I am using the Belchertown skin and have modified it to use the National
> Weather Service(NWS) current observations to get the current icon and
> current observation summary.
>
> It all wo
I am using the Belchertown skin and have modified it to use the National
Weather Service(NWS) current observations to get the current icon and
current observation summary.
It all works well when I manually run the wee_reports.
But when I reload the page after the update interval it does not
I am running weewx 4.1.0 on a Raspberry Pi 3 B+. I'm using the wxMesh
driver as my data is published over MQTT.
Most everything works(had to modify wxMesh). But I'm not getting data on
the web page for the outTemp or the barometer. I'm using a different Pi to
generate MQTT messages from
14 matches
Mail list logo
