Re: [weewx-user] weewx V5 report not updating
Thanks. I don't really know what that link meant. I have just disabled the skin. That was easier. On Thursday, 7 September 2023 at 12:14:59 UTC+10 gary@gmail.com wrote: > You may wish to look at > https://github.com/Daveiano/weewx-wdc/issues/14 > > On Wednesday, September 6, 2023 at 6:30:21 PM UTC-4 Greg from Oz wrote: > >> # configuration file for the weewx-wdc skin >> SKIN_NAME = Weather Data Center >> SKIN_VERSION = 3.0.0 >> >> On Wednesday, 6 September 2023 at 23:52:14 UTC+10 gary@gmail.com >> wrote: >> >>> What version of WDC? I'm on 3.3.0 >>> >>> >>> On Monday, September 4, 2023 at 5:11:20 PM UTC-4 Greg from Oz wrote: >>> It was running for weeks. I only have 1 year of data. Something must have changed somewhere. I have disabled that skin and all is running as it was before. On Tuesday, 5 September 2023 at 06:38:50 UTC+10 gary@gmail.com wrote: > It'll only do that once. I only have data back to 2016, but it took a > long time to finish. Afterwards, just as quick as any other skin. > I think it is the NOAA reports. > > On Sunday, September 3, 2023 at 10:39:39 PM UTC-4 vince wrote: > >> Perhaps try turning WDC off and see if the problem goes away. >> Certainly a skin taking longer than your archive period to complete is >> going to cause havoc for your setup >> >> On Sunday, September 3, 2023 at 7:34:39 PM UTC-7 Greg from Oz wrote: >> >>> It has been doing it days >>> There were a lot of entries in the syslog. >>> >>> >>> On Monday, 4 September 2023 at 12:32:27 UTC+10 Graham Eddy wrote: >>> perhaps it was generating all reports, as from a clean slate, and in future it could just be incremental and less of an issue *⊣GE⊢* On 4 Sep 2023, at 12:10 pm, Greg from Oz wrote: I guess it was wdc: Sep 3 00:21:24 moonbi weewx[1440347] INFO weewx.cheetahgenerator: Generated 11 files for report WdcReport in 330.15 seconds -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/19d27c03-3d43-4534-a1b5-754eb5d76c36n%40googlegroups.com.
[weewx-user] Re: Sudden WeeWx crashing
Update: it was neither of those issues. My sdr.py was running fine for years the way it was. The issue seems to be that my sdr must have been picking up that PrologueTHPacket, which isn't even coming from any of my devices.I was monitoring rtl_433 yesterday, saw one instance of the PrologueTH scroll by. Today, it's not showing, and WeeWx is running and reporting just fine once again. I've previously set up my sdr / rtl_433 to only parse my own sensor_id packets. So I'm wondering if mayhaps the PrologueTH just happens to have the same sensor_id as mine, which caused it to throw a glitch? Thanks On Wednesday, 6 September 2023 at 16:00:38 UTC-4 gjr80 wrote: > Your error is in sdr.py, nothing to do with your hardware or rtl_433. Try > editing /usr/share/weewx/user/sdr.py, goto line 2690, it should be: > > pkt = Packet.add_identifiers(pkt, sensor_id, PrologueTHPacket.name) > > change it to read: > > pkt = Packet.add_identifiers(pkt, sensor_id, PrologueTHPacket.__name__) > > (that is a double underscore before and after name). Save the file and > restart WeeWX. > > Monitor the log and see how that goes. > > Gary > > On Wednesday, 6 September 2023 at 23:59:13 UTC+10 Elie R wrote: > >> Have been happily churning along with no issues on 4.10.2 >> >> Using SDR to capture from an Atlas sensor array, and a BME280 for >> pressure. >> >> Just out of the blue, WeeWx stopped reporting a few days ago. Tried >> rebooting and watching the log output. It starts off ok with the parsing of >> the BME280 pressure data, but then it suddenly throws the following error >> and exits: >> >> Sep 6 09:19:33 atlas weewx[2139] INFO weewx.engine: Main loop exiting. >> Shutting engine down. >> Sep 6 09:19:33 atlas weewx[2139] INFO user.sdr: shutdown process >> /usr/local/bin/rtl_433 -M utc -F json >> Sep 6 09:19:45 atlas weewx[2139] INFO user.sdr: timed out waiting for >> stderr-thread >> Sep 6 09:19:45 atlas weewx[2139] CRITICAL __main__: Caught unrecoverable >> exception: >> Sep 6 09:19:45 atlas weewx[2139] CRITICAL __main__: class >> PrologueTHPacket has no attribute 'name' >> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: Traceback >> (most recent call last): >> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File >> "/usr/share/weewx/weewxd", line 154, in main >> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: >> engine.run() >> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File >> "/usr/share/weewx/weewx/engine.py", line 208, in run >> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: for >> packet in self.console.genLoopPackets(): >> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File >> "/usr/share/weewx/user/sdr.py", line 3155, in genLoopPackets >> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: for >> packet in PacketFactory.create(lines): >> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File >> "/usr/share/weewx/user/sdr.py", line 3026, in create >> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: pkt = >> PacketFactory.parse_json(lines) >> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File >> "/usr/share/weewx/user/sdr.py", line 3042, in parse_json >> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: return >> parser.parse_json(obj) >> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File >> "/usr/share/weewx/user/sdr.py", line 2690, in parse_json >> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: pkt = >> Packet.add_identifiers(pkt, sensor_id, PrologueTHPacket.name) >> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: >> AttributeError: class PrologueTHPacket has no attribute 'name' >> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: Exiting. >> >> Any thoughts? I'm thinking my SDR dongle might have decided to give up >> the ghost? >> > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/bb023c5b-e72f-49d2-b24a-1c97ce8bb233n%40googlegroups.com.
[weewx-user] Re: Sudden WeeWx crashing
If the 'setup up my sdr / rtl_433' was done in via the [SDR] [[sensor_map]] stanza in weewx.conf then all you were doing was limiting what sensor data is passed onto WeeWX in loop packets; the SDR driver would still have processed all sensor packets provided by rtl_433, but only those that match the sensors defined in the [SDR] [[sensor_map]] are included in loop packets. There is a typo in line 2690 of the SDR driver version you are using, and if it receives any more PrologueTH packets from rtl_433 it will fail and cause WeeWX to exit. I am no rtl_433 expert, but you may be able to configure rtl_433 to ignore the PrologueTH packets and not pass them to SDR and avoid the error that way, but I suspect fixing the typo in sdr.py will be easier. Gary On Friday, 8 September 2023 at 00:04:03 UTC+10 Elie R wrote: > Update: it was neither of those issues. > My sdr.py was running fine for years the way it was. The issue seems to > be that my sdr must have been picking up that PrologueTHPacket, which isn't > even coming from any of my devices.I was monitoring rtl_433 yesterday, saw > one instance of the PrologueTH scroll by. Today, it's not showing, and > WeeWx is running and reporting just fine once again. > > I've previously set up my sdr / rtl_433 to only parse my own sensor_id > packets. So I'm wondering if mayhaps the PrologueTH just happens to have > the same sensor_id as mine, which caused it to throw a glitch? > > Thanks > > On Wednesday, 6 September 2023 at 16:00:38 UTC-4 gjr80 wrote: > >> Your error is in sdr.py, nothing to do with your hardware or rtl_433. >> Try editing /usr/share/weewx/user/sdr.py, goto line 2690, it should be: >> >> pkt = Packet.add_identifiers(pkt, sensor_id, PrologueTHPacket.name) >> >> change it to read: >> >> pkt = Packet.add_identifiers(pkt, sensor_id, PrologueTHPacket.__name__) >> >> (that is a double underscore before and after name). Save the file and >> restart WeeWX. >> >> Monitor the log and see how that goes. >> >> Gary >> >> On Wednesday, 6 September 2023 at 23:59:13 UTC+10 Elie R wrote: >> >>> Have been happily churning along with no issues on 4.10.2 >>> >>> Using SDR to capture from an Atlas sensor array, and a BME280 for >>> pressure. >>> >>> Just out of the blue, WeeWx stopped reporting a few days ago. Tried >>> rebooting and watching the log output. It starts off ok with the parsing of >>> the BME280 pressure data, but then it suddenly throws the following error >>> and exits: >>> >>> Sep 6 09:19:33 atlas weewx[2139] INFO weewx.engine: Main loop exiting. >>> Shutting engine down. >>> Sep 6 09:19:33 atlas weewx[2139] INFO user.sdr: shutdown process >>> /usr/local/bin/rtl_433 -M utc -F json >>> Sep 6 09:19:45 atlas weewx[2139] INFO user.sdr: timed out waiting for >>> stderr-thread >>> Sep 6 09:19:45 atlas weewx[2139] CRITICAL __main__: Caught >>> unrecoverable exception: >>> Sep 6 09:19:45 atlas weewx[2139] CRITICAL __main__: class >>> PrologueTHPacket has no attribute 'name' >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: Traceback >>> (most recent call last): >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File >>> "/usr/share/weewx/weewxd", line 154, in main >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: >>> engine.run() >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File >>> "/usr/share/weewx/weewx/engine.py", line 208, in run >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: for >>> packet in self.console.genLoopPackets(): >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File >>> "/usr/share/weewx/user/sdr.py", line 3155, in genLoopPackets >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: for >>> packet in PacketFactory.create(lines): >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File >>> "/usr/share/weewx/user/sdr.py", line 3026, in create >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: pkt = >>> PacketFactory.parse_json(lines) >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File >>> "/usr/share/weewx/user/sdr.py", line 3042, in parse_json >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: >>> return parser.parse_json(obj) >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File >>> "/usr/share/weewx/user/sdr.py", line 2690, in parse_json >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: pkt = >>> Packet.add_identifiers(pkt, sensor_id, PrologueTHPacket.name) >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: >>> AttributeError: class PrologueTHPacket has no attribute 'name' >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: Exiting. >>> >>> Any thoughts? I'm thinking my SDR dongle might have decided to give up >>> the ghost? >>> >> -- You received this message because you are subscribed to the Google
[weewx-user] Re: Sudden WeeWx crashing
Thanks Gary, I'll try correcting the typo on 2690 and see what happens. You are correct in your assumption, I was only including my sensor for WeeWx loop data. It's nothing new for me to see many random neighbour sensor packets when running rtl_433 (other stations, tpms sensors, other wireless thermometers including my own, etc), but the first time I've encountered these PrologueTH packets or any WeeWx hiccup. New neighbours? ;p On Thursday, 7 September 2023 at 14:44:18 UTC-4 gjr80 wrote: > If the 'setup up my sdr / rtl_433' was done in via the [SDR] > [[sensor_map]] stanza in weewx.conf then all you were doing was limiting > what sensor data is passed onto WeeWX in loop packets; the SDR driver would > still have processed all sensor packets provided by rtl_433, but only those > that match the sensors defined in the [SDR] [[sensor_map]] are included > in loop packets. There is a typo in line 2690 of the SDR driver version you > are using, and if it receives any more PrologueTH packets from rtl_433 it > will fail and cause WeeWX to exit. I am no rtl_433 expert, but you may be > able to configure rtl_433 to ignore the PrologueTH packets and not pass > them to SDR and avoid the error that way, but I suspect fixing the typo in > sdr.py will be easier. > > Gary > > On Friday, 8 September 2023 at 00:04:03 UTC+10 Elie R wrote: > >> Update: it was neither of those issues. >> My sdr.py was running fine for years the way it was. The issue seems to >> be that my sdr must have been picking up that PrologueTHPacket, which isn't >> even coming from any of my devices.I was monitoring rtl_433 yesterday, saw >> one instance of the PrologueTH scroll by. Today, it's not showing, and >> WeeWx is running and reporting just fine once again. >> >> I've previously set up my sdr / rtl_433 to only parse my own sensor_id >> packets. So I'm wondering if mayhaps the PrologueTH just happens to have >> the same sensor_id as mine, which caused it to throw a glitch? >> >> Thanks >> >> On Wednesday, 6 September 2023 at 16:00:38 UTC-4 gjr80 wrote: >> >>> Your error is in sdr.py, nothing to do with your hardware or rtl_433. >>> Try editing /usr/share/weewx/user/sdr.py, goto line 2690, it should be: >>> >>> pkt = Packet.add_identifiers(pkt, sensor_id, PrologueTHPacket.name) >>> >>> change it to read: >>> >>> pkt = Packet.add_identifiers(pkt, sensor_id, PrologueTHPacket.__name__) >>> >>> (that is a double underscore before and after name). Save the file and >>> restart WeeWX. >>> >>> Monitor the log and see how that goes. >>> >>> Gary >>> >>> On Wednesday, 6 September 2023 at 23:59:13 UTC+10 Elie R wrote: >>> Have been happily churning along with no issues on 4.10.2 Using SDR to capture from an Atlas sensor array, and a BME280 for pressure. Just out of the blue, WeeWx stopped reporting a few days ago. Tried rebooting and watching the log output. It starts off ok with the parsing of the BME280 pressure data, but then it suddenly throws the following error and exits: Sep 6 09:19:33 atlas weewx[2139] INFO weewx.engine: Main loop exiting. Shutting engine down. Sep 6 09:19:33 atlas weewx[2139] INFO user.sdr: shutdown process /usr/local/bin/rtl_433 -M utc -F json Sep 6 09:19:45 atlas weewx[2139] INFO user.sdr: timed out waiting for stderr-thread Sep 6 09:19:45 atlas weewx[2139] CRITICAL __main__: Caught unrecoverable exception: Sep 6 09:19:45 atlas weewx[2139] CRITICAL __main__: class PrologueTHPacket has no attribute 'name' Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: Traceback (most recent call last): Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File "/usr/share/weewx/weewxd", line 154, in main Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: engine.run() Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File "/usr/share/weewx/weewx/engine.py", line 208, in run Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: for packet in self.console.genLoopPackets(): Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File "/usr/share/weewx/user/sdr.py", line 3155, in genLoopPackets Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: for packet in PacketFactory.create(lines): Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File "/usr/share/weewx/user/sdr.py", line 3026, in create Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: pkt = PacketFactory.parse_json(lines) Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File "/usr/share/weewx/user/sdr.py", line 3042, in parse_json Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: return parser.parse_json(obj) Sep 6 09:19:46 atlas weewx[2139] CRITICAL __ma
[weewx-user] Re: Sudden WeeWx crashing
Have you configured the command line in weewx.conf to only use the drivers you require? Mine is just: cmd = rtl_433 -M utc -F json but you can change it to something like: cmd = rtl_433 -M utc -F json -R 32 -R 78 -R 190 -R 142 On Thursday, 7 September 2023 at 15:04:03 UTC+1 Elie R wrote: > Update: it was neither of those issues. > My sdr.py was running fine for years the way it was. The issue seems to > be that my sdr must have been picking up that PrologueTHPacket, which isn't > even coming from any of my devices.I was monitoring rtl_433 yesterday, saw > one instance of the PrologueTH scroll by. Today, it's not showing, and > WeeWx is running and reporting just fine once again. > > I've previously set up my sdr / rtl_433 to only parse my own sensor_id > packets. So I'm wondering if mayhaps the PrologueTH just happens to have > the same sensor_id as mine, which caused it to throw a glitch? > > Thanks > > On Wednesday, 6 September 2023 at 16:00:38 UTC-4 gjr80 wrote: > >> Your error is in sdr.py, nothing to do with your hardware or rtl_433. >> Try editing /usr/share/weewx/user/sdr.py, goto line 2690, it should be: >> >> pkt = Packet.add_identifiers(pkt, sensor_id, PrologueTHPacket.name) >> >> change it to read: >> >> pkt = Packet.add_identifiers(pkt, sensor_id, PrologueTHPacket.__name__) >> >> (that is a double underscore before and after name). Save the file and >> restart WeeWX. >> >> Monitor the log and see how that goes. >> >> Gary >> >> On Wednesday, 6 September 2023 at 23:59:13 UTC+10 Elie R wrote: >> >>> Have been happily churning along with no issues on 4.10.2 >>> >>> Using SDR to capture from an Atlas sensor array, and a BME280 for >>> pressure. >>> >>> Just out of the blue, WeeWx stopped reporting a few days ago. Tried >>> rebooting and watching the log output. It starts off ok with the parsing of >>> the BME280 pressure data, but then it suddenly throws the following error >>> and exits: >>> >>> Sep 6 09:19:33 atlas weewx[2139] INFO weewx.engine: Main loop exiting. >>> Shutting engine down. >>> Sep 6 09:19:33 atlas weewx[2139] INFO user.sdr: shutdown process >>> /usr/local/bin/rtl_433 -M utc -F json >>> Sep 6 09:19:45 atlas weewx[2139] INFO user.sdr: timed out waiting for >>> stderr-thread >>> Sep 6 09:19:45 atlas weewx[2139] CRITICAL __main__: Caught >>> unrecoverable exception: >>> Sep 6 09:19:45 atlas weewx[2139] CRITICAL __main__: class >>> PrologueTHPacket has no attribute 'name' >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: Traceback >>> (most recent call last): >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File >>> "/usr/share/weewx/weewxd", line 154, in main >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: >>> engine.run() >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File >>> "/usr/share/weewx/weewx/engine.py", line 208, in run >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: for >>> packet in self.console.genLoopPackets(): >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File >>> "/usr/share/weewx/user/sdr.py", line 3155, in genLoopPackets >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: for >>> packet in PacketFactory.create(lines): >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File >>> "/usr/share/weewx/user/sdr.py", line 3026, in create >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: pkt = >>> PacketFactory.parse_json(lines) >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File >>> "/usr/share/weewx/user/sdr.py", line 3042, in parse_json >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: >>> return parser.parse_json(obj) >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: File >>> "/usr/share/weewx/user/sdr.py", line 2690, in parse_json >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: pkt = >>> Packet.add_identifiers(pkt, sensor_id, PrologueTHPacket.name) >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: >>> AttributeError: class PrologueTHPacket has no attribute 'name' >>> Sep 6 09:19:46 atlas weewx[2139] CRITICAL __main__: Exiting. >>> >>> Any thoughts? I'm thinking my SDR dongle might have decided to give up >>> the ghost? >>> >> -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/708e08ca-2dbd-4420-b72c-dc10836d51edn%40googlegroups.com.
[weewx-user] Weewx Mqtt not totaling the rain count right
We got over .800" of rain and looks like Weewx mqtt skipped some of the
count for some reason, here is the script
Sep 7 14:40:10 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0,
retain: 0, payload: b'{"readings": {"rain_per_second": 0.0025905,
"pressure": 948.04, "temperature": 24.65, "humidity": 73.33,
"wind_direction": 90, "luminance": 16.12, "rain": 1.5543, "voltage": 0.0,
"wind_speed": 0}, "nickname": "river-wx", "model": "weather", "uid":
"e6614c311b62b034", "timestamp": "2023-09-07T18:40:05Z"}'
Sep 7 14:40:10 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
TopicManager data-> incoming enviro/river-wx: 'luminance': '16.12',
'outHumidity': '73.33', 'outTemp': '24.65', 'pressure': '948.04', 'rain':
'1.5543', 'windDir': '90.0', 'windSpeed': '0.0'
Sep 7 14:40:12 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
TopicManager data-> outgoing enviro/river-wx: 'dateTime':
'1694112010.9298928', 'luminance': '16.12', 'outHumidity': '73.33',
'outTemp': '24.65', 'pressure': '948.04', 'rain': '1.5543', 'usUnits':
'17', 'windDir': '90.0', 'windSpeed': '0.0'
Sep 7 14:40:12 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
data-> final loop packet is enviro/river-wx 2023-09-07 14:40:10 EDT
(1694112010): 'dateTime': '1694112010.9298928', 'luminance': '16.12',
'outHumidity': '73.33', 'outTemp': '24.65', 'pressure': '948.04', 'rain':
'1.5543', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
Sep 7 14:50:11 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0,
retain: 0, payload: b'{"readings": {"rain_per_second": 0.02331449,
"pressure": 949.13, "temperature": 19.46, "humidity": 78.25,
"wind_direction": 90, "luminance": 11.5, "rain": 13.9887, "voltage": 0.0,
"wind_speed": 0}, "nickname": "river-wx", "model": "weather", "uid":
"e6614c311b62b034", "timestamp": "2023-09-07T18:50:05Z"}'
Sep 7 14:50:11 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
TopicManager data-> incoming enviro/river-wx: 'luminance': '11.5',
'outHumidity': '78.25', 'outTemp': '19.46', 'pressure': '949.13', 'rain':
'12.4344', 'windDir': '90.0', 'windSpeed': '0.0'
Sep 7 14:50:13 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
TopicManager data-> outgoing enviro/river-wx: 'dateTime':
'1694112611.381946', 'luminance': '11.5', 'outHumidity': '78.25',
'outTemp': '19.46', 'pressure': '949.13', 'rain': '12.4344', 'usUnits':
'17', 'windDir': '90.0', 'windSpeed': '0.0'
Sep 7 14:50:13 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
data-> final loop packet is enviro/river-wx 2023-09-07 14:50:11 EDT
(1694112611): 'dateTime': '1694112611.381946', 'luminance': '11.5',
'outHumidity': '78.25', 'outTemp': '19.46', 'pressure': '949.13', 'rain':
'12.4344', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
Sep 7 15:00:10 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0,
retain: 0, payload: b'{"readings": {"rain_per_second": 0.01206888,
"pressure": 947.8, "temperature": 17.78, "humidity": 92.74,
"wind_direction": 90, "luminance": 55.23, "rain": 7.253399, "voltage": 0.0,
"wind_speed": 0}, "nickname": "river-wx", "model": "weather", "uid":
"e6614c311b62b034", "timestamp": "2023-09-07T19:00:06Z"}'
Sep 7 15:00:10 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
TopicManager data-> incoming enviro/river-wx: 'luminance': '55.23',
'outHumidity': '92.74', 'outTemp': '17.78', 'pressure': '947.8', 'rain':
'None', 'windDir': '90.0', 'windSpeed': '0.0'
Sep 7 15:00:11 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
TopicManager data-> outgoing enviro/river-wx: 'dateTime':
'1694113210.8160872', 'luminance': '55.23', 'outHumidity': '92.74',
'outTemp': '17.78', 'pressure': '947.8', 'rain': 'None', 'usUnits': '17',
'windDir': '90.0', 'windSpeed': '0.0'
Sep 7 15:00:11 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
data-> final loop packet is enviro/river-wx 2023-09-07 15:00:10 EDT
(1694113210): 'dateTime': '1694113210.8160872', 'luminance': '55.23',
'outHumidity': '92.74', 'outTemp': '17.78', 'pressure': '947.8', 'rain':
'None', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
Current Conditions ♦
Outside Temperature 73.3°F
Heat Index 74.8°F
Wind Chill 73.3°F
Dew Point 71.7°F
Outside Humidity 95%
Barometer 29.850 inHg (-0.049)
Wind 0 mph N/A ( N/A)
Rain Today 0.55 in
Rain Rate 0.00 in/h
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/cbcf37bc-4cf9-47f3-9584-5970cb2f8f0bn%40googlegroups.com.
[weewx-user] Re: Weewx Mqtt not totaling the rain count right
Based on the information provided here are my assumptions and guesses on
what might being happening.
At Sep 7 14:40:10 MQTTSubscribe received a json formatted MQTT message with
a rain value of 1.5543 and reported rain of 1.5543. Inches, mm, cm? Unsure,
but at this point probably not important.
At Sep 7 14:50:11 MQTTSubscribe received a json formatted MQTT message with
a rain value of 13.9887 and reported rain of 12.4344 (13.9887 - 1.5543).
So, MQTTSubscribe is probably configured to deal with rain as a cumulative
observation.
At Sep 7 15:00:10 MQTTSubscribe received a json formatted MQTT message with
a rain value of 7.253399. Going on the assumption that rain has been
configured as a cumulative value, the delta amount of rain received is
7.253399 - 13.9887, or -6.735301. Being a negative rainfall, MQTTSubscribe
reports a value of ‘None’.
So if my guesses that your sensor is reporting cumulative rain and
MQTTSubscribe is configured to calculate the delta, the first question to
answer is; why is the cumulative rain 13.9887 at Sep 7 14:50:11 and
7.253399 at Sep 7 15:00:10?
rich
On Thursday, 7 September 2023 at 19:09:26 UTC-4 kufuu wrote:
> We got over .800" of rain and looks like Weewx mqtt skipped some of the
> count for some reason, here is the script
>
> Sep 7 14:40:10 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0,
> retain: 0, payload: b'{"readings": {"rain_per_second": 0.0025905,
> "pressure": 948.04, "temperature": 24.65, "humidity": 73.33,
> "wind_direction": 90, "luminance": 16.12, "rain": 1.5543, "voltage": 0.0,
> "wind_speed": 0}, "nickname": "river-wx", "model": "weather", "uid":
> "e6614c311b62b034", "timestamp": "2023-09-07T18:40:05Z"}'
> Sep 7 14:40:10 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
> TopicManager data-> incoming enviro/river-wx: 'luminance': '16.12',
> 'outHumidity': '73.33', 'outTemp': '24.65', 'pressure': '948.04', 'rain':
> '1.5543', 'windDir': '90.0', 'windSpeed': '0.0'
> Sep 7 14:40:12 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
> TopicManager data-> outgoing enviro/river-wx: 'dateTime':
> '1694112010.9298928', 'luminance': '16.12', 'outHumidity': '73.33',
> 'outTemp': '24.65', 'pressure': '948.04', 'rain': '1.5543', 'usUnits':
> '17', 'windDir': '90.0', 'windSpeed': '0.0'
> Sep 7 14:40:12 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
> data-> final loop packet is enviro/river-wx 2023-09-07 14:40:10 EDT
> (1694112010): 'dateTime': '1694112010.9298928', 'luminance': '16.12',
> 'outHumidity': '73.33', 'outTemp': '24.65', 'pressure': '948.04', 'rain':
> '1.5543', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
>
> Sep 7 14:50:11 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0,
> retain: 0, payload: b'{"readings": {"rain_per_second": 0.02331449,
> "pressure": 949.13, "temperature": 19.46, "humidity": 78.25,
> "wind_direction": 90, "luminance": 11.5, "rain": 13.9887, "voltage": 0.0,
> "wind_speed": 0}, "nickname": "river-wx", "model": "weather", "uid":
> "e6614c311b62b034", "timestamp": "2023-09-07T18:50:05Z"}'
> Sep 7 14:50:11 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
> TopicManager data-> incoming enviro/river-wx: 'luminance': '11.5',
> 'outHumidity': '78.25', 'outTemp': '19.46', 'pressure': '949.13', 'rain':
> '12.4344', 'windDir': '90.0', 'windSpeed': '0.0'
> Sep 7 14:50:13 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
> TopicManager data-> outgoing enviro/river-wx: 'dateTime':
> '1694112611.381946', 'luminance': '11.5', 'outHumidity': '78.25',
> 'outTemp': '19.46', 'pressure': '949.13', 'rain': '12.4344', 'usUnits':
> '17', 'windDir': '90.0', 'windSpeed': '0.0'
> Sep 7 14:50:13 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
> data-> final loop packet is enviro/river-wx 2023-09-07 14:50:11 EDT
> (1694112611): 'dateTime': '1694112611.381946', 'luminance': '11.5',
> 'outHumidity': '78.25', 'outTemp': '19.46', 'pressure': '949.13', 'rain':
> '12.4344', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
>
> Sep 7 15:00:10 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0,
> retain: 0, payload: b'{"readings": {"rain_per_second": 0.01206888,
> "pressure": 947.8, "temperature": 17.78, "humidity": 92.74,
> "wind_direction": 90, "luminance": 55.23, "rain": 7.253399, "voltage": 0.0,
> "wind_speed": 0}, "nickname": "river-wx", "model": "weather", "uid":
> "e6614c311b62b034", "timestamp": "2023-09-07T19:00:06Z"}'
> Sep 7 15:00:10 zero-wx weewx[15766] DEBUG user.MQTTSubscribe: (Driver)
> TopicManager data-> incoming enviro/river-wx: 'luminance': '55.23',
> 'outHumidity': '92.74', 'outTemp': '17.78', 'pressure': '947.8', 'rain':
> 'None', 'windDir': '90.0', 'windSpeed': '0.0'
> Sep 7 15:00:11 zero-wx weewx[1
Re: [weewx-user] Re: weewx with rtl-davis - Installation Assistance?
It happens every night for me…
On Tuesday, September 5, 2023 at 7:48:45 AM UTC-4 Lorin Tremblay wrote:
> Having the same issue about once a day for 4-6 hours
>
> Sep 5 07:34:18 WeeWx-APRS270 weewx[610] INFO weewx.engine: Main loop
> exiting. Shutting engine down.
> Sep 5 07:34:18 WeeWx-APRS270 weewx[610] INFO user.rtldavis: shutdown
> process /home/pi/bin/rtldavis -ex 200 -tf US -tr 1
> Sep 5 07:34:18 WeeWx-APRS270 weewx[610] INFO user.rtldavis: rtldavis with
> pid 1847 killed
> Sep 5 07:34:18 WeeWx-APRS270 weewx[610] CRITICAL __main__: Caught
> WeeWxIOError: rtldavis process stalled
> Sep 5 07:34:18 WeeWx-APRS270 weewx[610] CRITICAL __main__:
> Waiting 60 seconds then retrying...
>
> On Thursday, August 10, 2023 at 4:05:04 PM UTC-4 vince wrote:
>
>> FWIW - I did get this to work on v5 beta with some tweaks in my install
>> script solely due to the weewx commands being a little different than v4
>> and earlier, but it was a little bit of a struggle here too. I had to do
>> a lot of plugging/unplugging the rtl_sdr dongle as it seemed to lock up
>> with device in use when I was trying to run things in the foreground.
>>
>> Eventually weewx succeed interactively before I tried it from systemd
>>
>> (weewx-venv) pi@pi4jr:~/weewx-data $ weewxd
>> LOOP: 2023-08-10 12:41:54 PDT (1691696514) 'altimeter': 'None',
>> 'appTemp': 'None', 'barometer': 'None', 'cloudbase': 'None', 'dateTime':
>> '1691696514', 'dewpoint': 'None', 'ET': 'None', 'heatindex': 'None',
>> 'humidex': 'None', 'inDewpoint': 'None', 'maxSolarRad': '0.0', 'pressure':
>> 'None', 'rainRate': '0.0', 'txBatteryStatus': '0', 'usUnits': '1',
>> 'windchill': 'None', 'windDir': '325.3162055335968', 'windrun': 'None',
>> 'windSpeed': '2.0'
>> LOOP: 2023-08-10 12:41:57 PDT (1691696517) 'altimeter': 'None',
>> 'appTemp': 'None', 'barometer': 'None', 'cloudbase': 'None', 'dateTime':
>> '1691696517', 'dewpoint': 'None', 'ET': 'None', 'heatindex': 'None',
>> 'humidex': 'None', 'inDewpoint': 'None', 'maxSolarRad': '0.0', 'outTemp':
>> '70.1', 'pressure': 'None', 'rainRate': '0.0', 'txBatteryStatus': '0',
>> 'usUnits': '1', 'windchill': '70.1', 'windDir': '325.3162055335968',
>> 'windrun': 'None', 'windSpeed': '2.0'
>>
>> In repeated previous repetitions I got the following and needed to
>> unplug/replug it to get it to release.
>>
>> (weewx-venv) pi@pi4jr:~/weewx-data $ rtldavis -tf US -v -tr 1
>> 12:40:37.537010 rtldavis.go VERSION=0.15
>> 12:40:37.537808 tr=1 fc=0 ppm=0 gain=0 maxmissed=51 ex=0
>> receiveWindow=300 actChan=[0] maxChan=1
>> 12:40:37.537957 undefined=false verbose=true disableAfc=false
>> deviceString=0
>> 12:40:37.539019 BitRate: 19200
>> 12:40:37.539132 SymbolLength: 14
>> 12:40:37.539222 SampleRate: 268800
>> 12:40:37.539704 Preamble: 1100101110001001
>> 12:40:37.539840 PreambleSymbols: 16
>> 12:40:37.539941 PreambleLength: 224
>> 12:40:37.540165 PacketSymbols: 80
>> 12:40:37.540687 PacketLength: 1120
>> 12:40:37.540778 BlockSize: 512
>> 12:40:37.540866 BufferLength: 2048
>> usb_claim_interface error -6
>> 12:40:37.603160 resource busy
>>
>> Also saw the same 'killed' thing you saw:
>>
>> (weewx-venv) pi@pi4jr:~/weewx-data $ rtldavis -tf US -v
>> 12:35:28.026250 rtldavis.go VERSION=0.15
>> 12:35:28.026668 tr=1 fc=0 ppm=0 gain=0 maxmissed=51 ex=0
>> receiveWindow=300 actChan=[0] maxChan=1
>> 12:35:28.026720 undefined=false verbose=true disableAfc=false
>> deviceString=0
>> 12:35:28.026986 BitRate: 19200
>> 12:35:28.027010 SymbolLength: 14
>> 12:35:28.027031 SampleRate: 268800
>> 12:35:28.027051 Preamble: 1100101110001001
>> 12:35:28.027071 PreambleSymbols: 16
>> 12:35:28.027091 PreambleLength: 224
>> 12:35:28.027111 PacketSymbols: 80
>> 12:35:28.027131 PacketLength: 1120
>> 12:35:28.027151 BlockSize: 512
>> 12:35:28.027171 BufferLength: 2048
>> Detached kernel driver
>> Found Rafael Micro R820T tuner
>> 12:35:28.488329 tr=0 ch=0 freqCorr=0 lastFreqError=0, freqerrTrChList=[0
>> 0 0 0 0 0 0 0 0 0]
>> 12:35:28.488722 Hop: {ChannelIdx:0 ChannelFreq:902419338 FreqError:0
>> Transmitter:0}
>> Exact sample rate is: 268800.001367 Hz
>> 12:35:28.667136 GetTunerGain: 0 Db
>> 12:35:28.667276 SetFreqCorrection 0 ppm Successful
>> 12:35:28.671473 Init channels: wait max 135 seconds for a message of each
>> transmitter
>> 12:37:30.504786 m1: -0.217316 l: 224 c: 16 x: [-0.31 -0.28 -0.30 -0.28
>> 0.21 0.19 0.11 -0.35 -0.34 -0.28 -0.33 -0.33 -0.30 -0.28 -0.31 -0.30]
>> 12:37:30.504885 TRANSMITTER 0 SEEN
>> 12:37:30.505103 tr=0 ch=19 freqCorr=0 lastFreqError=0, freqerrTrChList=[0
>> 0 0 0 0 0 0 0 0 0]
>> 12:37:30.505277 Hop: {ChannelIdx:19 ChannelFreq:911952597 FreqError:0
>> Transmitter:0}
>> 12:37:30.505324 applied freqCorrection=0
>> 12:37:33.068797 m1: -0.211359 l: 224 c: 16 x: [0.13 -0.32 -0.30 -0.28
>> -0.21 0.22 0.08 -0.37 -0.35 -0.33 -0.27 -0.27 -0.26 -0.29 -0.32 -0.26]
>> 12:37:33.068901 E000E9780100BE3D 2 0 0 0 0 msg.ID=0
>> 12:37:33.068981 tr=0 ch=41 freqCorr=0 lastFreqError=0, freqer
Re: [weewx-user] Re: weewx with rtl-davis - Installation Assistance?
Why are you setting -ex 200 ? The defaults worked fine for me for multiple days with a VP2 (one ISS), FWIW. On Thursday, September 7, 2023 at 8:16:53 PM UTC-7 Lorin Tremblay wrote: It happens every night for me… On Tuesday, September 5, 2023 at 7:48:45 AM UTC-4 Lorin Tremblay wrote: Having the same issue about once a day for 4-6 hours Sep 5 07:34:18 WeeWx-APRS270 weewx[610] INFO weewx.engine: Main loop exiting. Shutting engine down. Sep 5 07:34:18 WeeWx-APRS270 weewx[610] INFO user.rtldavis: shutdown process /home/pi/bin/rtldavis -ex 200 -tf US -tr 1 Sep 5 07:34:18 WeeWx-APRS270 weewx[610] INFO user.rtldavis: rtldavis with pid 1847 killed Sep 5 07:34:18 WeeWx-APRS270 weewx[610] CRITICAL __main__: Caught WeeWxIOError: rtldavis process stalled Sep 5 07:34:18 WeeWx-APRS270 weewx[610] CRITICAL __main__: Waiting 60 seconds then retrying... -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/758b20dd-db70-468f-b76c-bc3d90f20401n%40googlegroups.com.
Re: [weewx-user] Re: weewx with rtl-davis - Installation Assistance?
Don’t remember, but tried without it, still does the same thing and it always restart in the morning…… On Thursday, September 7, 2023 at 11:22:57 PM UTC-4 vince wrote: > Why are you setting -ex 200 ? > The defaults worked fine for me for multiple days with a VP2 (one ISS), > FWIW. > > On Thursday, September 7, 2023 at 8:16:53 PM UTC-7 Lorin Tremblay wrote: > > > It happens every night for me… > On Tuesday, September 5, 2023 at 7:48:45 AM UTC-4 Lorin Tremblay wrote: > > Having the same issue about once a day for 4-6 hours > > Sep 5 07:34:18 WeeWx-APRS270 weewx[610] INFO weewx.engine: Main loop > exiting. Shutting engine down. > Sep 5 07:34:18 WeeWx-APRS270 weewx[610] INFO user.rtldavis: shutdown > process /home/pi/bin/rtldavis -ex 200 -tf US -tr 1 > Sep 5 07:34:18 WeeWx-APRS270 weewx[610] INFO user.rtldavis: rtldavis with > pid 1847 killed > Sep 5 07:34:18 WeeWx-APRS270 weewx[610] CRITICAL __main__: Caught > WeeWxIOError: rtldavis process stalled > Sep 5 07:34:18 WeeWx-APRS270 weewx[610] CRITICAL __main__: > Waiting 60 seconds then retrying... > > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/f1deaaff-562d-4a6b-bf8a-10afc8dd5ed7n%40googlegroups.com.
