[FHZ] noob @ FHEM + CUL + NSLU2

[Guest]

Originally posted by: <email address deleted>

Hello and thank you,

I followed this project for more than a year and found it very
interesting. Now I started to get things running and decided to choose
the NSLU with the CUL HW, as I like open HW and a server consuming not
more than 3W.

I must say with all these very good instructions i came very far, even
as an M$ addict, I am really happy with this stuff. Here I will write
down what seemed to be easy and what not and where I am struggling.

1.)
First I got the CUL running. The CUL comes with no firmware at all, so
there is no need to push the button while inserting. I took the Atmel
flash tool for Windows which served me well.
It took some time to find the actual firmware which I took straight
from the Berlios Repos here: http://developer.berlios.de/projects/culfw/
I just took the latest, but is there some announcement which is the
one to be used?
In the end, the CUL reported my FHT devices on a Windows Terminal
server. Very nice.

2.)
Installation of the NSLU2. I closely followed the instructions from
Martin Haas. Before that I had trouble to find the second hand NSLU on
the net, but the not official downloadable NSLU2-SetupWizard can do
magic to the slug without knowing its IP. Very interesting.
The installation took ages on my Slug. I did not want to keep my PC
running all night, so it took four attempts for a timeslot long
enough. The instructions a very accurate and simple to follow. Thanks
for that.

3.)
starting FHEM. The webfrontend came up nicely I tried to define CUL
device.
And thats the point where I am struggling. I do not know which version
was on Martin Haas NSLU script and how do I find out? I would like to
have this info in the log maybe?
>From the log I would say the FHEM version is out of date:
History   2009.01.31 21:26:21 5: Cmd: >define CUL CUL /dev/ttyACM0<
History   2009.01.31 21:26:21 1: Unknown type CUL
History   2009.01.31 21:26:21 5: Cmd: >port 7072<

The next noob problem is, how do I update FHEM? Where is it located?
I am very familiar with good old DOS, but Unix is new to me. Can
anyone recommend a good introduction to commandline linux?


So far thank you, this is really nice.
swifty






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

[Dr. Boris Neubert]

                                                   

> I just took the latest, but is there some announcement which is the
> one to be used?
There is no such thing as "stable", but the current version is more or
less useable. I planned to set up a website wit a tar file in the
moment sending to the FHT works, but I got distracted lately with some
other stuff (like working for the living, etc).

> In the end, the CUL reported my FHT devices on a Windows Terminal
> server. Very nice.
Can you write down what did you done for a HOWTO? I am not an M$
addict, so help from you would be nice.

> From the log I would say the FHEM version is out of date:
> History 2009.01.31 21:26:21 5: Cmd: >define CUL CUL /dev/ttyACM0<
> History 2009.01.31 21:26:21 1: Unknown type CUL

I think you are right. The version line in "list global" from the
telnet prompt should tell you the version. CUL is only supported with
the current (4.5) or CVS versions. If "list global" does not work,
then you have a completely outdated pre 4.0 version. If you used the
nslu2fhz-package version 0.1.3 (this is the only one I found on the
net), then you got a pre 4.0 fhem. The good news is that you won't
need to upgrade any other packages, just fhem. The steps for the
upgrade:
- copy the 4.5 or CVS version of fhem to the NSLU2.
- Unpack it in a directory (e.g. cd /home; tar zxvf fhem-4.5.tar.gz)
- Follow the HOWTO: http://www.koeniglich.de/fhem/HOWTO.html
- Put the new fhem in the startup, and remove the old. A quick and
dirty way is to edit the existing /etc/init.d/fhz1000 and replace the
old files.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHZ1000 users on Linux" group.
To post to this group, send email to FHZ1000-users-on-unix@googlegroups.com
To unsubscribe from this group, send email to FHZ1000-users-on-unix+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/FHZ1000-users-on-unix?hl=en
-~----------~----~----~----~------~----~------~--~-

[Dr. Boris Neubert]

Originally posted by: <email address deleted>

OK,

really noob here. I managed to download and extract the 4-5 files.
But I cannot edit, remove or do anything with fhz1000.d. I get only
errors.
If I can get rid of the .d file I can follow the steps of the howto?

Where and how do I execute the make install-pgm2?

swifty

PS: I put some hints in the CUL Group how to handle the CUL with
Windows.


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

[rudolfkoenig]

Originally posted by: <email address deleted>

Well, it's getting a little frustrating right now.

I managed to do the make install-pgm2. It was not possible, because
the make package was not installed....

I believe the Howto is not complete. When the gz is extracted there is
no .cfg at the specified command :
perl /usr/local/bin/fhem.pl fhem.cfg

I copied the one from /test and started with the line above.

What I get:
fhz:/home/fhem-4.5# perl /usr/local/bin/fhem.pl fhem.cfg
2009.02.09 20:21:47 1: FHZ device is none, commands will be echoed
only
2009.02.09 20:21:49 1: SCIVT device is none, commands will be echoed
only
2009.02.09 20:21:49 2: SCIVT 13,66;0,0;30;13,62;15,09;-0,2;2,8; (raw)
2009.02.09 20:21:49 3: Undefined type init
2009.02.09 20:21:49 3: Undefined type state
2009.02.09 20:21:49 3: Undefined type unknown_85
2009.02.09 20:21:49 3: Undefined type init
2009.02.09 20:21:49 3: Undefined type state
2009.02.09 20:21:49 3: Undefined type unknown_85
2009.02.09 20:21:49 0: Server started (version 4.5 from 2008-12-23
($Id: fhem.pl,v 1.59 2008/12/09 14:12:40 rudolfkoenig Exp $), pid
2035)

When I try to reach the website, I get an error, but the errors may
lie a few steps before.

Any help appreciated.


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

[rudolfkoenig]

                                                   

> I believe the Howto is not complete. When the gz is extracted there is
> no .cfg at the specified command :

You are right. The standard configuration file is copied to /var/log/
fhem/fhem.cfg
I'll change the HOWTO. Please try it again with:

perl /usr/local/bin/fhem.pl /var/log/fhem/fhem.cfg


> I copied the one from /test and started with the line above.

The test config file is not the best starting point, as it will define
a lot of unusual devices just for testing purposes. Besides I think it
is outdated at the moment.

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

[Guest]

Originally posted by: <email address deleted>

Thanks for the info.

Finally i found WinSCP and I am feeling home now....

Still not everything is working as I would like it to.

I believe the make command should also create this directory:
 /var/log/fhem/fhem/

or there will be errors:
fhz:/home/FHZ/fhem-4.5# perl /usr/local/bin/fhem.pl /var/log/fhem/
fhem.cfg
Can't open /var/log/fhem/fhem/fhem-2009-02.log: No such file or
directory at /usr/local/bin/fhem.pl line 1321, <$fh> line 5.

Or change the default fhem.cfg

the default fhem.cfg also gives this:
attr global modpath /var/log/fhem/fhem/fhem
I don't understand that, is that right? I would like to have these
files cpd to a standard dir by the makefile.


which leads to my logfile
2009.02.10 20:42:21 3: modpath must point to a directory where the
FHEM subdir is
2009.02.10 20:42:21 3: Unknown argument FHEMWEB, choose one of
2009.02.10 20:42:21 3: Please define WEB first
2009.02.10 20:42:21 3: Unknown argument FileLog, choose one of
No modpath specified in the configfile.



with modifications my config looks like this:


attr global logfile /var/log/fhem/fhem/fhem-%Y-%m.log
attr global statefile /var/log/fhem/fhem/fhem.save   # where to save
the state of the devices
attr global verbose 3                  # "normal" verbosity (min 1,
max 5)
attr global port 7072                  # our TCP/IP port (localhost
only)
attr global modpath /usr/local/lib                 # where our FHEM
directory is
define WEB FHEMWEB 8083
attr WEB plotmode SVG
# Fake logfile, to access the global log
define Logfile FileLog /var/log/fhem/fhem/fhem-%Y-%m.log fakelog


and logs like:
2009.02.10 20:57:15 3: Unknown argument FHEMWEB, choose one of CM11
CUL CUL_EM CUL_WS EM EMEM EMGZ EMWZ FHT FHZ FS20 FileLog HMS IPWE
KS300 LIRC M232 M232Counter M232Voltage SCIVT WS2000 WS300 X10 at
dummy notify watchdog
2009.02.10 20:57:15 3: Please define WEB first
2009.02.10 20:57:15 0: Server started (version 4.5 from 2008-12-23
($Id: fhem.pl,v 1.59 2008/12/09 14:12:40 rudolfkoenig Exp $), pid
2174)
2009.02.10 20:58:00 1: Can't open server port at 7072: Address already
in use

What is wrong with the pgm2 config?
How do I restart fhem?

Any hints welcome
swifty

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

[Dr. Boris Neubert]

                                                   

> I believe the make command should also create this directory:
>  /var/log/fhem/fhem/

You are right. It should create /usr/local/bin, /usr/local/lib and /
var/log/fhem. The first two are most probably already present, but the
third not. Could you please create it now manually (mkdir -p /var/log/
fhem), then execute make install-pgm2 again? I added the mkdir to the
Makefile, so the next version will have it. You can take a look at the
Makefile if you wish, it is not that cryptic I think. Just make sure
not to replace the tabs with spaces in it.

> 2009.02.10 20:57:15 3: Unknown argument FHEMWEB, choose one of CM11

Looks like the FHEMWEB module is not part of the FHEM directory. Most
likely you either using the FHEM directory from the source directly
(attr global modpath ), or issued "make install" instead of "make
install-pgm2"

> 2009.02.10 20:58:00 1: Can't open server port at 7072: Address already in use

Please shut down the old one with "telnet 7072" and then issue
"shutdown"
Now start it again with the command which is displayed at the end of
the "make install-pgm2" output.

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

[Dr. Boris Neubert]

Originally posted by: <email address deleted>

Thanks again,

the shutdown command is not really successful, don't know why:
fhz:/home/FHZ/fhem-4.5# telnet localhost 7072
Trying 127.0.0.1...
Trying ::1...
telnet: Unable to connect to remote host: Connection refused


The log looks fine now:
2009.02.11 19:35:25 2: FHEMWEB port 8083 opened
2009.02.11 19:35:25 0: Server started (version 4.5 from 2008-12-23
($Id: fhem.pl,v 1.59 2008/12/09 14:12:40 rudolfkoenig Exp $), pid
1992)

But I can't reach it:
@http://192.168.178.35:8083/fhem nothing answers.
Is the webfrontend available at the localhost only?

Now I am lost at the configuration of pgm3, which should be easy...
Well a few hours later, pgm3 is runnings somehow.
I had to adjust the /etc/apache2/sites-available/default to point to
the files specified on Martins Webpage. OK (hope)
The next hurdle was to get the index page for the nslu running with
the new locations of the files. It still does not display any logs.
Does anybody know if this is able to read rotating logs?
Or is it related to the fakelog?:

# Fake logfile, to access the global log
define Logfile FileLog /var/log/fhem/fhem/fhem-%Y-%m.log fakelog

I would like to see pgm2 running. Any help on this?

swifty

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

[rudolfkoenig]

                                                   

> the shutdown command is not really successful, don't know why:
Probably you rebooted the system before.

> Is the webfrontend available at the localhost only?
Yes, this is the default.  Please append "global" to the FHEMWEB
definition line.
See http://www.koeniglich.de/fhem/commandref.html#FHEMWEB for details.

> Now I am lost at the configuration of pgm3, which should be easy...
Sorry, pgm3 is not my playground.

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

[Dr. Boris Neubert]

Originally posted by: <email address deleted>

Hi,

nachdem mein FHEM mit einem CUL rennt (die FHZ1350PC ist derzeit
im Austausch) und auch 1a S300TH-Sensoren (Temperatur, Luftfeuchte)
-- endlich mal günstige Sensoren! -- empfängt, parallel zu normalen
FS20 also auch EM1000EM, bekomme ich Lust auf mehr

Konkret suche ich nach einem Helligkeits- oder Luxsensor, also et-
was, welches die Sonnenscheindauer und ggf. auch den Zustand »Däm-
merung« recht verläßlich ermittelt. Ich habe lustige Umbauten von
u. a. ASH2000 gefunden¹, aber eigentlich wäre so ein nativer Sen-
sor mir doch lieber.

Konkret interessiere ich mich für den »Helligkeitssensor S 2500 H«²,
weiß jemand, ob der funktioniert (mit FHEM & CUL, nichts weiter)?

MfG,
         kai


[English summary: Now that I'm successfully using FHEM with CUL,
I'm looking for more sensors, especially for lux/luminance. Does
anyone know if »Helligkeitssensor S 2500 H«² would work with FHEM
and CUL? Or could name any similar ones working with FHEM + CUL?]

_____
¹ http://www.pc-wetterstation.de/wetter/solarsensor.html
²  http://www.elv.de/output/controller.aspx?cid=74&detail=10&de tail2=7439

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

[Dirk]

                                                   

Hi,

> Konkret interessiere ich mich für den »Helligkeitssensor S 2500 H«², weiß
> jemand, ob der funktioniert (mit FHEM & CUL, nichts weiter)?

Den S2500 hab Ich hier auch am Laufen. Allerdings wird der nicht von den
FHZ1xxx empfangen weil 433 MHz. Man kann das Sendemodul zwar gegen ein 866
MHz Version austauschen, aber ich glaube nicht, dass die FHZ das Protokoll
versteht.

Mein S2500 wird vom Wetterempfänger empfangen. Gab es als Bausatz. Finde es
derzeit aber nicht im Katalog. Die WS300 sollte das Protokoll nach Umbau
aber verstehen. Diese wird von FHEM auch unterstützt.

Gruss
Dirk


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