• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[solved] kwmobile: repeating the remote signal doesn't work
#1
Hi,

I have a working setup with at least two different switch vendors already.
Now i bought a set from kwmobile (remote, 2xE27, 3xSwitch) and it behaves strange.
With my pilight-usb-nano I recorded switch 1 turning on multiple times:

Code:
c:1111111212121212112211223;p:120,560,220,5320@
c:1111111212121212112211223;p:130,550,210,5320@
c:1111111212121212112211223;p:130,550,200,5330@
c:1111111212121212112211223;p:130,550,210,5320@
c:1111111212121212112211223;p:140,540,220,5310@
c:1111111212121212112211223;p:110,570,240,5340@
c:1111111212121212112211223;p:130,550,210,5310@



Now, when I repeat that by sending one of those codes or a "normalized one" to my pilight-usb-nano, e.g.:

Code:
c:1111111212121212112211223;p:130,550,210,5320;r:16@
or
c:1111111212121212112211223;p:100,600,200,5300;r:16@



It simply doesn't work...
Any idea what the problem might be?

(I made sure, that if I send known codes of other switch vendors I use, it works)
 
Reply
#2
Start by using code tags.
 
Reply
#3
The output of sudo ./pilight-raw -L is:


Code:
433nano: 160 520 160 520 160 520 160 520 160 520 160 520 160 520 160 200 160 520 160 200 160 520 160 200 160 520 160 200 160 520 160 200 160 520 160 520 160 200 160 200 160 520 160 520 160 200 160 200 160 5300 -# 49
433nano: 160 520 160 520 160 520 160 520 160 520 160 520 160 520 160 220 160 520 160 220 160 520 160 220 160 520 160 220 160 520 160 160 160 520 160 520 160 220 160 220 160 520 160 520 160 220 160 220 160 5310 -# 49
433nano: 130 550 130 550 130 550 130 550 130 550 130 550 130 550 130 130 130 550 130 130 130 550 130 200 130 550 130 200 130 550 130 200 130 550 130 550 130 200 130 200 130 550 130 550 130 200 130 200 130 5320 -# 49
433nano: 170 520 170 520 170 520 170 520 170 520 170 520 170 520 170 170 170 520 170 170 170 520 170 200 170 520 170 170 170 520 170 200 170 520 170 520 170 200 170 200 170 520 170 520 170 200 170 200 170 5300 -# 49
433nano: 160 520 160 520 160 520 160 520 160 520 160 520 160 520 160 200 160 520 160 200 160 520 160 200 160 520 160 200 160 520 160 200 160 520 160 520 160 200 160 200 160 520 160 520 160 200 160 200 160 5320 -# 49
 
Reply
#4
Have you tried sending the raw codes using pilight-send?
 
Reply
#5
I did, doesn't work...
pilight-receive says it is the impulse protocol, but using that also doesn't work...
 
Reply
#6
Can you try connecting the sender and receiver directly to the pi?
 
Reply
#7
I'd really like to fix that in SW...
So I had a look at the firmware of the pilight-usb-nano (which i proudly bought in the pilight shop 2016)
I lowered MIN_PULSELENGTH and gave the device different parameters via the serial interface for minrawlen, maxrawlen, mingaplen and maxgaplen
It seems to come down to the mentioned codes from #1 after all
Any thoughts?
 
Reply
#8
No, have you tried my suggestion?
 
Reply
#9
(10-12-2018, 07:44 PM)curlymo Wrote: No, have you tried my suggestion?

Sorry, it took me a while to find time to resolder it. I now have it working on a Odroid-C2 and those codes seem to work to turn Unit 1 on:

Code:
pilight-send -p raw -c "254 424 275 412 259 423 256 424 265 419 251 432 256 427 553 126 250 434 556 124 253 429 554 130 247 437 551 131 245 437 552 131 250 431 265 418 559 121 541 149 238 440 255 424 554 130 535 149 241 5212"
pilight-send -p raw -c "236 444 249 433 255 428 244 440 248 432 257 424 256 418 560 136 270 406 551 132 240 442 550 134 243 439 544 141 235 442 553 133 240 442 242 442 548 138 529 151 226 457 248 431 553 132 531 154 222 5233"
pilight-send -p raw -c "226 459 247 432 247 433 243 439 238 443 255 428 241 443 573 109 233 450 578 101 240 444 568 119 228 452 576 104 236 449 557 127 219 459 242 442 566 119 555 130 216 463 243 438 573 111 547 140 225 5225"
pilight-send -p raw -c "230 446 244 436 248 435 247 436 247 435 238 443 236 446 569 111 241 447 552 129 236 450 550 130 226 453 548 136 232 447 558 130 225 455 242 438 566 116 548 141 217 460 243 445 555 125 339 29 159 167 213 5228"
(the last one confuses me)

Is there an easy way to convert those to pulsetrains?
Do you think those as pulsetrains will work with the pilight-usb-nano?
 
Reply
#10
(10-25-2018, 01:11 PM)dawncrow Wrote: Do you think those as pulsetrains will work with the pilight-usb-nano?

UPDATE: It works Smile

(10-25-2018, 01:11 PM)dawncrow Wrote: Is there an easy way to convert those to pulsetrains?

Still that would be a cool tool, I simply did it by hand for now for those I use
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  Solved - On / Off Command is the same command tigrablue 11 315 07-23-2019, 11:24 AM
Last Post: curlymo
  Remote with two crystals 10.000mhz and 7.3728 MSTNGSPRTS 0 125 04-18-2019, 10:33 PM
Last Post: MSTNGSPRTS
  Plug not acting upon signal tulamidan 18 1,007 12-22-2018, 12:15 PM
Last Post: curlymo
  pilight v8.0 - Current work in progress curlymo 32 25,088 12-06-2018, 10:06 PM
Last Post: curlymo
Exclamation Brennenstuhl 433MHz RC C1 - pilight not work pitje87 0 504 10-31-2018, 12:38 PM
Last Post: pitje87
  ["SOLVED"] Not able to control intertechno ITR-1500 Kambaramba 12 1,337 10-03-2018, 05:52 PM
Last Post: curlymo
  [solved] raw and debug Traeumer 2 450 09-27-2018, 09:43 PM
Last Post: Traeumer
  [SOLVED] Home Assistant switch gpio segalion 5 704 09-10-2018, 12:39 PM
Last Post: segalion
  smtp / solved Traeumer 7 609 08-21-2018, 08:47 PM
Last Post: curlymo
  [SOLVED] pilight wont start since update from 8.0.8 to 8.1.2 pukington 5 1,332 08-08-2018, 05:34 PM
Last Post: curlymo

Forum Jump:


Browsing: 1 Guest(s)