Struggling with node-red-contrib-rfxcom with Cotech SmartHome series devices (PT2262)

487 views
Skip to first unread message

Mark Setrem

unread,
Oct 4, 2015, 5:27:04 PM10/4/15
to Node-RED

I saw that Clas Ohlson has launched a new series of SmartHome devices, e.g.:


The descriptions say they are compatible with TellStick Net gateway so they "should" be compatible with the rfxtrx433.

I've paired the remote control with the dimmer switch and its worked, and using the PT2262-In node I can receive  the following

[Press "On" ] : { "status": { "rssi": 5 }, "raw": { "data": "0xBB92AC", "pulseWidth": 394 }, "_msgid": "55eb4bc6.aa14b4" } 
[Press "Off" ] :{ "status": { "rssi": 5 }, "raw": { "data": "0xB0ECBC", "pulseWidth": 384 }, "_msgid": "c5241264.3adbf" }

But I'm struggling to understand the terminology of the rfxcom nodes to configure to PT2262-Out nodes.

what is the address?  
If I configure it to "get address from message topic"
and configure 

a device:

setting up a message with the topic and payload isn't triggering the light.  


I've got a funny feeling I'm missing something obvious but for the life of me I cannot see it!








 

Mike Biddell

unread,
Oct 4, 2015, 6:08:37 PM10/4/15
to Node-RED
Mark

I use PT2262 a lot. Your code for OFF is wrong, but as far as I can see that shud work. The only difference between my flows and yours is that my topic is "PT2262" and my payloads are like "switch ON" and "switch OFF". The code matches the topic and payload in the table and sends the corresponding code !!! The only difference is the slash in your topic.... shouldn't make a difference should it?????

mike

Walter Kraembring

unread,
Oct 4, 2015, 11:55:21 PM10/4/15
to Node-RED
 

Have you tried a different pulse width? I think 350 micro sec is some kind of 'default' 

What firmware version do you have?
Do you have the RFXtrx433E?

I know, maybe bad taste, but have you tested it also in Windows with the RFXmngr?

Max Hadley

unread,
Oct 5, 2015, 2:08:48 AM10/5/15
to Node-RED
What firmware is your RFXtrx433 running? I think Bert has recently fixed a bug in reporting the pulse width that I work round in the node, so the reported value may now be out by a factor of 4. I'm hoping to give the code a going over, now the nights are drawing in.

Max

Mark Setrem

unread,
Oct 7, 2015, 12:38:50 PM10/7/15
to Node-RED

Many thanks for the suggestions & replies.

I've got a RFXtrx433 , not the RFXtrx433, but as far as I'm aware that shouldn't make any difference as I thought there was only 1 protocol the E can handle that the original can't?

I'm running the v92Type1 firmware. For each of the codes I have tried I've used the pulse timing that came from the recording.

And yep in tidying up the post I changed the off value but neither of them work!

When I press the same button on remote switch more than once I get a different code generated with a different pulse timing.  Entering them into the node and trying immediately after receiving a signal from the remote (which worked) the RFXtrx sent code then doesn't work.
I Emailed Clas Ohlson to see if i could get more details of what protocol it uses and received the less than helpful response of "The manufacturer will not provide information about which protocol it usesHowever, it is compatible with Tellstick and Zipabox." especially as its their own make!
I've found Clas Olson to be good at responding to "geeky" queries before.

The next thing to try will be as Walter suggested to try from within RFXmngr.  I'll update this thread when I've had time to move the kit closer to the PC ;-)



 






Max Hadley

unread,
Oct 7, 2015, 3:13:56 PM10/7/15
to Node-RED


On Wednesday, 7 October 2015 17:38:50 UTC+1, Mark Setrem wrote:

When I press the same button on remote switch more than once I get a different code generated with a different pulse timing.  Entering them into the node and trying immediately after receiving a signal from the remote (which worked) the RFXtrx sent code then doesn't work.

Are the pulse timings much different? If they are greatly different it's probably not really PT2262 compatible. if they are close (1 or 2 different) but the data words change, it may be a 'code hopping' type controller, but I VERY much doubt that for the money. I don't see any reference to CO/TECH in the RFXtrx user manual, so you may be out of luck, and it's not really a PT2262-alike at all.

As far as I know, the Tellstick is just another brand of 'universal' 433MHz transceiver, so it may well support devices the RFXtrx doesn't (and vice-versa). Have you tried emailing Bert at sup...@rfxcom.com?

Cheers
Max

Mark Setrem

unread,
Oct 7, 2015, 4:00:23 PM10/7/15
to Node-RED
No the pulse value changes by 20-30

I've also found an article on the telldus forum from someone who can't get it to work with the Tellstick either!
http://www.telldus.com/forum/viewtopic.php?f=2&t=5515 (in Swedish).

I think I'll be returning them tomorrow.

Mike Biddell

unread,
Oct 8, 2015, 5:24:30 AM10/8/15
to Node-RED
For ages I have been thinking about the possibility of actually recording any code, regardless of its protocol and re-transmitting it.
Bit bang the receive GPIO or USB at full tilt CPU and record the logic level in contiguous RAM locations. So a single logic 1 could occupy numerous RAM locations. In effect you would have a sort of running representation of a binary code. Then play it back at the same speed and this method should override any and all protocols ???? Obviously only change the output if the logic level changes 0 to 1, or 1 to 0.

Would this be the esperanto work for all protocols apart from rolling??

What am I rambling on about? Answers on a postcard.

mike
Reply all
Reply to author
Forward
0 new messages