Working great from here.
I too have incorrigible fingers when writing configs.
On Wed, Jan 22, 2020, 2:47 PM Gordon Dickens wrote:
> Hello Mr. Hammer,
>
> I believe that I have fixed everything. Please check my site now at
>
> https://crabapple.dickens.com
>
> For some reason, I thought that
Hello Mr. Hammer,
I believe that I have fixed everything. Please check my site now at
https://crabapple.dickens.com
For some reason, I thought that the websocket port was udp and so I
therefore set up iptables wrong. As soon as I changed the websockets
iptables rule to tcp then everything
Hello Mr. Hammer,
Its working on all of my devices and my wife's devices both under Linux,
Windows, Android and iphone. Please try a different browser and/or clear
the cache and delete browser history for crabapple.dickens.com. Otherwise,
I cannot recreate what you are seeing.
Thanks!
No, I still don't get MQTT data when I connect using the Dickens domain
address.
On Wed, Jan 22, 2020, 7:31 AM Gordon Dickens wrote:
> Hi Ryan Kramer and G. Hammer,
>
> Thanks for replying, however, I got everything working three days ago on
> January 19 as per this post:
>
>
Hi Ryan Kramer and G. Hammer,
Thanks for replying, however, I got everything working three days ago on
January 19 as per this post:
https://groups.google.com/d/msg/weewx-user/HRhNyrWRIn0/X2fAHkfGEQAJ
Then, yesterday, I spent most of the day switching the domain from
zeebytes.org to
When I go to the site you gave zeebytes.org, I actually get
crabapple.dickens.com
Redirects are possible, but I have no idea where to start since I haven't
configured any for my domain.
That is where MQTT is attempting to connect as well.
mqttws31.min.js:36 WebSocket connection to
Looking at your site, you have something wrong in your config yet. Per
the includes, you have crabapple.dickens.com as your MQTT server. Doesn't
look like that is responding to anything.
view-source:https://crabapple.dickens.com/js/belchertown.js?1579622117
client = new
Hi Gary,
Thanks very much for your reply! As you suggested, I set the host
name to be my FQDN,"zeebytes.org", instead of "localhost". I also
added a non-ssl url with http://zeebytes.org (as opposed to
https://zeebytes.org) and I set the mqtt_websockets_topic =
Glad to hear it is working now.
On Sunday, January 19, 2020 at 10:36:14 AM UTC-5, Gordon Dickens wrote:
>
> I got it working. I'm not sure exactly why but I think the problem was
> related to running the site with https while running Belchertown with
> mqtt_websockets_ssl = 0. As soon as I
I got it working. I'm not sure exactly why but I think the problem was
related to running the site with https while running Belchertown with
mqtt_websockets_ssl = 0. As soon as I amended my apache2 config so that
weewx was running unencrypted with htttp instead of https then it started
I also had to change from mqtt_websockets_host = "localhost" to
mqtt_websockets_host = "FQDN" with FQDN being the full public name of the
server.
On Saturday, January 18, 2020 at 8:48:36 AM UTC-5, Gordon Dickens wrote:
>
> Hello everybody,
>
> I have the Belchertown skin up and running nicely
I think it is because you are going to the site via https but do not have
ssl enabled for the skin mqtt_websockets_ssl = 0 vs mqtt_websockets_ssl = 1
I'd also change the topic to weather/loop vs weather/#
On Saturday, January 18, 2020 at 8:48:36 AM UTC-5, Gordon Dickens wrote:
>
> Hello
12 matches
Mail list logo
