Re: [weewx-user] Decode the value of the DateTime field

[Mielmari]

Thanks! 


El viernes, 15 de diciembre de 2017, 8:35:06 (UTC+1), Glenn McKechnie 
escribió:
>
> It's Unixtime or epochtime. Run the command
> man date
> from a terminal window and you'll be bedazzled by the options.
>
> To convert that number string to something human readable, enter the 
> following into your terminal and press enter.
>
> date -d @1510918732
>
>
>
>
>
> Cheers
>  Glenn
>
> rorpi - read only raspberry pi & various weewx addons
> https://github.com/glennmckechnie
>
> On 15 December 2017 at 17:25, Mielmari  
> wrote:
>
>>
>> Hello
>> Using DB Browser for SQLite, in the database in the field 'dateTime' I 
>> see values like this "1510918732". How is this value converted to year, 
>> month, day, hour etc?
>>
>> Thanks for your kind help.
>>
>> -- 
>> 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 .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx-wd getting keyerror: meter

[Radar]

thanks for the quick reply.  i had added them to extensions.py but after a 
long look i see that i had added a group for distance a few years back, 
after taking it out all works now.
thanks again it never crossed my mind to look there.

On Monday, December 11, 2017 at 6:20:46 PM UTC-6, Radar wrote:
>
> just installed weewx 3.8.0 and weewx-wd 1.0.3 and getting keyerror: meter 
> from Testtags, wdClientraw, wdSteelGauges 
> wdPWS and wdStackedWindRose are working
>
> here is the log and weewx.conf files
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx-wd getting keyerror: meter

[gjr80]

I think I have an idea as to what might be going on. Judging by your 
weewx.conf you are adding a lot of obs to the archive records and/or loop 
packets. Nothing wrong with this, weeWX will handle it, but when you add an 
observation to the an archive record it is just a value with an expectation 
that the value is in the relevant units given the usUnits value in the 
archive record/loop packet. So if usUnits is 1 (ie US customary) any 
temperature obs in the record/packet should be in degrees F, if not you 
will have conversion problems if you (or weeWX) ever converts that value to 
degrees C. Adding the value in the right units is only half of the 
solution, weeWX also needs to know wheter the value you have added is a 
temperature, a speed as distance etc. That way weeWX knows that when 
converting, say extraTemp11, extraTemp11 is a temeperature so use the C to 
F or F to C conversion not the km to mph conversion.

The first part, adding the value to the record/packet in the correct units, 
is normally done in the driver or service that is creating or adding the 
values. The second part, defining what type of obs you are adding, can be 
done in a number of ways but is usually done by adding some lines to 
bin/user/extension.py (it's possible that in the future this may be 
something that can be defined in weewx.conf but that's not the case yet). 
weeWX-WD handles this slightly differently, the weeWX-WD database schema is 
fixed so the groups for the extra weeWX-WD obs are setup in the weeWX-WD 
code rather than bin/user/extension.py. Given that the interceptor driver 
does not know what fields you will be using (since the user defines them in 
weewx.conf) you need to add the group settings yourself.

So to cut along story short, in some areas weeWX-WD needs some fields in 
particular units so it converts the archive/record to a given units group 
(I think metric is causing the problem here). If weeWX does not know how to 
interpret a value (is it a temperature or speed?) such conversion causes an 
error. I think that is what is happening here. Did you do anything in terms 
of defining the groups for each of your additional obs that you added? Have 
a look in bin/user/extension.py, are there any lines like:

import weewx.units 
weewx.units.obs_group_dict["heatindex7"] = "group_temperature" 
weewx.units.obs_group_dict["windchill12"] = "group_temperature"

If not you will need to add a line for each of the extra obs you have 
added. Use the format (don't forget the import weewx.units statement):

weewx.units.obs_group_dict["obs_name"] = "group_name" 

where obs_name is the name of the field you are adding and group_name is 
the name of the group you are assigning the obs to. The available groups 
are listed in the Unit groups, members and options table 
 in the Customization Guide. 
If you have an obs that does not fit any of the groups, eg say luminous 
intensity measured in candela, then you need to define a new group and some 
conversion functions. Let us know if this is the case. Chances are though 
most of your groups will exist already in the table I linked.

Once you have defined your obs groups save extensions.py and restart weeWX. 
extensions.py is in the bin/user directory so it will be preserved across 
upgrades, though if your additions are lengthy it might be worth keeping a 
copy in case of a re-install.

Gary

On Tuesday, 12 December 2017 10:20:46 UTC+10, Radar wrote:
>
> just installed weewx 3.8.0 and weewx-wd 1.0.3 and getting keyerror: meter 
> from Testtags, wdClientraw, wdSteelGauges 
> wdPWS and wdStackedWindRose are working
>
> here is the log and weewx.conf files
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] --reading failure in weewx_3.8.0-1 and weewx-owfs-0.21 Raspberry Pi & DS18B20

[mixpc75]

Glen,

Thank you for your support all along. It's fantastic.

I have read and follow your indications, so here we go:

[OWFS] uninstalled
pi@raspberrypi:~ $ sudo wee_extension --uninstall owfs
Request to remove extension 'owfs'
Finished removing extension 'owfs'


pi@raspberrypi:~ $ sudo nano /usr/share/weewx/user/ds18b20.py
edited as indicated DEBUG > INFO

pi@raspberrypi:~ $ sudo systemctl restart weewx.service

pi@raspberrypi:~ $ sudo systemctl status weewx.service
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx; generated; vendor preset: enabled)
   Active: active (running) since Sat 2017-12-16 00:16:56 CET; 3min 55s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 1149 ExecStop=/etc/init.d/weewx stop (code=exited,
status=0/SUCCESS)
  Process: 1180 ExecStart=/etc/init.d/weewx start (code=exited,
status=0/SUCCESS)
   CGroup: /system.slice/weewx.service
   └─1195 python /usr/bin/weewxd --daemon
--pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf

Dec 16 00:16:57 raspberrypi weewx[1195]: restx: CWOP: Posting not enabled.
Dec 16 00:16:57 raspberrypi weewx[1195]: restx: WOW: Posting not enabled.
Dec 16 00:16:57 raspberrypi weewx[1195]: restx: AWEKAS: Posting not enabled.
Dec 16 00:16:57 raspberrypi weewx[1195]: engine: Starting up weewx version
3.8.0
Dec 16 00:16:57 raspberrypi weewx[1195]: engine: Clock error is -0.57
seconds (positive is fast)
Dec 16 00:16:57 raspberrypi weewx[1195]: engine: Starting main packet loop.
Dec 16 00:20:18 raspberrypi weewx[1195]: ds18b20: found value of 71.4866
Dec 16 00:20:18 raspberrypi weewx[1195]: manager: Added record 2017-12-16
00:20:00 CET (151338) to database 'weewx.sdb'
Dec 16 00:20:18 raspberrypi weewx[1195]: manager: Added record 2017-12-16
00:20:00 CET (151338) to daily summary in 'weewx.sdb'
Dec 16 00:20:49 raspberrypi weewx[1195]: cheetahgenerator: Generated 14
files for report StandardReport in 27.79 seconds

pi@raspberrypi:~ $ tail /var/log/syslog
Dec 16 00:16:57 raspberrypi weewx[1195]: engine: Starting up weewx version
3.8.0
Dec 16 00:16:57 raspberrypi weewx[1195]: engine: Clock error is -0.57
seconds (positive is fast)
Dec 16 00:16:57 raspberrypi weewx[1195]: engine: Starting main packet loop.
Dec 16 00:17:01 raspberrypi CRON[1204]: (root) CMD (   cd / && run-parts
--report /etc/cron.hourly)
Dec 16 00:20:18 raspberrypi weewx[1195]: ds18b20: found value of 71.4866
Dec 16 00:20:18 raspberrypi weewx[1195]: manager: Added record 2017-12-16
00:20:00 CET (151338) to database 'weewx.sdb'
Dec 16 00:20:18 raspberrypi weewx[1195]: manager: Added record 2017-12-16
00:20:00 CET (151338) to daily summary in 'weewx.sdb'
Dec 16 00:20:49 raspberrypi weewx[1195]: cheetahgenerator: Generated 14
files for report StandardReport in 27.79 seconds
Dec 16 00:20:53 raspberrypi weewx[1195]: imagegenerator: Generated 12
images for StandardReport in 4.09 seconds
Dec 16 00:20:53 raspberrypi weewx[1195]: copygenerator: copied 9 files to
/var/www/html/weewx

Great! 71.48F So temperature readings are indeed being read and stored.

I will have a good look at Customizing reports, thank you for the link.
Looks very interesting.

pi@raspberrypi:~ $ sudo systemctl stop weewx.service

pi@raspberrypi:~ $ sudo /usr/share/weewx/weewxd /etc/weewx/weewx.conf
LOOP:   2017-12-16 00:30:12 CET (1513380612) altimeter: 31.0947369861,
appTemp: 28.2105115068, barometer: 31.0999349264, cloudbase: 1246.45336708,
dateTime: 1513380612, dewpoint: 26.9858954849, heatindex: 32.4558545686,
humidex: 32.4558545686, inDewpoint: 31.0785201424, inHumidity:
29.9973971396, inTemp: 63.0013014302, maxSolarRad: None, outHumidity:
79.9980477911, outTemp: 32.4558545686, pressure: 31.0999349264, radiation:
0, rain: 0.0, rainRate: 0.04, usUnits: 1, UV: 0, windchill: 32.4558545686,
windDir: 359.988286747, windGust: 0.000390441770883, windGustDir:
359.988286747, windSpeed: 0.000325368142403
LOOP:   2017-12-16 00:30:15 CET (1513380615) altimeter: 31.0947359449,
appTemp: 28.2085542481, barometer: 31.0999338852, cloudbase: 1246.44544679,
dateTime: 1513380615, dewpoint: 26.9841848881, heatindex: 32.4541091226,
humidex: 32.4541091226, inDewpoint: 31.0785039227, inHumidity:
29.9973554963, inTemp: 63.0013222519, maxSolarRad: None, outHumidity:
79.9980165566, outTemp: 32.4541091226, pressure: 31.0999338852, radiation:
0, rain: 0.0, rainRate: 0.04, usUnits: 1, UV: 0, windchill: 32.4541091226,
windDir: 359.98809934, windGust: 0.000396688671222, windGustDir:
359.98809934, windSpeed: 0.000330573892684
REC:2017-12-16 00:30:00 CET (1513380600) altimeter: 31.0947817327,
appTemp: 28.3384578077, barometer: 31.0999796687, cloudbase: 1247.01954441,
dateTime: 1513380600.0, dewpoint: 27.0975535731, ET: 0.0, extraTemp1:
71.2616, heatindex: 32.5700038371, humidex: 32.5700038371, inDewpoint:
31.0792171359, inHumidity: 29.9991867618, inTemp: 63.0004066191, interval:
5, maxSolarRad: None, outHumidity: 79.9993900603, outTemp: 32.5700038371,
pressure: 31.0999796687, radiation: 0.0, rain: 0.0, 

Re: [weewx-user] --reading failure in weewx_3.8.0-1 and weewx-owfs-0.21 Raspberry Pi & DS18B20

[Glenn McKechnie]

Returning from the discusion at
https://groups.google.com/forum/#!topic/weewx-user/CfhGLIF8aaU


On 16 December 2017 at 02:49, mixpc75  wrote:
>
> Glenn,
>
> We're on the right track! I noticed Horacio's message and tried to
implement it in an earlier attempt but maybe I messed it up or maybe - as I
think of it now - it was just a matter of getting
>
> owfs-common_2.9p8-6_all.deb

[...]

Just so we are clear on it - those packages don't apply to your case
anymore. Neither owfs or OWFS are relevant here.

> sudo nano /usr/share/weewx/user/ds18b20.py with Horacio's code
> edited self.filename to show my ds18b20 id
>
> sudo nano /etc/weewx/weewx.conf
> added to [[services]] the line
> data_services = user.ds18b20.ds18b20_Service
> and commented
> #data_services = ,
> to avoid duplication
>
> No ther changes done so [OWFS] section remains the same as well as
[Station] showing station_type = Simulator
>

[OWFS] is redundant - it no longer applies as you are not using the owfs
driver/service. Use wee_extension --uninstall owfs to remove it cleanly
(unless you hand edited back in?). Either way remove it.
Using the Simulator is okay at this stage, you are using it to allow weewx
to start and run.


> The fact is that starting weewx now produces no error!
>
> pi@raspberrypi:~ $ sudo systemctl start weewx.service
>
> pi@raspberrypi:~ $ sudo systemctl status weewx.service
> ● weewx.service - LSB: weewx weather system
>Loaded: loaded (/etc/init.d/weewx; generated; vendor preset: enabled)
>Active: active (running) since Fri 2017-12-15 12:23:34 CET; 6s ago

[...]

Yep, while I dislike systemd's logging. Those summaries do show it's
working. :-)


[...]

> As the guideline
> https://github.com/weewx/weewx/wiki/add-sensor
> indicates: "The data will not be displayed on the weather station
console, but they will be displayed in WeeWX reports." So needless to run:
>
> PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/owfs.py --sensors
> sudo PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/owfs.py
--sensors

Needless. Yes, these are only of use if you're using mwalls driver with a
1-wire bus master.

>
> So temperature readings are taking place every 5 minutes, great! :) But
they are not being displayed by the webserver 192.16.1.2 which shows the
default weewx webpage:

There are several things - not necessarily in order.

A quick and temporary way to see if the script is returning a value is to
change DEBUG to INFO around line 39 -ish...
[...]
syslog.syslog(syslog.LOG_DEBUG, "ds18b20: found value of %s" %
value)
becomes
   # syslog.syslog(syslog.LOG_DEBUG, "ds18b20: found value of %s" %
value)
syslog.syslog(syslog.LOG_INFO, "ds18b20: found value of %s" %
value)

and run tail -f /var/log/syslog in another terminal. You should see that
message pop up, with a value every 5 minutes.

>From Horacios post...

>> As a result the extraTemp1 value is available in weewx. It is possible
to change the event label in the third line from the bottom of ds18b20.py

You don't want to change the event label until you're more confident with
weewx, but as it is now you should have values being placed into the
database under extraTemp1
If they are there, then it's reading and storing the value. You can then
use them in your reports by configuring your skin.conf and the
index.html.tmpl accordingly.
http://www.weewx.com/docs/customizing.htm#customizing_reports

Also.
>From Horacios ds18b20.py script...
  [...]
self.bind(weewx.NEW_ARCHIVE_RECORD, self.read_temp)

Shows that they should be showing up in the archive record.

stop weewx and run it directly (
http://www.weewx.com/docs/usersguide.htm#Running_directly ) using...

 /usr/share/weewx/weewxd  /etc/weewx/weewx.conf

You'll see lines starting with LOOP: and REC:  REC is the
NEW_ARCHIVE_RECORD and that's where they should show up. They won't be seen
under LOOP: as the driver doesn't use that - (perhaps it should?)

[...]

> But since it configured as a service, how should weewx.conf be edited so
that it takes values from Horacio's script?

[...]

> But what about this particular case? Editing station_type = DS18B20

Short answer - No.
Long answer: Not sure how you go running one sensor like this. Usually it's
supplementing an exisiting stations data. That's a question for those more
knowledgeable although the documentation has a section showing how to
implement it as a driver :)
http://www.weewx.com/docs/customizing.htm#Implement_the_driver

> and then adding a [DS18B20] tag at the end of the file?
>
> [OWFS]
> interface = u
> [[sensor_map]]
> outTemp = extraTemp1 # variable from
/usr/share/weewx/user/ds18b20.py

Nope. ds18b20.py doesn't use section headings (such as [DS18B20]) so it
won't be looking for any user additions to the weewx.conf file. If it was a
driver in it's own right then you could have and use a [DS18B20] section.

However you may be able to remap 

Re: [weewx-user] Re: weewx-owfs failure with new Raspbian Stretch

[Glenn McKechnie]

Howard,

Good. I've subscribed and will follow the issue there.

Miguel,

I'll reply to your issue back on your original thread at
https://groups.google.com/forum/#!topic/weewx-user/yO-z8aqzcU0
as it's unrelated to Howards problem here.


Cheers
 Glenn

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


On 16 December 2017 at 07:34, Howard Walter  wrote:
> A bug report about this issue has been sent to the owfs-developers email
> list.
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: install error

[Eric Gammeter]

NP-  this is a clean install-  so I don't have anything to loose by 
reinstalling Debian 9!  It turns out to be good instruction/learning for 
me.  No need to pursue this issue. Thank you much!  /Eric G.  

On Friday, December 15, 2017 at 2:17:44 PM UTC-5, Eric Gammeter wrote:
>
> Installing WEEWX 3.8.0 tar.gz onto my Debian 9 box and I get the following 
> error:
>
> I do not know how to proceed.  Any input?  
>
> /Thanks much...
>
> root@debian:~# apt-get install weewx
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Suggested packages:
>   sqlite ftp python-dev python-pip
> The following NEW packages will be installed:
>   weewx
> 0 upgraded, 1 newly installed, 0 to remove and 31 not upgraded.
> Need to get 1,205 kB of archives.
> After this operation, 4,981 kB of additional disk space will be used.
> Get:1 http://weewx.com/apt squeeze/main all weewx all 3.8.0-1 [1,205 kB]
> Fetched 1,205 kB in 2s (478 kB/s)
> Preconfiguring packages ...
> Selecting previously unselected package weewx.
> (Reading database ... 158328 files and directories currently installed.)
> Preparing to unpack .../archives/weewx_3.8.0-1_all.deb ...
> Unpacking weewx (3.8.0-1) ...
> Setting up weewx (3.8.0-1) ...
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_config", line 14, in 
> from weecfg.config import ConfigEngine
>   File "/usr/share/weewx/weecfg/__init__.py", line 18, in 
> import configobj
> ImportError: No module named configobj
> dpkg: error processing package weewx (--configure):
>  subprocess installed post-installation script returned error exit status 1
> Processing triggers for systemd (232-25+deb9u1) ...
> Errors were encountered while processing:
>  weewx
> E: Sub-process /usr/bin/dpkg returned an error code (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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx-owfs failure with new Raspbian Stretch

[Howard Walter]

A bug report about this issue has been sent to the owfs-developers email 
list.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: install error

[vince]

On Friday, December 15, 2017 at 11:57:36 AM UTC-8, Eric Gammeter wrote:
>
> Thank you very much for your assistance.
>
>>
>>
I just did a quick clean install in a new debian9 vagrant VM from the apt 
package, which installed just fine (so the package is ok).

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: install error

[Eric Gammeter]

Thank you very much for your assistance.
/Eric

On Friday, December 15, 2017 at 2:17:44 PM UTC-5, Eric Gammeter wrote:
>
> Installing WEEWX 3.8.0 tar.gz onto my Debian 9 box and I get the following 
> error:
>
> I do not know how to proceed.  Any input?  
>
> /Thanks much...
>
> root@debian:~# apt-get install weewx
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Suggested packages:
>   sqlite ftp python-dev python-pip
> The following NEW packages will be installed:
>   weewx
> 0 upgraded, 1 newly installed, 0 to remove and 31 not upgraded.
> Need to get 1,205 kB of archives.
> After this operation, 4,981 kB of additional disk space will be used.
> Get:1 http://weewx.com/apt squeeze/main all weewx all 3.8.0-1 [1,205 kB]
> Fetched 1,205 kB in 2s (478 kB/s)
> Preconfiguring packages ...
> Selecting previously unselected package weewx.
> (Reading database ... 158328 files and directories currently installed.)
> Preparing to unpack .../archives/weewx_3.8.0-1_all.deb ...
> Unpacking weewx (3.8.0-1) ...
> Setting up weewx (3.8.0-1) ...
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_config", line 14, in 
> from weecfg.config import ConfigEngine
>   File "/usr/share/weewx/weecfg/__init__.py", line 18, in 
> import configobj
> ImportError: No module named configobj
> dpkg: error processing package weewx (--configure):
>  subprocess installed post-installation script returned error exit status 1
> Processing triggers for systemd (232-25+deb9u1) ...
> Errors were encountered while processing:
>  weewx
> E: Sub-process /usr/bin/dpkg returned an error code (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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: install error

[Eric Gammeter]

root@debian:/etc/apt# cat sources.list
# 

# deb cdrom:[Debian GNU/Linux 9.2.1 _Stretch_ - Official amd64 DVD Binary-1 
20171013-13:09]/ stretch contrib main

#deb cdrom:[Debian GNU/Linux 9.2.1 _Stretch_ - Official amd64 DVD Binary-1 
20171013-13:09]/ stretch contrib main

deb http://ftp.us.debian.org/debian/ stretch main
deb-src http://ftp.us.debian.org/debian/ stretch main

deb http://security.debian.org/debian-security stretch/updates main contrib
deb-src http://security.debian.org/debian-security stretch/updates main 
contrib

# stretch-updates, previously known as 'volatile'
deb http://ftp.us.debian.org/debian/ stretch-updates main contrib
deb-src http://ftp.us.debian.org/debian/ stretch-updates main contrib
deb-src http://http.us.debian.org/debian unstable main


root@debian:/home/eric# python -c "import sys;print sys.path;import 
configobj;print configobj.__file__"
['', '/usr/local/lib/python27.zip', '/usr/local/lib/python2.7', 
'/usr/local/lib/python2.7/plat-linux2', '/usr/local/lib/python2.7/lib-tk', 
'/usr/local/lib/python2.7/lib-old', '/usr/local/lib/python2.7/lib-dynload', 
'/usr/local/lib/python2.7/site-packages']
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named configobj


On Friday, December 15, 2017 at 2:17:44 PM UTC-5, Eric Gammeter wrote:
>
> Installing WEEWX 3.8.0 tar.gz onto my Debian 9 box and I get the following 
> error:
>
> I do not know how to proceed.  Any input?  
>
> /Thanks much...
>
> root@debian:~# apt-get install weewx
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Suggested packages:
>   sqlite ftp python-dev python-pip
> The following NEW packages will be installed:
>   weewx
> 0 upgraded, 1 newly installed, 0 to remove and 31 not upgraded.
> Need to get 1,205 kB of archives.
> After this operation, 4,981 kB of additional disk space will be used.
> Get:1 http://weewx.com/apt squeeze/main all weewx all 3.8.0-1 [1,205 kB]
> Fetched 1,205 kB in 2s (478 kB/s)
> Preconfiguring packages ...
> Selecting previously unselected package weewx.
> (Reading database ... 158328 files and directories currently installed.)
> Preparing to unpack .../archives/weewx_3.8.0-1_all.deb ...
> Unpacking weewx (3.8.0-1) ...
> Setting up weewx (3.8.0-1) ...
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_config", line 14, in 
> from weecfg.config import ConfigEngine
>   File "/usr/share/weewx/weecfg/__init__.py", line 18, in 
> import configobj
> ImportError: No module named configobj
> dpkg: error processing package weewx (--configure):
>  subprocess installed post-installation script returned error exit status 1
> Processing triggers for systemd (232-25+deb9u1) ...
> Errors were encountered while processing:
>  weewx
> E: Sub-process /usr/bin/dpkg returned an error code (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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] install error

[Thomas Keffer]

It looks like you have a PYTHONPATH problem.

What came before your posted excerpts? Did you add the WeeWX Debian
repository first? If so, it should have automatically done the necessary
installs. Or, did you install some manually, perhaps in an unusual spot?

Try running this command:

python -c "import sys;print sys.path;import configobj;print
configobj.__file__"


It should give us some clues.

On Fri, Dec 15, 2017 at 1:17 PM, Eric Gammeter  wrote:

> Installing WEEWX 3.8.0 tar.gz onto my Debian 9 box and I get the following
> error:
>
> I do not know how to proceed.  Any input?
>
> /Thanks much...
>
> root@debian:~# apt-get install weewx
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Suggested packages:
>   sqlite ftp python-dev python-pip
> The following NEW packages will be installed:
>   weewx
> 0 upgraded, 1 newly installed, 0 to remove and 31 not upgraded.
> Need to get 1,205 kB of archives.
> After this operation, 4,981 kB of additional disk space will be used.
> Get:1 http://weewx.com/apt squeeze/main all weewx all 3.8.0-1 [1,205 kB]
> Fetched 1,205 kB in 2s (478 kB/s)
> Preconfiguring packages ...
> Selecting previously unselected package weewx.
> (Reading database ... 158328 files and directories currently installed.)
> Preparing to unpack .../archives/weewx_3.8.0-1_all.deb ...
> Unpacking weewx (3.8.0-1) ...
> Setting up weewx (3.8.0-1) ...
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_config", line 14, in 
> from weecfg.config import ConfigEngine
>   File "/usr/share/weewx/weecfg/__init__.py", line 18, in 
> import configobj
> ImportError: No module named configobj
> dpkg: error processing package weewx (--configure):
>  subprocess installed post-installation script returned error exit status 1
> Processing triggers for systemd (232-25+deb9u1) ...
> Errors were encountered while processing:
>  weewx
> E: Sub-process /usr/bin/dpkg returned an error code (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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: install error

[Eric Gammeter]

Didn't do the trick.  
??

ot@debian:~# apt-get install python-configobj
Reading package lists... Done
Building dependency tree   
Reading state information... Done
python-configobj is already the newest version (5.0.6-2).
python-configobj set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 31 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up weewx (3.8.0-1) ...
Traceback (most recent call last):
  File "/usr/share/weewx/wee_config", line 14, in 
from weecfg.config import ConfigEngine
  File "/usr/share/weewx/weecfg/__init__.py", line 18, in 
import configobj
ImportError: No module named configobj
dpkg: error processing package weewx (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 weewx
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@debian:~# apt-get install weewx
Reading package lists... Done
Building dependency tree   
Reading state information... Done
weewx is already the newest version (3.8.0-1).
0 upgraded, 0 newly installed, 0 to remove and 31 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up weewx (3.8.0-1) ...
Traceback (most recent call last):
  File "/usr/share/weewx/wee_config", line 14, in 
from weecfg.config import ConfigEngine
  File "/usr/share/weewx/weecfg/__init__.py", line 18, in 
import configobj
ImportError: No module named configobj
dpkg: error processing package weewx (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 weewx
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@debian:~# apt-get remove weewx
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer 
required:
  python-cheetah python-serial python-usb
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  weewx
0 upgraded, 0 newly installed, 1 to remove and 31 not upgraded.
1 not fully installed or removed.
After this operation, 4,981 kB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 158537 files and directories currently installed.)
Removing weewx (3.8.0-1) ...
root@debian:~# apt-get install weewx
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Suggested packages:
  sqlite ftp python-dev python-pip
The following NEW packages will be installed:
  weewx
0 upgraded, 1 newly installed, 0 to remove and 31 not upgraded.
Need to get 0 B/1,205 kB of archives.
After this operation, 4,981 kB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously unselected package weewx.
(Reading database ... 158328 files and directories currently installed.)
Preparing to unpack .../archives/weewx_3.8.0-1_all.deb ...
Unpacking weewx (3.8.0-1) ...
Setting up weewx (3.8.0-1) ...
Traceback (most recent call last):
  File "/usr/share/weewx/wee_config", line 14, in 
from weecfg.config import ConfigEngine
  File "/usr/share/weewx/weecfg/__init__.py", line 18, in 
import configobj
ImportError: No module named configobj
dpkg: error processing package weewx (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (232-25+deb9u1) ...
Errors were encountered while processing:
 weewx
E: Sub-process /usr/bin/dpkg returned an error code (1)

On Friday, December 15, 2017 at 2:17:44 PM UTC-5, Eric Gammeter wrote:
>
> Installing WEEWX 3.8.0 tar.gz onto my Debian 9 box and I get the following 
> error:
>
> I do not know how to proceed.  Any input?  
>
> /Thanks much...
>
> root@debian:~# apt-get install weewx
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Suggested packages:
>   sqlite ftp python-dev python-pip
> The following NEW packages will be installed:
>   weewx
> 0 upgraded, 1 newly installed, 0 to remove and 31 not upgraded.
> Need to get 1,205 kB of archives.
> After this operation, 4,981 kB of additional disk space will be used.
> Get:1 http://weewx.com/apt squeeze/main all weewx all 3.8.0-1 [1,205 kB]
> Fetched 1,205 kB in 2s (478 kB/s)
> Preconfiguring packages ...
> Selecting previously unselected package weewx.
> (Reading database ... 158328 files and directories currently installed.)
> Preparing to unpack .../archives/weewx_3.8.0-1_all.deb ...
> Unpacking weewx (3.8.0-1) ...
> Setting up weewx (3.8.0-1) ...
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_config", line 14, in 
> from weecfg.config import ConfigEngine
>   File "/usr/share/weewx/weecfg/__init__.py", line 18, in 
> import configobj
> 

[weewx-user] Re: install error

[vince]

On Friday, December 15, 2017 at 11:17:44 AM UTC-8, Eric Gammeter wrote:
>
>  

> portError: No module named configobj
>
>
You're missing a package that needs to be installed.

try 'apt-get install python-configobj' and see if that gets you by the 
problem hopefully.   You'll probably need to retry your weewx installation 
I'm guessing.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] install error

[Eric Gammeter]

Installing WEEWX 3.8.0 tar.gz onto my Debian 9 box and I get the following 
error:

I do not know how to proceed.  Any input?  

/Thanks much...

root@debian:~# apt-get install weewx
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Suggested packages:
  sqlite ftp python-dev python-pip
The following NEW packages will be installed:
  weewx
0 upgraded, 1 newly installed, 0 to remove and 31 not upgraded.
Need to get 1,205 kB of archives.
After this operation, 4,981 kB of additional disk space will be used.
Get:1 http://weewx.com/apt squeeze/main all weewx all 3.8.0-1 [1,205 kB]
Fetched 1,205 kB in 2s (478 kB/s)
Preconfiguring packages ...
Selecting previously unselected package weewx.
(Reading database ... 158328 files and directories currently installed.)
Preparing to unpack .../archives/weewx_3.8.0-1_all.deb ...
Unpacking weewx (3.8.0-1) ...
Setting up weewx (3.8.0-1) ...
Traceback (most recent call last):
  File "/usr/share/weewx/wee_config", line 14, in 
from weecfg.config import ConfigEngine
  File "/usr/share/weewx/weecfg/__init__.py", line 18, in 
import configobj
ImportError: No module named configobj
dpkg: error processing package weewx (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (232-25+deb9u1) ...
Errors were encountered while processing:
 weewx
E: Sub-process /usr/bin/dpkg returned an error code (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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx-owfs failure with new Raspbian Stretch

[mixpc75]

Glenn,

We're on the right track! I noticed Horacio's message and tried to
implement it in an earlier attempt but maybe I messed it up or maybe - as I
think of it now - it was just a matter of getting

owfs-common_2.9p8-6_all.deb
libow-2.9-8_2.9p8-6_armhf.deb
python-ow_2.9p8-6_armhf.deb

as you brilliantly noted. The fact is that I have tried that approach now
(just hope Matthew won't be upset about not using fileparse.py) and

sudo nano /usr/share/weewx/user/ds18b20.py with Horacio's code
edited self.filename to show my ds18b20 id

sudo nano /etc/weewx/weewx.conf
added to [[services]] the line
data_services = user.ds18b20.ds18b20_Service
and commented
#data_services = ,
to avoid duplication

No ther changes done so [OWFS] section remains the same as well as
[Station] showing station_type = Simulator

The fact is that starting weewx now produces no error!

pi@raspberrypi:~ $ sudo systemctl start weewx.service

pi@raspberrypi:~ $ sudo systemctl status weewx.service
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx; generated; vendor preset: enabled)
   Active: active (running) since Fri 2017-12-15 12:23:34 CET; 6s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 821 ExecStop=/etc/init.d/weewx stop (code=exited,
status=0/SUCCESS)
  Process: 852 ExecStart=/etc/init.d/weewx start (code=exited,
status=0/SUCCESS)
   CGroup: /system.slice/weewx.service
   └─867 python /usr/bin/weewxd --daemon
--pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf

Dec 15 12:23:34 raspberrypi weewx[867]: manager: Starting backfill of daily
summaries
Dec 15 12:23:35 raspberrypi weewx[867]: restx: StationRegistry:
Registration not requested.
Dec 15 12:23:35 raspberrypi weewx[867]: restx: Wunderground: Posting not
enabled.
Dec 15 12:23:35 raspberrypi weewx[867]: restx: PWSweather: Posting not
enabled.
Dec 15 12:23:35 raspberrypi weewx[867]: restx: CWOP: Posting not enabled.
Dec 15 12:23:35 raspberrypi weewx[867]: restx: WOW: Posting not enabled.
Dec 15 12:23:35 raspberrypi weewx[867]: restx: AWEKAS: Posting not enabled.
Dec 15 12:23:35 raspberrypi weewx[867]: engine: Starting up weewx version
3.8.0
Dec 15 12:23:35 raspberrypi weewx[867]: engine: Clock error is -0.73
seconds (positive is fast)
Dec 15 12:23:35 raspberrypi weewx[867]: engine: Starting main packet loop.

And a few minutes later...

pi@raspberrypi:~ $ sudo systemctl status weewx.service
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx; generated; vendor preset: enabled)
   Active: active (running) since Fri 2017-12-15 12:23:34 CET; 11min ago
 Docs: man:systemd-sysv-generator(8)
  Process: 821 ExecStop=/etc/init.d/weewx stop (code=exited,
status=0/SUCCESS)
  Process: 852 ExecStart=/etc/init.d/weewx start (code=exited,
status=0/SUCCESS)
   CGroup: /system.slice/weewx.service
   └─867 python /usr/bin/weewxd --daemon
--pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf

Dec 15 12:25:18 raspberrypi weewx[867]: manager: Added record 2017-12-15
12:25:00 CET (1513337100) to database 'weewx.sdb'
Dec 15 12:25:18 raspberrypi weewx[867]: manager: Added record 2017-12-15
12:25:00 CET (1513337100) to daily summary in 'weewx.sdb'
Dec 15 12:25:47 raspberrypi weewx[867]: cheetahgenerator: Generated 14
files for report StandardReport in 27.19 seconds
Dec 15 12:26:11 raspberrypi weewx[867]: imagegenerator: Generated 36 images
for StandardReport in 21.48 seconds
Dec 15 12:26:11 raspberrypi weewx[867]: copygenerator: copied 9 files to
/var/www/html/weewx
Dec 15 12:30:17 raspberrypi weewx[867]: manager: Added record 2017-12-15
12:30:00 CET (1513337400) to database 'weewx.sdb'
Dec 15 12:30:17 raspberrypi weewx[867]: manager: Added record 2017-12-15
12:30:00 CET (1513337400) to daily summary in 'weewx.sdb'
Dec 15 12:30:27 raspberrypi weewx[867]: cheetahgenerator: Generated 14
files for report StandardReport in 8.06 seconds
Dec 15 12:30:31 raspberrypi weewx[867]: imagegenerator: Generated 12 images
for StandardReport in 3.48 seconds
Dec 15 12:30:31 raspberrypi weewx[867]: copygenerator: copied 0 files to
/var/www/html/weewx


and...

pi@raspberrypi:~ $ sudo systemctl status weewx.service
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx; generated; vendor preset: enabled)
   Active: active (running) since Fri 2017-12-15 12:23:34 CET; 13min ago
 Docs: man:systemd-sysv-generator(8)
  Process: 821 ExecStop=/etc/init.d/weewx stop (code=exited,
status=0/SUCCESS)
  Process: 852 ExecStart=/etc/init.d/weewx start (code=exited,
status=0/SUCCESS)
   CGroup: /system.slice/weewx.service
   └─867 python /usr/bin/weewxd --daemon
--pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf

Dec 15 12:30:17 raspberrypi weewx[867]: manager: Added record 2017-12-15
12:30:00 CET (1513337400) to database 'weewx.sdb'
Dec 15 12:30:17 raspberrypi weewx[867]: manager: Added record 2017-12-15
12:30:00 CET (1513337400) to daily summary in 'weewx.sdb'
Dec 15 12:30:27 raspberrypi weewx[867]: 

[weewx-user] Re: FineOffset Hang ups

[Redanman]

The insides didn't really tell me much.  The 433Mhz cable was pinched by 
the case as I've seen already mention here already, but not such that it 
was cut.  The USB connectors are permanent covered by the lead plugs, so 
there is no reason why grime would get in.  I had a look anyway and they 
are immaculate.  I changed the USB cable a little while back, but that had 
no effect.  I'll try a different power supply for the Pi as their 
performance can drop off with time or maybe I'll try and find a powered hub 
from somewhere.

On Monday, 11 December 2017 22:54:03 UTC, Redanman wrote:
>
> My old WH1080 is getting more more and more USB hang-ups.  I have to reset 
> the unit (remove the USB cable) to reboot the it.  I obviously lose the 
> data in the circular buffer, so, depending on when I notice the hang-up, it 
> leads to data loss of several hours or even days.
> I power the WH1080 through the USB cable connected to my Pi, but I do not 
> have a USB hub, so cannot cycle the power through the hub.  I have noticed 
> that if I reboot the Pi it cycles the power on the Pi's own USB ports, so 
> resetting the WH1080.  Is it possible to do this automatically within Weewx 
> if it detects a USB hang-up?
> Mike

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx-wd getting keyerror: meter

[gjr80]

Hi,

Not an error I have seen before. Apologies I have not had a chance to look 
at this so far, hopefully this weekend.

Gary

On Tuesday, 12 December 2017 10:20:46 UTC+10, Radar wrote:
>
> just installed weewx 3.8.0 and weewx-wd 1.0.3 and getting keyerror: meter 
> from Testtags, wdClientraw, wdSteelGauges 
> wdPWS and wdStackedWindRose are working
>
> here is the log and weewx.conf files
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx-owfs failure with new Raspbian Stretch

[Glenn McKechnie]

The first couple of lines at pastebin are revealing...

pi@raspberrypi:~ $ python temp_ds18b20.py
(21.812, 71.2616)
(21.812, 71.2616)
^CTraceback (most recent call last):
  File "temp_ds18b20.py", line 30, in 
time.sleep(1)
KeyboardInterrupt

That indicates that you aren't using an owfs compatabile interface (bus
master)

http://owfs.org/index.php?page=bus-masters

which means that, to my knowledge, running mwalls owfs driver, or any OWFS
software won't help you.

I could certainly be wrong but I don't think the GPIO and 1-wire kernel
module (enabled via raspi-config) talk to OWFS.

That shouldn't mean that you can't use it with weewx but you need to
approach it differently.

You've got a value being returned via your script (is it this
https://github.com/simonmonk/raspberrypi_cookbook_ed2/blob/master/temp_DS18B20.py
?) so you're half way there.  You need to find or write a script that will
enable you to present that data ( temperature value) and have it read by
weewx.
The fileparse driver could be a good starting point for the slurp end?
https://github.com/weewx/weewx/tree/master/examples/fileparse with your
script writing the data?

Or

Perhaps Horacio's work may speed you along.

How to add a ds18b20 thermometer to raspberry pi and weewx
https://groups.google.com/forum/#!searchin/weewx-user/ds18b20|sort:date/weewx-user/n1BbF3FAKh8/XxdPovR3AgAJ







Cheers
 Glenn

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

On 15 December 2017 at 19:55, mixpc75  wrote:

> Glen,
>
> That is fantastic! :) Clasp, clasp, clasp! :) I thank you for your two
> messages, this one and the one in the other thread. I preferred getting
> back to topic after trying from my side and let you know. I have not been
> as successful as you on mi RP1 and since I think I have folowed the steps
> correctly (again, writing a new image to SD, enabling 1-Wire, running a
> python script test it etc.). And I am beginning to wonder whether it might
> not work on a RPi1 but work successfully on a RPi3... I think I will mirror
> your steps in a RPi3 later on today and will get back with output.
>
> I have made myself sure I have installed your .deb packages
>
> My package versions matched yours
>
> pi@raspberrypi:~ $ dpkg --list | grep ow
> ii  libow-3.1-5:armhf   3.1p5-1
> armhf1-Wire File System full library
> ii  owfs-common 3.1p5-1
> all  common files used by any of the OWFS programs
> ii  python-ow   3.1p5-1
> armhfDallas 1-wire support: Python bindings
>
> And we are on the same version weewx-owfs-0.21.tgz as well and, of course,
> same weewx version.
>
> sudo apt-get remove libow-3.1-5 owfs-common python-ow
> sudo reboot
> sudo dpkg --install owfs-common_2.9p8-6_all.deb (this deb first)
> sudo dpkg --install libow-2.9-8_2.9p8-6_armhf.deb
> sudo dpkg --install python-ow_2.9p8-6_armhf.deb
>
> Here is a linked to a bash'ed log with every command issued. The -sensors
> commands are towards the botton, of course.
> https://pastebin.com/Nkk5Th6V
>
>
> Please, mind I'm running my tests on a RPi1 armv61.
>
> Thank you once more and regards,
>
>
>
>
> On 14 December 2017 at 21:41, Howard Walter  wrote:
>
>> Nice detective work Glenn!
>>
>> I'll have a chance in the next few days to try the older versions.
>>
>>
>>
>> --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx-owfs failure with new Raspbian Stretch

[mixpc75]

Glen,

That is fantastic! :) Clasp, clasp, clasp! :) I thank you for your two
messages, this one and the one in the other thread. I preferred getting
back to topic after trying from my side and let you know. I have not been
as successful as you on mi RP1 and since I think I have folowed the steps
correctly (again, writing a new image to SD, enabling 1-Wire, running a
python script test it etc.). And I am beginning to wonder whether it might
not work on a RPi1 but work successfully on a RPi3... I think I will mirror
your steps in a RPi3 later on today and will get back with output.

I have made myself sure I have installed your .deb packages

My package versions matched yours

pi@raspberrypi:~ $ dpkg --list | grep ow
ii  libow-3.1-5:armhf   3.1p5-1
armhf1-Wire File System full library
ii  owfs-common 3.1p5-1
all  common files used by any of the OWFS programs
ii  python-ow   3.1p5-1
armhfDallas 1-wire support: Python bindings

And we are on the same version weewx-owfs-0.21.tgz as well and, of course,
same weewx version.

sudo apt-get remove libow-3.1-5 owfs-common python-ow
sudo reboot
sudo dpkg --install owfs-common_2.9p8-6_all.deb (this deb first)
sudo dpkg --install libow-2.9-8_2.9p8-6_armhf.deb
sudo dpkg --install python-ow_2.9p8-6_armhf.deb

Here is a linked to a bash'ed log with every command issued. The -sensors
commands are towards the botton, of course.
https://pastebin.com/Nkk5Th6V


Please, mind I'm running my tests on a RPi1 armv61.

Thank you once more and regards,




On 14 December 2017 at 21:41, Howard Walter  wrote:

> Nice detective work Glenn!
>
> I'll have a chance in the next few days to try the older versions.
>
>
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.