• 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
KaKu ATMT-502 remote & pilight?
#1
Hello all,

Recently I've acquired a 433Mhz sender / receiver kit from the pilight store. I've attached these to an Arduino for LPF and all seems to be fine. I can receiver signals from a number of KaKu remotes, except for the ATMT-502 unit, which I basically use all the time

As the remote seems to be fine (it does toggle my KaKu switches) and pilight responds just fine to all other remotes, I'm a bit at a loss here.

pilight-raw seems to be able to data from the KaKu remote pass by:
Code:
 433nano: 230 2640 230 230 230 1330 230 300 230 1330 230 1330 230 230 230 230 230 1330 230 300 230 1330 230 300 230 1330 230 1330 230 300 230 1330 230 230 230 1330 230 300 230 300 230 1330 230 1330 230 300 230 1330 230 300 230 1330 230 300 230 300 230 1330 230 300 230 1330 230 300 230 1330 230 1330 230 300 230 1330 230 300 230 1330 230 300 230 300 230 1330 230 1330 230 300 230 300 230 1330 230 1330 230 300 230 1330 230 300 230 1330 230 300 230 300 230 1330 230 300 230 1330 230 300 230 1330 230 300 230 1330 230 1330 230 300 230 1330 230 300 230 300 230 1330 230 8640 -# 131
 433nano: 200 2650 200 310 200 1350 200 310 200 1350 200 1350 200 310 200 310 200 1350 200 310 200 1350 200 310 200 1350 200 1350 200 310 200 1350 200 310 200 1350 200 310 200 310 200 1350 200 1350 200 310 200 1350 200 310 200 1350 200 310 200 310 200 1350 200 310 200 1350 200 310 200 1350 200 1350 200 310 200 1350 200 310 200 1350 200 310 200 310 200 1350 200 1350 200 310 200 310 200 1350 200 1350 200 310 200 1350 200 310 200 1350 200 310 200 310 200 1350 200 310 200 1350 200 310 200 1350 200 310 200 1350 200 1350 200 310 200 1350 200 310 200 310 200 1350 200 8640 -# 131

What am I missing here? pilight 7.0 is running on my RPi3
 
Reply
#2
I can decode this raw stream as:
Code:
{
        "message": {
                "id": 9364398,
                "unit": 6,
                "state": "off"
        },
        "origin": "receiver",
        "protocol": "arctech_switch",
        "uuid": "0000-b8-27-eb-a989a9",
        "repeats": 1
}
Are you using the stable or the nightly release of pilight ?
 
Reply
#3
(11-29-2016, 06:58 PM)wo_rasp Wrote: I can decode this raw stream as:
Code:
{
        "message": {
                "id": 9364398,
                "unit": 6,
                "state": "off"
        },
        "origin": "receiver",
        "protocol": "arctech_switch",
        "uuid": "0000-b8-27-eb-a989a9",
        "repeats": 1
}
Are you using the stable or the nightly release of pilight ?

I am using the latest stable release of pilight. Could you perhaps tell me how I could decode this myself? A test tells me you got this right, it's working light a charm!
 
Reply
#4
That is one of the benefits of the -L option with pilight-raw.
I use the complete set of raw pulses, copy them to the clipboard and paste it back into a "pilight-send -p raw -c "" command between the two "" characters ...
Depending on what I am looking for, i may change the value of the footer pulse (typically you will find them in the wiki), i may reduce the number of pulses, i may check the protocol for transmission errors (e.q. i replace invalid pulses with valid ones).

I am using my own version of pilight, supporting more protocols than the regular development branch (check in the wiki the section for the philipshue protocol, it has the link to my github repository) and I run the tests In this particular case, no changes were required.

Typically it is sufficient to use the pilight nightly.
 
Reply
#5
(11-29-2016, 11:43 PM)wo_rasp Wrote: That is one of the benefits of the -L option with pilight-raw.
I use the complete set of raw pulses, copy them to the clipboard and paste it back into a "pilight-send -p raw -c "" command between the two "" characters ...
Depending on what I am looking for, i may change the value of the footer pulse (typically you will find them in the wiki), i may reduce the number of pulses, i may check the protocol for transmission errors (e.q. i replace invalid pulses with valid ones).

I am using my own version of pilight, supporting more protocols than the regular development branch (check in the wiki the section for the philipshue protocol, it has the link to my github repository) and I run the tests In this particular case, no changes were required.

Typically it is sufficient to use the pilight nightly.

Thanks, that's some useful info there; I gave pilight-raw -L a try before, just not like this Smile
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  problem publish to pilight MQTT server Emiks5 5 1,333 03-18-2021, 07:23 PM
Last Post: Emiks5
  No output to GPIO using Kaku protocol's Klaas Jan 2 289 03-01-2021, 08:05 PM
Last Post: Klaas Jan
  Hardware Switch and pilight-send/-control iTommix 3 471 02-14-2021, 09:25 PM
Last Post: iTommix
  pilight error after update to 8.1.5 on Odroid C2 WitchDoctor 4 1,612 02-07-2021, 09:50 PM
Last Post: pilightalpine
  pilight in Docker not accepting connections due to possible SYN flooding akloeckner 3 381 02-07-2021, 04:22 PM
Last Post: akloeckner
  pilight-debug format Rschnauzer 2 413 12-17-2020, 07:09 PM
Last Post: Rschnauzer
  pilight-flash not working danny 14 3,150 12-12-2020, 10:00 AM
Last Post: tox
  pilight does not start, Deamon is not found. Dekkertje 6 685 12-08-2020, 06:55 PM
Last Post: Dekkertje
  Failed pilight-send that say they succeeded hepcat72 2 437 12-05-2020, 05:30 PM
Last Post: hepcat72
  apt.pilight.org/dists/stable/main/binary 301 Moved Permanently Rschnauzer 6 739 11-23-2020, 01:49 PM
Last Post: Rschnauzer

Forum Jump:


Browsing: 1 Guest(s)