jamarju / livolo-firmware Goto Github PK

Hello Jamarju

Is it possible to change the code that the relays no longer switch but only make a short pulse ?
Unfortunately, I am not so experienced in the programming of the PIC

I just wanted to say thanks for doing all the investigation on the light switches.

It did a similar project for the Livolo thermostats https://github.com/tobiaswaldvogel/livolo-thermostat and now I'm also considering writing a new firmware for the Zigbee version of the Livolo Light switches, which is also totally buggy and does not work with any standard Zigbee product.
Another issue I noted with the 2 gang version is, that the sensitivity of the 2nd sensor is very bad. You have to touch exactly the center and preferably with the thumb, whereas the 1st one work just fine. So the idea is to fix this as well.

You documentation is a really great help for getting started.
One thing I wanted to ask is, how you did the debugging. For the thermostat I didn't want to unsold the PIC and use a debug header, because it is easy to break some of the SMD pins. I just used the display for debug output (e.g. display a 4 digit hex as 4 decimal numbers from 0 to 15, one after each other).
Probably the easiest way for the switches (at least for the Zigbee part) is just powering the board from the PICkit and use your UART bit-bang code on RB4 for debug output. I guess.

I know that this project is for VL-C701X-2 VER: C0 (1-gang, 1-way, no RF, EU version) version but i'm raising this issues as i have a different board and i think that we can help people with different hardware types from Livolo, in the future as we can use this issue also as a guide. I tried to buy that version but it wasn't available so i got he VL-C601-2 (1-gang, 1 way).

The issue that i'm facing at the moment is that the Blue led is always On.

Question 1: How do i change what led is on and what led is off. I already took a look at the PCI 16f690 and i can see that the blue led is connected to Pin 13 (RB4/AN10/SDI/SDA). I will try to draw a circuit diagram and update this issue later.

Question 2: For my project i don't plan to use the 220v part at all, all i want is to have it powered up and communicating with either a nodeMCU (esp8266) or an arduino mini. My second question is, what and how should i detect from the switch that the state of the switch has changed. I tried to connect the RF Tx and Rx pins to the Arduino and opened up a serial port with a 57600 baudrate and Serial.read(); in the loop() method, but all i got were special characters (like a sqare, romb and other symbols that don't mean anything) and i couldn't read or understand anything from it. Show what should i expect to be delivered on the Serial ?

*** Update 1 *** : I have tried to reproduce the diagram of VL-C601-2 with as much detail as i could.
I attached a picture of the diagram here(Please note that it might be incorrect and i might need a second look at the wires.).

For me it makes no sense on how the LED should operate, and furthermore how can i adapt your code to work with the 2 LEDs (i can power them from an Arduino if needed).

(However, i understand now why the Blue LED is always powered on when i power the board from the PICKIT3 using J5 RF connector)

Thanks.

Hi,

I have loaded the project and when i tried to compile i got the error: In file included from uart.c:4:
./uart.h:15:1: error: unknown type name 'bit'

I'm using MPLAB X IDE 5.05 with XC8 installed.

what could be the issue here?

*** Update ***
I found the problem. The C Standard setting in XC8 Global options was set to C99. Moved it to C90 and it works perfectly. Now my only problem is that when i want to program the livolo switch, i get the error: "Cannot program a production build to a debug header." .. Hmm i need to do more digging...

*** Update 2 ***
The problem was occuring because the debug header was enabled in my config. I disabled it by going to Project Properties -> Configuration -> Under "Supported Debug Header" I selected "None".
-> Make and Program device and everything was ok.

This issue can now be closed as the programming works fine. I will open another issue with another problem i'm facing after flash, in the hopes of also helping other people in the future.

Thanks,
Regards.