[weewx-user] Re: Ambient Weather WS-2902, GW-1000 Weekly Rain wrong.

[Dennis Isenberg]

With the help of my Son, we have it running.
The mqtt weekRain is in mm.  Not inch.
He created a template to convert it from mm to inch, and it is good now.

Also, daymaxwind was in Meters per Second.  So he converted to MPH.




On Thursday, September 10, 2020 at 2:08:38 PM UTC-5 Dennis Isenberg wrote:

> qLOOP:   2020-09-10 10:19:19 CDT (1599751159) altimeter: 30.4538968648, 
> appTemp: 44.3969758989, barometer: 30.474719126, beaufort: 2, cloudbase: 
> 1119.38247165, dateTime: 1599751159, daymaxwind: 7.1, dayRain: 
> 0.326771653543, dewpoint: 47.6615171247, extraTemp1: 103.64, heatindex: 
> 48.2, humidex: 49.462554089, inDewpoint: 50.3916531434, inHumidity: 54, 
> inTemp: 67.64, luminosity: 9563.0, maxSolarRad: None, monthRain: 
> 1.83858267717, outHumidity: 98, outTemp: 48.2, pressure: 29.3734785663, 
> rain: 0.0, rainRate: 0.0, relbarometer: 994.7, stormRain: 0.0, usUnits: 1, 
> UV: 0, uvradiation: 0.0, weekRain: 46.4, wh31_ch1_batt: 0, wh65_batt: 0, 
> windchill: 45.6240791662, windDir: 27, windGust: 6.93451974101, windSpeed: 
> 5.81604881504, yearRain: 1.83858267717
>
> Wireshark capture to ecowitt.net:
>
>
> PASSKEY=x=GW1000B_V1.6.3=2020-09-10+17:37:01=67.3=53=29.371=29.371=50.2=97=19=7.83=10.29=15.88=124.41=1=0.000=0.000=0.000=0.378=1.878=1.890=1.890=1.890=102.92=0=0=915M=GW1000_ProHTTP/1.1
>  
> 200 OK
>
> On Thursday, September 10, 2020 at 2:01:58 PM UTC-5 Dennis Isenberg wrote:
>
>> I have an Ambient Weather WS-2902.  I also have a GW-1000 wifi bridge.  
>> The Ws-2902 and GW-1000 both report proper weekly rain to ambient 
>> weather.com, and ecowitt.com.  Also to the WS View app.
>>
>> But, the MQTT send to my homeassistant reports weekRain that is way off.
>> Monthly rain looks good.
>>
>> the GW100 is sending weeklyrainin.
>> And monthlyrainin.
>> But, the MQTT is sending to homeassistant:
>> monthRain_in.  Which contains good data.
>> weekRain, which is bad data.
>>
>> Where do I start?
>> My son has the same setup, and the same results.
>>
>>
>>

-- 
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/60dc2e2d-9c24-4e77-a91d-cf0f25b39580n%40googlegroups.com.

[weewx-user] Re: Acurite Atlas Using sdr.py - No Output

[wxwatching]

I have the RTL-SDR Blog R820T2 RTL2832U 1PPM TCXO SMA Software Defined 
Radio that was purchased from Amazon:

https://www.amazon.com/gp/product/B0129EBDS2/ref=ppx_yo_dt_b_asin_title_o01_s00

-- 
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/1fd459b3-3b92-4de2-9f05-8e5ed4ef7756n%40googlegroups.com.

[weewx-user] Acurite Atlas Using sdr.py - No Output

[wxwatching]

I have installed the sdr.py driver to access my recently purchased Acurite 
Atlas. I have installed the rtl_433 driver from here:

https://github.com/merbanan/rtl_433

I ran this command:

sudo PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/sdr.py 
--cmd="rtl_433 -M utc -F json"
 
I get no output. Cursor just remains static.

I also ran the following command and this is the only output I get. Any 
suggestions on what I need to do to get this to work?

pi@raspberrypi:/ $ sudo rtl_433
rtl_433 version 20.02-145-gb091ab6 branch master at 202009071341 inputs 
file rtl_tcp RTL-SDR
Use -h for usage help and see https://triq.org/ for documentation.
Trying conf file at "rtl_433.conf"...
Trying conf file at "/root/.config/rtl_433/rtl_433.conf"...
Trying conf file at "/usr/local/etc/rtl_433/rtl_433.conf"...
Trying conf file at "/etc/rtl_433/rtl_433.conf"...
Registered 137 out of 166 device decoding protocols [ 1-4 8 11-12 
15-17 19-21 23 25-26 29-36 38-60 63 67-71 73-100 102-105 108-116 119 121 
124-128 130-149 151-161 163-166 ]
Detached kernel driver
Found Rafael Micro R820T tuner
Exact sample rate is: 25.000414 Hz
[R82XX] PLL not locked!
Sample rate set to 25 S/s.
Tuner gain set to Auto.
Tuned to 433.920MHz.
Allocating 15 zero-copy buffers

-- 
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/37a52853-6e6b-4516-aaa1-74064be64116n%40googlegroups.com.

[weewx-user] Re: Ambient Weather WS-2902, GW-1000 Weekly Rain wrong.

[Dennis Isenberg]

qLOOP:   2020-09-10 10:19:19 CDT (1599751159) altimeter: 30.4538968648, 
appTemp: 44.3969758989, barometer: 30.474719126, beaufort: 2, cloudbase: 
1119.38247165, dateTime: 1599751159, daymaxwind: 7.1, dayRain: 
0.326771653543, dewpoint: 47.6615171247, extraTemp1: 103.64, heatindex: 
48.2, humidex: 49.462554089, inDewpoint: 50.3916531434, inHumidity: 54, 
inTemp: 67.64, luminosity: 9563.0, maxSolarRad: None, monthRain: 
1.83858267717, outHumidity: 98, outTemp: 48.2, pressure: 29.3734785663, 
rain: 0.0, rainRate: 0.0, relbarometer: 994.7, stormRain: 0.0, usUnits: 1, 
UV: 0, uvradiation: 0.0, weekRain: 46.4, wh31_ch1_batt: 0, wh65_batt: 0, 
windchill: 45.6240791662, windDir: 27, windGust: 6.93451974101, windSpeed: 
5.81604881504, yearRain: 1.83858267717

Wireshark capture to ecowitt.net:

PASSKEY=x=GW1000B_V1.6.3=2020-09-10+17:37:01=67.3=53=29.371=29.371=50.2=97=19=7.83=10.29=15.88=124.41=1=0.000=0.000=0.000=0.378=1.878=1.890=1.890=1.890=102.92=0=0=915M=GW1000_ProHTTP/1.1
 
200 OK

On Thursday, September 10, 2020 at 2:01:58 PM UTC-5 Dennis Isenberg wrote:

> I have an Ambient Weather WS-2902.  I also have a GW-1000 wifi bridge.  
> The Ws-2902 and GW-1000 both report proper weekly rain to ambient 
> weather.com, and ecowitt.com.  Also to the WS View app.
>
> But, the MQTT send to my homeassistant reports weekRain that is way off.
> Monthly rain looks good.
>
> the GW100 is sending weeklyrainin.
> And monthlyrainin.
> But, the MQTT is sending to homeassistant:
> monthRain_in.  Which contains good data.
> weekRain, which is bad data.
>
> Where do I start?
> My son has the same setup, and the same results.
>
>
>

-- 
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/06038a07-ede4-4c43-a580-0c54637171f8n%40googlegroups.com.

[weewx-user] Ambient Weather WS-2902, GW-1000 Weekly Rain wrong.

[Dennis Isenberg]

I have an Ambient Weather WS-2902.  I also have a GW-1000 wifi bridge.  The 
Ws-2902 and GW-1000 both report proper weekly rain to ambient weather.com, 
and ecowitt.com.  Also to the WS View app.

But, the MQTT send to my homeassistant reports weekRain that is way off.
Monthly rain looks good.

the GW100 is sending weeklyrainin.
And monthlyrainin.
But, the MQTT is sending to homeassistant:
monthRain_in.  Which contains good data.
weekRain, which is bad data.

Where do I start?
My son has the same setup, and the same results.


-- 
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/c01f98fb-4b70-4683-8776-8cdc696fb9e4n%40googlegroups.com.

[weewx-user] Windy Plugin

[Michael Sanphillipo]

I just started sending data to Windy.com yesterday. I've checked and the 
data is being accepted but my PWS isn't showing anything. I have copied the 
data below it makes no sense to me, so possibly the plugin is sending bad 
data. My system details are as follows 
   
   - Station hardware: AcuRite 02032C
   - WeeWX version: 4.1.1
   - Belchertown Skin Version: 1.1
   - Windy  Station ID: f0689a3c  


This is the data: 

{"header":{"name":"Belcamp, 
MD","content":{"url":"https://belcampmdweather.tech/weewx/belchertown/","text":"ms372591"},"agl_temp":3,"agl_wind":3,"elev_m":27.43,"lat":39.47802588381403,"lon":-76.25279903411867,"stationType":"AcuRite
 

Re: [weewx-user] Monthly Summaries are empty

[icoj...@gmail.com]

I had the same symptom and deleting the NOAA txt files and allowing them to 
regenerate worked a treat (not that it helps with the OP's issue)

On Tuesday, 23 June 2020 at 14:48:45 UTC+1 tke...@gmail.com wrote:

> Hmmm, OK.
>
> A line is printed only if it contains one of temperature, rain, or wind. 
> It seems unlikely, but perhaps you are missing all three? To test that, in 
> the template NOAA-%Y-%m.txt.tmpl, change the lines
>
> #for $day in $month.days
> #if $day.outTemp.count.raw or $day.rain.count.raw or $day.wind.count.raw
> $day.dateTime.format($D, add_label=False) 
> $day.outTemp.avg.format($Temp,$NONE,add_label=False) 
> $day.outTemp.max.format($Temp,$NONE,add_label=False) 
> $day.outTemp.maxtime.format($Time,add_label=False) 
> $day.outTemp.min.format($Temp,$NONE,add_label=False) 
> $day.outTemp.mintime.format($Time,add_label=False) 
> $day.heatdeg.sum.format($Temp,$NONE,add_label=False) 
> $day.cooldeg.sum.format($Temp,$NONE,add_label=False) 
> $day.rain.sum.format($Rain,$NONE,add_label=False) 
> $day.wind.avg.format($Wind,$NONE,add_label=False) 
> $day.wind.max.format($Wind,$NONE,add_label=False) 
> $day.wind.maxtime.format($Time,add_label=False) 
> $day.wind.vecdir.format($Dir,$NONE,add_label=False)
> #else
> $day.dateTime.format($D)
> #end if
> #end for
>
> to
>
> #for $day in $month.days
> $day.dateTime.format($D, add_label=False) 
> $day.outTemp.avg.format($Temp,$NONE,add_label=False) 
> $day.outTemp.max.format($Temp,$NONE,add_label=False) 
> $day.outTemp.maxtime.format($Time,add_label=False) 
> $day.outTemp.min.format($Temp,$NONE,add_label=False) 
> $day.outTemp.mintime.format($Time,add_label=False) 
> $day.heatdeg.sum.format($Temp,$NONE,add_label=False) 
> $day.cooldeg.sum.format($Temp,$NONE,add_label=False) 
> $day.rain.sum.format($Rain,$NONE,add_label=False) 
> $day.wind.avg.format($Wind,$NONE,add_label=False) 
> $day.wind.max.format($Wind,$NONE,add_label=False) 
> $day.wind.maxtime.format($Time,add_label=False) 
> $day.wind.vecdir.format($Dir,$NONE,add_label=False)
> #end for
>
> This will print something for every line.
>
> -tk
>
> On Mon, Jun 22, 2020 at 4:42 PM John Pierce  wrote:
>
>>
>>
>> On Mon, Jun 22, 2020 at 4:51 AM Tom Keffer  wrote:
>>
>>> This is a known problem with v4.1.0. An upgrade to V4.1.1 will fix you 
>>> up.
>>>
>>> After the upgrade, delete all your NOAA files and let WeeWX 
>>> regenerate them.
>>>
>>
>> so I was already on 4.1.1...
>>
>>
>> well, I stopped weewx, deleted /var/weewx/reports/NOAA/*.txt, and 
>> restarted weewx, and still no-go on those summaries...  The current month 
>> is partially populated as expected, but all previous months are empty.
>>
>> https://freescruz.com/weewx/tabular.html?report=NOAA/NOAA-2020-05.txt
>> as an example of said previous month.
>>
>> ditto current year is partially populated, but the prior years since i 
>> started running weewx are empty.
>>  
>>
>>
>>
>>
>>
>> -- 
>> -john r pierce
>>   recycling used bits in santa cruz
>>
>> -- 
>> 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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/CAJnkzX%2B%2BA_Q%2BOy%2BOMfJhMROiPmoy4LWDDRWup6VS80LmeHJ3WQ%40mail.gmail.com
>>  
>> 
>> .
>>
>

-- 
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/50e28cd6-cf29-48e4-81a9-4e36edb47701n%40googlegroups.com.

[weewx-user] Re: 'Loading service w'

[jszit...@gmail.com]

Found the issue... for some reason, despite only ever editing with nano, 
under the [[Engine]] section, weewx.engine.StdArchive had been spaced out 
with commas between each letter.  Lots of searching for 'w' with space 
before and after, etc.  Hopefully this info will help someone in the future.

-JZ

On Thursday, September 10, 2020 at 8:29:53 AM UTC-5 jszit...@gmail.com 
wrote:

>
> Uggh... you fix one issue and something new pops up.  My issue initially 
> looks similar to this one: 
> https://groups.google.com/g/weewx-user/c/F1kqbMEzoXw/m/a7dtCaVYBgAJ and I 
> have replaced the contents of my weeutil.py with the code for v4.1 running 
> on another machine, but the error still persists.  Not sure if there is a 
> different file to check.
>
> Weewx 4.1 on raspbian buster.  DEB package install.  Was running fine, but 
> changed 
> something in my skin.conf and did a restart, now getting the following 
> error:
>
> Sep 10 08:19:41 derby weewx[8868]: Starting weewx weather system: weewx.
> Sep 10 08:19:41 derby systemd[1]: Started LSB: weewx weather system.
> Sep 10 08:19:41 derby weewx[8884] INFO __main__: Using configuration file 
> /etc/weewx/weewx.conf
> Sep 10 08:19:41 derby weewx[8884] INFO __main__: Debug is 1
> Sep 10 08:19:41 derby weewx[8884] DEBUG __main__: Initializing engine
> Sep 10 08:19:41 derby weewx[8884] INFO weewx.engine: Loading station type 
> ObserverIP (user.observerip)
> Sep 10 08:19:41 derby weewxd: observerip: version is 0.6
> Sep 10 08:19:41 derby weewxd: observerip: Unknown firmware version: ���
> Sep 10 08:19:42 derby weewxd: observerip: polling interval is 16.0
> Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Loading service 
> weewx.engine.StdTimeSynch
> Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdTimeSynch
> Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Loading service 
> weewx.engine.StdConvert
> Sep 10 08:19:42 derby weewx[8884] INFO weewx.engine: StdConvert target 
> unit is 0x1
> Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdConvert
> Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Loading service 
> weewx.engine.StdCalibrate
> Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdCalibrate
> Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Loading service 
> weewx.engine.StdQC
> Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdQC
> Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Loading service 
> weewx.wxservices.StdWXCalculate
> Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.manager: Daily summary 
> version is 2.0
> Sep 10 08:19:42 derby weewx[8884] INFO weewx.wxservices: The following 
> values will be calculated: pressure=prefer_hardware, 
> altimeter=prefer_hardware, appTemp=prefer_hardware, 
> barometer=prefer_hardware, beaufort=prefer_hardware, 
> cloudbase=prefer_hardware, dewpoint=prefer_hardware, ET=prefer_hardware, 
> heatindex=prefer_hardware, humidex=prefer_hardware, 
> inDewpoint=prefer_hardware, maxSolarRad=prefer_hardware, 
> rainRate=prefer_hardware, windchill=prefer_hardware, windrun=prefer_hardware
> Sep 10 08:19:42 derby weewx[8884] INFO weewx.wxservices: The following 
> algorithms will be used for calculations: altimeter=aaASOS, maxSolarRad=RS
> Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Finished loading 
> service weewx.wxservices.StdWXCalculate
> Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Loading service w
> Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__: Caught unrecoverable 
> exception:
> Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__:   Empty 
> module name
> Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__:   Traceback 
> (most recent call last):
> Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__: File 
> "/usr/share/weewx/weewxd", line 148, in main
> Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__:   engine 
> = weewx.engine.StdEngine(config_dict)
> Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 75, in __init__
> Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__:   
> self.loadServices(config_dict)
> Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 138, in loadServices
> Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__:   obj = 
> weeutil.weeutil.get_object(svc)(self,config_dict)
> Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__: File 
> "/usr/share/weewx/weeutil/weeutil.py", line 1093, in get_object
> Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__:   mod = 
> __import__(module)
> Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__:   ValueError: 
> Empty module name
> Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__:   

Re: [weewx-user] weewx-Weather34 installation questions

[ExprmntAl]

That was it!!!  The magic address was:

http://192.168.1.145/weewx/weather34/index.ph 
p 
  where "
192.168.1.145 
" is the 
local url to the web host.

I can now access it via VNC Viewer from outside my network and on all 
devices on my local network as well this way.  I didn't realize that I 
would have to use the same local webhost address on the RPi itself.

Thanks so much for the help Andrew!  I'm a happy camper now!!!

On Thursday, September 10, 2020 at 7:47:40 AM UTC-5 andrew.s...@gmail.com 
wrote:

> try the ip address of the php enabled web server if it is local on your 
> network or the external URL to the web host if extenal
>
>
>
> On Thursday, 10 September 2020 15:36:58 UTC+3, ExprmntAl wrote:
>>
>> Hi Glen.  Thanks for trying to help me out.   
>>
>> You need to access that file via
>> http://your_web_server_with_php_enabled/weewx/weather34/index.php  
>>
>> Can you give me an example of what this would look like?  I don't know 
>> what to use for the "your_web_server_with_php_enabled 
>> " 
>> portion of the address.  Though I didn't mention it, I have tried "
>> http://www/html/weewx/weather34/index.ph 
>> p 
>> " in 
>> Chromium on the RPi and this did not work either.  
>>
>> On Thursday, September 10, 2020 at 6:06:56 AM UTC-5 Glenn McKechnie wrote:
>>
>>> On 10/09/2020, ExprmntAl <72604...@compuserve.com> wrote: 
>>> > Tried your suggestion and still no go. See below. 
>>> > 
>>> > *pi@raspberrypi:~ $ sudo apt-get install libapache2-mod-php* 
>>> > *Reading package lists... Done* 
>>> > *Building dependency tree* 
>>> > *Reading state information... Done* 
>>> > *libapache2-mod-php is already the newest version (2:7.3+69).* 
>>> > *The following packages were automatically installed and are no longer 
>>> > required:* 
>>> > * libexiv2-14 libgfortran3 libgmime-2.6-0 libncurses5 libssl1.0.2 
>>> > rpi-eeprom-images* 
>>> > *Use 'sudo apt autoremove' to remove them.* 
>>> > *0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.* 
>>> > *pi@raspberrypi:~ $ sudo a2enmod php7.3* 
>>> > *Considering dependency mpm_prefork for php7.3:* 
>>> > *Considering conflict mpm_event for mpm_prefork:* 
>>> > *Considering conflict mpm_worker for mpm_prefork:* 
>>> > *Module mpm_prefork already enabled* 
>>> > *Considering conflict php5 for php7.3:* 
>>> > *Module php7.3 already enabled* 
>>> > *pi@raspberrypi:~ $ sudo systemctl restart apache2* 
>>> > *pi@raspberrypi:~ $ * 
>>>
>>> Everything you have done above allows a php file to be executed by 
>>> your webserver and therefore the html content generated and displayed 
>>> in the browser that views it. 
>>>
>>> > This is how I am entering the address in Chromium on the RPi. 
>>> > 
>>> > file://www/html/weewx/weather34/index.php 
>>>
>>> That's never going to work. 
>>>
>>> When you use the file:// method of browser access you are accessing 
>>> the file via your filesystem. You are bypassing the php interpreter 
>>> that you installed on your webserver. The browser does not know what 
>>> to do with it, so it displays it (the php contents) Nothing gets 
>>> executed. Nothing has been converted to html. 
>>>
>>> You need to access that file via 
>>> http://your_web_server_with_php_enabled/weewx/weather34/index.php 
>>>
>>> > The address "file://www/html/weewx/index.html" seams to work fine for 
>>> the 
>>> > seasons skin so I have been going off the assumption that a similar 
>>> address 
>>>
>>> It's a html file, the browser knows what to do with html. It displays 
>>> it. 
>>>
>>> > format to the php file should work as well but when I click enter, it 
>>> just 
>>> > downloads the index.php file instead of opening it in the browser. 
>>>
>>> Yep, that's exactly what it will do - no interpreter is available. No 
>>> html is generated. Access it via your webserver and you will get the 
>>> html page it generates. 
>>>
>>> -- 
>>>
>>>
>>> Cheers 
>>> Glenn 
>>>
>>> rorpi - read only raspberry pi & various weewx addons 
>>> https://github.com/glennmckechnie 
>>>
>>

-- 
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/a7ddb306-d5d9-4a4a-9c9b-03b2292cab48n%40googlegroups.com.

[weewx-user] 'Loading service w'

[jszit...@gmail.com]

Uggh... you fix one issue and something new pops up.  My issue initially 
looks similar to this one: 
https://groups.google.com/g/weewx-user/c/F1kqbMEzoXw/m/a7dtCaVYBgAJ and I 
have replaced the contents of my weeutil.py with the code for v4.1 running 
on another machine, but the error still persists.  Not sure if there is a 
different file to check.

Weewx 4.1 on raspbian buster.  DEB package install.  Was running fine, but 
changed 
something in my skin.conf and did a restart, now getting the following 
error:

Sep 10 08:19:41 derby weewx[8868]: Starting weewx weather system: weewx.
Sep 10 08:19:41 derby systemd[1]: Started LSB: weewx weather system.
Sep 10 08:19:41 derby weewx[8884] INFO __main__: Using configuration file 
/etc/weewx/weewx.conf
Sep 10 08:19:41 derby weewx[8884] INFO __main__: Debug is 1
Sep 10 08:19:41 derby weewx[8884] DEBUG __main__: Initializing engine
Sep 10 08:19:41 derby weewx[8884] INFO weewx.engine: Loading station type 
ObserverIP (user.observerip)
Sep 10 08:19:41 derby weewxd: observerip: version is 0.6
Sep 10 08:19:41 derby weewxd: observerip: Unknown firmware version: ���
Sep 10 08:19:42 derby weewxd: observerip: polling interval is 16.0
Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Loading service 
weewx.engine.StdTimeSynch
Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdTimeSynch
Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Loading service 
weewx.engine.StdConvert
Sep 10 08:19:42 derby weewx[8884] INFO weewx.engine: StdConvert target unit 
is 0x1
Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdConvert
Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Loading service 
weewx.engine.StdCalibrate
Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdCalibrate
Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Loading service 
weewx.engine.StdQC
Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdQC
Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Loading service 
weewx.wxservices.StdWXCalculate
Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.manager: Daily summary 
version is 2.0
Sep 10 08:19:42 derby weewx[8884] INFO weewx.wxservices: The following 
values will be calculated: pressure=prefer_hardware, 
altimeter=prefer_hardware, appTemp=prefer_hardware, 
barometer=prefer_hardware, beaufort=prefer_hardware, 
cloudbase=prefer_hardware, dewpoint=prefer_hardware, ET=prefer_hardware, 
heatindex=prefer_hardware, humidex=prefer_hardware, 
inDewpoint=prefer_hardware, maxSolarRad=prefer_hardware, 
rainRate=prefer_hardware, windchill=prefer_hardware, windrun=prefer_hardware
Sep 10 08:19:42 derby weewx[8884] INFO weewx.wxservices: The following 
algorithms will be used for calculations: altimeter=aaASOS, maxSolarRad=RS
Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Finished loading 
service weewx.wxservices.StdWXCalculate
Sep 10 08:19:42 derby weewx[8884] DEBUG weewx.engine: Loading service w
Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__: Caught unrecoverable 
exception:
Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__:   Empty module 
name
Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__:   Traceback 
(most recent call last):
Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__: File 
"/usr/share/weewx/weewxd", line 148, in main
Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__:   engine = 
weewx.engine.StdEngine(config_dict)
Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 75, in __init__
Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__:   
self.loadServices(config_dict)
Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 138, in loadServices
Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__:   obj = 
weeutil.weeutil.get_object(svc)(self,config_dict)
Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1093, in get_object
Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__:   mod = 
__import__(module)
Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__:   ValueError: 
Empty module name
Sep 10 08:19:42 derby weewx[8884] CRITICAL __main__:   Exiting.

-- 
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/622eceac-afe0-48ba-9b5e-0b1c13c41b43n%40googlegroups.com.

Re: [weewx-user] Issue displaying additional temperature

[Jonathan Zitelman]

Tom,

I just created an empty table called 'archive' with columns: datetime,
interval, sigLevel, usUnits.  This seems to have fixed the issue.  I was
able to run the rebuild and it created the daily summaries but left the
archive table empty.  Interestingly, I have another sensor on a cistern,
"HPtank" which was just recently added and was Version 2.0 (According to
the metadata), this table updated without any issues before adding the
'archive' table.  Not sure if it is just a small glitch or some left over
code, but all seems to be working now.

Thank you for all your help!  I'm sure when you first developed WeeWX over
10 years ago, you hadn't planned on a lifetime of support.  Thank you again
for all your work (along with the others that have joined in the past
several years) on developing such a great application!

-Jonathan

On Thu, Sep 10, 2020 at 7:40 AM Jonathan Zitelman 
wrote:

> MYSQL2 is a second MYSQL connection to an off-site server:
> [[MySQL2]]
> driver = weedb.mysql
> host = (secret host)
> user = weewx
> password = (secret password)
>
> The database is there, and weewx pulls the information correctly earlier
> in my HTML with a call to the main table "sensor_gamma" (i.e.:  class="stats_data">$latest($data_binding='well_binding').wellTemp).
> The database also contains the table "sensor_gamma_day_wellTemp" but
> wee_database doesn't seem to be able to populate it, even though it
> originally created it.  The only day summary table with information is
> metadata specifying Version 1.0.  If I drop any of the daily summary
> tables, weewx doesn't seem to recreate them, I assume because of the
> ongoing error.
>
> What's really odd if I have this exact same setup at a different location
> (though it uses pondTemp).
>
> -JZ
>
> On Thu, Sep 10, 2020 at 7:00 AM Tom Keffer  wrote:
>
>> 1. Looking through your [[sensors]] section we see
>>
>>  [[sensors]]
>> database_type = MySQL2
>> database_name = z_sensors_ranch
>>
>> I don't know what a database type of MySQL2 is. Your choices are normally
>> SQLite or MySQL. What is MySQL2?
>>
>> 2. This matters because well_binding is bound to the database 'sensors'.
>> In turn, 'sensors' specifies that it will contain a database named
>> 'z_sensors_ranch', which, apparently, is missing. Double check that.
>>
>> -tk
>>
>> On Wed, Sep 9, 2020 at 4:58 PM Jonathan Zitelman 
>> wrote:
>>
>>> I apologize as I didn't include the V4 schema I tried along with it's
>>> error message.  The syslog notation was the same: ERROR weewx.manager:
>>> Cannot get columns of table archive, and no schema specified
>>>
>>> V4 schema:
>>>
>>> """The extended wview schema."""
>>>
>>> table= [('dateTime', 'INTEGER NOT NULL UNIQUE PRIMARY KEY'),
>>>   ('usUnits',  'INTEGER NOT NULL'),
>>>   ('interval', 'INTEGER NOT NULL'),
>>>   ('wellTemp', 'REAL'),
>>>   ('wellFlow', 'REAL'),
>>>   ('battery',  'INTEGER'),
>>>   ('sigLevel', 'INTEGER'),
>>>   ('transID',  'INTEGER')]
>>>
>>>
>>> day_summaries = [(e[0], 'scalar') for e in table
>>>  if e[0] not in ('dateTime', 'usUnits', 'interval')]
>>>
>>> schema = {
>>> 'table': table,
>>> 'day_summaries' : day_summaries
>>> }
>>>
>>>
>>> Error produced from: sudo /usr/share/weewx/wee_database --rebuild-daily
>>> --binding=well_binding  (looks to be the same)
>>>
>>> Using configuration file /etc/weewx/weewx.conf
>>> Using database binding 'well_binding', which is bound to database
>>> 'sensors'
>>> Traceback (most recent call last):
>>>   File "/usr/share/weewx/wee_database", line 974, in 
>>> main()
>>>   File "/usr/share/weewx/wee_database", line 169, in main
>>> rebuildDaily(config_dict, db_binding, options)
>>>   File "/usr/share/weewx/wee_database", line 225, in rebuildDaily
>>> with weewx.manager.Manager.open(manager_dict['database_dict']) as
>>> dbmanager:
>>>   File "/usr/share/weewx/weewx/manager.py", line 131, in open
>>> dbmanager = cls(connection, table_name)
>>>   File "/usr/share/weewx/weewx/manager.py", line 83, in __init__
>>> self.sqlkeys = self.connection.columnsOf(self.table_name)
>>>   File "/usr/share/weewx/weedb/mysql.py", line 61, in guarded_fn
>>> raise klass(e)
>>> weedb.NoTableError: (1146, "Table 'z_sensors_ranch.archive' doesn't
>>> exist")
>>>
>>>
>>> -JZ
>>>
>>> On Wed, Sep 9, 2020 at 5:52 PM Jonathan Zitelman 
>>> wrote:
>>>
 1.  I reverted user/wellTemp.py back to the V3 schema as follows:

 """The wview schema, which is also used by weewx."""

 schema = [('dateTime', 'INTEGER NOT NULL UNIQUE PRIMARY
 KEY'),
   ('usUnits',  'INTEGER NOT NULL'),
   ('interval', 'INTEGER NOT NULL'),
   ('wellTemp', 'REAL'),
   ('wellFlow', 'REAL'),

Re: [weewx-user] weewx-Weather34 installation questions

[Andrew Milner]

try the ip address of the php enabled web server if it is local on your 
network or the external URL to the web host if extenal



On Thursday, 10 September 2020 15:36:58 UTC+3, ExprmntAl wrote:
>
> Hi Glen.  Thanks for trying to help me out.   
>
> You need to access that file via
> http://your_web_server_with_php_enabled/weewx/weather34/index.php  
>
> Can you give me an example of what this would look like?  I don't know 
> what to use for the "your_web_server_with_php_enabled 
> " 
> portion of the address.  Though I didn't mention it, I have tried "
> http://www/html/weewx/weather34/index.ph 
> p 
> " in 
> Chromium on the RPi and this did not work either.  
>
> On Thursday, September 10, 2020 at 6:06:56 AM UTC-5 Glenn McKechnie wrote:
>
>> On 10/09/2020, ExprmntAl <72604...@compuserve.com> wrote: 
>> > Tried your suggestion and still no go. See below. 
>> > 
>> > *pi@raspberrypi:~ $ sudo apt-get install libapache2-mod-php* 
>> > *Reading package lists... Done* 
>> > *Building dependency tree* 
>> > *Reading state information... Done* 
>> > *libapache2-mod-php is already the newest version (2:7.3+69).* 
>> > *The following packages were automatically installed and are no longer 
>> > required:* 
>> > * libexiv2-14 libgfortran3 libgmime-2.6-0 libncurses5 libssl1.0.2 
>> > rpi-eeprom-images* 
>> > *Use 'sudo apt autoremove' to remove them.* 
>> > *0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.* 
>> > *pi@raspberrypi:~ $ sudo a2enmod php7.3* 
>> > *Considering dependency mpm_prefork for php7.3:* 
>> > *Considering conflict mpm_event for mpm_prefork:* 
>> > *Considering conflict mpm_worker for mpm_prefork:* 
>> > *Module mpm_prefork already enabled* 
>> > *Considering conflict php5 for php7.3:* 
>> > *Module php7.3 already enabled* 
>> > *pi@raspberrypi:~ $ sudo systemctl restart apache2* 
>> > *pi@raspberrypi:~ $ * 
>>
>> Everything you have done above allows a php file to be executed by 
>> your webserver and therefore the html content generated and displayed 
>> in the browser that views it. 
>>
>> > This is how I am entering the address in Chromium on the RPi. 
>> > 
>> > file://www/html/weewx/weather34/index.php 
>>
>> That's never going to work. 
>>
>> When you use the file:// method of browser access you are accessing 
>> the file via your filesystem. You are bypassing the php interpreter 
>> that you installed on your webserver. The browser does not know what 
>> to do with it, so it displays it (the php contents) Nothing gets 
>> executed. Nothing has been converted to html. 
>>
>> You need to access that file via 
>> http://your_web_server_with_php_enabled/weewx/weather34/index.php 
>>
>> > The address "file://www/html/weewx/index.html" seams to work fine for 
>> the 
>> > seasons skin so I have been going off the assumption that a similar 
>> address 
>>
>> It's a html file, the browser knows what to do with html. It displays it. 
>>
>> > format to the php file should work as well but when I click enter, it 
>> just 
>> > downloads the index.php file instead of opening it in the browser. 
>>
>> Yep, that's exactly what it will do - no interpreter is available. No 
>> html is generated. Access it via your webserver and you will get the 
>> html page it generates. 
>>
>> -- 
>>
>>
>> Cheers 
>> Glenn 
>>
>> rorpi - read only raspberry pi & various weewx addons 
>> https://github.com/glennmckechnie 
>>
>

-- 
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/efbc48c1-6e01-4e07-ba5a-879a8c8149fao%40googlegroups.com.

[weewx-user] Re: Belchertown skin - working great, except Darksky Forecasts

[Tom Cichowicz]

Pat;

   I figured it out...

I was able to get into my hosting provider's webserver control panel. (I've 
never used it before)

stumbled around for awhile - haven't done any web development in over 
20years needless to say things have changed.

I found that there wasn't any MIME type defined for JSON files ... I just 
added one to the list (“application/json .json” is the correct JSON content 
type entry.)

   That fixed it!  http://www.mpython.com/weather/belchertown/

  Thanks for ALL your help, looking forward to version 1.2 - I'm sure it 
will be GREAT!

  and Thanks for all your hard work and sharing AND Helping those that 
surely need it. 

On Wednesday, September 9, 2020 at 3:53:06 PM UTC-4 Pat wrote:

> Yep, that link looks good. You should be able to view the json files 
> without restriction - just browse to them. 
>
> For example, this is returning a 404: 
> http://www.mpython.com/weather/belchertown/json/weewx_data.json
>
> But on my site, you can browse to it without a problem. 
> https://belchertownweather.com/json/weewx_data.json
>
> Once you get access working to the json files, the rest should (hopefully) 
> fall in line. 
> On Wednesday, September 9, 2020 at 3:50:43 PM UTC-4 tcich...@gmail.com 
> wrote:
>
>> Pat;
>>
>> I can't seem to figure it out, seems like a relative/absolute path 
>> issue?  Those kinda problems get my head spinning - like trying to think 
>> about double negatives! 
>>
>>   However, I poked a hole in my router temporarily - allowing my 
>> rpi/weewx exposing my server to the world @ , 
>> http://idlewood.dyndns.org/weewx/belchertown/
>>
>>It runs as it does from a local URL, only the one error in the browser 
>> console  - related to a file that truly doesn't exist -> custom.css
>>
>>   I may just setup another rpi to act as an external webserver -- But 
>> would prefer to figure out what it's not working from my mpython.com 
>> domain ---
>>
>>
>>
>>
>> On Wednesday, September 9, 2020 at 3:07:13 PM UTC-4 Tom Cichowicz wrote:
>>
>>> Pat;
>>>
>>>I moved the remote webserver - path directly off the root so the 
>>> URL is now...
>>>  
>>>
>>>the problem still exists - after rebuilding the file/folders.. 
>>>
>>> ???
>>>
>>> On Wednesday, September 9, 2020 at 1:02:19 PM UTC-4 Pat wrote:
>>>
 Start by fixing your JSON file missing errors - that might solve all of 
 your issues. 

 On Wednesday, September 9, 2020 at 12:58:23 PM UTC-4 tcich...@gmail.com 
 wrote:

> sorry here's a link to my public webpage...
> Link to page 
>
>  I'll have to turn debug back on and grab a tail --- may be a bit for 
> that.
>
> On Wednesday, September 9, 2020 at 12:56:16 PM UTC-4 Tom Cichowicz 
> wrote:
>
>> OK, thanks ...
>>
>>  I changed my Secret id and API to my Aeris account values...
>>
>> I am getting forecast ONLY on my internal local webserver (weewx pi ) 
>> that is running as well.
>>
>> However public server host by Go Daddy - not displaying forecast,  or 
>> graphs. ??
>>
>> Plus the rounding of ALL values not happening. as well as the 
>> undefined messages along with the value in some locations.
>>
>> I did go through and delete ALL the index.html files under the 
>> ../blechertown folder on my remote webserver - and restarted weewx.
>>
>> Hasn't yet changed anything.
>>
>> [image: weewx_no_rounding2.PNG]
>>
>> On Tuesday, September 8, 2020 at 8:56:17 PM UTC-4 Pat wrote:
>>
>>> Need a little more information than this. A link to your website? 
>>> Debug logs? 
>>>
>>> Skin version 1.2 will be released tomorrow if all goes to plan, and 
>>> I advise you to switch to Aeris weather since DarkSky will be stopping 
>>> their API usage at some point. 
>>>
>>> On Sunday, September 6, 2020 at 12:14:48 PM UTC-4 tcich...@gmail.com 
>>> wrote:
>>>
 I've got it creating a Darksky forecast json file - with data - 
 however web page doesn't display..
  ??  version 1.1?

>>>

-- 
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/48171fca-0349-45a6-be30-c255606fda40n%40googlegroups.com.

Re: [weewx-user] weewx-Weather34 installation questions

[ExprmntAl]

Hi Glen.  Thanks for trying to help me out.   

You need to access that file via
http://your_web_server_with_php_enabled/weewx/weather34/index.php  

Can you give me an example of what this would look like?  I don't know what 
to use for the "your_web_server_with_php_enabled 
" 
portion of the address.  Though I didn't mention it, I have tried "
http://www/html/weewx/weather34/index.ph 
p 
" in 
Chromium on the RPi and this did not work either.  

On Thursday, September 10, 2020 at 6:06:56 AM UTC-5 Glenn McKechnie wrote:

> On 10/09/2020, ExprmntAl <72604...@compuserve.com> wrote:
> > Tried your suggestion and still no go. See below.
> >
> > *pi@raspberrypi:~ $ sudo apt-get install libapache2-mod-php*
> > *Reading package lists... Done*
> > *Building dependency tree*
> > *Reading state information... Done*
> > *libapache2-mod-php is already the newest version (2:7.3+69).*
> > *The following packages were automatically installed and are no longer
> > required:*
> > * libexiv2-14 libgfortran3 libgmime-2.6-0 libncurses5 libssl1.0.2
> > rpi-eeprom-images*
> > *Use 'sudo apt autoremove' to remove them.*
> > *0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.*
> > *pi@raspberrypi:~ $ sudo a2enmod php7.3*
> > *Considering dependency mpm_prefork for php7.3:*
> > *Considering conflict mpm_event for mpm_prefork:*
> > *Considering conflict mpm_worker for mpm_prefork:*
> > *Module mpm_prefork already enabled*
> > *Considering conflict php5 for php7.3:*
> > *Module php7.3 already enabled*
> > *pi@raspberrypi:~ $ sudo systemctl restart apache2*
> > *pi@raspberrypi:~ $ *
>
> Everything you have done above allows a php file to be executed by
> your webserver and therefore the html content generated and displayed
> in the browser that views it.
>
> > This is how I am entering the address in Chromium on the RPi.
> >
> > file://www/html/weewx/weather34/index.php
>
> That's never going to work.
>
> When you use the file:// method of browser access you are accessing
> the file via your filesystem. You are bypassing the php interpreter
> that you installed on your webserver. The browser does not know what
> to do with it, so it displays it (the php contents) Nothing gets
> executed. Nothing has been converted to html.
>
> You need to access that file via
> http://your_web_server_with_php_enabled/weewx/weather34/index.php
>
> > The address "file://www/html/weewx/index.html" seams to work fine for the
> > seasons skin so I have been going off the assumption that a similar 
> address
>
> It's a html file, the browser knows what to do with html. It displays it.
>
> > format to the php file should work as well but when I click enter, it 
> just
> > downloads the index.php file instead of opening it in the browser.
>
> Yep, that's exactly what it will do - no interpreter is available. No
> html is generated. Access it via your webserver and you will get the
> html page it generates.
>
> -- 
>
>
> Cheers
> Glenn
>
> rorpi - read only raspberry pi & various weewx addons
> https://github.com/glennmckechnie
>

-- 
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/34b6dc31-0c41-4f6b-b115-1d0a3bcf04cen%40googlegroups.com.

Re: [weewx-user] Issue displaying additional temperature

[Tom Keffer]

1. Looking through your [[sensors]] section we see

 [[sensors]]
database_type = MySQL2
database_name = z_sensors_ranch

I don't know what a database type of MySQL2 is. Your choices are normally
SQLite or MySQL. What is MySQL2?

2. This matters because well_binding is bound to the database 'sensors'. In
turn, 'sensors' specifies that it will contain a database named
'z_sensors_ranch', which, apparently, is missing. Double check that.

-tk

On Wed, Sep 9, 2020 at 4:58 PM Jonathan Zitelman 
wrote:

> I apologize as I didn't include the V4 schema I tried along with it's
> error message.  The syslog notation was the same: ERROR weewx.manager:
> Cannot get columns of table archive, and no schema specified
>
> V4 schema:
>
> """The extended wview schema."""
>
> table= [('dateTime', 'INTEGER NOT NULL UNIQUE PRIMARY KEY'),
>   ('usUnits',  'INTEGER NOT NULL'),
>   ('interval', 'INTEGER NOT NULL'),
>   ('wellTemp', 'REAL'),
>   ('wellFlow', 'REAL'),
>   ('battery',  'INTEGER'),
>   ('sigLevel', 'INTEGER'),
>   ('transID',  'INTEGER')]
>
>
> day_summaries = [(e[0], 'scalar') for e in table
>  if e[0] not in ('dateTime', 'usUnits', 'interval')]
>
> schema = {
> 'table': table,
> 'day_summaries' : day_summaries
> }
>
>
> Error produced from: sudo /usr/share/weewx/wee_database --rebuild-daily
> --binding=well_binding  (looks to be the same)
>
> Using configuration file /etc/weewx/weewx.conf
> Using database binding 'well_binding', which is bound to database 'sensors'
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_database", line 974, in 
> main()
>   File "/usr/share/weewx/wee_database", line 169, in main
> rebuildDaily(config_dict, db_binding, options)
>   File "/usr/share/weewx/wee_database", line 225, in rebuildDaily
> with weewx.manager.Manager.open(manager_dict['database_dict']) as
> dbmanager:
>   File "/usr/share/weewx/weewx/manager.py", line 131, in open
> dbmanager = cls(connection, table_name)
>   File "/usr/share/weewx/weewx/manager.py", line 83, in __init__
> self.sqlkeys = self.connection.columnsOf(self.table_name)
>   File "/usr/share/weewx/weedb/mysql.py", line 61, in guarded_fn
> raise klass(e)
> weedb.NoTableError: (1146, "Table 'z_sensors_ranch.archive' doesn't exist")
>
>
> -JZ
>
> On Wed, Sep 9, 2020 at 5:52 PM Jonathan Zitelman 
> wrote:
>
>> 1.  I reverted user/wellTemp.py back to the V3 schema as follows:
>>
>> """The wview schema, which is also used by weewx."""
>>
>> schema = [('dateTime', 'INTEGER NOT NULL UNIQUE PRIMARY KEY'),
>>   ('usUnits',  'INTEGER NOT NULL'),
>>   ('interval', 'INTEGER NOT NULL'),
>>   ('wellTemp', 'REAL'),
>>   ('wellFlow', 'REAL'),
>>   ('battery',  'INTEGER'),
>>   ('sigLevel', 'INTEGER'),
>>   ('transID',  'INTEGER')]
>>
>>
>> 2. The associated sections from weewx.conf:
>>
>> [DataBindings]
>>
>> [[wx_binding]]
>>  database = archive_mysql
>> table_name = archive
>> manager = weewx.manager.DaySummaryManager
>> schema = schemas.wview_extended.schema
>>
>> [[well_binding]]
>> database = sensors
>> table_name = sensor_gamma
>> manager = weewx.wxmanager.WXDaySummaryManager
>> schema = user.wellTemp.schema
>>
>> [[HPt_binding]]
>> database = sensors
>> table_name = sensor_HPtank
>> manager = weewx.wxmanager.WXDaySummaryManager
>> schema = user.hpTank.schema
>>
>> [Databases]
>>
>> [[archive_mysql]]
>> database_name = weewx
>> database_type = MySQL
>>
>> [[sensors]]
>> database_type = MySQL2
>> database_name = z_sensors_ranch
>>
>>
>> 3a.  The full error text when trying to backfill the daily summaries:
>>
>> $ /usr/share/weewx/wee_database --rebuild-daily --binding=well_binding
>>
>> Using configuration file /etc/weewx/weewx.conf
>> Using database binding 'well_binding', which is bound to database
>> 'sensors'
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/wee_database", line 974, in 
>> main()
>>   File "/usr/share/weewx/wee_database", line 169, in main
>> rebuildDaily(config_dict, db_binding, options)
>>   File "/usr/share/weewx/wee_database", line 225, in rebuildDaily
>> with weewx.manager.Manager.open(manager_dict['database_dict']) as
>> dbmanager:
>>   File "/usr/share/weewx/weewx/manager.py", line 131, in open
>> dbmanager = cls(connection, table_name)
>>   File "/usr/share/weewx/weewx/manager.py", line 83, in __init__
>> self.sqlkeys = self.connection.columnsOf(self.table_name)
>>   File "/usr/share/weewx/weedb/mysql.py", line 61, in guarded_fn
>> raise klass(e)
>> weedb.NoTableError: (1146, 

Re: [weewx-user] weewx-Weather34 installation questions

[Glenn McKechnie]

On 10/09/2020, ExprmntAl <72604.3...@compuserve.com> wrote:
> Tried your suggestion and still no go.  See below.
>
> *pi@raspberrypi:~ $ sudo apt-get install libapache2-mod-php*
> *Reading package lists... Done*
> *Building dependency tree*
> *Reading state information... Done*
> *libapache2-mod-php is already the newest version (2:7.3+69).*
> *The following packages were automatically installed and are no longer
> required:*
> *  libexiv2-14 libgfortran3 libgmime-2.6-0 libncurses5 libssl1.0.2
> rpi-eeprom-images*
> *Use 'sudo apt autoremove' to remove them.*
> *0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.*
> *pi@raspberrypi:~ $ sudo a2enmod php7.3*
> *Considering dependency mpm_prefork for php7.3:*
> *Considering conflict mpm_event for mpm_prefork:*
> *Considering conflict mpm_worker for mpm_prefork:*
> *Module mpm_prefork already enabled*
> *Considering conflict php5 for php7.3:*
> *Module php7.3 already enabled*
> *pi@raspberrypi:~ $ sudo systemctl restart apache2*
> *pi@raspberrypi:~ $ *

Everything you have done above allows a php file to be executed by
your webserver and therefore the html content generated and displayed
in the browser that views it.

> This is how I am entering the address in Chromium on the RPi.
>
> file://www/html/weewx/weather34/index.php

That's never going to work.

When you use the file://  method of browser access you are accessing
the file via your filesystem. You are bypassing the php interpreter
that you installed on your webserver. The browser does not know what
to do with it, so it displays it (the php contents) Nothing gets
executed. Nothing has been converted to html.

You need to access that file via
http://your_web_server_with_php_enabled/weewx/weather34/index.php

> The address "file://www/html/weewx/index.html" seams to work fine for the
> seasons skin so I have been going off the assumption that a similar address

It's a html file, the browser knows what to do with html. It displays it.

> format to the php file should work as well but when I click enter, it just
> downloads the index.php file instead of opening it in the browser.

Yep, that's exactly what it will do - no interpreter is available. No
html is generated. Access it via your webserver and you will get the
html page it generates.

-- 


Cheers
 Glenn

rorpi - read only raspberry pi & various weewx addons
https://github.com/glennmckechnie

-- 
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/CAAraAziEOyfWE3xByVhjgzA_xfw7ruxu1nvyAwd1OO1j06UokQ%40mail.gmail.com.

Re: [weewx-user] weewx-Weather34 installation questions

[ExprmntAl]

Tried your suggestion and still no go.  See below.

*pi@raspberrypi:~ $ sudo apt-get install libapache2-mod-php*
*Reading package lists... Done*
*Building dependency tree*
*Reading state information... Done*
*libapache2-mod-php is already the newest version (2:7.3+69).*
*The following packages were automatically installed and are no longer 
required:*
*  libexiv2-14 libgfortran3 libgmime-2.6-0 libncurses5 libssl1.0.2 
rpi-eeprom-images*
*Use 'sudo apt autoremove' to remove them.*
*0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.*
*pi@raspberrypi:~ $ sudo a2enmod php7.3*
*Considering dependency mpm_prefork for php7.3:*
*Considering conflict mpm_event for mpm_prefork:*
*Considering conflict mpm_worker for mpm_prefork:*
*Module mpm_prefork already enabled*
*Considering conflict php5 for php7.3:*
*Module php7.3 already enabled*
*pi@raspberrypi:~ $ sudo systemctl restart apache2*
*pi@raspberrypi:~ $ *

This is how I am entering the address in Chromium on the RPi.

file://www/html/weewx/weather34/index.php

The address "file://www/html/weewx/index.html" seams to work fine for the 
seasons skin so I have been going off the assumption that a similar address 
format to the php file should work as well but when I click enter, it just 
downloads the index.php file instead of opening it in the browser.
On Thursday, September 10, 2020 at 1:37:21 AM UTC-5 steep...@gmail.com 
wrote:

> Sorry I missed a line: -
>
> sudo apt-get install libapache2-mod-php before running the next two lines
>
>
> sudo a2enmod php7.3
> sudo systemctl restart apache2
>
>
>
> On Thu, 10 Sep 2020 at 07:32, steeple ian  wrote:
>
>> Allan,
>>
>> You may have missed this part of the instructions which would make sense 
>> with what Rich T has suggested: -
>>
>> sudo a2enmod php7.3
>> sudo systemctl restart apache2
>>
>>
>> On Thu, 10 Sep 2020 at 01:25, ExprmntAl <72604...@compuserve.com> wrote:
>>
>>> UPDATE:
>>>
>>> I tried accessing the Weather34 index.php file via both the Edge and IE 
>>> browsers on a Windows 10 machine on the same network as the RPi and it 
>>> works fine using the address:
>>>
>>> http://192.168.1.145/weewx/weather34/index.php (where 192.168.1.145 is 
>>> the RPi local address).  The sensor data from my Tempest is displayed 
>>> including the rapid fire wind values using this method.
>>>
>>> I have tried a number of variations of addresses that work with my 
>>> seasons skin using the weather34 html directory, but I still can't get the 
>>> Chromium Browser on the RPi to open the index.php file for some reason 
>>> though.
>>>
>>> The seasons skin file is accessed by putting 
>>> "file:///var/www/html/weewx/index.html" into the Chromium browser on the 
>>> RPi and this works normally.  It would follow that to access the Weather34 
>>> skin I would use "file:///var/www/html/weewx/weather34/index.php".  This 
>>> starts downloading the file instead of rendering the skin.
>>>
>>> Does Chromium need to be configured in some way on the RPi to render php 
>>> files?
>>> On Wednesday, September 9, 2020 at 12:59:36 PM UTC-5 ExprmntAl wrote:
>>>
 PHP is installed for sure see below.  You had me install it before 
 getting to the weewx-Weather34 installation.  I assumed that with PHP 
 installed, that anything *.php would open similar to a *.html file in the 
 Chromium browser.  Is this correct?

 *pi@raspberrypi:~/weewx-Weather34 $ php -v*
 *PHP 7.3.19-1~deb10u1 (cli) (built: Jul  5 2020 06:46:45) ( NTS )*
 *Copyright (c) 1997-2018 The PHP Group*
 *Zend Engine v3.3.19, Copyright (c) 1998-2018 Zend Technologies*
 *with Zend OPcache v7.3.19-1~deb10u1, Copyright (c) 1999-2018, by 
 Zend Technologies*
 *pi@raspberrypi:~/weewx-Weather34 $*



 On Wednesday, September 9, 2020 at 8:56:49 AM UTC-5 steep...@gmail.com 
 wrote:

> Allan,
>
> Just to make sure php is installed: -
>
> sudo apt install php -y
>
>
> On Wed, 9 Sep 2020 at 12:54, ExprmntAl <72604...@compuserve.com> 
> wrote:
>
>> That seems to have done it! 
>>
>> *pi@raspberrypi:~ $ cd weewx-Weather34*
>> *pi@raspberrypi:~/weewx-Weather34 $ sudo python3 w34_installer.py*
>> *!!! THIS INSTALL IS USING PYTHON VERSION 3.7.3 IS THIS CORRECT? 
>> (Yes/No)*
>> *Install will continue with Python Version 3.7.3*
>> *1 -> macos.conf*
>> *2 -> packaged.conf*
>> *3 -> setup_py.conf*
>> *Enter the NUMBER of the installer config file 2*
>> *Installer Config file packaged.conf was chosen.*
>> *Updating weewx config*
>> *Done!*
>> *pi@raspberrypi:~/weewx-Weather34 $*
>>
>> Another stupid question:  Looking at the files generated in 
>> the /var/www/html/weewx/weather34 directory.  They are all .php files.  
>> For 
>> some reason the Chrome browser on the RPi doesn't recognize those files. 
>>  
>> Is there something that needs to be done to get these PHP files to 

Re: [weewx-user] weewx-Weather34 installation questions

[steeple ian]

Sorry I missed a line: -

sudo apt-get install libapache2-mod-php before running the next two lines


sudo a2enmod php7.3
sudo systemctl restart apache2



On Thu, 10 Sep 2020 at 07:32, steeple ian  wrote:

> Allan,
>
> You may have missed this part of the instructions which would make sense
> with what Rich T has suggested: -
>
> sudo a2enmod php7.3
> sudo systemctl restart apache2
>
>
> On Thu, 10 Sep 2020 at 01:25, ExprmntAl <72604.3...@compuserve.com> wrote:
>
>> UPDATE:
>>
>> I tried accessing the Weather34 index.php file via both the Edge and IE
>> browsers on a Windows 10 machine on the same network as the RPi and it
>> works fine using the address:
>>
>> http://192.168.1.145/weewx/weather34/index.php (where 192.168.1.145 is
>> the RPi local address).  The sensor data from my Tempest is displayed
>> including the rapid fire wind values using this method.
>>
>> I have tried a number of variations of addresses that work with my
>> seasons skin using the weather34 html directory, but I still can't get the
>> Chromium Browser on the RPi to open the index.php file for some reason
>> though.
>>
>> The seasons skin file is accessed by putting
>> "file:///var/www/html/weewx/index.html" into the Chromium browser on the
>> RPi and this works normally.  It would follow that to access the Weather34
>> skin I would use "file:///var/www/html/weewx/weather34/index.php".  This
>> starts downloading the file instead of rendering the skin.
>>
>> Does Chromium need to be configured in some way on the RPi to render php
>> files?
>> On Wednesday, September 9, 2020 at 12:59:36 PM UTC-5 ExprmntAl wrote:
>>
>>> PHP is installed for sure see below.  You had me install it before
>>> getting to the weewx-Weather34 installation.  I assumed that with PHP
>>> installed, that anything *.php would open similar to a *.html file in the
>>> Chromium browser.  Is this correct?
>>>
>>> *pi@raspberrypi:~/weewx-Weather34 $ php -v*
>>> *PHP 7.3.19-1~deb10u1 (cli) (built: Jul  5 2020 06:46:45) ( NTS )*
>>> *Copyright (c) 1997-2018 The PHP Group*
>>> *Zend Engine v3.3.19, Copyright (c) 1998-2018 Zend Technologies*
>>> *with Zend OPcache v7.3.19-1~deb10u1, Copyright (c) 1999-2018, by
>>> Zend Technologies*
>>> *pi@raspberrypi:~/weewx-Weather34 $*
>>>
>>>
>>>
>>> On Wednesday, September 9, 2020 at 8:56:49 AM UTC-5 steep...@gmail.com
>>> wrote:
>>>
 Allan,

 Just to make sure php is installed: -

 sudo apt install php -y


 On Wed, 9 Sep 2020 at 12:54, ExprmntAl <72604...@compuserve.com> wrote:

> That seems to have done it!
>
> *pi@raspberrypi:~ $ cd weewx-Weather34*
> *pi@raspberrypi:~/weewx-Weather34 $ sudo python3 w34_installer.py*
> *!!! THIS INSTALL IS USING PYTHON VERSION 3.7.3 IS THIS CORRECT?
> (Yes/No)*
> *Install will continue with Python Version 3.7.3*
> *1 -> macos.conf*
> *2 -> packaged.conf*
> *3 -> setup_py.conf*
> *Enter the NUMBER of the installer config file 2*
> *Installer Config file packaged.conf was chosen.*
> *Updating weewx config*
> *Done!*
> *pi@raspberrypi:~/weewx-Weather34 $*
>
> Another stupid question:  Looking at the files generated in
> the /var/www/html/weewx/weather34 directory.  They are all .php files.  
> For
> some reason the Chrome browser on the RPi doesn't recognize those files.
> Is there something that needs to be done to get these PHP files to open in
> the browser?  Ian walked me through the installation of PHP and all its
> libraries prior up at the top of this thread and I thought that that would
> configure the browser for PHP as well.
>
> On Wednesday, September 9, 2020 at 5:33:30 AM UTC-5 tke...@gmail.com
> wrote:
>
>> So, weewxd is using python3, and configobj is definitely installed
>> under python3.
>>
>> This is probably a simple case of configobj being installed under
>> Python 3, but not Python 2. Looking back in this thread, the original
>> problem was probably caused by using  the wrong version of Python. Try 
>> this:
>>
>>
>> *sudo python3 w34_installer.py*
>>
>> -tk
>>
>> On Tue, Sep 8, 2020 at 6:38 PM ExprmntAl <72604...@compuserve.com>
>> wrote:
>>
>>> Appologies TK.  Here is the log capturing the weewx start as well.
>>>
>>> *Sep  8 19:00:10 raspberrypi dbus-daemon[14817]: [session uid=0
>>> pid=14814] Activating service name='ca.desrt.dconf' requested by ':1.0'
>>> (uid=0 pid=14807 comm="mousepad ")*
>>> *Sep  8 19:00:10 raspberrypi dbus-daemon[14817]: [session uid=0
>>> pid=14814] Successfully activated service 'ca.desrt.dconf'*
>>> *Sep  8 19:00:16 raspberrypi dbus-daemon[385]: [system] Activating
>>> via systemd: service name='org.freedesktop.hostname1'
>>> unit='dbus-org.freedesktop.hostname1.service' requested by ':1.87' 
>>> (uid=0
>>> pid=14807 comm="mousepad ")*
>>> *Sep  8 19:00:16 raspberrypi systemd[1]: 

Re: [weewx-user] weewx-Weather34 installation questions

[steeple ian]

Allan,

You may have missed this part of the instructions which would make sense
with what Rich T has suggested: -

sudo a2enmod php7.3
sudo systemctl restart apache2


On Thu, 10 Sep 2020 at 01:25, ExprmntAl <72604.3...@compuserve.com> wrote:

> UPDATE:
>
> I tried accessing the Weather34 index.php file via both the Edge and IE
> browsers on a Windows 10 machine on the same network as the RPi and it
> works fine using the address:
>
> http://192.168.1.145/weewx/weather34/index.php (where 192.168.1.145 is
> the RPi local address).  The sensor data from my Tempest is displayed
> including the rapid fire wind values using this method.
>
> I have tried a number of variations of addresses that work with my seasons
> skin using the weather34 html directory, but I still can't get the Chromium
> Browser on the RPi to open the index.php file for some reason though.
>
> The seasons skin file is accessed by putting
> "file:///var/www/html/weewx/index.html" into the Chromium browser on the
> RPi and this works normally.  It would follow that to access the Weather34
> skin I would use "file:///var/www/html/weewx/weather34/index.php".  This
> starts downloading the file instead of rendering the skin.
>
> Does Chromium need to be configured in some way on the RPi to render php
> files?
> On Wednesday, September 9, 2020 at 12:59:36 PM UTC-5 ExprmntAl wrote:
>
>> PHP is installed for sure see below.  You had me install it before
>> getting to the weewx-Weather34 installation.  I assumed that with PHP
>> installed, that anything *.php would open similar to a *.html file in the
>> Chromium browser.  Is this correct?
>>
>> *pi@raspberrypi:~/weewx-Weather34 $ php -v*
>> *PHP 7.3.19-1~deb10u1 (cli) (built: Jul  5 2020 06:46:45) ( NTS )*
>> *Copyright (c) 1997-2018 The PHP Group*
>> *Zend Engine v3.3.19, Copyright (c) 1998-2018 Zend Technologies*
>> *with Zend OPcache v7.3.19-1~deb10u1, Copyright (c) 1999-2018, by
>> Zend Technologies*
>> *pi@raspberrypi:~/weewx-Weather34 $*
>>
>>
>>
>> On Wednesday, September 9, 2020 at 8:56:49 AM UTC-5 steep...@gmail.com
>> wrote:
>>
>>> Allan,
>>>
>>> Just to make sure php is installed: -
>>>
>>> sudo apt install php -y
>>>
>>>
>>> On Wed, 9 Sep 2020 at 12:54, ExprmntAl <72604...@compuserve.com> wrote:
>>>
 That seems to have done it!

 *pi@raspberrypi:~ $ cd weewx-Weather34*
 *pi@raspberrypi:~/weewx-Weather34 $ sudo python3 w34_installer.py*
 *!!! THIS INSTALL IS USING PYTHON VERSION 3.7.3 IS THIS CORRECT?
 (Yes/No)*
 *Install will continue with Python Version 3.7.3*
 *1 -> macos.conf*
 *2 -> packaged.conf*
 *3 -> setup_py.conf*
 *Enter the NUMBER of the installer config file 2*
 *Installer Config file packaged.conf was chosen.*
 *Updating weewx config*
 *Done!*
 *pi@raspberrypi:~/weewx-Weather34 $*

 Another stupid question:  Looking at the files generated in
 the /var/www/html/weewx/weather34 directory.  They are all .php files.  For
 some reason the Chrome browser on the RPi doesn't recognize those files.
 Is there something that needs to be done to get these PHP files to open in
 the browser?  Ian walked me through the installation of PHP and all its
 libraries prior up at the top of this thread and I thought that that would
 configure the browser for PHP as well.

 On Wednesday, September 9, 2020 at 5:33:30 AM UTC-5 tke...@gmail.com
 wrote:

> So, weewxd is using python3, and configobj is definitely installed
> under python3.
>
> This is probably a simple case of configobj being installed under
> Python 3, but not Python 2. Looking back in this thread, the original
> problem was probably caused by using  the wrong version of Python. Try 
> this:
>
>
> *sudo python3 w34_installer.py*
>
> -tk
>
> On Tue, Sep 8, 2020 at 6:38 PM ExprmntAl <72604...@compuserve.com>
> wrote:
>
>> Appologies TK.  Here is the log capturing the weewx start as well.
>>
>> *Sep  8 19:00:10 raspberrypi dbus-daemon[14817]: [session uid=0
>> pid=14814] Activating service name='ca.desrt.dconf' requested by ':1.0'
>> (uid=0 pid=14807 comm="mousepad ")*
>> *Sep  8 19:00:10 raspberrypi dbus-daemon[14817]: [session uid=0
>> pid=14814] Successfully activated service 'ca.desrt.dconf'*
>> *Sep  8 19:00:16 raspberrypi dbus-daemon[385]: [system] Activating
>> via systemd: service name='org.freedesktop.hostname1'
>> unit='dbus-org.freedesktop.hostname1.service' requested by ':1.87' (uid=0
>> pid=14807 comm="mousepad ")*
>> *Sep  8 19:00:16 raspberrypi systemd[1]: Starting Hostname Service...*
>> *Sep  8 19:00:16 raspberrypi dbus-daemon[385]: [system] Successfully
>> activated service 'org.freedesktop.hostname1'*
>> *Sep  8 19:00:16 raspberrypi systemd[1]: Started Hostname Service.*
>> *Sep  8 19:00:46 raspberrypi systemd[1]: systemd-hostnamed.service:
>> Succeeded.*
>> *Sep  8