you probably need to define the units/unit group for pm4_0 in
extensions.py 😎
On 01.08.2024 08:08, j.fri...@gmail.com wrote:
Hi Gary,
the v0.6.3b1 works wery well. There is only one possible issue with
PMI 4. index.html page shows it in other way then others values .
Thank you very much for your help.
Jarda
*Outout from the driver :*
'pm1_0': '9.5', 'pm1_0_24h_avg': '1.5', 'pm2_55': '10.6',
'pm2_55_24h_avg': '2.5', 'pm4_0': '11.0', 'pm4_0_24h_avg': '3.2',
'pm10_0': '11.2', 'pm10_0_24h_avg': '3.6'
*Database values :*
PM1.0 = 10.6333333333333
PM2.5 = 11.7
PM4.0 = 12.0666666666667
PM10 = 12.2666666666667
*Index.html page :*
Výstřižek.PNG
Dne úterý 30. července 2024 v 13:51:16 UTC+2 uživatel gjr80 napsal:
You can try v0.6.3b1 which includes support for the WH46 air
quality sensor. If a WH46 is connected the v0.6.3 driver should
emit the same temperature, PM2.5, PM10 and CO2 fields as with a
WH45. Additional fields pm1_0, pm1_0_24h_avg, pm4_0,
pm4_0_24h_avg should also be emitted with the WH46 PM1 and PM4
data and 24hour averages respectively. v0.6.3 should also
automatically determine whether a WH45 or WH46 is present and
correctly name WH45/WH46 battery and signal state fields.
Note that I have had to change the names of a the PM10 fields
emitted by the driver when used with a WH45 sensor. This will only
affect you if you previously used a WH45 sensor. The driver now
emits pm10_0 and pm10_0_24h_avg fields (previously the fields were
pm10 and pm10_24h_avg). Users who have previously used a WH45
sensor will need to either change their field map if mapping these
fields to some other WeeWX field, or if the pm10 and
pm10_24h_avgfields are used in the database schema the database
fields will need to be renamed to the new field names.
v0.6.3 also includes support for the WS85 sensor array as well as
including a revised approach to device discovery that is much more
reliable than the previous approach. Note the recommended approach
remains to specify the device IP address in the WeeWX config file
rather than have the driver rely on discovery
I have not released v0.6.3 yet, rather I have kept it at b1 until
someone verifies it's use it with a WH45/46. If you wish to try
v0.6.3b1 the following instructions should be used:
1. Rename your existing gateway driver to gw1000_0_6_1.pyso you
can easily revert if necessary:
$ cp /etc/weewx/bin/user/gw1000.py /etc/weewx/bin/user/gw1000_0_6_1.py
2. Download the v0.6.3b1 driver file and save it to
/etc/weewx/bin/user:
$ wget -P /etc/weewx/bin/user
https://raw.githubusercontent.com/gjr80/weewx-gw1000/v0.6.3/bin/user/gw1000.py
3. You can run the driver directly as you did in you OP, you
should see the WH46 obs fields as well as WH46 battery and signal
state data. You might also find using the --live-data option
useful when running the driver directly.
4. If you are happy running the driver directly you can restart
WeeWX and it will pick up the v0.6.3 driver.
Note the above commands may require prefixing with sudo. If you
need to revert to your original driver just delete
/etc/weewx/bin/user/gw1000.py and rename
/etc/weewx/bin/user/gw1000_0_6_1.py to /etc/weewx/bin/user/gw1000.py.
If any problems please let me know.
Gary
On Monday 29 July 2024 at 22:55:21 UTC+10 j.fri...@gmail.com wrote:
Hello,
I added new WH46 to my Ecowitt system. I can view data in
ecowitt.net <http://ecowitt.net> and in mobile application too.
My main system is weewx https://pocasi.frimlovi.com but the
new WH46 data didn't appear automatically in dashboard.
If I run PYTHONPATH=/usr/share/weewx:/etc/weewx/bin python3
/etc/weewx/bin/user/gw1000.py --test-service
--ip-address=my_IP it shows data from all measures correctly
but from WH46 it shows only data about battery and signal -
'wh45_batt': '5', 'wh45_sig': '4'
I use the latest version of GW1000 driver - 0.6.1
I tryed to add data in weewx.conf - [[field_map_extensions]]
and in skin.conf in appearance but nothing changed.
Can you help me please ?
Thank you in advance.
Jarda
--
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/5d259c56-7ed4-46aa-8185-3b7fcb55c289n%40googlegroups.com
<https://groups.google.com/d/msgid/weewx-user/5d259c56-7ed4-46aa-8185-3b7fcb55c289n%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/b5c0dc8b-438c-4919-8f60-d99d23d71d84%40gmail.com.
