FHT80b not transmitting properly

[Guest]

Originally posted by: <email address deleted>

2 of my 10 FHT80b devices have stopped transmitting any values other
than actuator %. I have tried sending refreshvalues to them, and
taking the batteries out for a while, but this had no effect.

Any other suggestions for kicking them back into life?

thanks!

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Zrrronggg!]

                                                     

"I have tried sending refreshvalues to them" means you sent "report2
255" to them?
If not plz try that.

otherwise tell us a bit more about your installation.  FHZ1x00, CUL,
CUN? Do you use a RFR CUL?  Any LOVF Messages in the log?



On 9 Okt., 13:40, Al wrote:
> 2 of my 10 FHT80b devices have stopped transmitting any values other
> than actuator %. I have tried sending refreshvalues to them, and
> taking the batteries out for a while, but this had no effect.
>
> Any other suggestions for kicking them back into life?
>
> thanks!

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

Yes, I have tried that. I have moved the 2 FHT80Bs into the same room
as the FHZ to eliminate range problems.
Here is my cfg file. It is the Guest_Bedroom and Lounge_2 which I have
a problem with. I have also pasted the last few hours of lines from
the Guest Bedroom log.
#####
#Global
#attr global autoload_undefined_devices 1
attr global logfile c:/FHEM/log/__fhem-%Y-%m.log
attr global modpath c:/FHEM
attr global nofork 1
attr global port 7072
attr global verbose 3
define WEB FHEMWEB 8083 global
define WEBphone FHEMWEB 8084 global
attr WEBphone smallscreen
define WEBtablet FHEMWEB 8085 global
attr WEBtablet touchpad
define Logfile FileLog c:/FHEM/log/__fhem-%Y-%m.log fakelog
define FHZ1 FHZ COM9
attr FHZ1 fhtsoftbuffer 0
define autocreate autocreate
attr autocreate device_room %TYPE
attr autocreate filelog c:/FHEM/log/%NAME-%Y-%m.log
attr autocreate weblink
attr autocreate weblink_room Plots

#Log
define A_OfficeLog FileLog c:/FHEM/log/_A_Office-%Y-%m.log A_Office
define Bathroom_0Log FileLog c:/FHEM/log/_Bathroom_0-%Y-%m.log
Bathroom_0
define Bathroom_1Log FileLog c:/FHEM/log/_Bathroom_1-%Y-%m.log
Bathroom_1
define BedroomLog FileLog c:/FHEM/log/_Bedroom-%Y-%m.log Bedroom
define HallLog FileLog c:/FHEM/log/_Hall-%Y-%m.log Hall
define J_OfficeLog FileLog c:/FHEM/log/_J_Office-%Y-%m.log J_Office
define KitchenLog FileLog c:/FHEM/log/_Kitchen-%Y-%m.log Kitchen
define LoungeLog FileLog c:/FHEM/log/_Lounge-%Y-%m.log Lounge
define Lounge_2Log FileLog c:/FHEM/log/_Lounge_2-%Y-%m.log Lounge_2
define Guest_BedroomLog FileLog c:/FHEM/log/_Guest_Bedroom-%Y-%m.log
Guest_Bedroom

#Define
define A_Office FHT 1415
define Bathroom_0 FHT 3204
define Bathroom_1 FHT 494c
define Bedroom FHT 1414
define Guest_Bedroom FHT 3d56
define Hall FHT 522a
define J_Office FHT 2a5e
define Kitchen FHT 5362
define Lounge FHT 3758
define Lounge_2 FHT 4252

#Retry
attr A_Office retrycount 10
attr Bathroom_0 retrycount 10
attr Bathroom_1 retrycount 10
attr Bedroom retrycount 10
attr Guest_Bedroom retrycount 10
attr Hall retrycount 10
attr J_Office retrycount 10
attr Kitchen retrycount 10
attr Lounge retrycount 10
attr Lounge_2 retrycount 10

#Lazy
attr A_Office lazy 1
attr Bathroom_0 lazy 1
attr Bathroom_1 lazy 1
attr Bedroom lazy 1
attr Guest_Bedroom lazy 1
attr Hall lazy 1
attr J_Office lazy 1
attr Kitchen lazy 1
attr Lounge lazy 1
attr Lounge_2 lazy 1

#Report
define A_OfficeReport at +*06:00:00 set A_Office report1 255 report2
255
define Bathroom_0Report at +*06:00:00 set Bathroom_0 report1 255
report2 255
define Bathroom_1Report at +*06:00:00 set Bathroom_1 report1 255
report2 255
define BedroomReport at +*06:00:00 set Bedroom report1 255 report2 255
define Guest_BedroomReport at +*06:00:00 set Guest_Bedroom report1 255
report2 255
define HallReport at +*06:00:00 set Hall report1 255 report2 255
define J_OfficeReport at +*06:00:00 set J_Office report1 255 report2
255
define KitchenReport at +*06:00:00 set Kitchen report1 255 report2 255
define LoungeReport at +*06:00:00 set Lounge report1 255 report2 255
define Lounge_2Report at +*06:00:00 set Lounge_2 report1 255 report2
255

#ReportNow
set A_Office refreshvalues
set Bathroom_0 refreshvalues
set Bathroom_1 refreshvalues
set Bedroom refreshvalues
set Hall refreshvalues
set J_Office refreshvalues
set Kitchen refreshvalues
set Lounge refreshvalues
set Lounge_2 refreshvalues
set Guest_Bedroom refreshvalues

Log file

2011-10-10_02:33:13 Guest_Bedroom actuator: 0%
2011-10-10_02:35:10 Guest_Bedroom actuator: 0%
2011-10-10_02:37:08 Guest_Bedroom actuator: 0%
2011-10-10_02:39:06 Guest_Bedroom actuator: 0%
2011-10-10_02:41:03 Guest_Bedroom actuator: 0%
2011-10-10_02:43:01 Guest_Bedroom actuator: 0%
2011-10-10_02:44:59 Guest_Bedroom actuator: 0%
2011-10-10_02:46:56 Guest_Bedroom actuator: 0%
2011-10-10_02:48:54 Guest_Bedroom actuator: 0%
2011-10-10_02:50:52 Guest_Bedroom actuator: 0%
2011-10-10_02:52:49 Guest_Bedroom actuator: 0%
2011-10-10_02:54:47 Guest_Bedroom actuator: 0%
2011-10-10_02:56:45 Guest_Bedroom actuator: 0%
2011-10-10_02:58:43 Guest_Bedroom actuator: 0%
2011-10-10_03:00:40 Guest_Bedroom actuator: 0%
2011-10-10_03:00:41 Guest_Bedroom start-xmit: 100
2011-10-10_03:00:41 Guest_Bedroom start-xmit: 100
2011-10-10_03:00:41 Guest_Bedroom start-xmit: 100
2011-10-10_03:02:38 Guest_Bedroom actuator: 0%
2011-10-10_03:04:36 Guest_Bedroom actuator: 0%
2011-10-10_03:06:33 Guest_Bedroom actuator: 0%
2011-10-10_03:08:31 Guest_Bedroom actuator: 0%
2011-10-10_03:10:29 Guest_Bedroom actuator: 0%
2011-10-10_03:12:26 Guest_Bedroom actuator: 0%
2011-10-10_03:14:24 Guest_Bedroom actuator: 0%
2011-10-10_03:16:22 Guest_Bedroom actuator: 0%
2011-10-10_03:18:20 Guest_Bedroom actuator: 0%
2011-10-10_03:20:17 Guest_Bedroom actuator: 0%
2011-10-10_03:21:20 Guest_Bedroom report1 255 report2 255
2011-10-10_03:30:06 Guest_Bedroom start-xmit: 100
2011-10-10_03:59:32 Guest_Bedroom start-xmit: 100
2011-10-10_04:30:00 Guest_Bedroom start-xmit: 100
2011-10-10_04:30:01 Guest_Bedroom start-xmit: 100
2011-10-10_04:59:26 Guest_Bedroom start-xmit: 100
2011-10-10_04:59:27 Guest_Bedroom start-xmit: 100
2011-10-10_05:28:51 Guest_Bedroom start-xmit: 100
2011-10-10_05:28:52 Guest_Bedroom start-xmit: 100
2011-10-10_05:58:17 Guest_Bedroom start-xmit: 100
2011-10-10_05:58:18 Guest_Bedroom start-xmit: 100
2011-10-10_06:27:42 Guest_Bedroom start-xmit: 100

On Oct 10, 4:37 am, "Zrrronggg!" wrote:
> "I have tried sending refreshvalues to them" means you sent "report2
> 255" to them?
> If not plz try that.
>
> otherwise tell us a bit more about your installation.  FHZ1x00, CUL,
> CUN? Do you use a RFR CUL?  Any LOVF Messages in the log?
>
> On 9 Okt., 13:40, Al wrote:
>
>
>
>
>
>
>
> > 2 of my 10 FHT80b devices have stopped transmitting any values other
> > than actuator %. I have tried sending refreshvalues to them, and
> > taking the batteries out for a while, but this had no effect.
>
> > Any other suggestions for kicking them back into life?
>
> > thanks!

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[rudolfkoenig]

                                                   

> 2011-10-10_06:27:42 Guest_Bedroom start-xmit: 100

100 == not paired

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

> 100 == not paired

Thanks Rudolf, I have now paired it again with the actuator, and the
start-xmit 100 message has gone. I still only get the actuator 0%
messages through though, and nothing else. Any ideas on how to kick it
back into life?
Thanks

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Zrrronggg!]

                                                     

>I have now paired it again with the actuator,

You have paired the actuator with the FHT80b?

start-xmit 100

means that the FHT80 is not paired with FEHM!
Please do that again.


On 11 Okt., 00:10, Al wrote:
> > 100 == not paired
>
> Thanks Rudolf, I have now paired it again with the actuator, and the
> start-xmit 100 message has gone. I still only get the actuator 0%
> messages through though, and nothing else. Any ideas on how to kick it
> back into life?
> Thanks

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

> >I have now paired it again with the actuator,
>
> You have paired the actuator with the FHT80b?
>
> start-xmit 100
>
> means that the FHT80 is not paired with FEHM!
> Please do that again.
>

I have tried to re-pair it with the FHZ by setting "Cent" to "na" and
sending a "time" command to the fht. It still does not pair, and I
still get the start-xmit 100. How do I pair it?

thanks!

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Zrrronggg!]

                                                     

Well, that should have worked.

I'm a bit out of ideas.

If the pairing did not work, the "cent" must still be showing "na" is
that the case?

Maybe for some reason the buffer of the FHZ might be full.

I guess you are aware of this, but just in case:

It may take "some" time until the time-command is actually sent to the
FHT. You have 10 FHTs. Maybe you have sent during testing a lot of
commands to the different FHTs ( to make sure they work f.e.): that
can pile up in the buffer, since commands can only be sent every 2
minutes or so to the FHT. If you have issued only one separate command
to every other FHT prior to the pairing attempt, it can take up to 20
Minutes until the "time" command actually reaches the FHT in
question.

You may even run in LOVF Problems during testing. That happens usually
if I try to debug some FHTs problems.

Just thinking out loud here.



On 11 Okt., 21:40, Al wrote:
> > >I have now paired it again with the actuator,
>
> > You have paired the actuator with the FHT80b?
>
> > start-xmit 100
>
> > means that the FHT80 is not paired with FEHM!
> > Please do that again.
>
> I have tried to re-pair it with the FHZ by setting "Cent" to "na" and
> sending a "time" command to the fht. It still does not pair, and I
> still get the start-xmit 100. How do I pair it?
>
> thanks!

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

Hi, thanks for the thoughts. I have tried removing all of the FHT
devices from the cfg file except the 2 problem ones, and still have
the same problem. Yes the devices still show "na".

Really not sure what to do now - any other ideas?


thanks

On Oct 12, 2:56 am, "Zrrronggg!" wrote:
> Well, that should have worked.
>
> I'm a bit out of ideas.
>
> If the pairing did not work, the "cent" must still be showing "na" is
> that the case?
>
> Maybe for some reason the buffer of the FHZ might be full.
>
> I guess you are aware of this, but just in case:
>
> It may take "some" time until the time-command is actually sent to the
> FHT. You have 10 FHTs. Maybe you have sent during testing a lot of
> commands to the different FHTs ( to make sure they work f.e.): that
> can pile up in the buffer, since commands can only be sent every 2
> minutes or so to the FHT. If you have issued only one separate command
> to every other FHT prior to the pairing attempt, it can take up to 20
> Minutes until the "time" command actually reaches the FHT in
> question.
>
> You may even run in LOVF Problems during testing. That happens usually
> if I try to debug some FHTs problems.
>
> Just thinking out loud here.
>
> On 11 Okt., 21:40, Al wrote:
>
>
>
>
>
>
>
> > > >I have now paired it again with the actuator,
>
> > > You have paired the actuator with the FHT80b?
>
> > > start-xmit 100
>
> > > means that the FHT80 is not paired with FEHM!
> > > Please do that again.
>
> > I have tried to re-pair it with the FHZ by setting "Cent" to "na" and
> > sending a "time" command to the fht. It still does not pair, and I
> > still get the start-xmit 100. How do I pair it?
>
> > thanks!

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Zrrronggg!]

                                                     

>  any other ideas?

I'm afraid not.

You do use a FHZ1x00, no CUL / CUN, right?

(With CUL / CUN it could be worth trying to fumble with frequency and
bandwidth a bit, as they are a bit more "picky" compared to the FHZ
due to  different edge steepness)


On 12 Okt., 19:42, Al wrote:
> Hi, thanks for the thoughts. I have tried removing all of the FHT
> devices from the cfg file except the 2 problem ones, and still have
> the same problem. Yes the devices still show "na".
>
> Really not sure what to do now - any other ideas?
>
> thanks
>
> On Oct 12, 2:56 am, "Zrrronggg!" wrote:
>
>
>
>
>
>
>
> > Well, that should have worked.
>
> > I'm a bit out of ideas.
>
> > If the pairing did not work, the "cent" must still be showing "na" is
> > that the case?
>
> > Maybe for some reason the buffer of the FHZ might be full.
>
> > I guess you are aware of this, but just in case:
>
> > It may take "some" time until the time-command is actually sent to the
> > FHT. You have 10 FHTs. Maybe you have sent during testing a lot of
> > commands to the different FHTs ( to make sure they work f.e.): that
> > can pile up in the buffer, since commands can only be sent every 2
> > minutes or so to the FHT. If you have issued only one separate command
> > to every other FHT prior to the pairing attempt, it can take up to 20
> > Minutes until the "time" command actually reaches the FHT in
> > question.
>
> > You may even run in LOVF Problems during testing. That happens usually
> > if I try to debug some FHTs problems.
>
> > Just thinking out loud here.
>
> > On 11 Okt., 21:40, Al wrote:
>
> > > > >I have now paired it again with the actuator,
>
> > > > You have paired the actuator with the FHT80b?
>
> > > > start-xmit 100
>
> > > > means that the FHT80 is not paired with FEHM!
> > > > Please do that again.
>
> > > I have tried to re-pair it with the FHZ by setting "Cent" to "na" and
> > > sending a "time" command to the fht. It still does not pair, and I
> > > still get the start-xmit 100. How do I pair it?
>
> > > thanks!

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

Yes it is an FHZ. I don't think it is a reception issue as I get the
actuator 0% and start-xmit 100 messages regularly. Is there no other
way to factory reset the FHTs? is there a jumper or anything inside?

On Oct 12, 7:04 pm, "Zrrronggg!" wrote:
> >  any other ideas?
>
> I'm afraid not.
>
> You do use a FHZ1x00, no CUL / CUN, right?
>
> (With CUL / CUN it could be worth trying to fumble with frequency and
> bandwidth a bit, as they are a bit more "picky" compared to the FHZ
> due to  different edge steepness)
>
> On 12 Okt., 19:42, Al wrote:
>
>
>
>
>
>
>
> > Hi, thanks for the thoughts. I have tried removing all of the FHT
> > devices from the cfg file except the 2 problem ones, and still have
> > the same problem. Yes the devices still show "na".
>
> > Really not sure what to do now - any other ideas?
>
> > thanks
>
> > On Oct 12, 2:56 am, "Zrrronggg!" wrote:
>
> > > Well, that should have worked.
>
> > > I'm a bit out of ideas.
>
> > > If the pairing did not work, the "cent" must still be showing "na" is
> > > that the case?
>
> > > Maybe for some reason the buffer of the FHZ might be full.
>
> > > I guess you are aware of this, but just in case:
>
> > > It may take "some" time until the time-command is actually sent to the
> > > FHT. You have 10 FHTs. Maybe you have sent during testing a lot of
> > > commands to the different FHTs ( to make sure they work f.e.): that
> > > can pile up in the buffer, since commands can only be sent every 2
> > > minutes or so to the FHT. If you have issued only one separate command
> > > to every other FHT prior to the pairing attempt, it can take up to 20
> > > Minutes until the "time" command actually reaches the FHT in
> > > question.
>
> > > You may even run in LOVF Problems during testing. That happens usually
> > > if I try to debug some FHTs problems.
>
> > > Just thinking out loud here.
>
> > > On 11 Okt., 21:40, Al wrote:
>
> > > > > >I have now paired it again with the actuator,
>
> > > > > You have paired the actuator with the FHT80b?
>
> > > > > start-xmit 100
>
> > > > > means that the FHT80 is not paired with FEHM!
> > > > > Please do that again.
>
> > > > I have tried to re-pair it with the FHZ by setting "Cent" to "na" and
> > > > sending a "time" command to the fht. It still does not pair, and I
> > > > still get the start-xmit 100. How do I pair it?
>
> > > > thanks!

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Zrrronggg!]

                                                     

Not that I know off.  Taking out batteries and waiting for some 5
Minutes shoul do it.

On 12 Okt., 20:08, Al wrote:
> Yes it is an FHZ. I don't think it is a reception issue as I get the
> actuator 0% and start-xmit 100 messages regularly. Is there no other
> way to factory reset the FHTs? is there a jumper or anything inside?
>
> On Oct 12, 7:04 pm, "Zrrronggg!" wrote:
>
>
>
>
>
>
>
> > >  any other ideas?
>
> > I'm afraid not.
>
> > You do use a FHZ1x00, no CUL / CUN, right?
>
> > (With CUL / CUN it could be worth trying to fumble with frequency and
> > bandwidth a bit, as they are a bit more "picky" compared to the FHZ
> > due to  different edge steepness)
>
> > On 12 Okt., 19:42, Al wrote:
>
> > > Hi, thanks for the thoughts. I have tried removing all of the FHT
> > > devices from the cfg file except the 2 problem ones, and still have
> > > the same problem. Yes the devices still show "na".
>
> > > Really not sure what to do now - any other ideas?
>
> > > thanks
>
> > > On Oct 12, 2:56 am, "Zrrronggg!" wrote:
>
> > > > Well, that should have worked.
>
> > > > I'm a bit out of ideas.
>
> > > > If the pairing did not work, the "cent" must still be showing "na" is
> > > > that the case?
>
> > > > Maybe for some reason the buffer of the FHZ might be full.
>
> > > > I guess you are aware of this, but just in case:
>
> > > > It may take "some" time until the time-command is actually sent to the
> > > > FHT. You have 10 FHTs. Maybe you have sent during testing a lot of
> > > > commands to the different FHTs ( to make sure they work f.e.): that
> > > > can pile up in the buffer, since commands can only be sent every 2
> > > > minutes or so to the FHT. If you have issued only one separate command
> > > > to every other FHT prior to the pairing attempt, it can take up to 20
> > > > Minutes until the "time" command actually reaches the FHT in
> > > > question.
>
> > > > You may even run in LOVF Problems during testing. That happens usually
> > > > if I try to debug some FHTs problems.
>
> > > > Just thinking out loud here.
>
> > > > On 11 Okt., 21:40, Al wrote:
>
> > > > > > >I have now paired it again with the actuator,
>
> > > > > > You have paired the actuator with the FHT80b?
>
> > > > > > start-xmit 100
>
> > > > > > means that the FHT80 is not paired with FEHM!
> > > > > > Please do that again.
>
> > > > > I have tried to re-pair it with the FHZ by setting "Cent" to "na" and
> > > > > sending a "time" command to the fht. It still does not pair, and I
> > > > > still get the start-xmit 100. How do I pair it?
>
> > > > > thanks!

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

I am also experiencing this problem with some of my FHT80Bs.

First it was one only and now it is three of them (out of ten
altogether)

An example log shows:
2011-10-21_20:14:47 FHT_5009 actuator: 0%
2011-10-21_20:14:47 FHT_5009 start-xmit: 100
2011-10-21_20:14:47 FHT_5009 start-xmit: 100
2011-10-21_20:14:47 FHT_5009 start-xmit: 100
2011-10-21_20:16:42 FHT_5009 actuator: 0%
2011-10-21_20:18:38 FHT_5009 actuator: 0%
2011-10-21_20:20:33 FHT_5009 actuator: 0%
2011-10-21_20:22:29 FHT_5009 actuator: 0%
2011-10-21_20:24:24 FHT_5009 actuator: 0%
2011-10-21_20:26:20 FHT_5009 actuator: 0%
2011-10-21_20:28:15 FHT_5009 actuator: 0%
2011-10-21_20:30:11 FHT_5009 actuator: 0%
2011-10-21_20:32:06 FHT_5009 actuator: 0%
2011-10-21_20:34:02 FHT_5009 actuator: 0%
2011-10-21_20:34:46 FHT_5009 time
2011-10-21_20:35:57 FHT_5009 actuator: 0%
2011-10-21_20:37:53 FHT_5009 actuator: 0%
2011-10-21_20:39:48 FHT_5009 actuator: 0%
2011-10-21_20:41:44 FHT_5009 actuator: 65%

Note the last entry which is 65% - this is because I manually adjusted
the large wheel on the FHT80B to set the temperature high.

So from this I deduce that FHEM is able to see the device and also to
read value of the actuator.
PROG > CENT is set to nA and seems to be stuck on this value.

I moved my FHZ1300 PC from a linux box (NSLU2) to a VMWare Win7 PC
(Test environment) and now finally to a standalone Win7 X64 PC.

I have tried sending a time command to the device ( 'set FHT_5009
time') but this hasn't made any difference.
Other devices are giving full details e.g.:

2011-10-21_20:34:46 FHT_2802 actuator: 36%
2011-10-21_20:35:28 FHT_2802 measured-temp: 20.9 (Celsius)
2011-10-21_20:35:28 FHT_2802 ack: 0
2011-10-21_20:35:29 FHT_2802 battery: ok
2011-10-21_20:35:29 FHT_2802 lowtemp: ok
2011-10-21_20:35:29 FHT_2802 window: closed
2011-10-21_20:35:29 FHT_2802 windowsensor: ok
2011-10-21_20:35:29 FHT_2802 warnings: none
2011-10-21_20:35:29 FHT_2802 ack: 0
2011-10-21_20:35:29 FHT_2802 end-xmit: 0
2011-10-21_20:36:42 FHT_2802 actuator: 36%

However, I have also noticed that if I set the desired temperature,
the device seems to ignore it - it used to work fine previously (via
the NSLU2).

Ideally it would be great to be able to reset every thing but I am not
sure how to achieve this.
I think I must be missing something obvious?


--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

> I am also experiencing this problem with some of my FHT80Bs.
>
> First it was one only and now it is three of them (out of ten
> altogether)

I believe the problem is that the FHT80b has "gone deaf" and the
receiver module is not receiving commands. It still transmits though.
I have contacted Conrad and they are replacing my 2 dead units which
are 2 years old. I hope no more units die like this.

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com