define TRX_LIGHT AC

[Guest]

Originally posted by: <email address deleted>

Hello,

I'm owning a rfxtrx433 and trying to define a TRX_LIGHT dimmer but ran
into some problems.

When I define it like the manual says it would be:
define light TRX_LIGHT AC A1 light
The item will be created in Fhem, but then doesn't work as it gives
back the error when i push on:
Error set name=light deviveid=a1

When i control the dimmer through the management software of rfxcom i
have to define the device with a different id like: 1 01 01 01 instead
of a1. Could this be the problem. Already try to define the device
with id's like that, but that doesn't work. Unfortunatelly.

Did make the dimmer work with the TRX_LIGHT ARC, but that i can only
set on / off and can't set the level.

Please advise what to do.

Regards,
Coennie

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

[Guest]

Originally posted by: <email address deleted>

Am Samstag, 12. Mai 2012 13:04:30 UTC+2 schrieb Coennie:
 

> Did make the dimmer work with the TRX_LIGHT ARC, but that i can only
> set on / off and can't set the level.
>
>
The firmware of TRX433 does not support dim for ARC. Thus dim is not
available for this protocol on my driver.


> When i control the dimmer through the management software of rfxcom i
> have to define the device with a different id like: 1 01 01 01 instead
> of a1. Could this be the problem. Already try to define the device
> with id's like that, but that doesn't work. Unfortunatelly.
>
>
If you have an Remote-Control for the AC protocol, everything should work
automatically using autocreate.
For AC, HomeEasy EU, ANSLUT you have to specify a 10 Byte HEX-String for
the deviceid, consisting of
- unid-id: 8 Byte Hex: 00000001 to 03FFFFFF
- unit-code: 2 Byte Hex: 01 to 10

Example:

define light TRX_LIGHT AC 0101010101 light

AC was recently added to my FHEM driver. I forgot to describe how to set
the deviceid for lighting2 protocols. I will add this soon to
commendref.html.

I do not have any AC devices to test. This I have tested it with dummy data.
If you have any problems, please try RFXmngr and tell me what parameters on
Lighting2 you used to get your devices work with RFXmngr. It would be also
good to know what hexstring is sent to TRX433 by RFXmngr.

With this information I can check if my implementation is correct.

Regards

Willi

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

[Guest]

Originally posted by: <email address deleted>

Hi Willi,

Thank you for your answer. I don't get any errors when using the
define string you send me, but I can't control the lights. I've
included a log file of the RFXcom manager where I received a thermo
device and controled the lights. I set the lightning with the
following data:

Type AC
ID 1 01 01 01
Unit code 1

I hope this will give you enough information. If there is anything I
can do please let me know.

Regards,
Coennie

###############

================================================
Reset receiver/transceiver:0D 00 00 00 00 00 00 00 00 00 00 00 00 00
================================================
Get Status:0D 00 00 01 02 00 00 00 00 00 00 00 00 00
------------------------------------------------
0D010001025327004E6F00000000
Packettype        = Interface Message
subtype           = Interface Response
Sequence nbr      = 1
response on cmnd  = Get Status
Transceiver type  = 433.92MHz
Firmware version  = 39
Undec             off
X10               enabled
ARC               enabled
AC                enabled
HomeEasy EU       enabled
Ikea Koppla       disabled
Oregon Scientific enabled
ATI               enabled
Visonic           disabled
Mertik            disabled
AD                enabled
Hideki            enabled
La Crosse         enabled
FS20              disabled
ProGuard          disabled
RFU protocol 7    disabled
Lighting2 command:0B 11 00 02 01 01 01 01 01 01 00 00
------------------------------------------------
0402010200
Packettype        = Receiver/Transmitter Message
subtype           = Transmitter Response
Sequence nbr      = 2
response          = ACK, data correct transmitted
------------------------------------------------
08500100040300AE49
Packettype    = TEMP
subtype       = TEMP1 - THR128/138, THC138
                channel 3
Sequence nbr  = 0
ID            = 1027
Temperature   = 17,4 °C
Signal level  = 4
Battery       = OK
Lighting2 command:0B 11 00 03 01 01 01 01 01 02 0F 00
------------------------------------------------
0402010300
Packettype        = Receiver/Transmitter Message
subtype           = Transmitter Response
Sequence nbr      = 3
response          = ACK, data correct transmitted
Lighting2 command:0B 11 00 04 01 01 01 01 01 02 09 00
------------------------------------------------
0402010400
Packettype        = Receiver/Transmitter Message
subtype           = Transmitter Response
Sequence nbr      = 4
response          = ACK, data correct transmitted
Lighting2 command:0B 11 00 05 01 01 01 01 01 02 02 00
------------------------------------------------
0402010500
Packettype        = Receiver/Transmitter Message
subtype           = Transmitter Response
Sequence nbr      = 5
response          = ACK, data correct transmitted
------------------------------------------------
08500101040300AF49
Packettype    = TEMP
subtype       = TEMP1 - THR128/138, THC138
                channel 3
Sequence nbr  = 1
ID            = 1027
Temperature   = 17,5 °C
Signal level  = 4
Battery       = OK
Lighting2 command:0B 11 00 06 01 01 01 01 01 02 04 00
------------------------------------------------
0402010600
Packettype        = Receiver/Transmitter Message
subtype           = Transmitter Response
Sequence nbr      = 6
response          = ACK, data correct transmitted
Lighting2 command:0B 11 00 07 01 01 01 01 01 02 0E 00
------------------------------------------------
0402010700
Packettype        = Receiver/Transmitter Message
subtype           = Transmitter Response
Sequence nbr      = 7
response          = ACK, data correct transmitted
------------------------------------------------
0B110002004B8B1A0A010F40
Packettype    = Lighting2
subtype       = AC
Sequence nbr  = 2
ID            = 04B8B1A
Unit          = 10
Command       = On
Signal level  = 4
------------------------------------------------
08500103040300B049
Packettype    = TEMP
subtype       = TEMP1 - THR128/138, THC138
                channel 3
Sequence nbr  = 3
ID            = 1027
Temperature   = 17,6 °C
Signal level  = 4
Battery       = OK
------------------------------------------------
08500104040300B049
Packettype    = TEMP
subtype       = TEMP1 - THR128/138, THC138
                channel 3
Sequence nbr  = 4
ID            = 1027
Temperature   = 17,6 °C
Signal level  = 4
Battery       = OK
------------------------------------------------
0B110005004B8B1A0A010F50
Packettype    = Lighting2
subtype       = AC
Sequence nbr  = 5
ID            = 04B8B1A
Unit          = 10
Command       = On
Signal level  = 5
------------------------------------------------
0B110006004B8B1A0A010F50
Packettype    = Lighting2
subtype       = AC
Sequence nbr  = 6
ID            = 04B8B1A
Unit          = 10
Command       = On
Signal level  = 5
------------------------------------------------
0B110007004B8B1A0A010F50
Packettype    = Lighting2
subtype       = AC
Sequence nbr  = 7
ID            = 04B8B1A
Unit          = 10
Command       = On
Signal level  = 5
------------------------------------------------
08500108040300B149
Packettype    = TEMP
subtype       = TEMP1 - THR128/138, THC138
                channel 3
Sequence nbr  = 8
ID            = 1027
Temperature   = 17,7 °C
Signal level  = 4
Battery       = OK

On 12 mei, 18:52, Willi wrote:
> Am Samstag, 12. Mai 2012 13:04:30 UTC+2 schrieb Coennie:
>
> > Did make the dimmer work with the TRX_LIGHT ARC, but that i can only
> > set on / off and can't set the level.
>
> The firmware of TRX433 does not support dim for ARC. Thus dim is not
> available for this protocol on my driver.
>
> > When i control the dimmer through the management software of rfxcom i
> > have to define the device with a different id like: 1 01 01 01 instead
> > of a1. Could this be the problem. Already try to define the device
> > with id's like that, but that doesn't work. Unfortunatelly.
>
> If you have an Remote-Control for the AC protocol, everything should work
> automatically using autocreate.
> For AC, HomeEasy EU, ANSLUT you have to specify a 10 Byte HEX-String for
> the deviceid, consisting of
> - unid-id: 8 Byte Hex: 00000001 to 03FFFFFF
> - unit-code: 2 Byte Hex: 01 to 10
>
> Example:
>
> define light TRX_LIGHT AC 0101010101 light
>
> AC was recently added to my FHEM driver. I forgot to describe how to set
> the deviceid for lighting2 protocols. I will add this soon to
> commendref.html.
>
> I do not have any AC devices to test. This I have tested it with dummy data.
> If you have any problems, please try RFXmngr and tell me what parameters on
> Lighting2 you used to get your devices work with RFXmngr. It would be also
> good to know what hexstring is sent to TRX433 by RFXmngr.
>
> With this information I can check if my implementation is correct.
>
> Regards
>
> Willi

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

[Guest]

Originally posted by: <email address deleted>

Hello Coennie,

thanks for the output of RFXmngr.

Your data says:
ID            = 04B8B1A
Unit          = 10
Unit 10 seems to be decimal, which is 0A hex.

Try the following define:

define light TRX_LIGHT AC  004B8B1A0A light

Regards

Willi

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

[Guest]

Originally posted by: <email address deleted>

Hi,

your seem to have two AC devices. I have overlooked the following:

Type AC
> ID 1 01 01 01
> Unit code 1
> ProGuard          disabled
> RFU protocol 7    disabled
> Lighting2 command:0B 11 00 02 01 01 01 01 01 01 00 00
>
>  
For this try:

define light TRX_LIGHT AC 0101010101 light

Regards

Willi

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

[Guest]

Originally posted by: <email address deleted>

Hello Coennie,

I haveverified my implementation.
There are some errors in setting up the right command. I am working to
solve it.

Regards

Willi

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

[Guest]

Originally posted by: <email address deleted>

Hello Coennie,

I have fixed some errors in 46_TRX_LIGHT.pm . Set for AC should (hopefully)
work now.

The new version is in FHEMs SVN now.

You may update tommorrow using updatefhem. I will also send you the fixed
version as a PM.

After this try to define

define light TRX_LIGHT AC 0101010101 light

Regards

Willi

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

[Guest]

Originally posted by: <email address deleted>

Hi Willi,

NICE!! It's now working including the set level function!

THNX


On 12 mei, 23:21, Willi wrote:
> Hello Coennie,
>
> I have fixed some errors in 46_TRX_LIGHT.pm . Set for AC should (hopefully)
> work now.
>
> The new version is in FHEMs SVN now.
>
> You may update tommorrow using updatefhem. I will also send you the fixed
> version as a PM.
>
> After this try to define
>
> define light TRX_LIGHT AC 0101010101 light
>
> Regards
>
> Willi

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

[Guest]

Originally posted by: <email address deleted>

Still a usefull old posting. It solved my issue.

 Just a small typo:

>  
> Error set name=light deviveid=a1
>
> should be deviceID (c instead off v) and maybe ID in capitals.

Thanks for the great work.

{HT}

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

[Guest]

Originally posted by: <email address deleted>

Am Freitag, 3. August 2012 15:40:23 UTC+2 schrieb dudler:
>
> Still a usefull old posting. It solved my issue.
>
>  Just a small typo:
>
>>  
>> Error set name=light deviveid=a1
>>
>> should be deviceID (c instead off v) and maybe ID in capitals.
>
>
>
Thanks for letting me know.

Typo corrected in SVN version.
 

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