Pat. You must have gave up on me...lol
On Sat, Oct 5, 2019, 1:42 AM K Weaver wrote:
> It appears the two separate readings are coming from weewx a interceptor
> and my mqtt.
>
> The Mqtt appears to be the most correct. I don't know how to stop
> interceptor without losing connection to my smart
It appears the two separate readings are coming from weewx a interceptor
and my mqtt.
The Mqtt appears to be the most correct. I don't know how to stop
interceptor without losing connection to my smart hub.
On Thu, Oct 3, 2019, 10:05 PM K Weaver wrote:
> Are you able to connect now?
>
> On Thu
Are you able to connect now?
On Thu, Oct 3, 2019, 9:50 PM Pat wrote:
> No, not for mqtt websockets. That's connected to your mosquitto
> installation and not a webserver like nginx or apache.
>
> Check your mosquitto logs to see what's happening
>
> On Thursday, October 3, 2019 at 9:45:02 PM UTC
No, not for mqtt websockets. That's connected to your mosquitto
installation and not a webserver like nginx or apache.
Check your mosquitto logs to see what's happening
On Thursday, October 3, 2019 at 9:45:02 PM UTC-4, K Weaver wrote:
>
> Does it matter if I'm using Apache or nginx?
>
>
> On Th
Does it matter if I'm using Apache or nginx?
On Thu, Oct 3, 2019, 2:54 PM K Weaver wrote:
> I used cloud but couldn't get the client to connect
>
> I can't figure out why it shuts down like that around 9 every morning.
>
> It seems like the sub for the client is connecting separately to the
I used cloud but couldn't get the client to connect
I can't figure out why it shuts down like that around 9 every morning.
It seems like the sub for the client is connecting separately to the raw
data and the real time.
On Thu, Oct 3, 2019, 1:25 PM Pat wrote:
> Have you considered trying a
Have you considered trying a free public broker to resolve some of the
other issues outlined in this post for the interim? Then once those are
fixed you can focus on making your broker stable?
On Thursday, October 3, 2019 at 11:40:38 AM UTC-4, K Weaver wrote:
>
> And checking from work its bac
And checking from work its back down again...😒
On Wed, Oct 2, 2019, 10:40 PM K Weaver wrote:
> 10:39 pm Its up. I'm not gonna try to make any edits if anyone wants to
> check it out.
> Sorry about that
>
>
> On Wed, Oct 2, 2019, 7:51 PM Pat wrote:
>
>> I still think you have something else goin
10:39 pm Its up. I'm not gonna try to make any edits if anyone wants to
check it out.
Sorry about that
On Wed, Oct 2, 2019, 7:51 PM Pat wrote:
> I still think you have something else going on. You posted 18 minutes ago,
> and I cannot reach it.
>
> WebSocket connection to 'ws://mosscrkmqtt.duck
I still think you have something else going on. You posted 18 minutes ago,
and I cannot reach it.
WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt' failed:
Unknown reason
On Wednesday, October 2, 2019 at 7:32:39 PM UTC-4, K Weaver wrote:
>
> It's accessable online now if anyon
It's accessable online now if anyone is available to check it out.
On Wed, Oct 2, 2019, 2:12 PM K Weaver wrote:
> for some reason it disconnects every morning around 9 am
>
> On Tue, Oct 1, 2019, 10:18 PM K Weaver wrote:
>
>> I'm able to pull it up on my phone without WiFi .
>>
>> On Tue, Oct 1
for some reason it disconnects every morning around 9 am
On Tue, Oct 1, 2019, 10:18 PM K Weaver wrote:
> I'm able to pull it up on my phone without WiFi .
>
> On Tue, Oct 1, 2019, 8:07 PM Pat wrote:
>
>> Looks like it's down again - or it's not working externally still
>>
>> On Tuesday, October
I'm able to pull it up on my phone without WiFi .
On Tue, Oct 1, 2019, 8:07 PM Pat wrote:
> Looks like it's down again - or it's not working externally still
>
> On Tuesday, October 1, 2019 at 6:39:02 PM UTC-4, K Weaver wrote:
>>
>> I'm home from work now and reset it.
>> I'm not sure why it shu
Looks like it's down again - or it's not working externally still
On Tuesday, October 1, 2019 at 6:39:02 PM UTC-4, K Weaver wrote:
>
> I'm home from work now and reset it.
> I'm not sure why it shut down...
>
> On Tue, Oct 1, 2019, 3:29 PM Pat >
> wrote:
>
>> Looks like it's down again or you hav
I'm home from work now and reset it.
I'm not sure why it shut down...
On Tue, Oct 1, 2019, 3:29 PM Pat wrote:
> Looks like it's down again or you have a firewall issue again.
>
> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt' failed:
> Unknown reason
>
>
> On Monday, September
Looks like it's down again or you have a firewall issue again.
WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt' failed:
Unknown reason
On Monday, September 30, 2019 at 10:26:05 PM UTC-4, K Weaver wrote:
>
> Hey, its back up and running now. Only thing now it appears to be
> f
Hey, its back up and running now. Only thing now it appears to be flipping
between raw data and real time data..
Here is a snippet of the log. You can really see it flipping back and
forth on the site.
': 1}
Sep 30 19:57:26 raspberrypi weewx[23528]: restx: MQTT: Published record
2019
17 matches
Mail list logo
