[FHZ] New module for weather forecasts from fhem

[Dr. Boris Neubert]

                                             

Hi,

I spent my afternoon implementing a new module that uses the Google Weather
API to retrieve current and forecast weather conditions for today,
tomorrow, ... You can retrieve FHEM/59_Weather.pm together with the updated
documentation from CVS.

Just do

   define e.ext.Weather Weather "Maintal,HE"

and then you type

   get e.ext.Weather condition
   e.ext.Weather condition => Mostly Cloudy

to get today's condition, or

   get e.ext.Weather fc1_high_c
   e.ext.Weather fc1_high_c => 24

for tomorrow's daily high (in degrees centigrade). More readings can be found
in the docs.

What use it is? Well, my idea was to infinitely increase the WAF of our
brand-new automatic shutters by keeping the sun out in the summer and the
rooms cool. More specifically, the shutters on the east side of the house
should be closed from 9:00 to 12:00 and the shutters on the west side should
be closed from 12:00 to 17:00 if the (forecast) condition is Sunny or Clear
and the outside temperature is already above a certain level and we have May
to September. Reasonable conditions for closing still need some
experimenting, though

Regards,
Boris




   


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-

[Guest]

Originally posted by: <email address deleted>

Good Idea, although I would depend my shutters on the current weather
conditions and not just on forcasts.
(Personaly I would depend it on the outside/inside temperature and
kind of level of sun intensity. As I am planing building a new house,
I will install some brightness sensor outside)

Suggestion: I would suggest to name the module as it is: Something
like GoogleWeatherForcast or so, there could be other implementations
(yahoo, wetter.de) also.
What do you think?

Still, great to see, that fhem is very open to all kind of ideas
Greetings
Maz
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-

[Dr. Boris Neubert]

                                             

Hi Maz,

Am Montag, 1. Juni 2009 schrieb Maz:
> Good Idea, although I would depend my shutters on the current weather
> conditions and not just on forcasts.

I am open for suggestions. The "condition" reading of the weather device gives
the current condition (Sunny or Clear would be the mandatory conditions to
trigger further action). Next weekend, I will start experimenting  to see
what combinations of readings yield plausible results.

> (Personaly I would depend it on the outside/inside temperature and
> kind of level of sun intensity. As I am planing building a new house,
> I will install some brightness sensor outside)

A brightness sensor would be probably the most reasonable choice. Alas, there
is none to buy to my knowledge which fits my equipment. Last year I planned
to use a photo diode and a handful (<10) discrete electronics parts
(Transimpedanzverstaerker) to convert the photo current to a voltage to be
measured by M232. For some reason the project got stuck in its beginnings. If
anyone is interested in the details, I am willing to share the setup in
detail.

> Suggestion: I would suggest to name the module as it is: Something
> like GoogleWeatherForcast or so, there could be other implementations
> (yahoo, wetter.de) also.
> What do you think?

Well, the naming of the module is quite absolutist. Nonetheless, it could be
even more so, e.g. 30_Weather.pm I thought about it myself for a while...
I checked out several similar services and the already available perl modules
and I came to the conclusion that the Google Weather API is most appropriate
for the actual purpose. If the need for a concurrent service arises, it would
be included in the same module and an additional parameter would be added to
the define statement to distinguish between the two of them.

> Still, great to see, that fhem is very open to all kind of ideas

Maybe even a solution for home automation enthusiasts without a weather sensor
8^o .

.. any volunteers to integrate the forecasts into the web interface(s)?

Regards,
Boris


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-

[Guest]

Originally posted by: <email address deleted>

> I am open for suggestions. The "condition" reading of the weather device gives
> the current condition (Sunny or Clear would be the mandatory conditions to
> trigger further action). Next weekend, I will start experimenting  to see
> what combinations of readings yield plausible results.

Do you habe the "Wetter-Willi" in mind? I did a long term analysis and
can provide you with information, how to decode the condition
forcasts. (I am documenting this on my homepage, not ready jet)

But my local Weatherstation showed the last 4 days upon the constant
sinking air pressure that it expects that it will be raining.
But we had fantastic sunny weather.


> A brightness sensor would be probably the most reasonable choice. Alas, there
> is none to buy to my knowledge which fits my equipment.

Have a look here: http://www.pc-wetterstation.de/wetter/solarsensor.html
It is not a out of the box solution, but maybe also the SH300 could be
ammended to deliver the brightness ?!?!

Greetings
Maz
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-

[Dr. Boris Neubert]

                                             

Maz wrote:
>
>> I am open for suggestions. The "condition" reading of the weather device gives
>> the current condition (Sunny or Clear would be the mandatory conditions to
>> trigger further action). Next weekend, I will start experimenting  to see
>> what combinations of readings yield plausible results.
>
> Do you habe the "Wetter-Willi" in mind? I did a long term analysis and
> can provide you with information, how to decode the condition
> forcasts. (I am documenting this on my homepage, not ready jet)

I do not know exactly what you mean. I have a KS300 weather station. I
would like to find the readings of KS300, clock, calendar and Weather
that coincide with my notion "What sunshine! What heat! I should close
the shutters to lock the heat out".

>> A brightness sensor would be probably the most reasonable choice. Alas, there
>> is none to buy to my knowledge which fits my equipment.

> Have a look here: http://www.pc-wetterstation.de/wetter/solarsensor.html
> It is not a out of the box solution, but maybe also the SH300 could be
> ammended to deliver the brightness ?!?!

Very good link, thank you. ASH2000 and SH300 seem to be out of stock,
are they? But the general idea is clear: replace a temperature sensor by
a light sensor and keep the electronics and the data protocol. I have to
seriously think about it.

Regards,
Boris


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-

[Dr. Boris Neubert]

                                             

>> Have a look here: http://www.pc-wetterstation.de/wetter/solarsensor.html
>> It is not a out of the box solution, but maybe also the SH300 could be
>> ammended to deliver the brightness ?!?!
>
> Very good link, thank you. ASH2000 and SH300 seem to be out of stock,
> are they? But the general idea is clear: replace a temperature sensor by
> a light sensor and keep the electronics and the data protocol. I have to
> seriously think about it.

I checked the ELV shop again and found ASH2200 as possible successor of
ASH2000 as well as a S300IA. Assuming that both use a termistor with
resistances between 1 and 100 kOhm, the modification that replaces the
thermistor by the Hygrotec light sensor as described in
 http://home.arcor.de/carsten.reichstein/wetter_sw/bastel.htm is my favorite.

To my knowledge, both devices cannot be received by FHZ1300. Can CUL
with culfw directly handle these devices or does one need another
weather station device? If yes, which one? The interoperability of ELV's
weather station product lines is far from being clear to me.

Regards,
Boris



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-

[tostmann]

                                                 

How about building one? After investigating you would need:

* Sensor ie.: ISL29102 - http://www.intersil.com/data/fn/fn6483.pdf
* CPM - http://busware.de/tiki-index.php?page=CPM
* a battery delivering 1.8 ... 3.3 V ( 2 x AAA even Akkus)
* peace of software to glue it
* (an outdoor case - ie.: ELV G203C)

The already normalized output of the Sensor (2.50 EUR) gets A/D
converted by the Attiny84 (on CPM) and transmitted in any protocol
fashion using the CC1101 chip.

CPM can be sent to "sleep" with 4.5..10 µA current consumtion, waking
periodically up from watchdog to measure ...

This can also be used to trigger FS20 commands replacing a FS20 SD. In
this case you would need to add some extra keys for programming.

Ideas?

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-

[Dr. Boris Neubert]

                                             

Am Samstag, 6. Juni 2009 schrieb TOSTi:

> * Sensor ie.: ISL29102 - http://www.intersil.com/data/fn/fn6483.pdf

The input luminance range is from 0.3 lux to 10,000 lux. A sunny day gives
100,000 lux. Thus the sensor should be placed into an attenuator such as a
yellow cap of a spray can. From what I read this is a good idea anyway as the
cap acts as a diffusor and increases the sensitivity.

The software must correct for the nonlinearity of the
OutputVoltage(LightIntensity) function

> * peace of software to glue it

CC1101 programming is still my weak spot, as you know...

Idea: emulate a HMS100 device so also FHZ-only users can receive the output.

Total cost would be 24 EUR for the CPM, 2.50 EUR for the sensor, a few EUR for
shipping, the case and the battery holder, so around 35 EUR in total. ASH2200
costs about 30 EUR, the Hygrotec sensor 12 EUR, plus shipping makes 50 EUR.  
S300IA based solution is 10 EUR more expensive.

I would go for the CPM-based solution if someone else develops the firmware
(FHEM part of the thing would be easy).

Regards,
Boris


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-

[Guest]

Originally posted by: <email address deleted>

> > * Sensor ie.: ISL29102 -http://www.intersil.com/data/fn/fn6483.pdf

I can nor find any distributor, having this part on stock.
@Tosti:: Pls. hlp.


> The input luminance range is from 0.3 lux to 10,000 lux. A sunny day gives
> 100,000 lux.

I would take two sensors. (As I understand, CPM will have 2 free ADC-
Ports.)
One sensor without any diffuser to measure the lower band. and one
with diffusor to measure the bright sunny light.

In addition I would also take a DS1822 Thermo sensor and would take
the protocol of S300TH.
That means the temperature is sent absolute and the light as a
percentage value (used as humidity by S300TH).
It would also be nice to have a serie of free configurable switching
points, where defined FS20 commands will be sent (i.e. switch on
heating if temperature goes below a defined value, close shutters when
light  and temperatur is above a defined value, etc.)

Big Problem: How to enter/transfer the configuration without
hassle?!?!?
(Maybe inventing new FS20 commands?)

> > * peace of software to glue it
>
> CC1101 programming is still my weak spot, as you know...

I would say, that most of the parts could be taken from culfw. (a bit
naive )

As I am right now planing my new home, I am interested in all kind of
sensors (so also light sensor).
I am waiting for FUL becoming ready and will then order some peaces
from Tosti. (also CPMs)
Then I hope, I will have the time to start the first steps. Will keep
you informed.

In the meanwhile any idea for the transfer of configuration is
appreciated.


> I would go for the CPM-based solution if someone else develops the firmware
> (FHEM part of the thing would be easy).

So, i will

cu
Maz
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-

[tostmann]

                                                 

On 9 Jun., 00:01, Maz wrote:
> > > * Sensor ie.: ISL29102 -http://www.intersil.com/data/fn/fn6483.pdf
>
> I can nor find any distributor, having this part on stock.
> @Tosti:: Pls. hlp.

 http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail& name=ISL29102IROZ-T7CT-ND

I ordered two to start testing, if you need some let me know (to avoid
shipping cost) ...

> Big Problem: How to enter/transfer the configuration without
> hassle?!?!?
> (Maybe inventing new FS20 commands?)

You might do so by utilizing the real CC1101 functionallity (FIFOs)
and press a button to escape the firmware to a "configurator". This
might be a simple serial radio link to a CUL which allows you to
configure the device easily (and remotely) with a terminal.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-

[tostmann]

                                                 

> In addition I would also take a DS1822 Thermo sensor and would take
> the protocol of S300TH.

Addition: The CC1101 itself has a temperature sensor on-chip. No need
for additional external components ...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-

[Guest]

Originally posted by: <email address deleted>

>
>  http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail& name=ISL2...
>
> I ordered two to start testing, if you need some let me know (to avoid
> shipping cost) ...

I would take 6. Would you pls. order for me. I will order some CPMs
and a CUL when FUL is available.


> You might do so by utilizing the real CC1101 functionallity (FIFOs)
> and press a button to escape the firmware to a "configurator". This
> might be a simple serial radio link to a CUL which allows you to
> configure the device easily (and remotely) with a terminal.

Yeah, but I had in mind to change the configuration on runtime. So you
can adjust the threshold and switching points etc. in fhem on runtime.
(while the sensor is installed outdoor). So maybe we will start
without this feauture.

>Addition: The CC1101 itself has a temperature sensor on-chip. No need for additional external components ...
Great. Good to know.

cu
Maz
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-

[tostmann]

                                                 

Here the prototype:
http://busware.de/tiki-browse_gallery.php?galleryId=15

Now software is due ...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-

[tostmann]

                                                 

Here all details:
http://busware.de/tiki-index.php?page=CPM-BS

Maz is going to check and writing a firmware ...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-