Confused. I see weewx loop data every couple seconds...
$ mosquitto_sub -t 'Wetter/loop' -h wxvm.bz3gfkrlqtrsc3sv.myfritz.net
{"dateTime": "1728419863.0", "inTemp_C": "23.299999999999997", "outTemp_C":
"14.9", "inHumidity": "49.0", "outHumidity": "94.0", "pressure_mbar":
"993.4", "relbarometer_mbar": "996.2", "luminosity_lux": "0.0",
"uvradiation_Wpm2": "0.2", "UV": "0.0", "soilMoist1_centibar": "17.0",
"soilMoist2_centibar": "20.0", "soilMoist3_centibar": "20.0",
"soilMoist4_centibar": "50.0", "lightning_distance_km": "0.0",
"lightning_last_det_time": "1727356355.0", "lightningcount_count": "0.0",
"lightning_strike_count_count": "0.0", "heap_free_byte": "28880.0",
"rain_cm": "0.0", "stormRain_cm": "1.6500000000000001",
"rainRate_cm_per_hour": "0.0", "dayRain_cm": "1.73", "weekRain_cm": "1.73",
"monthRain_cm": "4.5200000000000005", "yearRain_cm": "77.59", "windDir":
"135.0", "windSpeed_kph": "4.32001073732089", "windGust_kph":
"7.200017895534816", "daymaxwind_kph": "21.96005458138119",
"wh25_batt_count": "0.0", "wh65_batt_count": "0.0", "wh51_ch1_batt_volt":
"1.5", "wh51_ch2_batt_volt": "1.5", "wh51_ch3_batt_volt": "1.5",
"wh51_ch4_batt_volt": "1.5", "wh57_batt_count": "2.0", "wh25_sig_count":
"4.0", "wh65_sig_count": "4.0", "wh51_ch1_sig_count": "4.0",
"wh51_ch2_sig_count": "4.0", "wh51_ch3_sig_count": "4.0",
"wh51_ch4_sig_count": "4.0", "wh57_sig_count": "4.0", "radiation_Wpm2":
"0.0", "altimeter_mbar": "1002.8582768770635", "appTemp_C":
"15.304960048993621", "barometer_mbar": "1002.747303342425",
"cloudbase_meter": "198.40961163679043", "dewpoint_C":
"13.941895630939834", "heatindex_C": "14.899999999999995", "humidex_C":
"18.237831152343837", "inDewpoint_C": "11.976036849734465",
"maxSolarRad_Wpm2": "0.0", "windchill_C": "14.9", "hourRain_cm": "0.0",
"rain24_cm": "1.7299999999999955", "usUnits": "16.0"}
and I can see you moving.....
$ mosquitto_sub -t 'RVGPS/loop' -h wxvm.bz3gfkrlqtrsc3sv.myfritz.net
{"dateTime": "1728418872", "latitude": "43.367867", "longitude":
"-3.032074"}
{"dateTime": "1728418876", "latitude": "43.367867", "longitude":
"-3.032073"}
{"dateTime": "1728418882", "latitude": "43.367867", "longitude":
"-3.032072"}
Is there any chance you're not getting to the websockets port 9001 ?
On Tuesday, October 8, 2024 at 12:58:11 PM UTC-7 [email protected] wrote:
> A few of questions/clarifications
> So you RV Router can publish to your MQTT broker? Is this some type of
> built in functionality of the router?
> This is the router that the PI is behind that cannot publish or subscribe?
> Are you running MQTT Explorer on the PI. If so, it appears that can
> subscribe, correct?
> The browser is also runing on the PI, correct?
> Things are pointing to something in paho mqtt client, used by both
> MQTTSubscribe WeeWX-MQTT… Unfortunately I still don’t have any good ideas
> yet. I was really hoping that the IP address would work…
>
> Note, 1.6.1 is not the latest version. The version installed by apt is
> behind. The version is up to 2.1.0
> BUT, I would be very hesitant to upgrade to that. 2.0 introduced many
> breaking changes and many python clients broke. In theory 2.1.0 ‘fixes’
> this, but since I have updated all my MQTT clients to work with 2.x and
> 1.6, I cannot verify that.
> AND, I do not see anything in the release notes that leads me to think
> this would be fixed.
> rich
>
> On Tuesday 8 October 2024 at 15:37:06 UTC-4 Stefan Gliessmann wrote:
>
>> Continuing to find some more details/hints/breadcrumbs ...
>> For MQTT.Subscribe I used the IP of the broker which gets resolved via
>> ping. Still not reachable.
>> Then I set MQTT.Subcribe enable = false to see if the other client can
>> connect to the same broker. and ... no ...
>>
>> *ERROR user.mqtt: Failed to connect to MQTT server
>> (mqtt://teffi:[email protected]:1883/
>> <http://teffi:[email protected]:1883/>): [Errno 101]
>> Network is unreachable*
>>
>> *ERROR weewx.restx: MQTT: Failed to publish record 2024-10-08 21:18:25
>> CEST (1728415105): MQTT client not available*
>>
>> So it seems to be a "port 1883 issue", but where? Pi, the RV router, the
>> home router, the VM on which the broker runs? (But why would it work in
>> Germany just fine ...?)
>> Can the internet provider limit port 1883?
>> The SIM card in the RV router is from Vodafone Germany ...
>> In the meantime, I rebooted the ubuntu box with my home weewx on which
>> also my MQTT broker resides, too. Still "Errno 101"
>>
>> That the MQTT broker works at home and receives the GPS topic from my RV
>> router and republishes them under RVGPS can be seen below (for real-time
>> weather data, the topic would be RV:
>>
>> [image: Screenshot 2024-10-08 at 21.27.31.png]
>> On Tuesday, October 8, 2024 at 8:50:38 PM UTC+2 Stefan Gliessmann wrote:
>>
>>> Hi gents -
>>>
>>> I did not know that they are using different clients, but I knew the
>>> difference in the port numbers 1883 vs 9001 ;)
>>>
>>> My raspbi runs python3-paho-mqtt is already the newest version
>>> (1.6.1-1).
>>>
>>> I started with restarting weewx, then mosquitto, then the Raspberry Pi
>>> and just for good measure also the internet router ... nothing resolved the
>>> issue.
>>>
>>> In the meantime I arrived in Spain and I have still the same issue.
>>>
>>> My GPS router is the Teltonika RUTX11 which runs BusyBox v1.34.1 The
>>> GPS coordinates are read from a GPS receiver connected to the router and
>>> send via "Modbus TCP Devices" to my home MQTT broker under the topic RVGPS
>>> ...
>>> I will now start enabling log = true & debug = 1
>>>
>>> Thanks for the input so far - I will keep you posted ...
>>> Cheers
>>>
>>>
>>> On Tue, Oct 8, 2024 at 1:28 AM [email protected] <[email protected]>
>>> wrote:
>>>
>>>> It is another interesting data point. A couple of things to note.
>>>> 1. The connections are using two different protocols. Belchertown is
>>>> connecting over websockets and MQTTSubscribe is connecting over MQTT.
>>>> 2. It is two different MQTT clients. Belchertown is using a javascript
>>>> client while MQTTSubscribe uses a python client.
>>>> So, it appears that the javascript client/websockets can handle the
>>>> network change and the paho mqtt client/mqtt client cannot. Now to figure
>>>> out why…
>>>>
>>>> Out of curiosity, what version of the paho mqtt client are you using?
>>>> rich
>>>>
>>>> On Monday 7 October 2024 at 15:42:20 UTC-4 Stefan Gliessmann wrote:
>>>>
>>>>> Interestingly, rv.stegli.de sees the web socket of my home MQTT
>>>>> broker ...
>>>>>
>>>>> [image: Screenshot 2024-10-07 at 21.39.47.png]
>>>>>
>>>>> On Monday, October 7, 2024 at 9:25:34 PM UTC+2 Stefan Gliessmann wrote:
>>>>>
>>>>>> Thanks, Vince!
>>>>>>
>>>>>> I am puzzled what it could be blocking here in France compared when
>>>>>> it worked just fine in Germany. (rv.stegli.de shows the last data
>>>>>> before crossing over to France).
>>>>>>
>>>>>> On Monday, October 7, 2024 at 9:20:34 PM UTC+2 vince wrote:
>>>>>>
>>>>>>> I can subscribe to your data from the USA too so you must have some
>>>>>>> kind of networking thing going on that is preventing port 1883 in from
>>>>>>> wherever you are.
>>>>>>>
>>>>>>> On Monday, October 7, 2024 at 12:08:40 PM UTC-7 Stefan Gliessmann
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Yes, I can ping it and it gets resolved correctly ...
>>>>>>>> My internet router in my RV forwards the GPS coordinates per MQTT
>>>>>>>> to my home broker correctly, too ...
>>>>>>>>
>>>>>>>> On Monday, October 7, 2024 at 9:06:15 PM UTC+2 vince wrote:
>>>>>>>>
>>>>>>>>> I can ping that FQDN from the USA if that matters.....
>>>>>>>>>
>>>>>>>>> On Monday, October 7, 2024 at 11:51:31 AM UTC-7 Stefan Gliessmann
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hello -
>>>>>>>>>>
>>>>>>>>>> I am running a mobile WeeWX station in my RV. I use MQTT to
>>>>>>>>>> provide real-time weather data from the basic ecowitt gateway. I
>>>>>>>>>> augment
>>>>>>>>>> the weather data via MQTT every 5 min or so with data from
>>>>>>>>>> OpenWeather.
>>>>>>>>>> Additionally, I share my GPS coordinates and a calculated altitude.
>>>>>>>>>>
>>>>>>>>>> WeeWX runs on a raspberry pi in my RV. Internet is provided by an
>>>>>>>>>> internet router via 4G mobile phone network.
>>>>>>>>>>
>>>>>>>>>> All this worked great as long as I was in Germany. The moment I
>>>>>>>>>> crossed boarder to France and the mobile phone network switches to
>>>>>>>>>> the
>>>>>>>>>> other country, I receive this error:
>>>>>>>>>>
>>>>>>>>>> ""*ERROR user.MQTTSubscribe: (Service) Failed to connect to
>>>>>>>>>> wxvm.bz3gfkrlqtrsc3sv.myfritz.net
>>>>>>>>>> <http://wxvm.bz3gfkrlqtrsc3sv.myfritz.net> at 1883. '[Errno 101]
>>>>>>>>>> Network is
>>>>>>>>>> unreachable'*""
>>>>>>>>>>
>>>>>>>>>> I am a bit puzzled why my home MQTT broker's port cannot be
>>>>>>>>>> reached ...
>>>>>>>>>>
>>>>>>>>>> Any clue how I can trouble shoot this?
>>>>>>>>>>
>>>>>>>>>> Thank you guys in advance knowing that this isn't a core WeeWX
>>>>>>>>>> problem :)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>> 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/K8EABxk8R7o/unsubscribe.
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> [email protected].
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/weewx-user/3e1117e3-c4d6-4ac9-9613-707141f5d58bn%40googlegroups.com
>>>>
>>>> <https://groups.google.com/d/msgid/weewx-user/3e1117e3-c4d6-4ac9-9613-707141f5d58bn%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/78f8ba90-64ee-49c8-87a2-0d243dba80ben%40googlegroups.com.
