So with a modification to the parameters section I get: - Using configuration file /home/weewx/weewx.conf
Interrogating GW1000 at 192.168.1.234:45000 GW1000 frequency: 1 (868Mhz) GW1000 sensor type: 1 (WH65) GW1000 decoded UTC: 2020-07-28 07:52:28 UTC (1595922748) GW1000 timezone: 39 On Tue, 28 Jul 2020 at 07:41, steeple ian <steeple...@gmail.com> wrote: > Gary, > > This is my output (my GW1000 is 868MHz): - > > Using configuration file /home/weewx/weewx.conf > > Interrogating GW1000 at 192.168.1.234:45000 > > GW1000 frequency: 1 (Unknown) > GW1000 sensor type: 1 (WH65) > GW1000 decoded UTC: 2020-07-28 07:37:39 UTC (1595921859) > GW1000 timezone: 39 > > > > On Tue, 28 Jul 2020 at 02:41, gjr80 <gjroder...@gmail.com> wrote: > >> Yes, not surprised, am still working through sensor names and the API to >> get the code right. Fortunately, this disconnect does not affect the >> observational data only battery state field names and some of the >> 'informational' commands such as --system-params. Once I get the battery >> states into the loop packets they can be easily fixed (temporarily) with a >> few field map extensions. >> >> Gary >> >> On Tuesday, 28 July 2020 11:04:45 UTC+10, gary....@gmail.com wrote: >>> >>> Though this is not a WH65 >>> >>> I have a GW1000, WS68, WH40, WH32-EP, WH32B >>> >>> On Monday, July 27, 2020 at 8:58:54 PM UTC-4 gary....@gmail.com wrote: >>> >>>> This is a 915 MHz unit >>>> >>>> Interrogating GW1000 at 10.10.100.125:45000 >>>> >>>> GW1000 frequency: 2 (Unknown) >>>> GW1000 sensor type: 1 (WH65) >>>> GW1000 decoded UTC: 2020-07-27 20:57:43 UTC (1595883463) >>>> GW1000 timezone: 19 >>>> >>>> >>>> On Monday, July 27, 2020 at 8:53:36 PM UTC-4 gjr80 wrote: >>>> >>>>> v0.1.0b6 added the --system-params command line option to the driver >>>>> to display a number of GW1000 system parameters, eg: >>>>> >>>>> GW1000 frequency: 0 (433MHz) >>>>> GW1000 sensor type: 0 (WH24) >>>>> GW1000 decoded UTC: 2020-07-28 10:31:46 UTC (1595932306) >>>>> GW1000 timezone: 94 >>>>> >>>>> Whilst I know which byte to look at for the frequency, and what value >>>>> represents 433MHz as used on my GW1000, I do not know what value is used >>>>> to >>>>> represent operation on 868MHZ and 915MHz. Was wondering if any users of >>>>> v0.1.0b6 that use a GW1000 operating on 868MHz or 915MHZ could post the >>>>> frequency their GW1000 uses as well as the output from the following >>>>> command (adjusting python version and path as required): >>>>> >>>>> $ PYTHONPATH=/home/weewx/bin python -m user.gw1000 --system-params >>>>> >>>>> I don't believe any of the information is particularly sensitive, but >>>>> if you are concerned I really just need to know the frequncy your GW1000 >>>>> operates on as well as the line starting 'GW1000 frequency'. If you don't >>>>> know what frequency your GW1000 operates on it should be printed on the >>>>> back of your GW1000 (well at least mine is like that!) >>>>> >>>>> thanks, >>>>> Gary >>>>> >>>> -- >> 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/d6b32000-d7a8-483d-9822-6b47d24e1b23o%40googlegroups.com >> <https://groups.google.com/d/msgid/weewx-user/d6b32000-d7a8-483d-9822-6b47d24e1b23o%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CADASSaQBfUKcoBGaCz9aSQXdCXyHisWMujCMqRefMmh5qjYkKg%40mail.gmail.com.
