• 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


[Fully Supported] Arctech Old
#11
I need to hold the button but then I get this data, and then deamon quits.

Code:
[Aug 13 23:11:40] pilight-daemon: DEBUG: called archtech_old parseRaw()


378 1052 387 1044 1095 335 406 1050 379 1054 385 1046 1095 360 363 1071 375 1058 384 1050 377 1062 376 1061 379 1052 383 1048 377 1068 372 1066 373 1063 378 1059 1076 359 372 1068 1081 363 374 1052 1095 340 386 11358

[Aug 13 23:11:40] pilight-daemon: DEBUG: socket write succeeded: {"code":null,"origin":"receiver","protocol":"archtech_old"}

[Aug 13 23:11:40] pilight-daemon: DEBUG: socket write succeeded: {"code":null,"origin":"receiver","protocol":"sartano"}

[Aug 13 23:11:40] pilight-daemon: DEBUG: called archtech_old parseRaw()


383 1072 355 1059 1091 358 371 1060 385 1067 376 1049 1095 362 341 1091 373 1050 372 1064 388 1046 403 1035 393 1036 368 1072 364 1076 387 1048 373 1056 373 1086 1085 324 401 1076 1074 340 378 1061 1078 358 365 11354

[Aug 13 23:11:40] pilight-daemon: DEBUG: default freq of the lirc_rpi module set
[Aug 13 23:11:40] pilight-daemon: DEBUG: deinitialized lirc_rpi module
[Aug 13 23:11:40] pilight-daemon: DEBUG: removed stale pid_file /var/run/pilight.pid
 
Reply
#12
Can you try the latest code from git?
 
Reply
#13
I think it is going the right way. I see a diverence now on every key:

Code:
[Aug 14 21:28:57] pilight-daemon: DEBUG: called archtech_old parseBinary()
[Aug 14 21:28:57] pilight-daemon: DEBUG: socket write succeeded: {"code":{"id":15,"unit":21,"state":"on"},"origin":"receiver","protocol":"archtech_old"}

[Aug 14 21:28:57] pilight-daemon: DEBUG: socket write succeeded: {"code":{"id":15,"unit":21,"state":"on"},"origin":"receiver","protocol":"sartano"}

[Aug 14 21:29:03] pilight-daemon: DEBUG: called archtech_old parseBinary()
[Aug 14 21:29:03] pilight-daemon: DEBUG: socket write succeeded: {"code":{"id":15,"unit":21,"state":"off"},"origin":"receiver","protocol":"archtech_old"}

[Aug 14 21:29:03] pilight-daemon: DEBUG: socket write succeeded: {"code":{"id":15,"unit":21,"state":"off"},"origin":"receiver","protocol":"sartano"}

This is turning the first unit off and on again with the remote. I'm not sure how I need to read it. Because the old kaku works with a home code (A to O). I use as home code 'K'.

K 1 = "id":15,"unit":21
K 2 = "id":15,"unit":5
K 3 = "id":14,"unit":21
K 4 = "id":14,"unit":5
K 5 = "id":13,"unit":21

I think you know what K 6 is Smile

I also see that the state is switched. When I turn on pilight says off.

I think it can't recieve if the homecode on the remote is changed. Here I have a pilight-learn output for homecode L:

Code:
header:         4
pulse:          4
footer:         39
rawLength:      50
binaryLength:   12

on-off bit(s):  11
all bit(s):
unit bit(s):    4 5 6 7

Raw code:
295 1180 1180 295 295 885 1180 295 295 1180 295 885 295 885 1180 295 295 1180 1180 295 295 1180 1180 295 295 1180 1180 295 295 1180 1180 295 295 1180 295 1180 295 1180 1180 295 295 1180 1180 295 295 1180 1180 295 295 11505
Raw simplified:
On:     01100110010101100101010101010101010101100110011001
Off:    01100110010101100101010101010101010101100110011001
All:    01100110010101100100010001000100010101100110011001
Unit 1: 01100110010101100101010101010101010101100110011001
Unit 2: 01100110010101100110010101010101010101100110011001
Unit 3: 01100110010101100110011001100110010101100110011001
Binary code:
On:     001011111000
Off:    001011111001
All:    001000001000
Unit 1: 001011111000
Unit 2: 001001111000
Unit 3: 001000001000
 
Reply
#14
I fixed the swapped state issue. So that should be ok now. Can you also tell me if controlling these switches work with the pilight-send?
 
Reply
#15
I tried it. but looks like my transmitter does not work right. I have the one that you say not to buy. I think I have to wait for the new one before I can test it right. It also does not work with raw send. I will come back to you as soon I have it Smile

(I hope this weekend, if not then next weekend)
 
Reply
#16
There is only a wrong receiver, not necessarily a wrong sender. Please check your connections to try if sending raw codes works.
 
Reply
#17
Hmm ok, Then I hope this does not have effect on the code that is recieving? I've tried 2 different recievers.

it is just connect the data pin of transmitter direct to gpio? and 5v and GND to the right pins? I will try again this evening.
 
Reply
#18
Not quiet sure what your saying here Smile
 
Reply
#19
I know my english is not very good Tongue

I mean you can directly connect the data of the transmitter pin to the GPIO pin? 17 I believe. Or 18? OR do I need to add something between it?
 
Reply
#20
Receiver 18
Sender 17

And yes, they both can be connected directly.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
Lightbulb [Fully Supported] Kaku Door sensor (AMST-606) geerttttt 54 23,882 10-19-2019, 06:26 PM
Last Post: curlymo
  [Partially Supported] TFA / Conrad Weather Yves 184 10,304 03-31-2019, 05:22 PM
Last Post: curlymo
  [Fully Supported] DHT22 IcedEarth 86 31,084 11-18-2018, 09:33 AM
Last Post: curlymo
  Switch Mumbi m-FS300 display as arctech-switch Rschnauzer 7 1,257 03-24-2018, 07:13 PM
Last Post: Rschnauzer
  [Fully Supported] Clarus Switches Marcin 69 23,953 01-30-2018, 07:10 PM
Last Post: Niek
  [Fully Supported] Remote Control Socket (RC101-U/RC201) Sean 18 10,501 01-04-2018, 06:18 AM
Last Post: ettman8
  [Fully Supported] LM75 and LM76 temperature sensor horst_dieter 64 24,751 11-19-2017, 08:54 PM
Last Post: edepi
  [Fully Supported] No-brand temp/humidity sensor (alecto_ws1700) meloen 57 34,838 12-25-2016, 09:53 PM
Last Post: creamers
  [Fully Supported] Impuls/SelectRemote Bram 113 46,987 05-28-2016, 02:53 PM
Last Post: Puuu
  [Fully Supported] KAKU ABST-604 (dusk/dawn sensor) Netopyr 15 7,585 03-04-2016, 05:43 PM
Last Post: Niek

Forum Jump:


Browsing: 1 Guest(s)