[weewx-development] Re: WeatherLink driver maintainer contact?
On Wednesday, August 7, 2019 at 8:11:01 AM UTC-5, mwall wrote: > > > hello scott, > > please post the complete driver here. i will do the diffs and merge it. > > Matthew, was there anything else you needed from me? I posted the driver to the list back in Sept...? Thanks, Scott -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-development+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/db348966-2c72-45e8-8dc0-e54b0194f81f%40googlegroups.com.
[weewx-development] Re: MQTTSubscribe with WeeWX 4.0.0.b8
I am now getting data from two of my MQTT sensors so I am not going to worry about the "b". Thanks again. On Tuesday, January 14, 2020 at 5:30:11 PM UTC-8, Rich Bell wrote: > > Great news! > Your memory is correct. But, in this case I am logging the exact payload - > before I decode it when running under python 3. > Since you are getting data, I will assume all is good until I hear > otherwise. And thank you for taking the leap and giving this a try. > Rich > > > On Tuesday, 14 January 2020 20:11:33 UTC-5, Ralph Underwood wrote: >> >> I put both the ' and : in quotes ( "," and ":") and I am getting some >> data from MQTT! >> >> I have another Rpi running NodeRed to watch the mqtt data and it is >> showing a continuous stream of data from two of the sensors with an >> occasional message from the third. Something else to sort out. >> >> My memory is getting bad - in the message below I see the "b" which I >> think indicates a unicode problem, which I solved in my standalone >> subscription program by adding 'decode' here and there a month ago a >> suggestion from Tom K. >> DEBUG user.MQTTSubscribe: MessageCallbackProvider For weather has QOS of >> 0 and retain of 0 received:* b*'TIME:0,soilTemp3:14.68,INHU:40.00' >> >> Thanks for the help! >> >> >> On Tuesday, January 14, 2020 at 4:37:56 PM UTC-8, Rich Bell wrote: >>> >>> Ralph, >>> My first guess is that it doesn’t like the comma in the config for the >>> delimiter. This is based on this line the log. >>> Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Message >>> callback config is {'type': 'keyword', 'keyword_delimiter': [], >>> 'keyword_separator': ':', 'label_map': {'soilTemp3': 'soilTemp3', >>> 'soilTemp2': 'soilTemp2', 'tempSoil1': 'soilTemp1'}} >>> It is showing the delimiter as an empty list. I’d have to run a few >>> tests to confirm and determine what is needed to change. Unfortunately a >>> busy few days here. In the meantime you could try quoting it... >>> Rich >>> >> -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-development+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/39636988-5a3a-4638-a12c-3a99e9d47577%40googlegroups.com.
[weewx-development] Re: MQTTSubscribe with WeeWX 4.0.0.b8
Great news! Your memory is correct. But, in this case I am logging the exact payload - before I decode it when running under python 3. Since you are getting data, I will assume all is good until I hear otherwise. And thank you for taking the leap and giving this a try. Rich On Tuesday, 14 January 2020 20:11:33 UTC-5, Ralph Underwood wrote: > > I put both the ' and : in quotes ( "," and ":") and I am getting some > data from MQTT! > > I have another Rpi running NodeRed to watch the mqtt data and it is > showing a continuous stream of data from two of the sensors with an > occasional message from the third. Something else to sort out. > > My memory is getting bad - in the message below I see the "b" which I > think indicates a unicode problem, which I solved in my standalone > subscription program by adding 'decode' here and there a month ago a > suggestion from Tom K. > DEBUG user.MQTTSubscribe: MessageCallbackProvider For weather has QOS of 0 > and retain of 0 received:* b*'TIME:0,soilTemp3:14.68,INHU:40.00' > > Thanks for the help! > > > On Tuesday, January 14, 2020 at 4:37:56 PM UTC-8, Rich Bell wrote: >> >> Ralph, >> My first guess is that it doesn’t like the comma in the config for the >> delimiter. This is based on this line the log. >> Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Message >> callback config is {'type': 'keyword', 'keyword_delimiter': [], >> 'keyword_separator': ':', 'label_map': {'soilTemp3': 'soilTemp3', >> 'soilTemp2': 'soilTemp2', 'tempSoil1': 'soilTemp1'}} >> It is showing the delimiter as an empty list. I’d have to run a few tests >> to confirm and determine what is needed to change. Unfortunately a busy few >> days here. In the meantime you could try quoting it... >> Rich >> > -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-development+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/231ff455-8c3e-4f64-935c-3b2df0cee872%40googlegroups.com.
[weewx-development] Re: MQTTSubscribe with WeeWX 4.0.0.b8
I put both the ' and : in quotes ( "," and ":") and I am getting some data from MQTT! I have another Rpi running NodeRed to watch the mqtt data and it is showing a continuous stream of data from two of the sensors with an occasional message from the third. Something else to sort out. My memory is getting bad - in the message below I see the "b" which I think indicates a unicode problem, which I solved in my standalone subscription program by adding 'decode' here and there a month ago a suggestion from Tom K. DEBUG user.MQTTSubscribe: MessageCallbackProvider For weather has QOS of 0 and retain of 0 received:* b*'TIME:0,soilTemp3:14.68,INHU:40.00' Thanks for the help! On Tuesday, January 14, 2020 at 4:37:56 PM UTC-8, Rich Bell wrote: > > Ralph, > My first guess is that it doesn’t like the comma in the config for the > delimiter. This is based on this line the log. > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Message > callback config is {'type': 'keyword', 'keyword_delimiter': [], > 'keyword_separator': ':', 'label_map': {'soilTemp3': 'soilTemp3', > 'soilTemp2': 'soilTemp2', 'tempSoil1': 'soilTemp1'}} > It is showing the delimiter as an empty list. I’d have to run a few tests > to confirm and determine what is needed to change. Unfortunately a busy few > days here. In the meantime you could try quoting it... > Rich > -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-development+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/472a3612-f585-4ef3-97cb-a76f217b2262%40googlegroups.com.
[weewx-development] Re: MQTTSubscribe with WeeWX 4.0.0.b8
Or since a comma is the default, comment it out for now. Rich On Tuesday, 14 January 2020 19:37:56 UTC-5, Rich Bell wrote: > > Ralph, > My first guess is that it doesn’t like the comma in the config for the > delimiter. This is based on this line the log. > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Message > callback config is {'type': 'keyword', 'keyword_delimiter': [], > 'keyword_separator': ':', 'label_map': {'soilTemp3': 'soilTemp3', > 'soilTemp2': 'soilTemp2', 'tempSoil1': 'soilTemp1'}} > It is showing the delimiter as an empty list. I’d have to run a few tests > to confirm and determine what is needed to change. Unfortunately a busy few > days here. In the meantime you could try quoting it... > Rich > > > On Tuesday, 14 January 2020 18:51:01 UTC-5, Ralph Underwood wrote: > > I have been working on getting *MQTTSubscribe* working on my development > station (RPi3 with Buster) running WeeWx 4.0.0.b8. I think I have managed > to get Python3 versions of all of the prerequisites for WeeWx and > MQTTSubscribe. I am using the Simulator as the driver, MQTTSubscribe as a > service. > > > Thanks for any help! > Ralph > > > *I'm getting a lot of messages - these standout to me:* > Jan 14 15:29:19 TestPi weewx[5118] DEBUG user.MQTTSubscribe: > MessageCallbackProvider For weather has QOS of 0 and retain of 0 received: > b'TIME:0,soilTemp3:14.68,INHU:40.00' > Jan 14 15:29:19 TestPi weewx[5118] ERROR user.MQTTSubscribe: > MessageCallbackProvider on_message_keyword failed with: must be str or > None, not list > Jan 14 15:29:19 TestPi weewx[5118] ERROR user.MQTTSubscribe: > MessageCallbackProvider Ignoring topic=weather and > payload=b'TIME:0,soilTemp3:14.68,INHU:40.00' > > > *This is log after a WeeWx restart:* > Jan 14 15:39:39 TestPi systemd[1]: Starting LSB: weewx weather system... > Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: Initializing weewx > version 4.0.0b8 > Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: Using Python 3.7.3 > (default, Apr 3 2019, 05:39:12) #012[GCC 8.2.0] > Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: Platform > Linux-4.19.75-v7+-armv7l-with-debian-10.1 > Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: Locale is > 'en_US.UTF-8' > Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: PID file is > /var/run/weewx.pid > Jan 14 15:39:40 TestPi weewx[5256] INFO weewx.engine: Using configuration > file /home/weewx/weewx.conf > Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Debug is 1 > Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Initializing engine > Jan 14 15:39:40 TestPi weewx[5256] INFO weewx.engine: Loading station type > Simulator (weewx.drivers.simulator) > Jan 14 15:39:40 TestPi weewx[5241]: Starting weewx weather system: weewx. > Jan 14 15:39:40 TestPi systemd[1]: Started LSB: weewx weather system. > Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Loading service > weewx.engine.StdTimeSynch > Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Finished loading > service weewx.engine.StdTimeSynch > Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Loading service > user.MQTTSubscribe.MQTTSubscribeService > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Service > binding is loop > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Overlap is 0.0 > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: TopicManager > config is {'unit_system': 'US', 'overlap': 0.0, 'weather': {}} > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Message > callback config is {'type': 'keyword', 'keyword_delimiter': [], > 'keyword_separator': ':', 'label_map': {'soilTemp3': 'soilTemp3', > 'soilTemp2': 'soilTemp2', 'tempSoil1': 'soilTemp1'}} > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Message > callback provider is user.MQTTSubscribe.MessageCallbackProvider > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Client id is > MQTTSubscribe-7942 > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Clean session > is True > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: MQTTSubscribe > version is 1.4.0 > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Host is > 192.168.7.37 > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Port is 1883 > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Keep alive is > 60 > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Username is > None > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Password is > not set > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Archive topic > is None > Jan 14 15:39:40 TestPi weewx[5256] DEBUG user.MQTTSubscribe: Starting loop > Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Finished loading > service user.MQTTSubscribe.MQTTSubscribeService > Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Loading service > weewx.engine.StdConvert > Jan 14 15:39:40 T
[weewx-development] Re: MQTTSubscribe with WeeWX 4.0.0.b8
Ralph, My first guess is that it doesn’t like the comma in the config for the delimiter. This is based on this line the log. Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Message callback config is {'type': 'keyword', 'keyword_delimiter': [], 'keyword_separator': ':', 'label_map': {'soilTemp3': 'soilTemp3', 'soilTemp2': 'soilTemp2', 'tempSoil1': 'soilTemp1'}} It is showing the delimiter as an empty list. I’d have to run a few tests to confirm and determine what is needed to change. Unfortunately a busy few days here. In the meantime you could try quoting it... Rich On Tuesday, 14 January 2020 18:51:01 UTC-5, Ralph Underwood wrote: > > I have been working on getting *MQTTSubscribe* working on my development > station (RPi3 with Buster) running WeeWx 4.0.0.b8. I think I have managed > to get Python3 versions of all of the prerequisites for WeeWx and > MQTTSubscribe. I am using the Simulator as the driver, MQTTSubscribe as a > service. > > > Thanks for any help! > Ralph > > > *I'm getting a lot of messages - these standout to me:* > Jan 14 15:29:19 TestPi weewx[5118] DEBUG user.MQTTSubscribe: > MessageCallbackProvider For weather has QOS of 0 and retain of 0 received: > b'TIME:0,soilTemp3:14.68,INHU:40.00' > Jan 14 15:29:19 TestPi weewx[5118] ERROR user.MQTTSubscribe: > MessageCallbackProvider on_message_keyword failed with: must be str or > None, not list > Jan 14 15:29:19 TestPi weewx[5118] ERROR user.MQTTSubscribe: > MessageCallbackProvider Ignoring topic=weather and > payload=b'TIME:0,soilTemp3:14.68,INHU:40.00' > > > *This is log after a WeeWx restart:* > Jan 14 15:39:39 TestPi systemd[1]: Starting LSB: weewx weather system... > Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: Initializing weewx > version 4.0.0b8 > Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: Using Python 3.7.3 > (default, Apr 3 2019, 05:39:12) #012[GCC 8.2.0] > Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: Platform > Linux-4.19.75-v7+-armv7l-with-debian-10.1 > Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: Locale is > 'en_US.UTF-8' > Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: PID file is > /var/run/weewx.pid > Jan 14 15:39:40 TestPi weewx[5256] INFO weewx.engine: Using configuration > file /home/weewx/weewx.conf > Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Debug is 1 > Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Initializing engine > Jan 14 15:39:40 TestPi weewx[5256] INFO weewx.engine: Loading station type > Simulator (weewx.drivers.simulator) > Jan 14 15:39:40 TestPi weewx[5241]: Starting weewx weather system: weewx. > Jan 14 15:39:40 TestPi systemd[1]: Started LSB: weewx weather system. > Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Loading service > weewx.engine.StdTimeSynch > Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Finished loading > service weewx.engine.StdTimeSynch > Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Loading service > user.MQTTSubscribe.MQTTSubscribeService > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Service > binding is loop > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Overlap is 0.0 > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: TopicManager > config is {'unit_system': 'US', 'overlap': 0.0, 'weather': {}} > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Message > callback config is {'type': 'keyword', 'keyword_delimiter': [], > 'keyword_separator': ':', 'label_map': {'soilTemp3': 'soilTemp3', > 'soilTemp2': 'soilTemp2', 'tempSoil1': 'soilTemp1'}} > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Message > callback provider is user.MQTTSubscribe.MessageCallbackProvider > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Client id is > MQTTSubscribe-7942 > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Clean session > is True > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: MQTTSubscribe > version is 1.4.0 > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Host is > 192.168.7.37 > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Port is 1883 > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Keep alive is > 60 > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Username is > None > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Password is > not set > Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Archive topic > is None > Jan 14 15:39:40 TestPi weewx[5256] DEBUG user.MQTTSubscribe: Starting loop > Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Finished loading > service user.MQTTSubscribe.MQTTSubscribeService > Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Loading service > weewx.engine.StdConvert > Jan 14 15:39:40 TestPi weewx[5256] INFO weewx.engine: StdConvert target > unit is 0x1 > Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Finished loading > servi
[weewx-development] MQTTSubscribe with WeeWX 4.0.0.b8
I have been working on getting *MQTTSubscribe* working on my development station (RPi3 with Buster) running WeeWx 4.0.0.b8. I think I have managed to get Python3 versions of all of the prerequisites for WeeWx and MQTTSubscribe. I am using the Simulator as the driver, MQTTSubscribe as a service. Thanks for any help! Ralph *I'm getting a lot of messages - these standout to me:* Jan 14 15:29:19 TestPi weewx[5118] DEBUG user.MQTTSubscribe: MessageCallbackProvider For weather has QOS of 0 and retain of 0 received: b'TIME:0,soilTemp3:14.68,INHU:40.00' Jan 14 15:29:19 TestPi weewx[5118] ERROR user.MQTTSubscribe: MessageCallbackProvider on_message_keyword failed with: must be str or None, not list Jan 14 15:29:19 TestPi weewx[5118] ERROR user.MQTTSubscribe: MessageCallbackProvider Ignoring topic=weather and payload=b'TIME:0,soilTemp3:14.68,INHU:40.00' *This is log after a WeeWx restart:* Jan 14 15:39:39 TestPi systemd[1]: Starting LSB: weewx weather system... Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: Initializing weewx version 4.0.0b8 Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: Using Python 3.7.3 (default, Apr 3 2019, 05:39:12) #012[GCC 8.2.0] Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: Platform Linux-4.19.75-v7+-armv7l-with-debian-10.1 Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: Locale is 'en_US.UTF-8' Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: PID file is /var/run/weewx.pid Jan 14 15:39:40 TestPi weewx[5256] INFO weewx.engine: Using configuration file /home/weewx/weewx.conf Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Debug is 1 Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Initializing engine Jan 14 15:39:40 TestPi weewx[5256] INFO weewx.engine: Loading station type Simulator (weewx.drivers.simulator) Jan 14 15:39:40 TestPi weewx[5241]: Starting weewx weather system: weewx. Jan 14 15:39:40 TestPi systemd[1]: Started LSB: weewx weather system. Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Loading service weewx.engine.StdTimeSynch Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Finished loading service weewx.engine.StdTimeSynch Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Loading service user.MQTTSubscribe.MQTTSubscribeService Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Service binding is loop Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Overlap is 0.0 Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: TopicManager config is {'unit_system': 'US', 'overlap': 0.0, 'weather': {}} Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Message callback config is {'type': 'keyword', 'keyword_delimiter': [], 'keyword_separator': ':', 'label_map': {'soilTemp3': 'soilTemp3', 'soilTemp2': 'soilTemp2', 'tempSoil1': 'soilTemp1'}} Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Message callback provider is user.MQTTSubscribe.MessageCallbackProvider Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Client id is MQTTSubscribe-7942 Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Clean session is True Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: MQTTSubscribe version is 1.4.0 Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Host is 192.168.7.37 Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Port is 1883 Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Keep alive is 60 Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Username is None Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Password is not set Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Archive topic is None Jan 14 15:39:40 TestPi weewx[5256] DEBUG user.MQTTSubscribe: Starting loop Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Finished loading service user.MQTTSubscribe.MQTTSubscribeService Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Loading service weewx.engine.StdConvert Jan 14 15:39:40 TestPi weewx[5256] INFO weewx.engine: StdConvert target unit is 0x1 Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Finished loading service weewx.engine.StdConvert Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Loading service weewx.engine.StdCalibrate Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Finished loading service weewx.engine.StdCalibrate Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Loading service weewx.engine.StdQC Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Finished loading service weewx.engine.StdQC Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Loading service weewx.wxservices.StdWXCalculate Jan 14 15:39:40 TestPi weewx[5256] DEBUG user.MQTTSubscribe: Connected with result code 0 Jan 14 15:39:40 TestPi weewx[5256] DEBUG user.MQTTSubscribe: Connected flags {'session present': 0} Jan 14 15:39:40 TestPi weewx[5256] DEBUG user.MQTTSubscribe: Subscribe to weather has a mid 1 and rc 0 Jan 14 1
Re: [weewx-development] MQTTSubscribe.py installing as service
I am using WeeWx 4.0.0.b8 (latest development version) and I copied MQTTSubscribe from your GitHub. I did not install via wee_extension. My plan was to replace my standalone python program which subscribes to MQTT and writes a file for the filepile.py extension. I converted it to Python3 so with WeeWx 4 I will be all Python3. That has worked fine on one of my stations, however my program does not have a queue and only handles one MQTT message and I want to add more MQTT sensors to the stations. I have a separate development station that I am working with to get MQTTSubscribe working. I am going to start over with a clean installation and use wee-extension to install MQTTSubscribe. It's snowing here in Seattle, so I should have some time to experiment. I will start a new thread to report success or ask for help - I didn't notice that there were 5 pages on this thread before I asked about running as a service. On Tuesday, January 14, 2020 at 12:02:43 PM UTC-8, Rich Bell wrote: > > Ralph, > What version of WeeWX and MQTTSubscribe? Did you install via > wee_extension? If you post a copy of your config (making sure to remove any > sensitive information), I’d be happy to take a look. > We should probably move this out of the wxMesh thread... > Rich > > > -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-development+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/70eea334-56d2-4a26-a102-5170bb26988f%40googlegroups.com.
Re: [weewx-development] MQTTSubscribe.py installing as service
Ralph, What version of WeeWX and MQTTSubscribe? Did you install via wee_extension? If you post a copy of your config (making sure to remove any sensitive information), I’d be happy to take a look. We should probably move this out of the wxMesh thread... Rich On Tuesday, 14 January 2020 14:48:03 UTC-5, Ralph Underwood wrote: > > I was replying to a post on an earlier page. I just found Rich's > MQTTSubscribe.py and have started to experiment with it as a service. > > I managed to get to this: > > Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: Caught > unrecoverable exception: > Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: Empty > module name > Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: > Traceback (most recent call last): > Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: File > "/home/weewx/bin/weewx/engine.py", line 897, in main > Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: > engine = StdEngine(config_dict) > Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: File > "/home/weewx/bin/weewx/engine.py", line 83, in __init__ > Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: > self.loadServices(config_dict) > Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: File > "/home/weewx/bin/weewx/engine.py", line 144, in loadServices > Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: > obj = weeutil.weeutil.get_object(svc)(self,config_dict) > Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: File > "/home/weewx/bin/weeutil/weeutil.py", line 1093, in get_object > Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: > mod = __import__(module) > Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: > ValueError: Empty module name > Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: > Exiting. > > Sleuthing begins. > -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-development+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/85171f1e-4b3d-46a1-a018-3428c6396843%40googlegroups.com.
Re: [weewx-development] MQTTSubscribe.py installing as service
I was replying to a post on an earlier page. I just found Rich's MQTTSubscribe.py and have started to experiment with it as a service. I managed to get to this: Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: Caught unrecoverable exception: Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: Empty module name Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: Traceback (most recent call last): Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: File "/home/weewx/bin/weewx/engine.py", line 897, in main Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: engine = StdEngine(config_dict) Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: File "/home/weewx/bin/weewx/engine.py", line 83, in __init__ Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: self.loadServices(config_dict) Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: File "/home/weewx/bin/weewx/engine.py", line 144, in loadServices Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: obj = weeutil.weeutil.get_object(svc)(self,config_dict) Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: File "/home/weewx/bin/weeutil/weeutil.py", line 1093, in get_object Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: mod = __import__(module) Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: ValueError: Empty module name Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: Exiting. Sleuthing begins. -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-development+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/0f790eb9-5cea-4056-8614-bb3340238b14%40googlegroups.com.
Re: [weewx-development] Re: continuation of discussion on wxMesh MQTT
I am setting up a test station with WeeWx version 4 on a Rpi. I have three sensors publishing MQTT and I want to test the wxMesh driver. Can this be run as a service with the Simulator driver running? Thanks, Ralph -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-development+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/37afe49a-5f05-4fd9-a542-d92bc1e488d1%40googlegroups.com.