unkown messages and problem with FHT

Begonnen von Guest, 26 Januar 2012, 13:15:15

Vorheriges Thema - Nächstes Thema

Guest

Originally posted by: <email address deleted>

Hello all,

Recently I switched to using a CUL (CC1101 with firmware v1.44) in my
fhem environment. I've got several FHT (5 pcs) , FHTTK, EM and FS20
components. Everything is still working fine except for the FHT
devices. Only the actuator messages are received, I see no other
messages anymore in  the logfile. Even changing the temperature on the
FHT device or within FHEM doesn't do anything
I switched on debugging on the CUL by enabling X67 and I see a lot of
'unknown message' entries. I'm not sure if the both are related but it
wouldn't surprise me.

I tried several things to solve this:
- new batteries
- switching value for Cent on the FHT device off and on
- (auto) recreate a FHT device.
- replacing the FHT device for a better/lower RSSI value

The only thing I see are actuator messages in the fht logfile and
unknown messages in the fhem logfile.
Who can help me solving this?

fht log:
2012-01-26_13:14:25 FHT_6323 actuator: 0%
2012-01-26_13:14:25 FHT_6323 RSSI: -81
2012-01-26_13:14:25 FHT_6323 RAWMSG: T632300A600F2
2012-01-26_13:14:25 FHT_6323 FHZ:can-xmit: 67
2012-01-26_13:14:25 FHT_6323 RSSI: -77
2012-01-26_13:14:25 FHT_6323 RAWMSG: T6323537743FA
2012-01-26_13:14:25 FHT_6323 FHZ:can-xmit: 67
2012-01-26_13:14:25 FHT_6323 RSSI: -77
2012-01-26_13:14:25 FHT_6323 RAWMSG: T6323537743FA
fhem log
2012.01.26 13:10:32.202 2: CUL1: unknown message p 3  400  320  624
560 12  6 6 F3 6311C014C001C4
2012.01.26 13:11:04.121 2: CUL1: unknown message p 3  800  368  288
832  9  6 2 F6 8A6758D4756FC0
2012.01.26 13:11:21.959 2: CUL1: unknown message p 3  416  320  576
528 10  6 6 05 18044014C00690
2012.01.26 13:11:22.028 2: CUL1: unknown message p 3  384  320  608
560 12  6 6 05 18044014C00690
2012.01.26 13:11:22.306 2: CUL1: unknown message p 3  800  352  320
864  9  6 2 2F 8C63D8CE754CC0
2012.01.26 13:11:34.476 2: CUL1: unknown message p 3  832  320  336
800 10  6 2 E2 8953D0C63DEE40
2012.01.26 13:11:39.973 2: CUL1: unknown message p 3  400  320  608
576 12  6 6 3C 3E91C014C0009C
2012.01.26 13:12:24.929 2: CUL1: unknown message p 3  400  336  592
528 12  5 5 F7 7748D7C05758
2012.01.26 13:12:24.968 2: CUL1: unknown message p 3  384  320  576
544 10  5 5 F7 7748D7D04F50
2012.01.26 13:12:29.355 2: CUL1: unknown message p 3  352  384  560
592 11  6 6 F1 6311C014C001C4
2012.01.26 13:12:33.671 2: CUL1: unknown message p 3  336  416  352
768 17 11 1 E8 40D06CA1780804020100EC80
2012.01.26 13:12:33.683 2: CUL1: unknown message p 3  336  400  352
768 17 11 1 E7 40D06CA1780804020100EC80
2012.01.26 13:12:33.694 2: CUL1: unknown message p 3  352  400  368
752 17 11 1 E8 40D06CA1780804020100EC80
2012.01.26 13:12:38.845 2: CUL1: unknown message p 3  384  368  560
544 12  5 5 FE 688CCAC05BA8
2012.01.26 13:12:38.851 2: CUL1: unknown message p 3  400  320  592
528 12  5 5 FE 688CCAD043A0
2012.01.26 13:13:05.319 2: CUL1: unknown message p 3  400  336  416
720 17 11 1 2F 40B06F3ABB0904024100FC80
2012.01.26 13:13:05.329 2: CUL1: unknown message p 3  416  320  400
720 17 11 1 2F 40B06F3ABB0904024100FC80
2012.01.26 13:13:05.340 2: CUL1: unknown message p 3  384  352  416
720 17 11 1 2F 40B06F3ABB0904024100FC80
2012.01.26 13:13:16.985 2: CUL1: unknown message p 3  400  320  608
544 12  6 6 05 18044014C00690
2012.01.26 13:13:16.999 2: CUL1: unknown message p 3  368  368  640
528 12  6 6 05 18044014C00690
2012.01.26 13:13:17.120 2: CUL1: unknown message p 3  384  368  560
576 12  5 5 E8 4773B2805060
2012.01.26 13:13:17.601 2: CUL1: unknown message p 3  352  368  560
576 12  5 5 E8 4773B2904868
2012.01.26 13:13:18.902 2: CUL1: unknown message p 3  432  304  640
544 12  6 6 E2 4091C014C000AC
2012.01.26 13:13:18.970 2: CUL1: unknown message p 3  416  320  624
544 12  6 6 E3 4091C014C000AC
2012.01.26 13:13:36.527 2: CUL1: unknown message p 3  400  320  608
560 12  6 6 3C 3E91C014C0009C

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

rudolfkoenig

                                                   

> I switched on debugging on the CUL by enabling X67 and I see a lot of

X67 is too much for fhem, so "unknown message" is normal".
X67 it is for looking for new type of messages received by the CUL.
What you are looking for is X61.

What I see from the log is that an FHT is sending actuator messages (00A600),
and somebody (probably the CUL) is trying to talk to this FHT. But the FHT
won't answer. One probable cause is, that it is not paired with the CUL.

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

Guest

Originally posted by: <email address deleted>

Hmm, that would be the explanation. I changed from a CUNO to CUL so
yes offcourse, I have to pair them again.
Unfortunately a moment ago I did an updatefhem. A message appeared
that fhem.pl had to be restarted. After rebooting the system (Ubuntu)
I get an error in the fhem log saying "Can't open /dev/ttyS0:
Permission denied"
I can connect with putty to the CUL and it works normally. Did
something changed in fhem.pl that is causing this?


On 26 jan, 13:43, Rudolf Koenig wrote:
> > I switched on debugging on the CUL by enabling X67 and I see a lot of
>
> X67 is too much for fhem, so "unknown message" is normal".
> X67 it is for looking for new type of messages received by the CUL.
> What you are looking for is X61.
>
> What I see from the log is that an FHT is sending actuator messages (00A600),
> and somebody (probably the CUL) is trying to talk to this FHT. But the FHT
> won't answer. One probable cause is, that it is not paired with the CUL.

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

rudolfkoenig

                                                   

> I can connect with putty to the CUL and it works normally. Did
> something changed in fhem.pl that is causing this?

It may be: when fhem is started as root, and there is a fhem user in
/etc/passwd, then fhem is now using all the groups assigned to this fhem user,
instead of using the hardcoded dialin group.

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

Guest

Originally posted by: <email address deleted>

Hello Rudy,

I changed the security settings for /dev/ttyS0 and it is working
again.
After pairing the FHT seems to be working like before. So problem
solved :)

On 26 jan, 14:42, Rudolf Koenig wrote:
> > I can connect with putty to the CUL and it works normally. Did
> > something changed in fhem.pl that is causing this?
>
> It may be: when fhem is started as root, and there is a fhem user in
> /etc/passwd, then fhem is now using all the groups assigned to this fhem user,
> instead of using the hardcoded dialin group.

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