Hi Gary,
It’s no trouble at all. I sincerely appreciate all the help you are providing and am not in a rush. Truthfully, my time is fairly limited for this. I’ve been trying to respond to everyone as timely as possible. I have a three year old and a 4 month old, so my day time hours to tinker with this are limited! As for your questions: It is a GW1100, the newer model. Firmware is GW1100B_V2.0.4 when I run the sensors command with debug 3 I get this output in the debug.log file Sep 25 09:42:15 weewx weewx[86253] DEBUG __main__: Sending packet 'FF FF 26 03 29' to '192.168.0.200:45000'-truncated by __main__ Sep 25 09:42:15 weewx weewx[86253] DEBUG __main__: Received response 'FF FF 26 09 E8 DB 84 E7 23 6C EC'-truncated by __main__ Sep 25 09:42:15 weewx weewx[86253] DEBUG __main__: Sending packet 'FF FF 30 03 33' to '192.168.0.200:45000'-truncated by __main__ Sep 25 09:42:15 weewx weewx[86253] DEBUG __main__: Received response 'FF FF 30 0B 02 01 61 4F 6E A2 27 01 26'-truncated by __main__ Sep 25 09:42:15 weewx weewx[86253] DEBUG __main__: Sending packet 'FF FF 3C 03 3F' to '192.168.0.200:45000'-truncated by __main__ I don’t see anything in the debug log after running the firmware version command, and I didn’t see anything after running the live data command, which is weird. Is this the right location for the log? Thanks Evan On Saturday, September 25, 2021 at 9:44:28 AM UTC-4 Cameron D wrote: > I am pretty sure the semicolon is *not *what you want with Bourne shell > syntax. > > 1. with no semicolon, the variable is placed in the environment of the > program being executed > 2. with a semicolon, it is a simple assignment to a variable in the > environment of the current shell and is *not *passed onto the program > being executed > > I tend to make things clearer by assigning/exporting it to the environment > on a line on its own, then run the command and then, if necessary, remove > it if it is going to interfere with subsequent commands. > > On Saturday, 25 September 2021 at 4:39:38 am UTC+10 matthew wall wrote: > >> actually, i get the same behavior with either bash or ksh, at least on an >> old macos system (10.14.6) - the semicolon is necessary. same thing on a >> modern debian system. >> >> so i guess the semicolon is necessary! all the many times i have done >> that before i must have been in the PYTHONPATH directory, or in a directory >> that weewx resolves in its sys/os path magic at the beginning of each entry >> point. >> > -- 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/df3b9dfb-96f5-4412-8544-991a726ca5ddn%40googlegroups.com.
