MQTT for Belchertown skin

693 views
Skip to first unread message

Tom Hackett

unread,
Mar 27, 2021, 9:33:10 AM3/27/21
to weewx-user
I'm new to weewx and raspberry pi.
I installed the Belchertown skin on a Raspberry Pi4.
I'm trying to setup a MQTT server on the raspberry pi.
I installed MQTT:
"pi@raspberrypi:~ $ sudo wget -O weewx-mqtt.zip https://github.com/matthewwall/weewx-mqtt/archive/master.zip
Resolving github.com (github.com)... 140.82.112.3
Connecting to github.com (github.com)|140.82.112.3|:443... connected.
HTTP request sent, awaiting response... 302 Found
Resolving codeload.github.com (codeload.github.com)... 140.82.114.10
Connecting to codeload.github.com (codeload.github.com)|140.82.114.10|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/zip]
Saving to: ‘weewx-mqtt.zip’

weewx-mqtt.zip          [ <=>                ]   8.43K  --.-KB/s    in 0.002s  

2021-03-27 08:25:49 (4.81 MB/s) - ‘weewx-mqtt.zip’ saved [8632]

pi@raspberrypi:~ $ sudo wee_extension --install weewx-mqtt.zip
Request to install 'weewx-mqtt.zip'
Extracting from zip archive weewx-mqtt.zip
Saving installer file to /usr/share/weewx/user/installer/mqtt
Saved configuration dictionary. Backup copy at /etc/weewx/weewx.conf.20210327082627
Finished installing extension 'weewx-mqtt.zip'"
My wwewx.conf file is:
under [StdRESTful]
[[MQTT]]
        server_url = mqtt://tph06784:xxxx@localhost:1883
        topic = weather
        unit_system = US
        binding = archive, loop
        aggregation = aggregate
        log_success = true

under [Extras] in skin.conf
 # MQTT Websockets defaults
    mqtt_websockets_enabled = 1
    mqtt_websockets_host = "192.168.1.170"
    mqtt_websockets_port = 9001
    mqtt_websockets_ssl = 0
    mqtt_websockets_topic = "weather/loop"
    disconnect_live_website_visitor = 300000
and under [Engine]
restful_services = weewx.restx.StdStationRegistry, weewx.restx.StdWunderground, weewx.restx.StdPWSweather, weewx.restx.StdCWOP, weewx.restx.StdWOW, weewx.restx.StdAWEKAS, user.mqtt.MQTT

Part of my syslog that seems to be revelant
Mar 27 09:26:23 raspberrypi weewx[13200] INFO user.mqtt: service version is 0.23
Mar 27 09:26:23 raspberrypi weewx[13200] INFO user.mqtt: binding to ['archive', 'loop']
Mar 27 09:26:23 raspberrypi weewx[13200] INFO user.mqtt: topic is weather
Mar 27 09:26:23 raspberrypi weewx[13200] INFO user.mqtt: desired unit system is US
Mar 27 09:26:23 raspberrypi weewx[13200] INFO user.mqtt: data will be uploaded to mqtt://tph06784:xxx@localhost:1883
Mar 27 09:26:23 raspberrypi weewx[13200] DEBUG weewx.engine: Finished loading service user.mqtt.MQTT
Mar 27 09:26:23 raspberrypi weewx[13200] DEBUG weewx.engine: Loading service weewx.engine.StdPrint
Mar 27 09:26:23 raspberrypi weewx[13200] DEBUG weewx.engine: Finished loading service weewx.engine.StdPrint
Mar 27 09:26:23 raspberrypi weewx[13200] DEBUG weewx.engine: Loading service weewx.engine.StdReport
Mar 27 09:26:23 raspberrypi weewx[13200] DEBUG weewx.engine: Finished loading service weewx.engine.StdReport
Mar 27 09:26:23 raspberrypi weewx[13200] INFO __main__: Starting up weewx version 4.4.0
Mar 27 09:26:23 raspberrypi weewx[13200] DEBUG weewx.engine: Station does not support reading the time
Mar 27 09:26:23 raspberrypi weewx[13200] INFO weewx.engine: Using binding 'wx_binding' to database 'weewx.sdb'
Mar 27 09:26:23 raspberrypi weewx[13200] INFO weewx.manager: Starting backfill of daily summaries
Mar 27 09:26:23 raspberrypi weewx[13200] INFO weewx.manager: Daily summaries up to date
Mar 27 09:26:23 raspberrypi weewx[13200] INFO weewx.engine: Starting main packet loop.
Mar 27 09:26:23 raspberrypi weewx[13200] INFO user.gw1000: Using 'rainyear' for rain total
Mar 27 09:26:23 raspberrypi weewx[13200] INFO user.gw1000: skipping rain measurement of 170.6: no last rain
Mar 27 09:26:23 raspberrypi weewx[13200] INFO user.gw1000: Using 'rainyear' for rain total
Mar 27 09:26:23 raspberrypi weewx[13200] INFO user.gw1000: skipping rain measurement of 170.6: no last rain
Mar 27 09:26:23 raspberrypi weewx[13200] INFO weewx.wxxtypes: Type beaufort has been deprecated. Use unit beaufort instead.
Mar 27 09:26:23 raspberrypi weewx[13200] DEBUG weewx.manager: Daily summary version is 4.0
Mar 27 09:26:23 raspberrypi weewx[13200] INFO weewx.restx: MQTT: Published record 2021-03-27 09:26:21 EDT (1616851581)
Mar 27 09:26:41 raspberrypi weewx[13200] DEBUG user.gw1000: Next update in 20 seconds
Mar 27 09:26:41 raspberrypi weewx[13200] INFO weewx.restx: MQTT: Published record 2021-03-27 09:26:41 EDT (1616851601)

I just can't figure this out.
Any help would be appreciated.
Thanks, Tom



Graham Eddy

unread,
Mar 27, 2021, 10:25:24 AM3/27/21
to weewx...@googlegroups.com
what’s not working?

Tom Hackett

unread,
Mar 27, 2021, 10:33:58 AM3/27/21
to weewx...@googlegroups.com
Site only says Connecting to weather station real time data and no updates are happening.

--
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 weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/7A79B922-E098-48AE-A46C-3A128A3F9D90%40gmail.com.


--

mh081...@gmail.com

unread,
Mar 27, 2021, 11:47:11 AM3/27/21
to weewx-user
Hi,

if you will that mqtt working from ootside of your website you must config public dns names . 

example from mx site

weewx.conf

    [[MQTT]]
        server_url = mqtt://pi:pass...@gw.martenhinrichs.de:8883/
        topic = weather
        unit_system = METRIC
        binding = archive, loop
        aggregation = aggregate
        log_success = False
        log_failure = True
        [[[tls]]]
            tls_version = tlsv12
            ca_certs = /etc/ssl/certs/ca-certificates.crt
        [[[inputs]]]
            [[[[dayRain]]]]
                name = dayRain_mm
                units = mm
            [[[[rainRate]]]]
                name = rainRate_mm_per_hour
                units = mm_per_hour

[[Belchertown]]
     [[[Extras]]]

            mqtt_websockets_enabled = 1
            mqtt_websockets_host = gw.martenhinrichs.de
            mqtt_websockets_port = 9001
            mqtt_websockets_ssl = 1
            mqtt_websockets_topic = weather/loop


Only difference i use ssl and metric

mh081...@gmail.com

unread,
Mar 27, 2021, 11:50:05 AM3/27/21
to weewx-user
And of course allow ports on your firewall/router etc.

vince

unread,
Mar 27, 2021, 11:51:54 AM3/27/21
to weewx-user
> server_url = mqtt://tph06784:xxxx@localhost:1883

This is becoming a FAQ.

Do not use 'localhost'.  Use the fully qualified domain name of the MQTT broker host or its IP address.

Tom Hackett

unread,
Mar 27, 2021, 12:42:38 PM3/27/21
to weewx...@googlegroups.com
I have changed MQTT to
[[MQTT]]
        server_url = mqtt://tph06784:03...@192.168.1.170:1883
        topic = weather
        unit_system = US

        binding = archive, loop
        aggregation = aggregate
        log_success = true1883

No change

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/ec03055f-9ec1-443c-89a2-b2961f5e0088n%40googlegroups.com.

Tom Hackett

unread,
Mar 27, 2021, 12:47:01 PM3/27/21
to weewx...@googlegroups.com
This is the mosquitto log since the change
1616862009: New connection from 192.168.1.170 on port 1883.
1616862009: New client connected from 192.168.1.170 as weewx_94c44d84 (c1, k60, u'tph06784').
1616862009: Client weewx_94c44d84 disconnected.
1616862028: New connection from 192.168.1.170 on port 1883.
1616862028: New client connected from 192.168.1.170 as weewx_61789889 (c1, k60, u'tph06784').
1616862028: Client weewx_61789889 disconnected.
1616862030: New connection from 192.168.1.170 on port 1883.
1616862030: New client connected from 192.168.1.170 as weewx_28e94234 (c1, k60, u'tph06784').
1616862030: Client weewx_28e94234 disconnected.
1616862048: New connection from 192.168.1.170 on port 1883.
1616862048: New client connected from 192.168.1.170 as weewx_38f31fdb (c1, k60, u'tph06784').
1616862048: Client weewx_38f31fdb disconnected.

Les Niles

unread,
Mar 27, 2021, 2:30:48 PM3/27/21
to weewx-user
It looks like weewx is sending updates to the mqtt server.  But the web browser isn’t connecting to the mqtt server to retrieve those updates.  Please post your mqtt (mosquito) config file — you need to have websockets enabled there, on port 9001.  

My suggestion is to turn off SSL on the websockets connection. If you’re not doing authentication on the websockets log-in — usually it’s just set up as read-only but publicly-available — then I don’t see much use for encrypting the connection.  At any rate, turn off SSL until you get everything working without it.

  -Les



Tom Hackett

unread,
Mar 27, 2021, 2:41:43 PM3/27/21
to weewx...@googlegroups.com
I believe SSL is off. I have mqtt_websockets_ssl = 0 in my skin.conf
My mqtt (mosquito) config file is in /etc/mosquitto/mosquitto.conf is
# Place your local configuration in /etc/mosquitto/conf.d/
#
# A full description of the configuration file is at
# /usr/share/doc/mosquitto/examples/mosquitto.conf.example

pid_file /var/run/mosquitto.pid

persistence true
persistence_location /var/lib/mosquitto/

log_dest file /var/log/mosquitto/mosquitto.log

#include_dir /etc/mosquitto/conf.d

There is also in /etc/mosquitto/conf.d/mosquitto.conf
# Place your local configuration in /etc/mosquitto/conf.d/
#
# A full description of the configuration file is at
# /usr/share/doc/mosquitto/examples/mosquitto.conf.example

#pid_file /var/run/mosquitto.pid

persistence false
allow_anonymous true
password_file /etc/mosquitto/passwd
acl_file /etc/mosquitto/acl
# Insecure mqtt to localhost only, and secure mqtt
listener 1883 localhost
listener 8883
certfile /etc/mosquitto/certs/cert.pem
cafile /etc/mosquitto/certs/chain.pem
keyfile /etc/mosquitto/certs/privkey.pem
protocol mqtt
# websockets
listener 9001
certfile /etc/mosquitto/certs/cert.pem
cafile /etc/mosquitto/certs/chain.pem
keyfile /etc/mosquitto/certs/privkey.pem
protocol websockets

#persistence_location /var/lib/mosquitto/

log_dest file /var/log/mosquitto/mosquitto.log

include_dir /etc/mosquitto/conf.d

Tom

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/9E5443B7-7618-42E4-9E58-91BB415B73BB%402pi.org.

Les Niles

unread,
Mar 27, 2021, 3:06:16 PM3/27/21
to weewx-user
The include_dir line in mosquitto.conf is commented out, so the stuff in /etc/mosquitto/conf.d/mosquitto.conf never gets picked up.  Remove the “#” at the beginning of the line. Also, remove the include_dir line in /etc/mosquitto/conf.d/mosquitto.conf to avoid a potentially infinite recursion. 

Please post your acl_file (should be /etc/mosquitto/acl).  It should have a line like
topic read weather/#
near the top, to enable anonymous read access.

What are you seeing in the mosquitto log?

  -Les



Tom Hackett

unread,
Mar 27, 2021, 3:52:29 PM3/27/21
to weewx...@googlegroups.com
/etc/mosquitto/mosquitto.conf:
# Place your local configuration in /etc/mosquitto/conf.d/
#
# A full description of the configuration file is at
# /usr/share/doc/mosquitto/examples/mosquitto.conf.example

#pid_file /var/run/mosquitto.pid


persistence true
persistence_location /var/lib/mosquitto/

log_dest file /var/log/mosquitto/mosquitto.log

include_dir /etc/mosquitto/conf.d

/etc/mosquitto/conf.d/mosquitto.conf:
# Place your local configuration in /etc/mosquitto/conf.d/
#
# A full description of the configuration file is at
# /usr/share/doc/mosquitto/examples/mosquitto.conf.example

pid_file /var/run/mosquitto.pid

#persistence false

allow_anonymous true
password_file /etc/mosquitto/passwd
acl_file /etc/mosquitto/acl
# Insecure mqtt to localhost only, and secure mqtt
listener 1883 localhost
listener 8883
certfile /etc/mosquitto/certs/cert.pem
cafile /etc/mosquitto/certs/chain.pem
keyfile /etc/mosquitto/certs/privkey.pem
protocol mqtt
# websockets
listener 9001
protocol websockets

certfile /etc/mosquitto/certs/cert.pem
cafile /etc/mosquitto/certs/chain.pem
keyfile /etc/mosquitto/certs/privkey.pem
protocol websockets

#persistence_location /var/lib/mosquitto/

log_dest file /var/log/mosquitto/mosquitto.log


The acl:
# Allow anonymous access to the sys
topic read $SYS/#

# Allow anonymous to read weather
topic read weather/#

# weewx readwrite to the loop
user <tph06784>
topic weather/#

Here is part of mosquitto log:
1616874562: New connection from 192.168.1.170 on port 1883.
1616874562: New client connected from 192.168.1.170 as weewx_4b8e89f4 (c1, k60, u'tph06784').
1616874562: Client weewx_4b8e89f4 disconnected.
1616874563: New connection from 192.168.1.170 on port 1883.
1616874563: New client connected from 192.168.1.170 as weewx_17c9704e (c1, k60, u'tph06784').
1616874563: Client weewx_17c9704e disconnected.
1616874565: New connection from 192.168.1.170 on port 1883.
1616874565: New client connected from 192.168.1.170 as weewx_3ad70f87 (c1, k60, u'tph06784').
1616874565: Client weewx_3ad70f87 disconnected.
1616874583: New connection from 192.168.1.170 on port 1883.
1616874583: New client connected from 192.168.1.170 as weewx_4d17e0e9 (c1, k60, u'tph06784').
1616874584: Client weewx_4d17e0e9 disconnected.
1616874585: New connection from 192.168.1.170 on port 1883.
1616874585: New client connected from 192.168.1.170 as weewx_aa8f33c8 (c1, k60, u'tph06784').
1616874585: Client weewx_aa8f33c8 disconnected.
1616874603: New connection from 192.168.1.170 on port 1883.
1616874603: New client connected from 192.168.1.170 as weewx_76212562 (c1, k60, u'tph06784').
1616874603: Client weewx_76212562 disconnected.
1616874605: New connection from 192.168.1.170 on port 1883.

Thanks for taking the time to look at this.
Tom

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/3E6BCDDD-1785-4C97-A3FD-567600D1F954%402pi.org.

Les Niles

unread,
Mar 27, 2021, 6:35:43 PM3/27/21
to weewx...@googlegroups.com
The only odd thing I see now are the certfile, cafile, and keyfile lines under the websockets listener — that may be turning on SSL for websockets.  You can just delete those lines (along with the second “protocol websockets”).  

And confirm that you’ve restarted mosquitto, so the conf changes will take effect?

The other potential issue is network topology & routing.  gw.martenhinrichs.de presumably points to the mosquitto server’s internal IP 192.168.1.170.  Does that address translation work for connecting from wherever your web browser is running?  I had to do some config on my router to make the “hairpin” connection work. 

  -Les



Tom Hackett

unread,
Mar 27, 2021, 6:52:55 PM3/27/21
to weewx...@googlegroups.com
Thanks.
I took out those lines. Since everything is running on same pi I figured I wouldn't need any special networking.
I'm now getting a connection refused.
Mosquitto.log:
1616884948: mosquitto version 1.5.7 starting
1616884948: Config loaded from /etc/mosquitto/mosquitto.conf.
1616884948: Opening ipv4 listen socket on port 1883.
1616884948: Opening ipv6 listen socket on port 1883.
1616884948: Opening websockets listen socket on port 9001.
1616884948: Error: Unable to create websockets listener on port 9001.
1616884948: mosquitto version 1.5.7 starting
1616884948: Config loaded from /etc/mosquitto/mosquitto.conf.
1616884948: Opening ipv4 listen socket on port 1883.
1616884948: Opening ipv6 listen socket on port 1883.
1616884948: Opening websockets listen socket on port 9001.
1616884948: Error: Unable to create websockets listener on port 9001.

syslog:
Mar 27 18:43:52 raspberrypi weewx[8242] ERROR weewx.restx: MQTT: Failed to publish record 2021-03-27 18:02:56 EDT (1616882576): Failed upload after 3 tries
Mar 27 18:43:52 raspberrypi weewx[8242] DEBUG user.mqtt: Failed upload attempt 1: [Errno 111] Connection refused
Mar 27 18:43:57 raspberrypi weewx[8242] DEBUG user.mqtt: Failed upload attempt 2: [Errno 111] Connection refused
Mar 27 18:44:00 raspberrypi weewx[8242] DEBUG user.gw1000: Next update in 20 seconds
Mar 27 18:44:02 raspberrypi weewx[8242] DEBUG user.mqtt: Failed upload attempt 3: [Errno 111] Connection refused
Mar 27 18:44:04 raspberrypi weewx[8242] DEBUG user.gw1000: Next update in 20 seconds
Mar 27 18:44:07 raspberrypi weewx[8242] ERROR weewx.restx: MQTT: Failed to publish record 2021-03-27 18:02:59 EDT (1616882579): Failed upload after 3 tries
Mar 27 18:44:07 raspberrypi weewx[8242] DEBUG user.mqtt: Failed upload attempt 1: [Errno 111] Connection refused
Mar 27 18:44:12 raspberrypi weewx[8242] DEBUG user.mqtt: Failed upload attempt 2: [Errno 111] Connection refused
Mar 27 18:44:17 raspberrypi weewx[8242] DEBUG user.mqtt: Failed upload attempt 3: [Errno 111] Connection refused
Mar 27 18:44:21 raspberrypi weewx[8242] DEBUG user.gw1000: Next update in 20 seconds

When I run systemctl status mosquitto.service I get 
mosquitto.service - Mosquitto MQTT v3.1/v3.1.1 Broker
   Loaded: loaded (/lib/systemd/system/mosquitto.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2021-03-27 18:42:29 EDT; 8min ago
     Docs: man:mosquitto.conf(5)
           man:mosquitto(8)
  Process: 20719 ExecStart=/usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf (code=exited, status=1/FAILURE)
 Main PID: 20719 (code=exited, status=1/FAILURE)

Mar 27 18:42:29 raspberrypi systemd[1]: mosquitto.service: Service RestartSec=100ms expired, scheduling restart.
Mar 27 18:42:29 raspberrypi systemd[1]: mosquitto.service: Scheduled restart job, restart counter is at 5.
Mar 27 18:42:29 raspberrypi systemd[1]: Stopped Mosquitto MQTT v3.1/v3.1.1 Broker.
Mar 27 18:42:29 raspberrypi systemd[1]: mosquitto.service: Start request repeated too quickly.
Mar 27 18:42:29 raspberrypi systemd[1]: mosquitto.service: Failed with result 'exit-code'.
Mar 27 18:42:29 raspberrypi systemd[1]: Failed to start Mosquitto MQTT v3.1/v3.1.1 Broker.

I seemed to have gone backwards today.



To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/7196B38C-A621-4525-A324-FD803D966E8D%402pi.org.

Les Niles

unread,
Mar 27, 2021, 8:32:41 PM3/27/21
to weewx...@googlegroups.com
Now it looks like something else is already running on port 9001.  Without trying to start mosquitto, see what you get with
sudo netstat -anp | grep 9001
If you get something like “tcp    0  0 0.0.0.0:9001     0.0.0.0:*     LISTEN   9676/something” then there’s another instance of <something> running on port 9001; that number right before the “/“ is the process ID.  

If not, then undo the last change and see if the publishing at least works again, because obviously I don’t know what I’m talking about.

BTW, once you get the publishing working again, if your web browser is running on the same pi, or at least on the same 192.168.1 subnet, then for testing purposes you could replace gw.martenhinrichs.de with the 192.168.1.170 IP address in the [[Belchertown]][[[Extras]]] config; if that magically makes it work, then the issue is related to your networking rather than the broker itself.   

  -Les



Tom Hackett

unread,
Mar 27, 2021, 8:43:42 PM3/27/21
to weewx...@googlegroups.com
This is my Belchertown skin setup
# MQTT Websockets defaults
    mqtt_websockets_enabled = 0
    mqtt_websockets_host = "192.168.1.170"
    mqtt_websockets_port = 9001

    mqtt_websockets_ssl = 0
    mqtt_websockets_topic = "weather/loop"
    disconnect_live_website_visitor = 300000

I tried sudo netstat -anp | grep 9001 and got 
pi@raspberrypi:~ $ sudo netstat -anp | grep 9001
tcp        0      0 0.0.0.0:9001            0.0.0.0:*               LISTEN      27650/mosquitto    
pi@raspberrypi:~ $ # MQTT Websockets defaults
pi@raspberrypi:~ $     mqtt_websockets_enabled = 0
bash: mqtt_websockets_enabled: command not found
pi@raspberrypi:~ $     mqtt_websockets_host = "192.168.1.170"
bash: mqtt_websockets_host: command not found
pi@raspberrypi:~ $     mqtt_websockets_port = 9001
bash: mqtt_websockets_port: command not found
pi@raspberrypi:~ $     mqtt_websockets_ssl = 0
bash: mqtt_websockets_ssl: command not found
pi@raspberrypi:~ $     mqtt_websockets_topic = "weather/loop"
bash: mqtt_websockets_topic: command not found
pi@raspberrypi:~ $     disconnect_live_website_visitor = 300000

I'll try tomorrow to find what is running.
Thanks,Tom

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/01587A70-F062-4C2A-A90E-134499EF40D9%402pi.org.

Les Niles

unread,
Mar 27, 2021, 9:35:07 PM3/27/21
to weewx-user
If you still have what you showed earlier

[[Belchertown]]
     [[[Extras]]]

            mqtt_websockets_enabled = 1
            mqtt_websockets_host = gw.martenhinrichs.de
            mqtt_websockets_port = 9001
            mqtt_websockets_ssl = 1
            mqtt_websockets_topic = weather/loop
 
in your weewx.conf, that will override those variable settings in Belchertown/skin.conf.  Just put the IP address in weewx.conf in place of gw.martenhinrichs.de.

There is an instance of mosquitto already running.  Probably time to reboot the pi. 

  -Les



Tom Hackett

unread,
Mar 29, 2021, 8:15:45 PM3/29/21
to weewx-user
I finally got mosquitto  running.
Still not working with weewx but I feel getting closer.
My syslog is:
Mar 29 20:06:59 raspberrypi mosquitto[3588]: 1617062819: New connection from ::1:49677 on port 1883.
Mar 29 20:06:59 raspberrypi mosquitto[3588]: 1617062819: New client connected from ::1:49677 as weewx_2f297bff (p2, c1, k60, u'tph06784').
Mar 29 20:06:59 raspberrypi mosquitto[3588]: 1617062819: Client weewx_2f297bff disconnected.

Is it supposed to disconnect or stay connected? What would cause the disconnection.
Here is part of service mosquitto status command:
pi@raspberrypi:~ $ sudo /etc/init.d/mosquitto restart
[ ok ] Restarting mosquitto (via systemctl): mosquitto.service.
pi@raspberrypi:~ $ service mosquitto status
\u25cf mosquitto.service - Mosquitto MQTT Broker
   Loaded: loaded (/lib/systemd/system/mosquitto.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2021-03-29 20:05:53 EDT; 15s ago
     Docs: man:mosquitto.conf(5)
           man:mosquitto(8)
  Process: 3584 ExecStartPre=/bin/mkdir -m 740 -p /var/log/mosquitto (code=exited, status=0/SUCCESS)
  Process: 3585 ExecStartPre=/bin/chown mosquitto: /var/log/mosquitto (code=exited, status=0/SUCCESS)
  Process: 3586 ExecStartPre=/bin/mkdir -m 740 -p /var/run/mosquitto (code=exited, status=0/SUCCESS)
  Process: 3587 ExecStartPre=/bin/chown mosquitto: /var/run/mosquitto (code=exited, status=0/SUCCESS)
 Main PID: 3588 (mosquitto)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/mosquitto.service
           \u2514\u25003588 /usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf

Mar 29 20:05:53 raspberrypi mosquitto[3588]: 1617062753: Opening ipv6 listen socket on port 1883.
Mar 29 20:05:53 raspberrypi mosquitto[3588]: 1617062753: Opening websockets listen socket on port 9001.
Mar 29 20:05:53 raspberrypi mosquitto[3588]: 1617062753: mosquitto version 2.0.9 running
Mar 29 20:05:53 raspberrypi systemd[1]: Started Mosquitto MQTT Broker.
Mar 29 20:05:56 raspberrypi mosquitto[3588]: 1617062756: New connection from ::1:60099 on port 1883.
Mar 29 20:05:56 raspberrypi mosquitto[3588]: 1617062756: New client connected from ::1:60099 as weewx_4d16f70b (p2, c1, k60, u'tph06784').
Mar 29 20:05:56 raspberrypi mosquitto[3588]: 1617062756: Client weewx_4d16f70b disconnected.
Mar 29 20:05:59 raspberrypi mosquitto[3588]: 1617062759: New connection from ::1:56299 on port 1883.
Mar 29 20:05:59 raspberrypi mosquitto[3588]: 1617062759: New client connected from ::1:56299 as weewx_261662b3 (p2, c1, k60, u'tph06784').
lines 1-23
Thanks.


Reply all
Reply to author
Forward
0 new messages