RFXtrx

[b_weijenberg]

Correct, I have tested Blyss with GROUP code A to P and the Blyss modules operate with these codes.
The RFXtrx433 firmware accepts the code already.

[sebquid]

Hi Walter,

I tried the new version. Sending works fine but receiving doesn't. The same message: "Decoding of message failed.....".

Best regards,

Seb

[krambriw]

Embarrassing, try this version

__init__.py

(372.67 KiB) Downloaded 274 times

[sebquid]

Good news Walter,

It works perfectly now. I can receive events from the transmitter. That's great!!! I can play with scenarios now....
Thanks a lot for your time and commitment (also to Bert). If I can help for beta test or whatever let me know. I would be very happy.

Regards,

Sebastien

[krambriw]

Thanks, official version with the above features now posted in first post

[thebeetleuk]

Hi All,

I currently use a web base front end for sending commands to EventGhost which works great. Only thing is I've not tried much more then turning lights on and off via the actions. So its either set levels to 0 or 15. What I'd rather do is pass a variable to EventGhost from the web front end (lets say set 50% - value '7' for arguments sake and set the lights to that level) but I have no idea how to call use python to send a specific action to a device. Other than creating a new macro for every level (which is just madness) I wonder has anyone else done this?

Thanks in advance. Martin.

P.s. Just installed the latest update which looks good.

[krambriw]

Easiest would be to create a macro with a python script inside that evaluates your dim events that is being sent from the web page. The python script must be able to filter out and identify the device id and the required light level and then just simply send the corresponding RFXtrx command. Best is if you could provide the address (AC) of the device already in the event from the web page to avoid having to maintain a mapping table.

How does the event from your web page look like when it appears in EG?

BR Walter

[fred38]

Hi !

I have at home remote sockets brand Phenix. I am able to send a command from my rfxtrx433 to swith on & off the sockets using "lighting 4"

I am looking for the same 'lighting 4" mode in your plug in but don't find it. Does it exist ?

Thanks a lot for your help

[krambriw]

Sorry, no, the "lighting 4" is not yet supported, I'll look into that but be prepared to do some testing, I do not have those devices myself.

Please tell me about your devices:
- do you have a link (I do not find phenix)?
- how do you turn on/off the device???

[fred38]

Hi !

Thanks a lot for your answer.

In fact, I have 2 sets of remote sockets. The first one is a Phenix Brand, ref YS 4000S.
This is a link : http://www.cdiscount.com/maison/bricola ... 4000s.html
Sorry, it is in French but this is exactly what I have.

The 2 set is an Inspektor brand. Ref 250137. No link found.

They both run on the same coding system with a PT2262 decoder

This is the message printed by the rfxmngr when I send a command with the remote controller :

09130001000551015E70
Packettype = Lighting4
subtype = PT2262
Sequence nbr = 1
Code = 000551
S1- S24 = 0000 0000 0000 0101 0101 0001
Pulse = 350 usec
Signal level = 7

I have a remote controller with each set of sockets and it runs perferctly when a use the rfxtrx lighting 4 to send a command.

I am ready to do all the test needed.
Thanks for your help !
Fred

[krambriw]

Hi Fred, I think and I hope this one works,

Best regards, Walter

__init__.py

(385.94 KiB) Downloaded 283 times

[fred38]

Hi walter !

It seams it works great ! Just test it on the Phenix socket and it is perfect !

Thanks a lot ! How may I thank you ?

Best regards
Fred

[fred38]

Hi Walter,

I did some additional tests and it works well at 90%. One of my socket doesn't want to switch off with a RFX command coming from EG but it works to switch on. (Socket C)

I have notice that to sequence sent by EG is not exactly the than the remote controller. The code is respected but not all the sequence.

Do you have an idea why ?
Thanks !
Fred

Log in RFXmgnr Log in Eventghost Result

Socket A On 09 13 00 01 00 05 51 01 5E 70 09 13 00 00 00 05 51 01 5E 00 Ok
Packettype = Lighting4
subtype = PT2262
Sequence nbr = 1
Code = 000551
S1- S24 = 0000 0000 0000 0101 0101 0001
Pulse = 350 usec
Signal level = 7

OFF 09 13 00 01 00 05 54 01 5E 70 09 13 00 00 00 05 54 01 5E 00 Ok
Packettype = Lighting4
subtype = PT2262
Sequence nbr = 1
Code = 000554
S1- S24 = 0000 0000 0000 0101 0101 0100
Pulse = 350 usec
Signal level = 7

Socket B On 09 13 00 01 00 15 5F 01 5E 70 09 13 00 00 00 11 51 01 5E 00 Ok
Packettype = Lighting4
subtype = PT2262
Sequence nbr = 1
Code = 001151
S1- S24 = 0000 0000 0001 0001 0101 0001
Pulse = 350 usec
Signal level = 7

Off 09 13 00 01 00 11 54 01 5E 70 09 13 00 00 00 11 54 01 5E 00 Ok
Packettype = Lighting4
subtype = PT2262
Sequence nbr = 1
Code = 001154
S1- S24 = 0000 0000 0001 0001 0101 0100
Pulse = 350 usec
Signal level = 7

Socket C On 09 13 00 01 00 14 51 01 5E 70 09 13 00 00 00 14 51 01 5E 00 Ok
Packettype = Lighting4
subtype = PT2262
Sequence nbr = 1
Code = 001451
S1- S24 = 0000 0000 0001 0100 0101 0001
Pulse = 350 usec
Signal level = 7

Off 09 13 00 01 00 14 54 01 5E 70 09 13 00 00 00 14 51 01 5E 00 Not OK
Packettype = Lighting4 Works with the remote but not with the RFX
subtype = PT2262
Sequence nbr = 1
Code = 001454
S1- S24 = 0000 0000 0001 0100 0101 0100
Pulse = 350 usec
Signal level = 7

Socket D On 09 13 00 01 00 15 11 01 5E 70 09 13 00 00 00 15 11 01 5E 00 Ok
Packettype = Lighting4
subtype = PT2262
Sequence nbr = 1
Code = 001511
S1- S24 = 0000 0000 0001 0101 0001 0001
Pulse = 350 usec
Signal level = 7

Off 09 13 00 01 00 15 14 01 5E 70 09 13 00 00 00 15 14 01 5E 00 ok
Packettype = Lighting4
subtype = PT2262
Sequence nbr = 1
Code = 001514
S1- S24 = 0000 0000 0001 0101 0001 0100
Pulse = 350 usec
Signal level = 7

[krambriw]

Hi Fred, it looks as if I did not fully understand how the devices are working. When I look at your logs (from RFXmngr I assume) it seems that the difference between 'on' and 'off' commands are in the last command byte ( like 0101 0001 for 'on' and 0101 0100 for 'off'). In the version you have, I do not separate this so you have to create on action for 'on' and one for 'off' considering this.

When you control device C you can see a difference
Off 09 13 00 01 00 14 54 01 5E 70 09 13 00 00 00 14 51 01 5E 00 Not OK

RFXtrx is not sending 00 14 54, instead is sending 00 14 51 (the 'on' command instead of the 'off'). Did you really change the 'off' command configuration of S1- S24 correctly for 'off'?

Best regards, Walter

[fred38]

Hi Walter,

Thanks for your answer.

I have well change the sequence for On and for OFF. But is doesn't works just for socket C.

I have tried with another set of 3 sockets brand inspektor and this time 2 sockets are running well and the third one is not answering to an OFF command.

I think that it is only an issue with the devices and not your code.

I have also adapt a bit your code to obtain exactly the same sequence with eg or with rfxmngr (the beginning and the end were a bit different) but it doesn't work better.

I will use only the socket running well, don't worry !

I will keep you informed if I experienced others difficulties

Best regards
Fred