[FHZ] FMS (Master-Slave-Funkschalter) & FHEM?

[rudolfkoenig]

Originally posted by: <email address deleted>

Hi,

I'm new to FS20, I bought an FHZ 1350 (recognized as 1300), set up
FHEM, made two ST-1 controllable from FHEM and am now rather
confused while fiddeling with my FMS transmitter.

I've got

2009.02.06 17:08:16 3: FS20 Unknown device ____ (1234____), Button 00
(1111) Code 12 (toggle), please define it

and did a define for it, which made the messages go away, but
if the state of the FMS changes, nothing's done within FHEM.
BTW, defining leads to

Use of uninitialized value in numeric comparison (<=>) at /usr/local/
bin/fhem.pl line 1049.

I can't set the appropriate attribute, as there's no "fs20fms"
definded.
This evening, after googling until the browser smoked for "FMS" and
"FHEM" -- still finding nothing --, I did a factory reset on the FMS,
re-
started FHEM and got

2009.02.08 00:54:47 3: FS20 Unknown device 6133 (23121414), Button 00
(1111) Code 11 (on), please define it
2009.02.08 00:57:50 3: FS20 Unknown device 6133 (23121414), Button 00
(1111) Code 00 (off), please define it
2009.02.08 00:58:29 3: FS20 Unknown device 6133 (23121414), Button 00
(1111) Code 00 (off), please define it

I then reprogrammed the FMS to old housecode (with it's 1960's one-
button-one-light-UI, an awesome experience ) and defined in FHEM:

define FMS1 FS20 1234____ 1111

Still no cigar. The LED on the FMS blinks as the load is switched
on or off, but I get nothing in FHEM or it's log. I programmed one
ST-2 to 1111 and now it switches like the load on the FMS -- but
I still see nothing on the FHEM?

During testing, the FMS was 2 sockets apart from the ST-2, both
were no more than 30cm away from the FHZ 1350 ...

Any ideas where I left the road to success? Are there (untold) known
problems with FMS'?

Ciao,
-kai

--
Kai 'wusel' Siering                 eMail @ home: wusel+google@uu.org
Traveller on the Information Highway doing full-time administration.

"Sehr schoene Worte Terra, nur leider voellig am Thema vorbei."
                          -- Christoph Badura in


--~--~---------~--~----~------------~-------~--~----~
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]

                                             

Good morning,

[FMS transmitter]

> 2009.02.06 17:08:16 3: FS20 Unknown device ____ (1234____), Button 00
> (1111) Code 12 (toggle), please define it
>
> and did a define for it, which made the messages go away, but
> if the state of the FMS changes, nothing's done within FHEM.
> Still no cigar. The LED on the FMS blinks as the load is switched
> on or off, but I get nothing in FHEM or it's log. I programmed one

your FMS is recognized as FS20 device. Did you define a log for the events?
Please try

define myFMSlog FileLog path-to-logs/myFMS.log myFMS

and tell us what you get.

Regards,
Boris


--~--~---------~--~----~------------~-------~--~----~
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]

                                                   

> 2009.02.06 17:08:16 3: FS20 Unknown device ____ (1234____), Button 00
> (1111) Code 12 (toggle), please define it

Was it really "____" or did you changed it manually?

> I can't set the appropriate attribute, as there's no "fs20fms"
> definded.

The model attribute is a "nice to have" thing for the web-browsers,
nothing else. I have a "master slave" device here working for a long
time, it is nothing unusual about it.

> Still no cigar. The LED on the FMS blinks as the load is switched
> on or off, but I get nothing in FHEM or it's log.

Try "inform timer" in the telnet prompt, you should get all generated
events.

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
-~----------~----~----~----~------~----~------~--~-

[ilmtuelp0815]

Originally posted by: <email address deleted>

Moin,

Dr. Boris Neubert wrote:

> your FMS is recognized as FS20 device. Did you define a log for the events?
> Please try
>
> define myFMSlog FileLog path-to-logs/myFMS.log myFMS
>
> and tell us what you get.

Err, isn't that covered by

| define Logfile FileLog /var/log/fhem/fhem-%Y-%m.log fakelog

from the default installation? Please see my fhem.cfg a the bottom
of this post.



Rudolf Koenig wrote:

>> 2009.02.06 17:08:16 3: FS20 Unknown device ____ (1234____), Button 00 (1111) Code 12 (toggle), please define it
>
> Was it really "____" or did you changed it manually?

I changed that as, as I wrote later on, I changed back to that
housecode and, maybe, it's not wise to post that publically

>> I can't set the appropriate attribute, as there's no "fs20fms"
>> definded.
>
> The model attribute is a "nice to have" thing for the web-browsers,
> nothing else. I have a "master slave" device here working for a long
> time, it is nothing unusual about it.

What shall I used as model attribute here?

>> Still no cigar. The LED on the FMS blinks as the load is switched
>> on or off, but I get nothing in FHEM or it's log.
>
> Try "inform timer" in the telnet prompt, you should get all generated
> events.

Hmm.

FHZ> inform timer
FHZ>

There seems something rather wrong with my FHEM installation or
my FHZ 1350; I have the FMS as well as an HGS, both are set to
trigger an FS-2 at address "1111" for testing purposes and they
work well -- only my FHZ 1350 seems not to recognize when they're
transmitting

I can toggle the switch "1111" from the Webfrontend, e. g. if I
click on "off" at HGS1, FHEM issues an "off" event and the ST-2
at "1111" then turns off.

Pressing the "PROG" button on the HGS toggles the ST-2 at "1111"
but FHEM does not notice anything

Here's my fhem.cfg (which install put to /var/log for what-
ever reason), after an s/$REALHOUSECODE/1234____:

----8<----
root@hdtvdr:~/fhem-4.5# more /var/log/fhem/fhem.cfg
#Sun Feb  8 19:51:46 2009

attr global logfile /var/log/fhem/fhem-%Y-%m.log
attr global modpath /usr/local/lib
attr global port 7072
attr global statefile /var/log/fhem/fhem.save
attr global verbose 3

define FHZ1 FHZ /dev/elv_fhz1300pc
attr FHZ1 fhtsoftbuffer 1

setdefaultattr
define FMS1 FS20 1234____ 1111
define HGS1 FS20 1234____ 1111
define Logfile FileLog /var/log/fhem/fhem-%Y-%m.log fakelog
define Terrarium_UV FS20 1102 01
attr Terrarium_UV model fs20st
define WEB FHEMWEB 8083
attr WEB plotmode SVG
define Wohnz_LED FS20 1234____ 1111
attr Wohnz_LED model fs20st
setdefaultattr
---->8----

"Terrarium_UV" needs to be reconfigured, but I'm waiting for a
FHT for that, i. e. it doesn't matter right now.

TIA,
         kai

--~--~---------~--~----~------------~-------~--~----~
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]

                                             

Hi,

Am Sonntag, 8. Februar 2009 schrieb Kai 'wusel' Siering:

> | define Logfile FileLog /var/log/fhem/fhem-%Y-%m.log fakelog

logs any event for device fakelog to the given logfile. Change fakelog to the
device's name FMS1. A device's events are usually not logged to the global
log file.

> There seems something rather wrong with my FHEM installation or
> my FHZ 1350; I have the FMS as well as an HGS, both are set to
> trigger an FS-2 at address "1111" for testing purposes and they
> work well -- only my FHZ 1350 seems not to recognize when they're
> transmitting

In your previous post, you copied an excerpt from the global log before
defining the devices showing that data from the devices are received. My
guess is that they just do not show up in the logs since you did not define
any for the devices.

Please define two log files to capture events from FMS1 and HGS1 as
exemplified in my previous post.

Good luck!
Boris


--~--~---------~--~----~------------~-------~--~----~
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>

Da googlen nicht weiterhalf, das Kästchen sich als FHZ 1300 PC
meldet und scheinbar nur auf der ELV-Verpackung und dem Gerät
selber was von "1350" aufgeklebt ist (Bilder siehe locr: http://de.locr.com/photo-simple-13632737,
http://de.locr.com/photo-simple-13632738, http://de.locr.com/photo-simple-13632740):
weiß jemand, was es mit der "1350" auf sich hat? Nicht, daß
meine Empfangsprobleme damit zu tun haben ...

root@hdtvdr:~/fhem-4.5# udevadm info --name=/dev/ttyUSB0 --attribute-walk
[...]
  looking at parent device '/devices/pci0000:00/0000:00:02.0/usb1/1-2/1-2:1.0':
    KERNELS=="1-2:1.0"
    SUBSYSTEMS=="usb"
    DRIVERS=="ftdi_sio"
    ATTRS{bInterfaceNumber}=="00"
    ATTRS{bAlternateSetting}==" 0"
    ATTRS{bNumEndpoints}=="02"
    ATTRS{bInterfaceClass}=="ff"
    ATTRS{bInterfaceSubClass}=="ff"
    ATTRS{bInterfaceProtocol}=="ff"
     ATTRS{modalias}=="usb:v0403pE0E8d0200dc00dsc00dp00icFFiscFFi pFF"
    ATTRS{interface}=="ELV FHZ 1300 PC"

  looking at parent device '/devices/pci0000:00/0000:00:02.0/usb1/1-2':
    KERNELS=="1-2"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{configuration}==""
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bmAttributes}=="a0"
    ATTRS{bMaxPower}==" 44mA"
    ATTRS{urbnum}=="11556299"
    ATTRS{idVendor}=="0403"
    ATTRS{idProduct}=="e0e8"
    ATTRS{bcdDevice}=="0200"
    ATTRS{bDeviceClass}=="00"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bMaxPacketSize0}=="8"
    ATTRS{speed}=="12"
    ATTRS{busnum}=="1"
    ATTRS{devnum}=="5"
    ATTRS{version}==" 1.10"
    ATTRS{maxchild}=="0"
    ATTRS{quirks}=="0x0"
    ATTRS{authorized}=="1"
    ATTRS{manufacturer}==" ELV AG"
    ATTRS{product}=="ELV FHZ 1300 PC"
    ATTRS{serial}=="EL4342G9"
[...]

Unterschied lt. ehomeportal:

- PC-Funkhaussteuerung FHZ1000 PC für FS20, HMS,FHT80b Module , Standardsoftware
- PC-Funksteuerung FHZ 1300 PC für FS20,HMS,FHT80b, FHT8b, KS300 StandardSoftware!
- PC-Funkhaussteuerung FHZ1350 für FS20,HMS,FHT8xb,KS300,AW50 Standard-Software!

Das liest sich so, als ob's einfach 'ne neuere Firmware für die 1300er
wäre, eine, die auch den AlarmWähler-50 unterstützte? Gibt es bekannte
Kontraindikationen bei FHEM bezüglich der 1350? Preislich war's bei
ehomeportal jedenfalls kein Unterschied, die 1350 aber war lieferbar

MfG,
         kai

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~-

[UliM]

Originally posted by: <email address deleted>

Hi,

Boris Neubert wrote:

>> | define Logfile FileLog /var/log/fhem/fhem-%Y-%m.log fakelog
>
> logs any event for device fakelog to the given logfile. Change fakelog to the
> device's name FMS1. A device's events are usually not logged to the global
> log file.

Hrmpft, missed that. Thanks.

root@hdtvdr:~/fhem-4.5# diff -u /var/log/fhem/fhem.cfg-as-posted /var/log/fhem/fhem.cfg-current
--- /var/log/fhem/fhem.cfg-as-posted    2009-02-08 20:57:11.000000000 +0100
+++ /var/log/fhem/fhem.cfg-current      2009-02-08 21:01:30.000000000 +0100
@@ -1,4 +1,4 @@
-#Sun Feb  8 19:51:46 2009
+#Sun Feb  8 20:54:34 2009

 attr global logfile /var/log/fhem/fhem-%Y-%m.log
 attr global modpath /usr/local/lib
@@ -11,7 +11,9 @@

 setdefaultattr
 define FMS1 FS20 1234____ 1111
+define FMS1Log FileLog /var/log/fhem/fms1-%Y-%m.log FMS1
 define HGS1 FS20 1234____ 1111
+define HGS1Log FileLog /var/log/fhem/hgs1-%Y-%m.log HGS1
 define Logfile FileLog /var/log/fhem/fhem-%Y-%m.log fakelog
 define Terrarium_UV FS20 1102 01
 attr Terrarium_UV model fs20st

> In your previous post, you copied an excerpt from the global log before
> defining the devices showing that data from the devices are received. My
> guess is that they just do not show up in the logs since you did not define
> any for the devices.
>
> Please define two log files to capture events from FMS1 and HGS1 as
> exemplified in my previous post.

If I'm not mistaken, the fms1 and hgs1-files should now get
populated if the HGS or the FMS issues switching commands?

But -- maybe I haven't recognized that in the howto either --
shouldn't FHEM already act upon receiving transmissions from
FMS or HGS, i. e. update the state on the webinterface?

I can click on FMS1, HGS1 or Wohnz_LED in the webinterface;
FHEM issues the corresponding signals and updates all three
"State" icons (a lightbulb) accordingly. In the logfiles I
get:

==> /var/log/fhem/fhem-2009-02.log <==
2009.02.08 21:06:22 2: FS20 set FMS1 on

==> /var/log/fhem/fms1-2009-02.log <==
2009-02-08_21:06:22 FMS1 on

==> /var/log/fhem/fhem-2009-02.log <==
2009.02.08 21:06:25 2: FS20 set HGS1 off

==> /var/log/fhem/hgs1-2009-02.log <==
2009-02-08_21:06:25 HGS1 off

==> /var/log/fhem/fhem-2009-02.log <==
2009.02.08 21:06:29 2: FS20 set Wohnz_LED on
2009.02.08 21:06:32 2: FS20 set Wohnz_LED off
2009.02.08 21:06:35 2: FS20 set FMS1 on

==> /var/log/fhem/fms1-2009-02.log <==
2009-02-08_21:06:35 FMS1 on

Since FMS and HGS are (should be) transmit-only to FHEM,
this behaviour rather confuses me. It seems to me as if
FHEM is actively ignoring the messages of the FMS or HGS
as it expects them not to transmit but to receive?

Basically, what I'm trying to achive here is:

Let the FMS report the state of the TV in the living room
to FHEM. Use FHEM to decide, based on other data (time of
day, day of year/sunset and -rise, external data), whether
to switch on the backlight behind the TV. (If that's not
working from within FHEM directly, I'll just use FHEM as
the state machine and frontend to my scriptwork.)
Furthermore, FHEM should make sure that those lights are
shut down if the TV isn't running anymore (e. g. with se-
veral minutes delay).

So, actually I'd just tell the FMS to address the FHZ, but
I haven't found the address of the FHZ. There seems to be
not "get/set FS20-address" in FHZ context, am I right?

(Later on, this will be extended to have the TV, by means
of it's serial interface, switch to the correct input if
PS3, Wii, T-Entertain, VHS/DVD or VDR are used, the funny
part will be most likely to best-guess which device is
going to be used (with PS3, Wii using BT, the others IR).
But that's a different story yet to be written )

Still curious where I went wrong, in my opinion I strickly
followed http://www.koeniglich.de/fhem/HOWTO.html regarding
both the receivers (which work) as well as the transmitters
(which don't work as expected for me). *sigh* Must be
Thursday
         kai

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~-

[UliM]

                                                   

Kai, please test it step-by-step:

1. Make the FMS trigger by switching on whatever is connected to it. -
> The red LED on the FHZ1350 should blink. If not: it is not receiving
any data.
2. Raise the loglevel (temporarily) with  "attr global verbose 5".
Watch the global logfile, and make the FMS trigger again. In the
logfile some data should appear.
3. Telnet to fhem (7072) and issue "inform timer". Make sure the FMS
is defined as a device in fhem. Now make FMS trigger again. You should
receive a line in the telnet prompt. This line consist of timestamp,
device type, devicename and event. Notify, Filelog and DbLog
definitions test their own regexp with "devicename" and
"devicename:event"

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
-~----------~----~----~----~------~----~------~--~-

[rudolfkoenig]

                                                   

> Das liest sich so, als ob's einfach 'ne neuere Firmware für die 1300er
> wäre, eine, die auch den AlarmWähler-50 unterstützte? Gibt es bekannte
> Kontraindikationen bei FHEM bezüglich der 1350? Preislich war's bei
> ehomeportal jedenfalls kein Unterschied, die 1350 aber war lieferbar

Meines Wissens nach hat bisher keiner den 1350 getestet mit fhem. Evtl
benoetigt man andere Initialisierungssequenzen, obwohl beim FHZ1000
und FHZ1300 kein Unterschied ist, aber man braucht unterschiedliche
Sequenzen, um FS20, HMS und FHT jeweils zu "aktivieren.

(komischer thread: mal english, mal deutsch...)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~-

[UliM]

Originally posted by: <email address deleted>

Hi Rudolf,

> Kai, please test it step-by-step:
>
> 1. Make the FMS trigger by switching on whatever is connected to it. -
>> The red LED on the FHZ1350 should blink. If not: it is not receiving
> any data.

(Rebootet this morning, so it's a fresh FHEM process as well
as a fresh connection to the FHZ.)

Checked. Plugged in a load, FMS' LED blinked and the ST-2 went
on.

> 2. Raise the loglevel (temporarily) with  "attr global verbose 5".
> Watch the global logfile, and make the FMS trigger again. In the
> logfile some data should appear.

Did that. All that changes is that I get info from http and
telnet accesses.

Switching the load at the FMS on and off makes the ST-2 toggle
accordingly but there is NO corresponding entry in any FHEM log.

root@hdtvdr:~/fhem-4.5# grep -i fms /var/log/fhem/*.log
/var/log/fhem/fhem-2009-02.log:2009.02.08 01:12:50 2: FS20 set FMS1 on
/var/log/fhem/fhem-2009-02.log:2009.02.08 01:35:40 2: FS20 FMS1 off
/var/log/fhem/fhem-2009-02.log:2009.02.08 21:06:22 2: FS20 set FMS1 on
/var/log/fhem/fhem-2009-02.log:2009.02.08 21:06:35 2: FS20 set FMS1 on
/var/log/fhem/fhem-2009-02.log:2009.02.09 10:53:54 5: Cmd: >define FMS1 FS20 12433443 1111<
/var/log/fhem/fhem-2009-02.log:2009.02.09 10:53:54 5: Cmd: >define FMS1Log FileLog /var/log/fhem/fms1-%Y-%m.log FMS1<
/var/log/fhem/fhem-2009-02.log:2009.02.09 10:53:54 5: Cmd: >setstate FMS1 on<
/var/log/fhem/fhem-2009-02.log:2009.02.09 10:53:54 5: Cmd: >setstate FMS1 2009-02-08 21:06:35 state on<
/var/log/fhem/fhem-2009-02.log:2009.02.09 10:53:54 5: Cmd: >setstate FMS1Log active<
/var/log/fhem/fms1-2009-02.log:2009-02-08_21:06:22 FMS1 on
/var/log/fhem/fms1-2009-02.log:2009-02-08_21:06:35 FMS1 on

> 3. Telnet to fhem (7072) and issue "inform timer". Make sure the FMS
> is defined as a device in fhem. Now make FMS trigger again. You should
> receive a line in the telnet prompt. This line consist of timestamp,
> device type, devicename and event. Notify, Filelog and DbLog
> definitions test their own regexp with "devicename" and
> "devicename:event"

Alas, will need a new housecode now , here we go:

FHZ> list FMS1
Internals:
   BTN        00
   DEF        12433443 1111
   IODev      FHZ1
   NAME       FMS1
   NR         2
   STATE      on
   TYPE       FS20
   XMIT       1ebe
   Code:
     1          1ebe 00
   Readings:
     2009-02-08 21:06:35   state           on
Attributes:

FHZ> inform timer
FHZ>

[Switching on the load on the FMS ... which turns on the ST-2. No
output in the telnet session nor the log.]

FHZ> inform timer
FHZ>

Logfile: root@hdtvdr:~/fhem-4.5# tail -6 /var/log/fhem/fhem-2009-02.log
2009.02.09 11:02:45 5: Cmd: >list FMS1<
2009.02.09 11:02:51 5: Cmd: >inform timer<
2009.02.09 11:02:51 4: Setting inform to timer
2009.02.09 11:04:14 4: Connection closed for FHEMWEB:127.0.0.1:48643
2009.02.09 11:04:55 5: Cmd: >inform timer<
2009.02.09 11:04:55 4: Setting inform to timer

So, my FHZ is sort of deaf? FWIW, I just factory-reset the HGS.
No change within FHEM; even if I press the PROG button on the
HGS which sends out a toggle signal, nothing in the fhem-log.

With kind regards,
         kai


--~--~---------~--~----~------------~-------~--~----~
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>

Rudolf Koenig wrote:

> Meines Wissens nach hat bisher keiner den 1350 getestet mit fhem. Evtl
> benoetigt man andere Initialisierungssequenzen, obwohl beim FHZ1000
> und FHZ1300 kein Unterschied ist, aber man braucht unterschiedliche
> Sequenzen, um FS20, HMS und FHT jeweils zu "aktivieren.

Na super Also nehme ich das Notbuch mit Fenstern, klatsche
da die Windows-SW von ELV drauf, gucke, ob's damit meine Sender
empfängt und tausche wenn ja, gegen 1000/1300 (was grade liefer-
bar) und falls nein, gegen neue 1350?
Da mich KS300 derzeit nicht interessiert (habe seit Jahren WS3600):
ist die 1300 wirklich "besser" als die 1000er, wie es in verschie-
denen Postings durchklingt? (Die 1000er soll angebl. Empfangspro-
bleme haben, wobei es auch Postings gibt, bei denen eine 1000er
besser "hört" als eine 1300er ...)

> (komischer thread: mal english, mal deutsch...)

Naja, auf der Infoseite steht als Sprache Englisch, aber wenn ich
mir das Archiv so ansehe, scheint Deutsch zumindest geduldet zu sein
         kai

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~-

[UliM]

                                                   

> Na super Also nehme ich das Notbuch mit Fenstern, klatsche
> da die Windows-SW von ELV drauf, gucke, ob's damit meine Sender
> empfängt und tausche wenn ja, gegen 1000/1300 (was grade liefer-
> bar) und falls nein, gegen neue 1350?

Oder noch besser: Initialisierung mitprotokollieren, damit man es ins
00_FHZ.pm aufnehmen kann.

> ist die 1300 wirklich "besser" als die 1000er, wie es in verschie-
> denen Postings durchklingt?

Ich hatte beides, merke aber kein Unterschied (bis auf KS300). Der
1300-er hat einen groesseren  FHT-Puffer, fuer den Fall dass man mit
dem FHT's viel reden will. In absehbarer Zeit werde ich den FHZ1300
durch den CUL ersetzen, der CUL hat den EM1010PC bei mir schon
abgeloestm FHT senden und HMS geht noch nicht. Falls Du nur FS20 hast,
dann wuerde ich es an deiner Stelle jetzt schon ernsthaft Ueberlegen.
--~--~---------~--~----~------------~-------~--~----~
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>

Rudolf Koenig wrote:
>> Na super Also nehme ich das Notbuch mit Fenstern, klatsche
>> da die Windows-SW von ELV drauf, gucke, ob's damit meine Sender
>> empfängt und tausche wenn ja, gegen 1000/1300 (was grade liefer-
>> bar) und falls nein, gegen neue 1350?
>
> Oder noch besser: Initialisierung mitprotokollieren, damit man es ins
> 00_FHZ.pm aufnehmen kann.

Da die Box auch unter Windows keine Signale empfängt (beim Anlernen
des FMS Klick auf "Adresse beziehen" (oder so), FMS schalten lassen:
keine Reaktion in "homeputer"), gehe ich mal davon aus, daß der
Empfänger mehr so DOA ist. Sorry für die Umstände.
         kai

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~-