Re: [weewx-user] Live weather on iOS

2020-12-07 Thread Constantine Samaklis 
I have submitted a new build where the topic can be specified. As soon as 
it gets approved, I will post a link where you can use testflight for you 
to test it and see if it works as expected.

On Sunday, December 6, 2020 at 7:42:20 PM UTC-5 bell...@gmail.com wrote:

> This looks really cool. I too am anxiously awaiting to be able to specify 
> the topic.  In my case, I am publishing json loop data to weather/loop, 
> json archive data to weather/archive, both to weather/looparchive.  So if I 
> could specify something like weather/loop-individual/#... but I could 
> easily publish to almost anything but weather/#. 
> Again, thanks for sharing! If I can help in any way, let me know.
> rich
>
> On Sunday, 6 December 2020 at 18:37:04 UTC-5 blu...@gmail.com wrote:
>
>> Ok understood; my topics are published as weather/corbett and 
>> weather/williams for different locations.  I look forward to that 
>> enhancement!  This looks like a cool app.  
>>
>> On Dec 6, 2020, at 3:27 PM, Constantine Samaklis  
>> wrote:
>>
>> Currently no. It defaults to weather/#. The gauges are also limited to 
>> the topics published by the MQTT extension so for example if you have 
>> configured the extension to run in metric, you will 
>> have weather/windchill_C for windchill and if you have it configured for 
>> imperial units, then it will listen for weather/windchill_F.
>>
>>
>> The pattern is similar across all the available gauges. 
>>
>> I have also left some topics as soil alarm and other alarm ones out, as 
>> they are present only in professional weather stations such as Vantage Pro, 
>> and have not seen them used, outside of farming applications. (On my todo 
>> list at some point though.)
>>
>> On Sunday, December 6, 2020 at 6:15:19 PM UTC-5 blu...@gmail.com wrote:
>>
>>> I love this!  Is there a way to change the topic name to look for? 
>>>
>>> On Dec 6, 2020, at 12:42 PM, Christopher Joseph Alemany <
>>> chri...@gmail.com> wrote:
>>>
>>> Very cool! Thank you Constantine and great work!  I’ll install the mqtt 
>>> extension just for this. Consider this friendly and appreciative 
>>> encouragement to port it to Swift! 
>>>
>>>
>>> Cheers
>>> Chris
>>> www.Alberniweather.ca
>>> “They always tell me it takes time. How much more time do you want...for 
>>> your progress?”
>>> James Baldwin
>>>
>>> Chris Alemany
>>> 3854 6th Ave
>>> Port Alberni, BC
>>> V9Y4M2
>>> h:250-723-0889
>>> w: 250-753-3245 x2106 <250-753-3245;2106>
>>> e: chri...@gmail.com
>>> w: www.chrisalemany.ca
>>> w: www.alberniweather.ca
>>> w: www.vifreightbyrail.ca
>>>
>>> On Dec 6, 2020, at 08:30, Constantine Samaklis  
>>> wrote:
>>>
>>> I have been using WeeWX for seven years or so and I have been inspired 
>>> by the work that Tom and others have put into making this software better 
>>> and also expandable.
>>>
>>> Ever since I added the MQTT extension to WeeWX I was able to incorporate 
>>> live weather data from my Vantage Pro weather station, which I think it is 
>>> very cool.
>>>
>>> I wanted to give back something to the community, so I spent some time 
>>> writing a GUI in Pythonista on my iPad, and I have ported it over to the 
>>> Apple store as a free application, in hopes that it can be useful to 
>>> others. 
>>>
>>> I am always mesmerized by moving dials and I also find that the 
>>> application, apart from giving you quick access to your weather station's 
>>> data, it looks quite good as a make shift screen, especially on larger iPad 
>>> screens. :-)
>>>
>>> You can fetch the application from the app store from the below link or 
>>> look for "weather mqtt" 
>>>
>>> https://apps.apple.com/us/app/weather-mqtt/id1542679289 
>>>
>>> I have also put together a quick user guide at; 
>>> https://www.samaklis.com/confluence/display/WEAT/2020/12/05/Weather+MQTT+Support
>>>  
>>>
>>> PS The application is a port from Python to Objective C, so you may 
>>> experience a crash from time to time as it is not OS native. I am in the 
>>> process of looking into SWIFT and in time, based on community interest, I 
>>> will try and put some work on porting the application to it. so it is iOS 
>>> native.
>>>
>>> Thanks again to all the weather enthusiasts out there that make 
>>> applications like WeeWX possible.
>>>
>>> 
>>>
>>> -- 
>>> 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/0084e413-3fac-446d-a8c1-7158db8ebb72n%40googlegroups.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, s

Re: [weewx-user] Upgrading weewx, plugins and python

2020-12-07 Thread Gordon Dickens 

  
  
Thanks very much Tom for your very helpful post! 
  I suspected that was the case and I will proceed by first
  upgrading weewx to V4 as you suggested.
  

On 12/7/20 1:43 PM, Tom Keffer wrote:


  
  
The error 'file' is not
  defined was fixed in WeeWX V4 as part of the port to Python 3.
  You will get LOTS of these kinds of errors trying to run WeeWX
  V3 under Python 3. Either upgrade WeeWX first, or use Python
  2.7.
  
  
  
On Mon, Dec 7, 2020 at 9:44 AM
  Gordon Dickens  wrote:


  Hello all,
  
  
  I have been successfully running the following versions
of weewx software, skins and python on Debian 10 and I need
to upgrade the software as depicted here:
  
weewx current version 3.9.2 needs upgrading to 4.2.0.
Belchertown Skin current version 1.0.1 needs upgrading
  to 1.2
Weather34 Skin current version WX-UB40-IHVN-0.9.1 needs
  upgrading toW34-HC-IMJD-3.0.0
Python current version 2.7 needs upgrading to Python
  3.7.3
  
  As an FYI, weewx is installed from the Debian weewx
package with the Debian package manager, apt.
  
  
  
  What is the recommended order for performing these
upgrades?
  
  
  My initial thoughts were to upgrade in this order:
  

  Upgrade Python to version 3.7.3
  Upgrade weew to version 4.2.0
  Upgrade the Belchertown skin to verion 1.2
  Upgrade the Weather34 skin to version
W34-HC-IMJD-3.0.0

So, I began the python upgrade by installing python
  3.7.3 and the python3 dependencies: python3-configobj
  python3-pil  python3-serial, python3-usb, python3-pip,
  python3-cheetah, 
  python3-ephem, python3-mysqldb.


I then
  used the update-alternatives package to
  switch the default python command to
  python 3.7.3.  Then, after I started the
  weewx service with "systemctl restart
  weewx", the command "systemctl status
  weewx" generates the following error
  dialog:



●
  weewx.service - LSB: weewx weather system
     Loaded: loaded (/etc/init.d/weewx;
  generated)
     Active: active (exited) since Mon
  2020-12-07 09:12:53 EST; 7s ago
   Docs: man:systemd-sysv-generator(8)
    Process: 28868
  ExecStart=/etc/init.d/weewx start
  (code=exited, status=0/SUCCESS)
  
  Dec 07 09:12:53 zeebytes.org
  weewx[28868]: Starting weewx weather
  system: weewxTraceback (most recent call
  last):
  Dec 07 09:12:53 zeebytes.org
  weewx[28868]:   File "/usr/bin/weewxd",
  line 64, in 
  Dec 07 09:12:53 zeebytes.org
  weewx[28868]:
  weewx.engine.main(options, args)
  Dec 07 09:12:53 zeebytes.org
  weewx[28868]:   File
  "/usr/share/weewx/weewx/engine.py", line
  845, in main
  Dec 07 09:12:53 zeebytes.org
  weewx[28868]:
  daemon.daemonize(pidfile=options.pidfile)
  Dec 07 09:12:53 zeebytes.org
  weewx[28868]:   File
  "/usr/share/weewx/daemon.py", line 71, in
  daemonize
  Dec 07 09:12:53 zeebytes.org
  weewx[28868]: si = file(stdin, 'r')
  Dec 07 09:12:53 zeebytes.org
  weewx[28868]: NameError: name 'file' is
  not defined
  Dec 07 09:12:53 zeebytes.org
  weewx[28868]: .
  Dec 07 09:12:53 zeebytes.org

Re: [weewx-user] Upgrading weewx, plugins and python

2020-12-07 Thread Gordon Dickens 


Thanks very much Tom for your very helpful post!  I suspected that was the 
case and I will proceed by first upgrading weewx to V4 as you suggested.
On Monday, December 7, 2020 at 1:43:40 PM UTC-5 tke...@gmail.com wrote:

> The error 'file' is not defined was fixed in WeeWX V4 as part of the port 
> to Python 3. You will get LOTS of these kinds of errors trying to run WeeWX 
> V3 under Python 3. Either upgrade WeeWX first, or use Python 2.7.
>
> On Mon, Dec 7, 2020 at 9:44 AM Gordon Dickens  wrote:
>
>> Hello all,
>>
>> I have been successfully running the following versions of weewx 
>> software, skins and python on Debian 10 and I need to upgrade the software 
>> as depicted here:
>>
>>- weewx current version 3.9.2 needs upgrading to 4.2.0.
>>- Belchertown Skin current version 1.0.1 needs upgrading to 1.2
>>- Weather34 Skin current version WX-UB40-IHVN-0.9.1 needs upgrading 
>>toW34-HC-IMJD-3.0.0
>>- Python current version 2.7 needs upgrading to Python 3.7.3
>>
>> As an FYI, weewx is installed from the Debian weewx package with the 
>> Debian package manager, apt.
>>
>> What is the recommended order for performing these upgrades?
>>
>> My initial thoughts were to upgrade in this order:
>>
>>1. Upgrade Python to version 3.7.3
>>2. Upgrade weew to version 4.2.0
>>3. Upgrade the Belchertown skin to verion 1.2
>>4. Upgrade the Weather34 skin to version W34-HC-IMJD-3.0.0
>>
>> So, I began the python upgrade by installing python 3.7.3 and the python3 
>> dependencies: python3-configobj python3-pil  python3-serial, 
>> python3-usb, python3-pip, python3-cheetah,  python3-ephem, 
>> python3-mysqldb.
>>
>> I then used the update-alternatives package to switch the default python 
>> command to python 3.7.3.  Then, after I started the weewx service with 
>> "systemctl restart weewx", the command "systemctl status weewx" generates 
>> the following error dialog:
>>
>> ● weewx.service - LSB: weewx weather system
>>Loaded: loaded (/etc/init.d/weewx; generated)
>>Active: active (exited) since Mon 2020-12-07 09:12:53 EST; 7s ago
>>  Docs: man:systemd-sysv-generator(8)
>>   Process: 28868 ExecStart=/etc/init.d/weewx start (code=exited, 
>> status=0/SUCCESS)
>>
>> Dec 07 09:12:53 zeebytes.org weewx[28868]: Starting weewx weather 
>> system: weewxTraceback (most recent call last):
>> Dec 07 09:12:53 zeebytes.org weewx[28868]:   File "/usr/bin/weewxd", 
>> line 64, in 
>> Dec 07 09:12:53 zeebytes.org weewx[28868]: 
>> weewx.engine.main(options, args)
>> Dec 07 09:12:53 zeebytes.org weewx[28868]:   File 
>> "/usr/share/weewx/weewx/engine.py", line 845, in main
>> Dec 07 09:12:53 zeebytes.org weewx[28868]: 
>> daemon.daemonize(pidfile=options.pidfile)
>> Dec 07 09:12:53 zeebytes.org weewx[28868]:   File 
>> "/usr/share/weewx/daemon.py", line 71, in daemonize
>> Dec 07 09:12:53 zeebytes.org weewx[28868]: si = file(stdin, 'r')
>> Dec 07 09:12:53 zeebytes.org weewx[28868]: NameError: name 'file' is not 
>> defined
>> Dec 07 09:12:53 zeebytes.org weewx[28868]: .
>> Dec 07 09:12:53 zeebytes.org systemd[1]: Started LSB: weewx weather 
>> system.
>>
>> I researched "NameError: name 'file' is not defined" and found a 
>> reference that stated that file() is not supported in Python3.  Is that the 
>> problem and if so, how do I fix it?  Otherwise, how do I get my existing 
>> weewx 3.9.2 installation to run Python3 or do I need to upgrade weewx to 
>> 4.2.0 for it to work with python3?
>>
>> Any comments on the best way to perform these upgrades would be most 
>> appreciated.
>>
>> Thanks,
>>
>> Gordon
>>
>> -- 
>> 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/988598aa-d167-48cc-b591-ca740d6b9afen%40googlegroups.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/b0ce2b72-d76f-4a22-9a27-e35bfc2ce619n%40googlegroups.com.

Re: [weewx-user] Upgrading weewx, plugins and python

2020-12-07 Thread Tom Keffer 
The error 'file' is not defined was fixed in WeeWX V4 as part of the port
to Python 3. You will get LOTS of these kinds of errors trying to run WeeWX
V3 under Python 3. Either upgrade WeeWX first, or use Python 2.7.

On Mon, Dec 7, 2020 at 9:44 AM Gordon Dickens  wrote:

> Hello all,
>
> I have been successfully running the following versions of weewx software,
> skins and python on Debian 10 and I need to upgrade the software as
> depicted here:
>
>- weewx current version 3.9.2 needs upgrading to 4.2.0.
>- Belchertown Skin current version 1.0.1 needs upgrading to 1.2
>- Weather34 Skin current version WX-UB40-IHVN-0.9.1 needs upgrading
>toW34-HC-IMJD-3.0.0
>- Python current version 2.7 needs upgrading to Python 3.7.3
>
> As an FYI, weewx is installed from the Debian weewx package with the
> Debian package manager, apt.
>
> What is the recommended order for performing these upgrades?
>
> My initial thoughts were to upgrade in this order:
>
>1. Upgrade Python to version 3.7.3
>2. Upgrade weew to version 4.2.0
>3. Upgrade the Belchertown skin to verion 1.2
>4. Upgrade the Weather34 skin to version W34-HC-IMJD-3.0.0
>
> So, I began the python upgrade by installing python 3.7.3 and the python3
> dependencies: python3-configobj python3-pil  python3-serial, python3-usb,
> python3-pip, python3-cheetah,  python3-ephem, python3-mysqldb.
>
> I then used the update-alternatives package to switch the default python
> command to python 3.7.3.  Then, after I started the weewx service with
> "systemctl restart weewx", the command "systemctl status weewx" generates
> the following error dialog:
>
> ● weewx.service - LSB: weewx weather system
>Loaded: loaded (/etc/init.d/weewx; generated)
>Active: active (exited) since Mon 2020-12-07 09:12:53 EST; 7s ago
>  Docs: man:systemd-sysv-generator(8)
>   Process: 28868 ExecStart=/etc/init.d/weewx start (code=exited,
> status=0/SUCCESS)
>
> Dec 07 09:12:53 zeebytes.org weewx[28868]: Starting weewx weather system:
> weewxTraceback (most recent call last):
> Dec 07 09:12:53 zeebytes.org weewx[28868]:   File "/usr/bin/weewxd", line
> 64, in 
> Dec 07 09:12:53 zeebytes.org weewx[28868]: weewx.engine.main(options,
> args)
> Dec 07 09:12:53 zeebytes.org weewx[28868]:   File
> "/usr/share/weewx/weewx/engine.py", line 845, in main
> Dec 07 09:12:53 zeebytes.org weewx[28868]:
> daemon.daemonize(pidfile=options.pidfile)
> Dec 07 09:12:53 zeebytes.org weewx[28868]:   File
> "/usr/share/weewx/daemon.py", line 71, in daemonize
> Dec 07 09:12:53 zeebytes.org weewx[28868]: si = file(stdin, 'r')
> Dec 07 09:12:53 zeebytes.org weewx[28868]: NameError: name 'file' is not
> defined
> Dec 07 09:12:53 zeebytes.org weewx[28868]: .
> Dec 07 09:12:53 zeebytes.org systemd[1]: Started LSB: weewx weather
> system.
>
> I researched "NameError: name 'file' is not defined" and found a reference
> that stated that file() is not supported in Python3.  Is that the problem
> and if so, how do I fix it?  Otherwise, how do I get my existing weewx
> 3.9.2 installation to run Python3 or do I need to upgrade weewx to 4.2.0
> for it to work with python3?
>
> Any comments on the best way to perform these upgrades would be most
> appreciated.
>
> Thanks,
>
> Gordon
>
> --
> 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/988598aa-d167-48cc-b591-ca740d6b9afen%40googlegroups.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/CAPq0zEA5QxUx855e%3DZ%3DYMszbzZiq2khJMu%3DZzDLJa%2B4W6jycxw%40mail.gmail.com.

[weewx-user] Re: Upgrading weewx, plugins and python

2020-12-07 Thread vince 
Well typically you want to do one thing at a time...
 - spin up a raspi or VM with weewx using the simulator driver
 - if you're using something other than sqlite3, get the db working too
 - then get all your skins working
 - then try to get the driver working assuming others have gone there before

I can't speak to weather34 and whether it's weewx-4.2/python3 compatible, 
but I know others can.
Other stuff I think is known good.

-- 
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/35f9f286-6cd4-4607-8325-974e7595a7a1n%40googlegroups.com.

[weewx-user] Upgrading weewx, plugins and python

2020-12-07 Thread Gordon Dickens 
Hello all,

I have been successfully running the following versions of weewx software, 
skins and python on Debian 10 and I need to upgrade the software as 
depicted here:

   - weewx current version 3.9.2 needs upgrading to 4.2.0.
   - Belchertown Skin current version 1.0.1 needs upgrading to 1.2
   - Weather34 Skin current version WX-UB40-IHVN-0.9.1 needs upgrading 
   toW34-HC-IMJD-3.0.0
   - Python current version 2.7 needs upgrading to Python 3.7.3

As an FYI, weewx is installed from the Debian weewx package with the Debian 
package manager, apt.

What is the recommended order for performing these upgrades?

My initial thoughts were to upgrade in this order:

   1. Upgrade Python to version 3.7.3
   2. Upgrade weew to version 4.2.0
   3. Upgrade the Belchertown skin to verion 1.2
   4. Upgrade the Weather34 skin to version W34-HC-IMJD-3.0.0

So, I began the python upgrade by installing python 3.7.3 and the python3 
dependencies: python3-configobj python3-pil  python3-serial, python3-usb, 
python3-pip, python3-cheetah,  python3-ephem, python3-mysqldb.

I then used the update-alternatives package to switch the default python 
command to python 3.7.3.  Then, after I started the weewx service with 
"systemctl restart weewx", the command "systemctl status weewx" generates 
the following error dialog:

● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx; generated)
   Active: active (exited) since Mon 2020-12-07 09:12:53 EST; 7s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 28868 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)

Dec 07 09:12:53 zeebytes.org weewx[28868]: Starting weewx weather system: 
weewxTraceback (most recent call last):
Dec 07 09:12:53 zeebytes.org weewx[28868]:   File "/usr/bin/weewxd", line 
64, in 
Dec 07 09:12:53 zeebytes.org weewx[28868]: weewx.engine.main(options, 
args)
Dec 07 09:12:53 zeebytes.org weewx[28868]:   File 
"/usr/share/weewx/weewx/engine.py", line 845, in main
Dec 07 09:12:53 zeebytes.org weewx[28868]: 
daemon.daemonize(pidfile=options.pidfile)
Dec 07 09:12:53 zeebytes.org weewx[28868]:   File 
"/usr/share/weewx/daemon.py", line 71, in daemonize
Dec 07 09:12:53 zeebytes.org weewx[28868]: si = file(stdin, 'r')
Dec 07 09:12:53 zeebytes.org weewx[28868]: NameError: name 'file' is not 
defined
Dec 07 09:12:53 zeebytes.org weewx[28868]: .
Dec 07 09:12:53 zeebytes.org systemd[1]: Started LSB: weewx weather system.

I researched "NameError: name 'file' is not defined" and found a reference 
that stated that file() is not supported in Python3.  Is that the problem 
and if so, how do I fix it?  Otherwise, how do I get my existing weewx 
3.9.2 installation to run Python3 or do I need to upgrade weewx to 4.2.0 
for it to work with python3?

Any comments on the best way to perform these upgrades would be most 
appreciated.

Thanks,

Gordon

-- 
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/988598aa-d167-48cc-b591-ca740d6b9afen%40googlegroups.com.