Lanbon L8

[dgomes]

Figured I would start a thread to gather information about the Lanbon L8

• What GPIO controls the border leds ?

Pin	Type	Group	Default
26	Mood Red	1	Low
32	Mood Green	2	Low
33	Mood Blue	3	Low

• Can I run the L8 Panel detached from the relays?

Yes, you can connect a 5v power supply to the L8 female pin-header.

[fvanroie]

You should configure the gpios as:

Pin	Type	Group	Default
12	Relay	1	Low
14	Relay	2	Low
26	Mood Red	4	Low
27	Relay	3	Low
32	Mood Green	5	Low
33	Mood Blue	6	Low

Edit: added Relay GPIOs

The group can be another number, but they all need to be different.

[gerry49]

Just purchased a 3 relay L8 and have managed to get it to work through Homeassistant switching on and dimming lights. The one thing i cannot work out is how to switch the onboard relays. I have configured the GPIO's as above. I have a sample toggle switch configured on the L8 and the appropriate YAML in homeassistant to switch one of my Zwave relays. I also have a second toggle switch( copy of above) but i don't know how to configure this one to switch the onboard relay. Help would be greatly appreciated. Attached the config.yaml entry i am using.
congig.yaml.odt

[fvanroie]

Check out the example pages.jsonl here. You need to add the groupid attribute to the switch.

[gerry49]

Thanks for reply. I picked up the jsonl programming pretty quickly and can create the buttons etc. i see the relay buttons at the bottom on the example. The problem i have is is with the yaml programming in homeassistant. I assume by your reply that the attached yaml file is ok except i need to insert the group id attribute. What do i need to enter for the entity_id for a gpio output. apologies for being so thick but i am learning this on my own and this is the only part that i am having problems with. You help is most appreciated

[gerry49]

Hi Fvanroie,
My apologies for the previous email. I have just looked at the pages.jsonl for the second time and have seen the highlighted area. I have loaded it into the lanbon and it works. I can now see from the jsonl line how they work. I must pay more attention. Many thanks and once again i apologise for my error.

[Rumbaar]

Check out the example pages.jsonl here. You need to add the groupid attribute to the switch.

Thanks for all your work, just want to point out that that linked examples the bottom 'navigation' bar sample code (Page 0) appears to be incorrectly labelled as the 'relay buttton' area. This is where it might have caused some previous confusion.

[dgomes]

The panel has 5v and 3.3V pins, if one wishes to run the panel without the relays, do we need to provide the 2 voltages or 5v is enough ?

[fvanroie]

I have been able to run the display detached from a 5V power supply, so 3.3V is not needed as that voltage is produced by an onboard power regulator.

My guess is that when you supply 5V, there will automatically be 3.3V generated on the 3.3V pin but I have not measured if that is indeed the case.

[sachinsid]

Hi @fvanroie/ @dgomes , I have one relay of the Lanbon L8 (3 gang version) physically connected to a lightning circuit in my theatre room. Before I consider flashing it with custom firmware, I wanted to know if the custom firmware makes it possible to use the Lanbon in a complete detached mode - i.e seperate the switch on the HASwitchPlate firmware from the relay itself. I have a number of Shelley's in my house which provide this option.

I would like to then use HomeAssistatant to control the relays via MQTT and use the remaining switches to trigger other scenes in my theatre room. Would be good to know before I consider flashing as I'm unable to change the wiring of the relay to the lightning circuit myself as it is not legal for me to carry out electrical works without a license.

[dgomes]

That is the default behaviour of openHasp (detached)

[sachinsid]

Thank you for the quick reply. Just to reconfirm again pls - In order for the detached relay capability to work that I don’t need to provide a separate 5v or 3.3v power supply to the Lanbon display panel? (because I don’t have an easy way to do so without requiring an electrician)

[fvanroie]

I don't understand what you are asking or trying to do...
Please continue this discussion on Discord, and provide a diagram if possible to explain your setup.

[fvanroie]

Maybe also some info about flashing:

The RX, TX, IO0, GND and power pins are all broken out on the female pinheader.
Either supply 3.3V or 5V on the corresponding power pin, depending on the voltage supplied by the UART ttl (not both at the same time).
There is no RESET pin broken out, so you need to power-cycle the board to get into flash mode.

If all else fails, you can also solder the chip directly.

I just connected some breadboard wires into the lanbon connector and connected to my CH340 usb ttl esp-01 flasher tool. The pins are nicely marked so it was a breeze to flash the Lanbon L8.

[dgomes]

Very happy with this project, decided to contribute by creating https://github.com/dgomes/hasp-lvgl to ease the process of synchronising the plate with HA. Already working sensors and switches/lights

I'm aware of https://github.com/blakadder/hasplvgl-hablueprints but I find this approach more clean and straightforward

[blakadder]

Looks promising and simple! Keep up the work

[fvanroie]

Cool @dgomes I'm gonna try this out and report back!

[nagyrobi]

EXCELLENT!

[fvanroie]

In 0.4.0 you will be able to configure all gpio's at once using command:

config/gpio={"config":[2360346,2491680,2623009,2097420,2097678,2097947,0,0]}

[nagyrobi]

Any way to pre-configure the gpio's through user_config_override.h or platformio_override.ini or lanbon_l8.ini?

[nagyrobi]

Is there a limit on the WiFi password length? Mine has 63 chars.
L8 doesn't connect, keeps rebooting. In serial console I get:

[              3.014][81008/127816 36][56808/56996  1] HTTP: Started
[              3.300][81008/125908 35][56808/56996  1] WIFI: No Connection... retry 1
Prompt > 284 - 137.00
[              7.332][81008/127544 36][56808/56996  1] WIFI: Disconnected from MYAP (Reason: handshake timeout [15])
[              8.026][81008/127544 36][56808/56996  1] WIFI: No Connection... retry 3
Prompt > 281 - 141.00
[             13.026][81008/127544 36][56808/56996  1] WIFI: No Connection... retry 4
Prompt > 282 - 141.00
[             18.027][81008/127544 36][56808/56996  1] WIFI: No Connection... retry 5
Prompt > 282 - 142.00
[             23.029][81008/127544 36][56808/56996  1] WIFI: No Connection... retry 6
Prompt > 278 - 142.00
[             28.026][81008/127452 36][56808/56996  1] WIFI: No Connection... retry 7
Prompt > 279 - 142.00
[             33.024][81008/127452 36][56808/56996  1] WIFI: No Connection... retry 8
Prompt > 283 - 142.00
[             33.216][81008/127344 36][56808/56996  1] WIFI: Disconnected from MYAP (Reason: handshake failed [204])
[             38.028][81008/127152 36][56808/56996  1] WIFI: No Connection... retry 10
Prompt > 285 - 142.00
[             38.135][81008/127216 36][56808/56996  1] WIFI: Disconnected from MYAP (Reason: handshake timeout [15])
[             43.025][81008/127216 36][56808/56996  1] WIFI: No Connection... retry 12

[nagyrobi]

Submitted a PR for this as I'm not the only one affected.

[nagyrobi]

The problem is that build doesn't run for Lanbon L8.

[fvanroie]

The PR has been merged and I pinned the platform = espressif32@3.0.0 version, so it fits within the partition.
The new v3.1.0 release is a bit bigger and won't fit anymore.

[Kopetenti2001]

Yes, you'll have to adjust wifiPassword[32] and set it to wifiPassword[64].

Can you help me troubleshoot some L8 switches stuck on wifi reboot ?

[fvanroie]

Can you help me troubleshoot some L8 switches stuck on wifi reboot ?

Sure. What version of openHASP are you running? And what do you mean with stuck on wifi reboot?
If you are able to jump on the Discord channel that would help in troubleshooting the issue.

[fvanroie]

I started a page on https://haswitchplate.github.io/openHASP-docs/#devices/lanbon-l8/ to collect all the information for the Lanbon L8 device.
It's still lacking detailed information, but can serve as a starting point to add hasp-docs PRs :)

Once we're happy with the page, we can add it to the menu.

[dgomes]

I think its quite useful in the current version.

[nagyrobi]

Created a PR to add it to the TOC

[fvanroie]

The page has been added to the hasp-docs menu.

[fvanroie]

If anyone has a Lanbon L8-HD Dimmer, feel free to test the gpio-redesign branch. It contains a GPIO type of Serial Dimmer. Set GPIO12 to this type and test it after reboot.

[sleepypig2003]

I've just got a hold of a dimmer.
Is the gpio-redesign branch already integrated into 0.6.1 ?

It doesn't work for me (yet)

I tried to set the dimmer with GPIO pin 12 set to L8-HD (EU), normal, set to group 1

I added a button and a dimmer in pages.json to try it, both doesn't seem to change the dimmer voltage when toggled.

{"page":1,"id":2,"obj":"btn","groupid":1,"x":10,"y":40,"w":105,"h":90,"toggle":true,"text":"\uE335","text_font":32,"mode":"break","align":1}

{"page":5,"obj":"slider","id":46,"groupid":1,"x":20,"y":121,"w":200,"h":30,"bg_color":"#C7BAA7","border_color":"#C7BAA7","border_width":0,"radius":15,"radius1":15,"radius2":20,"text_font":1,"val":65,"bg_color1":"#FFAC00","bg_color2":"#DC5C05"}

[htvekov]

Hi' @fvanroie

Can't get the EU config to work here neither. No dimming or on/off at all.
But the AU config seems to work on my EU version L8-HD. I can dim (some) and turn off/on light completely.
What's the exact difference for these two configs ?

Can't really test more thoroughly atm. as I don't own one single, normal dimmable bulb any longer.
All is now Zigbee or fixed led lightning.
Have to borrow one dimmable bulb from my parents in law 😁

[fvanroie]

What's the exact difference for these two configs ?

The difference is that the serial bits are inverted in the protocol. We first noticed there was a diference between my EU version and an AU model sold over there. I interpreted this as if inversion of the bits was linked to the region/model. But now that doesn't seem to be the case.

In short, you will have try them both and see which one works for you 😕
The naming should be Serial Dimmer Inverted and Serial Dimmer.

[htvekov]

No worries 👍
I won't be needing it atm.
The Lanbon will go straight in the wall as my wt32-sc01's - just for the display.

Just wanted to report my findings about the EU/AU config.
Could be that later versions differs from yours and it's perhaps pcb revision that is the identifier ?

[fvanroie]

Could be that later versions differs from yours and it's perhaps pcb revision that is the identifier ?

Could be, but the change should be in the PSU unit and not the display...

[sleepypig2003]

I noticed the lanbon8 has an analog temperature probe from https://blakadder.com/lanbon-L8-custom-firmware/

Bottom right is the analog temperature probe connected to GPIO39

Does anyone know if there is a way to get the temperature from that GPIO and display it in a page?

[fvanroie]

It is only present on earlier revisions of the board. More recent versions don't have it:

An earlier revision V1.14 (20191203) of the PCB had an analog temperature sensor onboard. It was removed from V1.15 (20200521) of the PCB. You are likely not to get it when buying a recent switch.

https://haswitchplate.github.io/openHASP-docs/0.6/devices/lanbon-l8/#features

[sleepypig2003]

I uploaded firmware backups of some different lanbon l8 firmware in case anyone is interested
https://github.com/sleepypig2003/lanbon-l8

[fritzhu]

I have a newly acquired Lanbon L8-HS, the three-relay version. I have erased and then flashed both the latest release of openHasp, as well as the most recent dev; joined to wifi and configured MQTT. It connects fine, but after some time, the panel freezes completely most of the time, but not every time.

Touch events are not registered, it does not respond to mqtt commands, and does not serve its web interface. It seems completely locked up.

I took it off the wall and ran it off my FTDI adapter to see if anything comes out through serial, but nothing of note does (just normal chatter) but the panel did not freeze at that time.

Thinking it was a hardware problem, I then flashed tasmota32 and reinstalled on the wall, but it has been running perfectly ever since despite a few disconnect/reconnects so must be software.

I tried running with or without the openhasp hassio component, with long and short idle, different pages including empty, and so on, but it always freezes when running openHasp, generally between 5 seconds and 30 minutes of being powered up.

Has anyone had a similar experience and knows what the issue might be? Any tips or tricks I can use to solve the problem?

Thanks in advance!

[fvanroie]

Try adding service stop console to offline.cmd, or send the service command with payload stop console after mqtt connect.

If you want the console permanently stopped, there is a way to disable it by customizing and compiling the firmware binary.

[Eric-timeit]

Hi @TUNER88, I can confirm that sending stop console works. I have an automation that sends this when state trigger changes from unavailable. I have 4 of these and no freezing since Sept.

[TUNER88]

@fvanroie isn't it already too late to disable it when devices is going offline? Or is it executed on boot before the plate is connecting to WiFi?

@ecos34 how can I check if the console is really disabled? I also have an automation that is fired when the backlight is going off, could it be a problem when I disable it to often (multiple times)? However my automation seems to have no effect. Here is how it looks like:

[nagyrobi]

I'd rather suggest adding service stop console to online.cmd file on the flash. If doesn't exist, just create it.

[Eric-timeit]

Hey @TUNER88
I would go with this option from @nagyrobi which is the same as my method, just cleaner. It will only be done when going online.
I have not had an issue with performing it multiple times.

[shozanax]

When I press the button on Lanbon L8, the button is clicked double (triple) and send the command to MQTT. Only reset of switch helps

telnet log:
https://pastebin.com/GpZifQGa

.jsonl
https://pastebin.com/ZfvPwBzD

.yaml
https://pastebin.com/bFu4uE6N

[fvanroie]

There seems to be a message loop in your logic, but from the logs I cannot see where the messages are coming from.
I suggest to disable the .yaml actions and enable them one-by-one to see which is causing the loop.

[Kopetenti2001]

Thanks for your help. I was able to revert them with the help of a friend. -- Sent from myMail for Android Thursday, 18 November 2021, 07:43p.m. -05:00 from fvanroie ***@***.*** :

…

>Can you help me troubleshoot some L8 switches stuck on wifi reboot ? Sure. What version of openHASP are you running? And what do you mean with stuck on wifi reboot? If you are able to jump on the Discord channel that would help in troubleshooting the issue. — You are receiving this because you commented. Reply to this email directly, view it on GitHub , or unsubscribe . Triage notifications on the go with GitHub Mobile for iOS or Android .

[robertsorensen]

I have several Lanbon L8 switches and 4 of these are mounted in my living room. 2 are the dimmer type; 2 are the 3-relay switch type. Each Lanbon are flashed with openHasp 0.6.2 and my mqtt broker runs on the a RaspBerry Pi4 as part of Home Assistant.
The 2 dimmer switches and one of the switch type works OK (ignoring that they occasionally loose connection to my MQTT broker).
The 4th one really gives me trouble and a fair amount of head scratching.
Here is what happens with the trouble maker. After I apply power and the they connect I observe a lot of rubbish on the debug port (top part of the screenshot). The bottom part is logging from the same switch but offset 5-7 millimeter from the wall. That's right - if the switch is screwed in completely I get the garbage output - if I unscrew the plate from the electrical box and let it hang loose - things are OK and things are OK as well as soon as it there are 5-7 millimeter between wall and back of the switch! Could this be a bad switch? No. I've tried 2 different switches and actually 3 different front-plates and I do see the same thing.
As for the switch - despite all the garbage message between HA and the switch appear to be OK but eventually the Lanbon L8 crashes and becomes un-responsive. I assume the crashes are related to all the "bad" messages.
Ideas would obviously be appreciated but as it is right now I'm definitely having problems convincing my wife that this is the way to control our lights :-)

[fvanroie]

Check out a few posts up.

Disabling the local serial console should fix/work around the issue.

[fvanroie]

The bottom part is logging from the same switch but offset 5-7 millimeter from the wall. That's right - if the switch is screwed in completely I get the garbage output - if I unscrew the plate from the electrical box and let it hang loose - things are OK and things are OK as well as soon as it there are 5-7 millimeter between wall and back of the switch! Could this be a bad switch? No. I've tried 2 different switches and actually 3 different front-plates and I do see the same thing.

This is intriguing. I have not been able to replicate this issue, but all reports point in the direction of some cross-talk between the RX and TX lines. I'm no electrical engineer, so I'm baffled about what could actually cause this behavior...

So far, the conclusion is to best disable the console service via command or mqtt when the switch is mounted in the wall.
Alternately, you can remove the console altogether in a custom build of the firmware.

This issue has come up quite often, but without a clear cause... I'll ponder as the how we can tackle this issue more elegantly.

[htvekov]

I got my first Lanbon L8-HD today, but had severe issues with artifacts, reverse coloring, white screen etc.
Pcb revision v1.17 20210805 Tuya version - but without the actual Tuya chip installed. Eu version

At @fvanroie suggestion I recompiled a new version with lowered SPI freq.

I changed SPI_FREQUENCY=80000000 to SPI_FREQUENCY=60000000 in lcd_config.ini, thats it.
Recompiled and hey presto, it works perfectly now !!

So I went from:

to:

[htvekov]

@nate922 Here's a link for a Lanbon openHASP fw dev version back from early february with SPI=60Mhz. Working fine on both my Lanbons (both pcb rev. v1.15 & v1.17) https://www.dropbox.com/s/8z0o86ypmbx2mkh/lanbon_l8_ota_v0.6.3-dev.own_build.SPI60_ok.bin?dl=0 Den man. 14. mar. 2022 kl. 15.32 skrev nate922 ***@***.***>:

…

@dgomes <https://github.com/dgomes> htvekov <https://github.com/htvekov> I'm also getting a white screen, I think this is happening with new versions of the device Any chance you could share the binary? Saves me stuffing something up and bricking the device. Cheers.

[nate922]

@htvekov Thanks so much for that, I managed to compile 0.6.2, got a little impatient :)

I'm also reading your Sonos integration too, Looks awesome.
Seems we've got similar interests, I've been playing around with Sonos/node-red as well..

Cheers & have a great evening.

[royco2]

I have installed 0.6.3 on a lanbon l8 - 1.17

After uploading my jsonl file, see attached... the device goes into a reboot loop;

000D�[0K�[96m[ 1.616]�[91m[110580/160584 31]�[92m[44904/44920 1]�[93m ATTR: src/hasp/hasp.cpp 491 0�[0m �[1000D�[0KPrompt > �[1000D�[9C�[1000D�[0K�[96m[ 1.629]�[91m[110580/160584 31]�[92m[44904/44920 1]�[93m ATTR: src/hasp/hasp.cpp 492 0�[0m �[1000D�[0KPrompt > �[1000D�[9C�[1000D�[0K�[96m[ 1.652]�[91m[110580/160584 31]�[92m[42976/43092 1]�[97m HASP: Custom theme loaded�[0m �[1000D�[0KPrompt > �[1000D�[9C�[1000D�[0K�[96m[ 1.677]�[91m[110580/160584 31]�[92m[41872/41912 1]�[37m HASP: Loading /pages.jsonl�[0m �[1000D�[0KPrompt > �[1000D�[9C�[1000D�[0K�[96m[ 1.729]�[91m[110580/154384 28]�[92m[41104/41140 1]�[93m ATTR: Unknown Font ID 28�[0m �[1000D�[0KPrompt > �[1000D�[9C�[1000D�[0K�[96m[ 1.751]�[91m[110580/154348 28]�[92m[40824/40864 1]�[93m ATTR: Unknown Font ID 22�[0m �[1000D�[0KPrompt > �[1000D�[9C�[1000D�[0K�[96m[ 1.774]�[91m[110580/154348 28]�[92m[40544/40584 1]�[93m ATTR: Unknown Font ID 28�[0m �[1000D�[0KPrompt > �[1000D�[9C�[1000D�[0K�[96m[ 1.810]�[91m[110580/154428 28]�[92m[39848/39852 1]�[97m MSGR: Jsonl fully parsed�[0m �[1000D�[0KPrompt > �[1000D�[9C�[1000D�[0K�[96m[ 1.823]�[91m[110580/160584 31]�[92m[39848/39852 1]�[97m HASP: Loaded /pages.jsonl�[0m �[1000D�[0KPrompt > �[1000D�[9C�[1000D�[0K�[96m[ 1.835]�[91m[110580/160584 31]�[92m[39848/39852 1]�[37m HASP: Changing page to 1�[0m �[1000D�[0KPrompt > �[1000D�[9C�[1000D�[0K�[96m[ 1.850]�[91m[110580/160584 31]�[92m[39652/39660 1]�[97m MQTT: Started: 2048 bytes�[0m �[1000D�[0KPrompt > �[1000D�[9C�[1000D�[0K�[96m[ 1.862]�[91m[110580/160584 31]�[92m[39652/39660 1]�[37m GPIO: Starting...�[0m �[1000D�[0KPrompt > �[1000D�[9C�[1000D�[0K�[96m[ 1.874]�[91m[110580/160584 31]�[92m[39652/39660 1]�[93m GPIO: Reboot counter 0�[0m �[1000D�[0KPrompt > �[1000D�[9CGuru Meditation Error: Core 1 panic'ed (IntegerDivideByZero). Exception was unhandled.

anyone know why?

[royco2]

20210805 is the tag. yep mood red is fine

[htvekov]

Hi' @royco2

Are you on master branch or 0.6.3 ?
20210805 doesn't sound like a commit ref.

master branch has the latest dev. changes regarding this issue.
Try and use latest version released from master branch or test my version a few posts up in this thread.
I have both v1.15 and v1.17 Lanbons and both are working perfectly with that fw.

[fvanroie]

I'm pretty sure that it has to do with Arduino v2 doing something wonky with PWM enabled on these pins.
I have reverted the Lanbon L8 to use Arduino v1 which should work fine.
Please test lanbon_l8_full_8MB_v0.6.3-dev_b5273fa.bin (the commit tag is b5273fa on this build).

[fvanroie]

I tested another device with Arduino v2.0.3-RC1 and it also crashes with PWM on pin 33...

[royco2]

Build b5273fa works fine with mood green and blue, though it seems to hang everytime i try to get the information screen:)

[evelant]

I'm stuck trying to flash a Lanbon L8 V1.17(20210805). Sorry if I'm missing something obvious but I have little experience with hardware. I hooked up a FT232 USB-serial adapter as directed and got the unit into bootloader mode by grounding IO0 (white screen). When I go to run esptool.py however the TX light flashes on my FT232 but esptool always reports fatal error occurred: Failed to connect to Espressif device: No serial data received.. I tried using a strong 5v phone power supply in case my usb-serial adapter wasn't outputting enough juice but no luck there either, same thing. The L8 boots normally to the default software, it just won't connect to flash.

[nagyrobi]

Try swapping RX/TX

[fvanroie]

If the serial adapter has a voltage jumper or selector, set it to 3.3V signal level.

Are you able to boot the normal firmware? Connecting RX/TX and GND when running the stock firmware should give you some output on the serial port to make sure the pins are connected correctly.

[evelant]

Turns out there were two issues, needed to swap RX/TX and I had a bad connection somewhere. Made new jumper wires and it flashed no problem first time! Thanks for the help =)

[fvanroie]

Anyone with the serial feedback issue (where the plate locks up if the serial interface is enables) can try the new 0.6.3-rc2 firmware.
It has the option to disable the serial port completely, which should fix the issue without the `online.cmd´ workaround.

Also 0.6.3-rc2 has a default 60MHz SPI bus for the display which solved the screen issues with PCB v1.17.

[bensuffolk]

I would really like to use the Lanbon L8 without WiFi. I started by thinking about using the serial port and maybe a little bit of hardware to conver to RS485 to give me a connection over a distance. This looked interesting [#256].

But then I considered a lot of features I would loose, and actually adding wired ethernet to the L8 would be a much better solution. Ideally I don't want to make any modifications to the main board, but am very happy to make a new daughter board, repalcing the transformer and relays etc.

I have checked out all the pins on the header and this is what I have found (I have the 1.17 revision board)

K1 -> Transistorised (Q1) Output from IO27
BP -> Transistorised (Q8) Output from IO15
HUMI -> Direct to SENS_VN / IO39 (Input Only)
3V3
CF -> Direct to IO35
IO0 -> Direct to IO0
GND
K2 -> Transistorised (Q2) Output from IO14
K3 -> Transistorised (Q3) Output from IO12
5V
TX -> Direct to TX
RX -> Direct to RX

So this means there are enough direct connections to add an WizNet W5500 Ethernet Module. If we are using the ESP-IDF lwIP Ethernet stack then we need 5 pins connected, and we have enough to do that!

INT = HUMI (IO39)
MISO = CF (IO35)
MOSI = IO0
SCLK = RX (IO3)
CS = TX (IO1)

Things are looking positive for this.

[bensuffolk]

I have managed to get a configuration to compile with the right settings for the W5500 connected as above, but unfortunately after a firmware update I got a boot loop of the logo. A full power reset just gives me a white screen.

So I'm going to have to do a bit of digging. I would have been pretty surprised if my first attempt had worked anyway :-)

The biggest issue is I can't connect a console as I'm using the TX & RX lines. So I think I'll go to a dev board where I can use other pins for the moment and still see whats going on via the console.

Will I be able to run without a screen & touch source, just to look at debug messages etc for ethernet? Or will that cause some fundamental issues during boot?

I'll be using a FireBeetle as thats the dev board I was able to get hold of quickly the other day when I started playing with ESP32.

[bensuffolk]

Time for a quick status update. I have written some wrapper code around the esp-idf functions to add the w5500 as an ethernet adapter. Currently on the firebeetle and thats connecting to ethernet, getting an IP address and telnet is working.

web server, MQTT and other services are not yet working. I have not had time to investigate this yet, but I’m hoping it’s some simple config type stuff as the low level network stuff seems to be working (telnet, ping, dhcp etc).

The bad news is we can’t use IO 0 as I had hoped as that’s used by the i2c bus for the touch controller on the Lanbon, but that’s something to overcome once I have the services running properly.

[bensuffolk]

Network and all services, including OTA firmware updates, are working as expected now. I have to sort out the online & offline scripts to move them from just being WiFi to the more abstracted network level, but I ran out of time. Once thats done I'll do PR with the network code.

Once thats done I can start looking at the Lanbon hardware again and figure out the best IO to use with minimum hardware changes. Once I have that working in prototype fashion I can look at a PCB design and I guess a 3D printed rear enclosure would be in order as well.

[bensuffolk]

I have it working on an L8!

There is a very small hardware mod needed as there are not quiet enough direct output pins, but you can still use all 3 relays. This is the output list

INT = HUMI (IO39)
MISO = IO35
CS = BP (This is where the hardware mod comes in)
SCLK = RX
MOSI = TX
V = 3.3
G = GND

Modification wise, you need to remove R33 & R32, then short the right hard part pad of R32 to the left hand pad of R33. This directly connects IO15 to the BP pin, bypassing the transistor used for it normally. I used an offcut from a resistor leg with a bit of heat shrink over it.

I have added a pull request #343 for the required code for you to review / merge if you wish.

[nagyrobi]

Wonder what that BP pin was intended to be originally...

[nagyrobi]

What's this BP pin used for, originally?

[nagyrobi]

Awesome.

[bensuffolk]

I did a re check of my PCB, and actually there isn't a problem with it, I was just forgetting it attached upside down to the when verifying pins with my meter. So its all working as expected.

@nagyrobi / @fvanroie if you want a blank or assembled PCB then drop me an email ben @ vanilla.net

[nagyrobi]

Thanks. Check your spam :)

[nagyrobi]

What's nice about this backpack is that it can also be used to solely power the Lanbon, which can run the WiFi binary. In that case Ethernet is not used, but power is accepted.

[iofo]

Hi,
I am really interested in what you guys are doing here. Is the PCB and 3d print design open source? My use case is a bit different than yours but if possible I would love to see your design for dimensions and ideas on how you did this. I would like to attach a custom PCB "backpack" I am designing to the back of the lanbon and use a modified openhasp as my user interface to 12 on/off relays from a very old residential lighting system. I have my hardware design almost complete for a device that will supply 5VDC and accept serial commands and send status feedback and just looking for suitable GUI and interface into mqtt etc.
Thanks
Tom

[patricktd]

Hi,
I'm trying to change the firmware of my lanbon l8-hs, but it always gives this error, how to fix it?

esptool.exe --port COM4 --baud 921600 write_flash 0x0 lanbon_l8_full_8MB_v0.6.3_497f611.bin
esptool.py v3.1
Serial port COM4
Connecting...
Detecting chip type... ESP32
Chip is ESP32-D0WD (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: ac:67:b2:f7:46:54
Stub is already running. No upload is necessary.
Changing baud rate to 921600
Changed.
Configuring flash size...
Flash will be erased from 0x00000000 to 0x00180fff...
Compressed 1572992 bytes to 1058789...
Wrote 1572992 bytes (1058789 compressed) at 0x00000000 in 12.6 seconds (effective 995.4 kbit/s)...
File md5: e00f9d73b6c16d4f8d1cc5a71bfe0819
Flash md5: 26ab2aff995f84b9a9aa4c8118bfe739
MD5 of 0xFF is 91baf4be0d99a611557122b1565eda5e

A fatal error occurred: MD5 of file does not match data in flash!

[fvanroie]

Please try with ESPtool.py 4.4 or use the online Web Installer

[nagyrobi]

After almost exactly 2 years of continuous operation, my first Lanbon L8 died.

First it looked like a bootloop, but removing and re-inserting the pate to the base a few times changed the time of the loop - that looked like a power supply fault.

Luckily the PSU is a daughterboard soldered with just 4 pins:

Since I also bought a dimmer version of Lanbon which I don't use atm, I was able to swap the PSU daughterboard from that and voila, it works.

It looks like a dedicated power supply designed for Lanbon, given the label on the board L8-HP-AD5V_V1.1 20200715. I couldn't find a direct replacement. The usual suspects are always the capacitors, I guess I'm gonna try to change them and see what happens.

However, similar sized modules seem to be available:
https://www.aliexpress.com/item/4000715809759.html
https://www.aliexpress.com/item/1005004804203189.html
They are not 1:1 fit as the pins don't match directly, but with short wires and proper insulation they could fit in nicely.
Don't know the Amper rating of the original PSU, but as usual, the bigger the better... ESP32 pulls about 5-600mA inrush current+display+peripherals, I think it's not worth getting anything under 1A 5V...

[nagyrobi]

Replacing the big capacitor of 4.7uF (400V) with a new one revived the PSU module.

[htvekov]

50 cents repair costs 👍

[Rumbaar]

I know it later models, though I brought mine in last 2021 and have it (Tuya EU & AU/US models), is there a way to configure and output information within OpenHASP for the temperature sensor on GPIO39? I'm running Home Assistant and everything else seems to work currently.

[dawtim]

Hi all, I've successfully flashed 10 of the v1.15 of the Lanbon L8 dimmer units. Just received 2 of the Lanbon L8 switch units which has v1.19 and can't progress with either of them to upload the firmware. Just have a row of dots moving along with it trying to sync. Has anyone successfully flashed v1.19? I have tried grounding IO0 both through the pin header as well as directly on the ESP32 chip directly at bootup to no success.

[Rumbaar]

I have three in transit, though they are the Tuya based versions of the US 220V ones. Expected in the next 5-10 days, I'll see how I go and share back. I had 2 previously purchased in 2021 (L8-HS_CB_V1.17(20210805)) that I had no issue with.

[devinmitchell]

Interesting re also supplying both 5V and 3.3V - I have only supplied 3.3 - I thought you could only supply one or the other

That was my initial understanding as well, though before we knew the HomeKit version has the external antenna I was buying whatever the cheapest was at the time. So my setup is mixed between HomeKit, Smart Living, Tuya Smart Life, and probably another. Some of the Lanbon’s worked fine with 3.3V, others needed 5v, and in a fit of frustration last year I connected both 3.3 and 5v and have done so since without issues. I

[fvanroie]

Interesting re also supplying both 5V and 3.3V - I have only supplied 3.3 - I thought you could only supply one or the other

@dawtim Same for me... Maybe you can verify if this allows you to flash the V1.19 PCB devices correctly? If so, I'll update the docs.

[Rumbaar]

Interesting re also supplying both 5V and 3.3V - I have only supplied 3.3 - I thought you could only supply one or the other

@dawtim Same for me... Maybe you can verify if this allows you to flash the V1.19 PCB devices correctly? If so, I'll update the docs.

I received following version (V1.19) and was able to successufully flash with the current active OpenHAPS 6.3 no issues, just supplying 5v. I'm able to flash OTA and even operate the relays.

[dawtim]

Hi @fvanroie sorry for the delay. Had to put on the backburner and just returned to the project. I can now confirm I have successfully flashed two of the v1.19 Lanbons using the 5V connector only (not 3.3), connected to a sparkfun usb to serial, set to supply 3.3v (the same unit I used to flash the v1.15 units. So the difference was simply connecting to the 5v pin rather than the 3v pin.
The screen did not light up at all but it responded to flashing. Used Expressif Flash tool v 3.9.3.

Suggest updating the notes to state if cannot flash using the 3.3v pin, try using the 5v pin instead (with 3.3v in my case).

Thanks for the suggestions everyone

[gerry49]

I started with 3.3 volts and the lanbon would not boot, so i tried 5v and it booted and flashed ok.

[fvanroie]

@gerry49 @devinmitchell Does your v1.19 PCB have the Tuya chip populated?

[devinmitchell]

Doesn’t look like it if it’s the chip in the middle on the image @Rumbaar posted above. Here’s a photo of the last one I bought, marketed as a HomeKit version. Also a second image to show the tidy little sonoff housing I found on Amazon.
Makes for a nice little desk device! 😀

[getselim-stack]

@gerry49 @devinmitchell Does your v1.19 PCB have the Tuya chip populated?

Does this prevent OpenHASP from flashing? I have two with the Tuya chip and the flashing process completes successfully but it still boots to the stock firmware. Interestingly there is only one antenna connected to the Tuya chip unlike @Rumbaar s picture above.

[devinmitchell]

@gerry49 @devinmitchell Does your v1.19 PCB have the Tuya chip populated?

Does this prevent OpenHASP from flashing? I have two with the Tuya chip and the flashing process completes successfully but it still boots to the stock firmware. Interestingly there is only one antenna connected to the Tuya chip unlike @Rumbaar s picture above.

No problems flashing, though I did have to erase_flash first or else it'd boot back using the stock firmware.
esptool.py --port /dev/tty.usbserial-0001 --baud 921600 erase_flash

[getselim-stack]

Thanks. I used install.openhasp.com and selected the erase function. Will try again using esptool to erase and install.

[m-kloeckner]

Is there any hint / best practice on how to use the L8 as a curtain switch / roller shutter? Setting up the two needed switches is easy in the L8-HS version. However, I want to make sure that both relays cannnot be on at the same time otherwise the roller motor will be harmed.

In Tasmota there is an Interlock feature exactly for that. https://tasmota.github.io/docs/Blinds-and-Shutters/
How can I achieve the same in OpenHASP?

[fvanroie]

There is no Interlock feature in openHASP. You need to set each GPIO specifically to OFF first before setting the other to ON.
This can be done in the same payload using the json command.

If your hardware requires Interlock:

• you can install Tasmota on the Lanbon L8 too
• maybe use a separate dual-relay device running Tasmota, like a Shelly or Sonof mini to drive the roller motor
• you can customize the firmware with the functionality you need and share it with other users
• post this as a new idea discussion to see if this is something other users want/need

[shades66]

Hi all, Just got a couple of the dimmer modules and been trying for the last few days trying to get them to work with this firmware, Screen/Backlight/Moodlight all work fine but the dimmer functionality I was not able to get working till I accidently found the issue trying the latest nightly version which maybe useful for anyone who has bought one recently and can't get it working.

It seems, as I've not seen it mentioned anywhere else in the issues/discussion, that the EU/UK power unit may of changed how the light is controlled as while K3 (GPIO12) controls the dimmer the actual power for the dimmer is controlled by a relay on K1 (GPIO27) which needs to be triggered first.

as a side note in case anyone is wondering what does the dimming that is controlled by the serial connection it appears to be a STC8G SOP8 chip mounted just under the mains connector on the bottom of the PCB. Looks like the unused header you can see under the cover is the programming port

PSU Programming header top left

PSU Board Version