Originally posted by: <email address deleted>
Hi - I'm hoping someone can help me.
I've recently installed FHEM on a Linux server along with with a
CC1101 configured with CUL v3.
Following the instructions online, it correctly sees my FHT-80B (v3)
and its able to remote set temperatures.
Is there any need to change the housecode for the CUL? (define CUL_0
CUL /dev/ttyACM0@9600 5555)
I thought this might be necessary for security purposes? however only
appears to communicate correctly with the FHT_80B if its set to 1234.
Cheers for any help you can give.
CP.
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Originally posted by: <email address deleted>
Little help please ;)
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Originally posted by: <email address deleted>
Hi,
would like to help, but can't remember quite well.
There have been discussions around the FHT-ID which is the 'housecode' you
set for the CUL (check here)
. This needs to be any but 0000, as 0000 means 'no FHT communication'.
The FHT-device should be defined automatically by autocreate, so no need to
bother with the ID stated in the define statement.
I'm not sure about any dependency between the FHT-ID declared on the
CUL-definition vs. the FHT-ID declared in the FHT define statement.
Maybe someone else can shed a light on this :)
Best, Uli
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Changing the FHT-ID to something different is not such a bad idea,
just in case your neighbor uses the same default... not very likely
though.
If you change the FHT-ID (aka FHT houscode) you need to repair the
FHT80 with the CUL. At the FHT80B go to the config menu and there
select CENT. Change it from "ON" to "n/a" and then send a command to
the FHT (set desired temp or anything else). That re-pairs the FHT
with the CUL to the new FHTID.
If you don't do that you can read the FHT's temp etc, but you cannot
controll the FHT.
On 23 Apr., 22:14, UliM
wrote:
> Hi,
> would like to help, but can't remember quite well.
> There have been discussions around the FHT-ID which is the 'housecode' you
> set for the CUL (check here)
> . This needs to be any but 0000, as 0000 means 'no FHT communication'.
> The FHT-device should be defined automatically by autocreate, so no need to
> bother with the ID stated in the define statement.
>
> I'm not sure about any dependency between the FHT-ID declared on the
> CUL-definition vs. the FHT-ID declared in the FHT define statement.
> Maybe someone else can shed a light on this :)
> Best, Uli
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
BTW:
> I'm not sure about any dependency between the FHT-ID declared on the
> CUL-definition vs. the FHT-ID declared in the FHT define statement.
There is none.
They are 2 parts of the overall addresscheme which consists of
1.
FHT-ID identifing the central radio interface the FHT is paired to
(such as CUL, CUN, FHZ1X00 PC or FHZ1000) and
2. each individuals FHT80's address.
So the "FHT-ID" declared in the FHT define statement is not the FHT-ID
but simply the FHT's address, which needs to correspond with the
address selected at the FHT device itself. In contrast to that you
cannot set the FHT-ID at the FHT80 itself; it only learns it while
pairing with the first Central-Device/Radio Adapter sending a command
after putting the FHT80 into pairing mode (CENT = N/A).
This is important if you use more then one radio adapter, such as a
CUL and a RFR CUL:
You cannot just interchange them between the 2 CULs f.e. by using
IOdev, you also need to unpair an repair them.
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Originally posted by: <email address deleted>
Sorry for not replying to this thread sooner, I've had some strange
issues after re-paring the FHT80b with the CUL where FHEM would
randomly change the desired temperature after setting it via the web
interface.
However that seems to have been sorted now after a clean up of the
config file.
Thanks to Zrrronggg! for being spot on with his advice and my
apologies for not being clear with the title of the post.
CP
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
> ... I've had some strange
> issues after re-paring the FHT80b with the CUL where FHEM would
> randomly change the desired temperature after setting it via the web
> interface.
Please note, that any changes are transmitted to the FHT only aprox.
all 2 Minutes, if everything goes well! If there are radio-problems it
even may take 2-3 attempts, this 4 or 6 Minutes.
So if you - to check the pairing - do some "test changes" they pile up
in the buffer of your CUL. Assuming you are a bit impatient, and
change temp say half a dozen times, it may take up 30 Minutes till the
last change is actually sent.
This may look like "I just changed to 23 degree, why does the FHT now
change to 12?" (Because you told fhem to change the FHTs temp to 12
about 20 Minutes ago...)
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com