I guess it is highly probable. At least, manual for VL-RMT-01 remote that I have says that buttons 7 (on), 9 (off), "+" (more light) and "-" (less light) can be used to control dimmer switch.
I don't have dimmer switches, that is why I have not scanned "+" and "-" buttons yet. I'm planning to do that this or next week, and after that you will be able to test dimmer feature.
Hi spch
Thanks for your reply.
I still cannot find new ID yet. For example, i use 6500 for ID which is 0001 1001 0110 0100. I though it follow your rule.
But it did not work either. Which pulse is not following your rule?
I understand that KOTI use FSK protocol. Still can decode?
I've just recorded what I believe are dimmer buttons. I have to sets of dimmer buttons (+/-) on the remote, and they have different keycodes. So here are both sets:
"+": 92 ; "-": 116
"+": 126; "-": 36
It's in the manual that I've found on the net that dimmer should be "paired" with buttons 7 and 9. Regretfully there is nothing on pairing and I don't have dimmer switch, so I can not test it.
winnaing,
It seems, you are right. Not all remote IDs are working. Sorry, I can not find the reason - it is really beyond my understanding. Maybe, I missed something or there is a bug in the code.
So there is a hit or miss approach: try different remote IDs to find ones that work. For example, I found that 7400, 6550, 10550 can be used with Livolo switches.
As to FSK, it is not really a protocol - it is method of modulation used to transmit data over RF. Basically it can be easily demodulated using FSK receiver (the same way as I demodulated Livolo's signal using ASK receiver). And there are two ways to use received data:
Try to "copy" code sequence without trying to understand underlying protocol;
Try to decode and use original protocol.
First will do if it is about fixed codes. Second is good to deal with fixed and dynamic codes, although to me dynamic codes are really hard to hack.
Hi spch
Thanks for new IDs.
As for FSK ; are you saying that it works with fsk receiver and will not work with ask receiver?
Then where can I find fsk receiver? It is like all arduino store sell ask receiver.
Just unzip Livolo folder under your Arduino/libraries folder, restart Arduino IDE if it was open at the moment, connect Arduino board with ASK RF transmitter to PC, upload test sketch and put your Livolo switch into learning mode.
If everything goes right, your light will turn on and off every 3 seconds. See readme.txt for more info.
Default TX pin is 8, but you can use any digital pin you like.
Hi spch
Thanks for the link. I have purchased the pair already.
Next, once I receive the switch and rf module, I try to decode them. If not successful, will shout for help.
Thanks for the library as well. I haven't tested yet, but should be fine. Well feedback to you after tested.
Sorry for previous message. I missed some pieces of code you wrote. I've just tested your code on Mega and it is working flawlessly.
I guess problem is in switch "pairing". Try clearing previous code from switch first. For example:
Hold switch button until it beeps twice
Release switch button
Hold switch button until it beeps once
Enter "1" in Arduino port monitor input field and press Enter (switch shoud beep and accept new button)
Enter "1" in Arduino port monitor input field and press Enter (switch should turn on)
In case switch still not responding, make sure you have right antenna (163 mm of wire soldered to transmitter) and that transmitter is quite close to switch (at least for testing).
I know that this is strictly an Arduino forum, but I am working on the same project a long time now to control my Livolo switches, but with a Raspberry pi instead. As far as now I have not managed to achieve it. Hopefully someone inside the forum can translate the already working code for Arduino and make it work on Raspberry pi. There are already some useful codes for Raspberry pi that control the GPIO and send pulses to them (RCSwitch-pi and wiringPi) but I can note make them work with Livolo. Thank you very much for your reading!
You are right, reading remote IDs with Audacity is an akward routine. And I did try to build a code to read remote IDs, but have not succeeded yet. What's more, I'm not really sure I can do it.
But I'll get back to it as soon as I have enough time.