Pat, This was the closest thread for this particular issue... I followed your blog guide and have mosquitto up and running on my RPi. Already had certbot running so that part was easy. I can subscribe on localhost with no problem on 1883 and see output from weewx, but cannot seem to connect remotely. Netstat shows to be listening on 8883 and 9001. MQTT address is jz.noip.me, skin is at seguin.texwx.info. I checked both SSL and Websocket ports and they all appear to be open and routed properly. Any ideas?
-Jonathan On Monday, August 27, 2018 at 8:12:58 PM UTC-5, Pat wrote: > > I should be good to go now. I've created a lab machine with the AEST > timezone and METRIC and METRICWX for units. Feel free to move your data > where you'd like... > > Thanks for having it up for me to test against. > > On Monday, August 27, 2018 at 7:45:27 PM UTC-4, Colin Larsen wrote: >> >> That's excellent - thanks Pat >> >> I'll leave the data posting to test.mosquitto.org for now so you have >> something to test against. >> >> Colin >> >> >> >> On Tue, Aug 28, 2018 at 12:58 AM Pat <[email protected]> wrote: >> >>> No need for the MQTT login details, I'm able to subscribe to your data >>> feed without a problem. This is helpful so I'll work on updating the MQTT >>> live portion's unit labels. >>> >>> MQTT may run on a Pi Zero - I haven't tried but, and I don't see why it >>> wouldn't work, so it's worth a shot. >>> >>> Try this to get you started: >>> >>> sudo apt-get update >>> sudo apt-get install mosquitto mosquitto-clients >>> >>> Then sudo nano /etc/mosquitto/conf.d/myconfig.conf >>> >>> persistence false >>> >>> allow_anonymous true >>> >>> # Non-SSL MQTT >>> listener 1883 >>> protocol mqtt >>> >>> # Non-SSL Websockets >>> listener 9001 >>> protocol websockets >>> >>> Then >>> >>> sudo service mosquitto stop >>> sudo service mosquitto start >>> >>> This will start your broker on port 1883 for MQTT and 9001 for >>> websockets (for the website). >>> >>> *This won't secure your MQTT broker*, and it allows anonymous users to >>> do whatever they want. So only use this in a development capacity. >>> >>> Once data is being published to the broker, you can use the mosquitto >>> subscribe client to subscribe to the topic and verify the data is there. >>> >>> mosquitto_sub -h localhost -p 1883 -t "your/topic" >>> >>> CTRL+C will exit the program. >>> >>> I'm working on a write up on how to secure the broker, but if you want >>> to read how to secure your broker beforehand, research mosquitto_passwd and >>> acl_file options. If you want to use SSL, you can secure your broker >>> and websockets using LetsEncrypt. Since this is just weather data, SSL may >>> not be necessary, but that's at your discretion. >>> >>> >>> >>> On Sunday, August 26, 2018 at 8:20:36 PM UTC-4, Colin Larsen wrote: >>>> >>>> Working fine with test.mosquitto.org >>>> weather/41south/# >>>> >>>> Haven't looked at the data for sanity :) >>>> >>>> >>>> >>>> On Mon, Aug 27, 2018 at 9:25 AM Colin Larsen <[email protected]> >>>> wrote: >>>> >>>>> That's all good Pat, I sure appreciate the time this is taking and >>>>> real work and family come first always, so certainly no rush on my part. >>>>> >>>>> I can send you a PM with my MQTT login if that helps for testing but >>>>> if Mosquito works I'm happy to shift to that also. In the medium to >>>>> short >>>>> term I'd like to get my own MQTT server running here, as much to save >>>>> data >>>>> being pushed everywhere as anything. Would a small server run on a pi >>>>> zero? >>>>> >>>>> Because I'm still using simulator and waiting for all the parts for my >>>>> station to arrive (building a WeatherDuino setup including air quality >>>>> monitoring) I've left it at US, however I probably should set it to >>>>> Metric >>>>> before any real data goes into the db. >>>>> >>>>> The WeatherDuino mimics a VP2 so I need to find out what sensors the >>>>> AQ data is stored as too so I can get it out and work on displaying it >>>>> ..... but that's another story down the track. >>>>> >>>>> Cheers >>>>> Colin >>>>> >>>>> >>>>> On Mon, 27 Aug 2018, 08:59 Pat, <[email protected]> wrote: >>>>> >>>>>> Yeah I need to upgrade as well. The 0.18rc1 has been working great. >>>>>> So I'm expecting 0.18 to work just as good. >>>>>> >>>>>> Your data's unit values to MQTT should be what you expect, and as you >>>>>> know we've been working out the kinks on the units with the non-live >>>>>> portion of the skin. >>>>>> >>>>>> The live portion processes the MQTT data a bit differently since it's >>>>>> live - it doesn't use weewx's StdConvert in real time - so there are >>>>>> some >>>>>> color charts that I have hard coded for Fahrenheit and I see an >>>>>> outTemp_F, >>>>>> rain inches, dew point F variables it's expecting from MQTT which >>>>>> probably >>>>>> needs to be updated. >>>>>> >>>>>> This weekend has been busy with (real) work, so no update on when I >>>>>> can get an update out quite yet >>>>>> >>>>>> What is your weewx.conf target_unit set to? >>>>>> >>>>>> >>>>>> On Sunday, August 26, 2018 at 4:17:05 PM UTC-4, Colin Larsen wrote: >>>>>>> >>>>>>> Pat that could be my bad on the version I'm using. I went with 0.17 >>>>>>> to get it running, I'll move to 0.18 today, that might solve the units >>>>>>> problem? >>>>>>> I ended up following the wiki install as I think yours was missing a >>>>>>> step, not 100% sure on that. Anyway let me update that. My data going >>>>>>> up to >>>>>>> mqtt certainly has deg C and Kph in it, it didn't look too closely at >>>>>>> the >>>>>>> actual data though >>>>>>> >>>>>>> On Mon, 27 Aug 2018, 05:06 Pat O'Brien, <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Understood and no worries, thanks! >>>>>>>> >>>>>>>> On Sun, Aug 26, 2018, 1:05 PM mwall <[email protected]> wrote: >>>>>>>> >>>>>>>>> On Sunday, August 26, 2018 at 12:49:25 PM UTC-4, Pat wrote: >>>>>>>>>> >>>>>>>>>> On an unrelated note, I have a pull request against your >>>>>>>>>> meteostick driver. Anything more I need to do with that? >>>>>>>>>> >>>>>>>>> >>>>>>>>> i see it. i'm slowly working through a backlog of weewx-related >>>>>>>>> emails and issues... >>>>>>>>> >>>>>>>>> -- >>>>>>>>> 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/FQfh0AAJmCA/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. >>>>>>>> >>>>>>> -- >>>>>> 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. >>>>>> >>>>> -- >>> 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. >>> >> -- 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.
