Originally posted by: <email address deleted>
Hi everyone,
I have a question with my 80TF-2 to get to work.
Thinking I have set everything correct (log):
2010.02.10 16:21:24 2: CUL: unknown message V 1.32 CUN
2010.02.10 16:21:35 2: CUL: unknown message T49F69802
2010.02.10 16:21:35 2: CUL: unknown message T49F69882
2010.02.10 16:22:38 2: CUL: unknown message T49F69802
2010.02.10 16:22:39 2: CUL: unknown message T49F69882
2010.02.10 16:23:11 3: Internals:
CODE 49f698
DEF 49F698
NAME Raam
NR 14
STATE ???
TYPE CUL_FHTTK
Attributes:
model 80tf-2
room Overig
Noticed the device is sometimes sending 9 HEX digits and sometimes 11 HEX
digits when monitoring by telnet.
Exempels:
T49F69881
T49F69801
T49F6980120
T49F6988121
Maybe this is related? However I have no clue what the last 2 HEX digits are
for.
Cheers, Zeo (zaleo)
--
You received this message because you are subscribed to the Google Groups "FHEM users" 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.
Originally posted by: <email address deleted>
Zeo Smeijsters wrote:
> Hi everyone,
>
> I have a question with my 80TF-2 to get to work.
>
> Thinking I have set everything correct (log):
>
> 2010.02.10 16:21:24 2: CUL: unknown message V 1.32 CUN
That looks strange to me. If I do a "get CUL version", I get e. g.
2010.02.10 17:16:34 3: CUL version => V 1.30 CUL868
(same for CUN)
> 2010.02.10 16:21:35 2: CUL: unknown message T49F69802
> 2010.02.10 16:21:35 2: CUL: unknown message T49F69882
> 2010.02.10 16:22:38 2: CUL: unknown message T49F69802
> 2010.02.10 16:22:39 2: CUL: unknown message T49F69882
# -wusel, 2009-11-06
#
# Parse messages from FHT80TK, normally interpreted only by FHT80
#
# Format as follows: "TCCCCCCXX" with CCCCCC being the id of the
# sensor in hex, XX being the current status: 02/82 is Window
# closes, 01/81 is Window open, 0C is synchronization, ?? is the
# battery low warning. FIXME!
Hmm, that shouldn't be "unknown message", should it?
> 2010.02.10 16:23:11 3: Internals:
> CODE 49f698
> DEF 49F698
> NAME Raam
> NR 14
> STATE ???
> TYPE CUL_FHTTK
> Attributes:
> model 80tf-2
> room Overig
>
> Noticed the device is sometimes sending 9 HEX digits and sometimes 11
> HEX digits when monitoring by telnet.
>
> Exempels:
>
> T49F69881
> T49F69801
> T49F6980120
> T49F6988121
>
> Maybe this is related? However I have no clue what the last 2 HEX digits
> are for.
Neither do I; it your's this one (the new TF version)?
http://www.elv.de/output/controller.aspx?cid=74&detail=10&detail2=26283&flv=1&bereich=&marke=
Maybe it's a new/extended protocol? On the other hand, I'm puzzled about this:
"Hinweis: Druckfehler im Hauptkatalog 2010 - Der FHT 80 TF-2 ist nicht kompatibel mit der FHZ 1000."
(Notice: error in out catalogue for 2010 - the FHT 80 TF-2 is not compatible with the FHZ 1000)
I don't think FHZ ever handled FHT80TF, did it?
kai
--
You received this message because you are subscribed to the Google Groups "FHEM users" 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.
Originally posted by: <email address deleted>
Thanks for your answer, sorry for mein schlechte deutsche
Sprache... :)
I do understand it a bit, but these discussion groups are to
complicated/technical deutsch fur Mich.
Yes it is that one the -2 indicates there was an previous version, I
assume. ;p
The message is strange as I was giving the "V" command directly in CUN/
CUL with a telnet session during troubleshooting. Don't think that is
related.
In FHEM it is "CUN version => V 1.32 CUN"
I think it is related to the 2 extra digits... (And I have no clue
what they do, but they applied to be incremental, maybe it is the time
the door/window is open.)
---
On 10 feb, 17:26, "Kai 'wusel' Siering"
wrote:
> Zeo Smeijsters wrote:
> > Hi everyone,
>
> > I have a question with my 80TF-2 to get to work.
>
> > Thinking I have set everything correct (log):
>
> > 2010.02.10 16:21:24 2: CUL: unknown message V 1.32 CUN
>
> That looks strange to me. If I do a "get CUL version", I get e. g.
>
> 2010.02.10 17:16:34 3: CUL version => V 1.30 CUL868
>
> (same for CUN)
>
> > 2010.02.10 16:21:35 2: CUL: unknown message T49F69802
> > 2010.02.10 16:21:35 2: CUL: unknown message T49F69882
> > 2010.02.10 16:22:38 2: CUL: unknown message T49F69802
> > 2010.02.10 16:22:39 2: CUL: unknown message T49F69882
>
> # -wusel, 2009-11-06
> #
> # Parse messages from FHT80TK, normally interpreted only by FHT80
> #
> # Format as follows: "TCCCCCCXX" with CCCCCC being the id of the
> # sensor in hex, XX being the current status: 02/82 is Window
> # closes, 01/81 is Window open, 0C is synchronization, ?? is the
> # battery low warning. FIXME!
>
> Hmm, that shouldn't be "unknown message", should it?
>
>
>
>
>
> > 2010.02.10 16:23:11 3: Internals:
> > CODE 49f698
> > DEF 49F698
> > NAME Raam
> > NR 14
> > STATE ???
> > TYPE CUL_FHTTK
> > Attributes:
> > model 80tf-2
> > room Overig
>
> > Noticed the device is sometimes sending 9 HEX digits and sometimes 11
> > HEX digits when monitoring by telnet.
>
> > Exempels:
>
> > T49F69881
> > T49F69801
> > T49F6980120
> > T49F6988121
>
> > Maybe this is related? However I have no clue what the last 2 HEX digits
> > are for.
>
> Neither do I; it your's this one (the new TF version)?
>
> http://www.elv.de/output/controller.aspx?cid=74&detail=10&detail2=262...
>
> Maybe it's a new/extended protocol? On the other hand, I'm puzzled about this:
>
> "Hinweis: Druckfehler im Hauptkatalog 2010 - Der FHT 80 TF-2 ist nicht kompatibel mit der FHZ 1000."
> (Notice: error in out catalogue for 2010 - the FHT 80 TF-2 is not compatible with the FHZ 1000)
>
> I don't think FHZ ever handled FHT80TF, did it?
> kai- Tekst uit oorspronkelijk bericht niet weergeven -
>
> - Tekst uit oorspronkelijk bericht weergeven -
--
You received this message because you are subscribed to the Google Groups "FHEM users" 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.
Originally posted by: <email address deleted>
OK, found something..
CUL V1.36CUL868 is not giving the 2 extra HEX digits
CUN V1.32 CUN is giving the 2 extra HEX digits
I also found out that the CUN is giving 2 extra digits as well for
FS20 commands, but it is working nicely. I am lost...
Now FHEM is not connected to the CUL..
When I reset the CUN it is working without the 2 extra digits, but as
soon as I connect FHEM I get this again:
V Manual request for version.
V 1.32 CUN Version number feedback
X01 Manual request for feedback off messages in air
F****0311 Test on remote
F****0300 Test on remote
F****0311 Test on remote
V 1.32 CUN Connecting FHEM
1111 Connection FHEM
F5BB0030002 Test on remote (extra 2 digits)
F5BB00311FF Test on remote (extra 2 digits)
Some how the connection of FHEM enabels a more extensive logging level
or something?
It seems to me there is a CUN FHTTK issue here or something in FHEM..
Maybe better when the FHTTK module ignores the 2 extra HEX digits?
---
More info:
This is what I added in my /var/log/fhem/fhem.cfg, before I was
working with FS20 only, hsould be good right?
define Raam CUL_FHTTK 49F698
attr Raam model FHT80TF
I also find this in my Log:
3: No I/O device found for Raam
But......
"The attribute IODev should be used only if you attached more than one
physical device capable of receiving signals for this logical device."
I only have one device connected to FHEM, so it should automatically
use the last physical device which can receive data for this type of
device, right?
--
You see, I only get more questions now... Damn.
Hoping by giving more data it gets a bit more clear, and not more
complicated.
--
You received this message because you are subscribed to the Google Groups "FHEM users" 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.
Originally posted by: <email address deleted>
Zaleo wrote:
> OK, found something..
I found something confusing in your other mail:
> The message is strange as I was giving the "V" command directly in CUN/
> CUL with a telnet session during troubleshooting. Don't think that is
> related.
> In FHEM it is "CUN version => V 1.32 CUN"
In my experience, you can't connect FHEM to CUN and open a telnet
session in parallel? That is, *I* can only telnet once to CUN, any
other attempt is stalled -- or did you connect CUN via USB to FHEM
and did a telnet in parallel?
> CUL V1.36CUL868 is not giving the 2 extra HEX digits
> CUN V1.32 CUN is giving the 2 extra HEX digits
Oops, seems I'm rather old-school here:
root@plug-2:~# fhem.pl 7072 "get CUL version"
CUL version => V 1.30 CUL868
root@plug-2:~# fhem.pl 7072 "get CUN version"
CUN version => V 1.31.4 CUN
> I also found out that the CUN is giving 2 extra digits as well for
> FS20 commands, but it is working nicely. I am lost...
That seems to be a firmware issue then; better addressed in cul-fans-
list, but maybe someone with the knowledge could shed a light here
as well?
> Now FHEM is not connected to the CUL..
>
> When I reset the CUN it is working without the 2 extra digits, but as
> soon as I connect FHEM I get this again:
>
> V Manual request for version.
> V 1.32 CUN Version number feedback
> X01 Manual request for feedback off messages in air
> F****0311 Test on remote
> F****0300 Test on remote
> F****0311 Test on remote
> V 1.32 CUN Connecting FHEM
> 1111 Connection FHEM
> F5BB0030002 Test on remote (extra 2 digits)
> F5BB00311FF Test on remote (extra 2 digits)
Hmm. I don't understand what you're trying to say; this seems to be neither
from the FHEM logfile nor from a screen/telnet/whatever session, as you say
"as I connect FHEM"?
> Some how the connection of FHEM enabels a more extensive logging level
> or something?
Nope. Not normally. Maybe some wierd fhem.cfg setting?
> It seems to me there is a CUN FHTTK issue here or something in FHEM..
Neither; it's either your setup or your culfw version for your CUN.
> Maybe better when the FHTTK module ignores the 2 extra HEX digits?
Tough. From 00_CUL.pm:
} elsif($fn eq "T") {
if ($len >= 11) { # Reformat for 11_FHT.pm
$dmsg = sprintf("81%02x04xx0909a001%s00%s",
$len/2+7, substr($dmsg,1,6), substr($dmsg,7));
$dmsg = lc($dmsg);
} else {
; # => 09_CUL_FHTTK.pm
}
==> With the additional digits, it would be of length 11, therefore we
couldn't (easily) differenciate between an FHT80b message or an FHT80TF
message. (In theory, the CUL_FHTTK.pm code should reside in FHT.pm, but
as a FHZ does not decode FHT80TK-messages and FHT.pm is only parsing
FHZ-style messages (which get reformatted by CUL from CUL to FHZ for-
mat), there's a catch 22 here ...)
But I think it's much easier to solve by another firmware ...
> ---
>
> More info:
> This is what I added in my /var/log/fhem/fhem.cfg, before I was
> working with FS20 only, hsould be good right?
>
> define Raam CUL_FHTTK 49F698
> attr Raam model FHT80TF
>
> I also find this in my Log:
>
> 3: No I/O device found for Raam
>
> But......
> "The attribute IODev should be used only if you attached more than one
> physical device capable of receiving signals for this logical device."
Hmm, which version of fhem are you running?
> I only have one device connected to FHEM, so it should automatically
> use the last physical device which can receive data for this type of
> device, right?
Yepp, that's the plan ;) And usually it's working; did you maybe
mixup versions? For FHTTK.pm to function, CUL.pm needed a patch,
too, so it's not sufficient to install any version of FHEM and just
add FHTTK.pm ...
kai
--
You received this message because you are subscribed to the Google Groups "FHEM users" 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.
Originally posted by: <email address deleted>
On 11.02.10 00:20, "Kai 'wusel' Siering" wrote:
>> OK, found something..
>
> I found something confusing in your other mail:
>
>> The message is strange as I was giving the "V" command directly in CUN/
>> CUL with a telnet session during troubleshooting. Don't think that is
>> related.
>> In FHEM it is "CUN version => V 1.32 CUN"
>
> In my experience, you can't connect FHEM to CUN and open a telnet
> session in parallel? That is, *I* can only telnet once to CUN, any
> other attempt is stalled -- or did you connect CUN via USB to FHEM
> and did a telnet in parallel?
Yes we can ;-) (on LAN)
a.
--
You received this message because you are subscribed to the Google Groups "FHEM users" 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.
HI all,
> In my experience, you can't connect FHEM to CUN and open a telnet
> session in parallel? That is, *I* can only telnet once to CUN, any
> other attempt is stalled -- or did you connect CUN via USB to FHEM
> and did a telnet in parallel?
>
Yes we can ;)
When CUN was released I have written a second makefile (makefile.2con)
for CUN, that enables 2 Telnet-Sessions in parallel.
Just recompile the CUN Firmware with this makefile, and you're done.
This was the result of a partial rewrite of the TCP-Connection Routing
for the firmware of CUN I have done at that time.
Best,
Olaf
--
You received this message because you are subscribed to the Google Groups "FHEM users" 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.
> CUL V1.36CUL868 is not giving the 2 extra HEX digits
> CUN V1.32 CUN is giving the 2 extra HEX digits
The extra two digits are the RSSI. It is sent depending on how you switch on
radio reception (X01 vs X21, see the CUL README). Current fhem versions
(00_CUL.pm) are defaulting to X21 (set CUL verbose 21). Do not touch X..
parallel to a connected fhem, else fhem will be confused. In future versions of
00_CUL.pm the verbose command will be removed completely, as it is hard to
implement it correctly.
> In my experience, you can't connect FHEM to CUN and open a telnet session in
> parallel?
You cannot open 2 TCP sessions without using the (non-default) patches from
Olaf, but you can open a TCP and a USB session in parallel. In earlier versions
(< 1.33 ?) every data would be sent back to both connections, current versions
send only the data requested back. Received RF telegrams are still sent to both
connections.
> 3: No I/O device found for Raam
>
> But......
> "The attribute IODev should be used only if you attached more than one
> physical device capable of receiving signals for this logical device."
A logical device (FS20) needs a physical device (CUN) defined before (in the
config file too). And you should check that you have the up to date versions of
CUL.pm and CUL_FHTTK, as CUL.pm must declare itself compatible with CUL_FHTTK
(Clients hash entry in CUL.pm)
For beginners it is best to check out the CVS version and enable autocreate
(e.g. with make install-pgm2). This still lacks an autodection for physical
hardware (CUL/CUN/FHZ), but it autocreates a lot of the logical devices.
--
You received this message because you are subscribed to the Google Groups "FHEM users" 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.
Originally posted by: <email address deleted>
Hi all,
Problem is still not really solved.
The "No I/O device found" is fixed, from what I understand is that the
current FHEM is using the X21 reporting mode of the CUN generating 2
extra digits.
The 00_CUL is looking for 9 digits and does not tigger FHTTK.
For me this seems to be a bug in the current FHEM.
I used the FHEM as yesterday on the CVS.
I dit do no more as the checkout, make install-pgm2 and mv-ed the
config file back as the auto install did make a backup nicely.
And yes i have used the second make file that allowes 2 sessions over
TCPIP.
Maybe time I complie the latest culfw for my CUN, but I don't think
this is a fw issue.
On 11 feb, 07:57, Rudolf Koenig wrote:
> A logical device (FS20) needs a physical device (CUN) defined before (in the
> config file too). And you should check that you have the up to date versions of
> CUL.pm and CUL_FHTTK, as CUL.pm must declare itself compatible with CUL_FHTTK
> (Clients hash entry in CUL.pm)
>
> For beginners it is best to check out the CVS version and enable autocreate
> (e.g. with make install-pgm2). This still lacks an autodection for physical
> hardware (CUL/CUN/FHZ), but it autocreates a lot of the logical devices.
Done it that way.
--
You received this message because you are subscribed to the Google Groups "FHEM users" 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.
Originally posted by: <email address deleted>
Hi,
Zaleo wrote:
> The 00_CUL is looking for 9 digits and does not tigger FHTTK.
> I used the FHEM as yesterday on the CVS.
> And yes i have used the second make file that allowes 2 sessions over
> TCPIP.
>
> Maybe time I complie the latest culfw for my CUN, but I don't think
> this is a fw issue.
Well, all I *can* say is that it's working with the aformentioned
culfws here on CUL/CUN, that it's working at your side with your CUL
as well and that I don't use more than 1 connection per device (CUL
and CUN). Thus, from my point of view, it's either the culfw you're
using or something with your fhem.cfg or something that you do on
the second telent session; the data sent do FHEM is simply wrong
(to much digits), but I'm at loss as to tell where they are triggered.
kai
--
You received this message because you are subscribed to the Google Groups "FHEM users" 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.
Am Mittwoch 10 Februar 2010 schrieb Kai 'wusel' Siering:
> [...]
> > Maybe this is related? However I have no clue what the last 2 HEX digits
> > are for.
>
> Neither do I; it your's this one (the new TF version)?
>
> http://www.elv.de/output/controller.aspx?cid=74&detail=10&detail2=26283&flv
> =1&bereich=&marke=
>
> Maybe it's a new/extended protocol? On the other hand, I'm puzzled about
> this:
nope ;-)
here are some 80TF and 80TF-2 defined.. running like a charm ;-)
best, martin
--
You received this message because you are subscribed to the Google Groups "FHEM users" 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.
btw:
kai, could you please remove (or push it to loglevel 5) the logentry
"FHTTK skipping state 02 as last similar telegram was received less than 5 (2)
secs ago"
thx..
--
You received this message because you are subscribed to the Google Groups "FHEM users" 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.
Originally posted by: <email address deleted>
Martin Fischer wrote:
> kai, could you please remove (or push it to loglevel 5) the logentry
> "FHTTK skipping state 02 as last similar telegram was received less than 5 (2)
> secs ago"
Ack; was at 4 in current CVS, will be at 5 at the next update (after merging
back changes made in the last days).
kai
--
You received this message because you are subscribed to the Google Groups "FHEM users" 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.
Originally posted by: <email address deleted>
Still I must do someting wrong here then...
This is my config file, did I forget something?
----
#
# Minimalistic fhem.pl & pgm2 configfile. Take a look at the other
examples for
# more.
#
attr global logfile /var/log/fhem/fhem-%Y-%m.log
attr global statefile ..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
attr global allowfrom 127.0.0.1
define CUN CUL 192.168.0.12:2323 1111
define WEB FHEMWEB 8083 global
attr WEB plotmode SVG
setdefaultattr room WoonRuimte
define Balkon CUL_FHTTK 49F698
define Klimaat HMS 1000
define Eetkamer FS20 22343411 06 lm 1244 fg 4421 gm 4444
define Woonkamer FS20 22343411 07 lm 1244 fg 4421 gm 4444
define Klok FS20 22343411 08 lm 1244 fg 4422 gm 4444
define KleurLamp FS20 22343411 09 lm 1244 fg 4422 gm 4444
setdefaultattr
setdefaultattr room WerkRuimte
define Kantoor FS20 22343411 03 lm 1344 fg 4421 gm 4444
define Berging FS20 22343411 05 lm 1144 fg 4421 gm 4444
setdefaultattr
setdefaultattr room SlaapRuimte
define Slaapkamer FS20 22343411 02 lm 1444 fg 4421 gm 4444
define Wekker FS20 22343411 53 lm 1444 fg 4422 gm 4444
define BedLamp FS20 22343411 0b lm 1444 fg 4422 gm 4444
setdefaultattr
setdefaultattr room Overig
define Gang FS20 22343411 00 lm 1144 fg 4421 gm 4444
define Keuken FS20 22343411 01 lm 1144 fg 4421 gm 4444
define Badkamer FS20 22343411 04 lm 1144 fg 4421 gm 4444
define CocaCola FS20 22343411 0a lm 1144 fg 4422 gm 4444
setdefaultattr
#define Forecast Weather "Sittard-Geleen,NL" 1800
define Master FS20 22343411 4444
attr Klimaat model hms100-tf
attr Balkon model FHT80TF
attr Wekker model fs20ze
attr Gang model fs20su
attr Badkamer model fs20su
attr Berging model fs20su
attr Keuken model fs20du
attr Slaapkamer model fs20du
attr Kantoor model fs20du
attr Eetkamer model fs20du
attr Woonkamer model fs20du
attr Klok model fs20st
attr KleurLamp model fs20st
attr CocaCola model fs20st
attr BedLamp model fs20di
# Laden van mijn coordinaten voor juiste sunset/rise
{ sunrise_coord("5.829", "50.970", "") }
# Automatische opdrachten
# define Opstaan at 08:00:00 set WekkerActie on
define AvondLichtUit at +{sunrise_rel()} set KleurLamp off
define AvondLichtAan at +{sunset_rel()} set KleurLamp on
# Als Dan...
define WekkerActie notify Wekker { \
if("%" eq "on") { \
fhem("set Slaapkamer dim100%% 288");; \
fhem("set BedLamp dim100%% 180");; \
} \
if("%" eq "off") { \
fhem("set Slaapkamer off");; \
fhem("set BedLamp off");; \
} \
if("%" eq "dimup") { fhem("set Slaapkamer dim100%%");; } \
if("%" eq "dimdown") { fhem("set Master off");; } \
}
# Fake logfile, to access the global log
define Logfile FileLog fhem-%Y-%m.log fakelog
--
You received this message because you are subscribed to the Google Groups "FHEM users" 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.
Originally posted by: <email address deleted>
I don't get it I defined a CUL device upfront but it keeps on saying
"No I/O device found for Balkon"..
--
You received this message because you are subscribed to the Google Groups "FHEM users" 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.
On Fri, Feb 12, 2010 at 08:17:42AM -0800, Zaleo wrote:
> I don't get it I defined a CUL device upfront but it keeps on saying
> "No I/O device found for Balkon"..
Most probably your 00_CUL.pm is out of date. Could you please verify that the
Client entry in 00_CUL.pm/CUL_Initialize() contains CUL_FHTTK?
--
You received this message because you are subscribed to the Google Groups "FHEM users" 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.
Originally posted by: <email address deleted>
On 13 feb, 18:32, Rudolf Koenig wrote:
> On Fri, Feb 12, 2010 at 08:17:42AM -0800, Zaleo wrote:
> > I don't get it I defined a CUL device upfront but it keeps on saying
> > "No I/O device found for Balkon"..
>
> Most probably your 00_CUL.pm is out of date. Could you please verify that the
> Client entry in 00_CUL.pm/CUL_Initialize() contains CUL_FHTTK?
I removed all files in this folder and did do the make install-pgm2
from the last CVS.
Part of my /usr/local/lib/FHEM/00_CUL.pm file :
CUL_Initialize($)
{
my ($hash) = @_;
# Provider
$hash->{ReadFn} = "CUL_Read";
$hash->{WriteFn} = "CUL_Write";
$hash->{Clients} =
":FS20:FHT:KS300:CUL_EM:CUL_WS:USF1000:HMS:CUL_FHTTK:CUL_RFR:FHT8V:";
my %mc = (
"1:USF1000" => "^81..(04|0c)..0101a001a5ceaa00....",
"2:FS20" => "^81..(04|0c)..0101a001",
"3:FHT" => "^81..(04|09|0d)..(0909a001|83098301|
c409c401)..",
"4:KS300" => "^810d04..4027a001",
"5:CUL_WS" => "^K.....",
"6:CUL_EM" => "^E0.................\$",
"7:HMS" => "^810e04....(1|5|9).a001",
"8:CUL_FHTTK" => "^T........",
"9:CUL_RFR" => "^[0-9A-F]{4}U.",
);
$hash->{MatchList} = \%mc;
$hash->{ReadyFn} = "CUL_Ready";
# Normal devices
$hash->{DefFn} = "CUL_Define";
$hash->{UndefFn} = "CUL_Undef";
$hash->{GetFn} = "CUL_Get";
$hash->{SetFn} = "CUL_Set";
$hash->{StateFn} = "CUL_SetState";
$hash->{AttrList}= "do_not_notify:1,0 dummy:1,0 " .
"showtime:1,0 model:CUL,CUN,CUR loglevel:
0,1,2,3,4,5,6 " .
"fhtsoftbuffer:1,0";
$hash->{ShutdownFn} = "CUL_Shutdown";
}
--
You received this message because you are subscribed to the Google Groups "FHEM users" 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.