Lanbon L9 #765
Replies: 26 comments 98 replies
-
|
This is a new device. We verified there is a ESP32-S3-Wroom-1U inside:
|
Beta Was this translation helpful? Give feedback.
-
|
I ordered one today and I’ll be happy to take it apart and see what we can do with it. Will need some guidance on how best to help the community. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks so much for posting the images and helping to identify the pins. More investigation is needed to identify the display and touch pins... |
Beta Was this translation helpful? Give feedback.
-
|
I'm trying to gauge interest in this device. Please indicate if you would consider the L9-HS : |
Beta Was this translation helpful? Give feedback.
-
|
don't think it would have power monitoring, but it does have "Advanced Radar Motion Sensor Switch" which i think is some sort of presence sensor. its not pir with the little plastic bulb shield popping out |
Beta Was this translation helpful? Give feedback.
-
|
The form factor looks a bit like the Hi-Link LD2410 modules, but would need to verify the markings on the presence sensor chip. |
Beta Was this translation helpful? Give feedback.
-
|
Now that I have one in hand. I will say for the convince of fitting in a standard US decora spot not sure how small the screen is worth it. I probably won't buy many more of these unless I really like the mmwave. We will see once it's all setup though. |
Beta Was this translation helpful? Give feedback.
-
The manufacturer confirmed that there is a dimmer version in the works but it's not available for order yet. |
Beta Was this translation helpful? Give feedback.
-
|
I love that fact that it fits a standard US light switch box and switch plate. This is the only screen I have seen in this form factor so far. I have not seen mmwave available on any of these small screens so this is also a big plus. I think this screen is a winner. I would buy a few for sure. |
Beta Was this translation helpful? Give feedback.
-
|
Display Module;:
Display PCB backside: Power Module:
|
Beta Was this translation helpful? Give feedback.
-
|
I am buying at least one, especially while there is a $10 off coupon. I am guessing that it is mmwave presence detection by looking at it. |
Beta Was this translation helpful? Give feedback.
-
|
Great, please share if you could help figuring out the mapping of the (display) pins to the ESP32-S3. |
Beta Was this translation helpful? Give feedback.
-
|
Will do. It is supposed to arrive today. |
Beta Was this translation helpful? Give feedback.
-
|
The display seems to be a HD19006C30 which indicates an ST7789V display controller instead of the ST7701S. This should make things a bit easier since there are examples out there for this display. I believe the pin mapping to be; Now we need to find out where each pin goes to the ESP32. |
Beta Was this translation helpful? Give feedback.
-
|
I think the next step would be to backup the factory firmware and try a test sketch to verify the pins. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah so I am having a problem getting them to go into serial bootloader mode. Pulling gpio 0 to ground just doesn't seem like it wants to go. Anyone had luck? |
Beta Was this translation helpful? Give feedback.
-
|
@stboch how are you applying the voltage? I feel like I needed to put a pin right on the esp chip instead of the headers when I was messing with it before |
Beta Was this translation helpful? Give feedback.
-
|
I have done both. I got it in my bdf and applied it directly with 3.3v I got it booting and got all the main uart logs of the firmware boot. When I tried to pull gpio0 to ground no good. Even tried pulling gpio46 low and also no good. |
Beta Was this translation helpful? Give feedback.
-
|
I have dumped the flash and can read write the ESP32 chip. It seems like you need to supply both 3.3V and 5V to the board, via the J4 header, which I'm doing with a bench supply right now. For GPIO0, I'm using pin 12 on the J4 header, and it works fine. |
Beta Was this translation helpful? Give feedback.
-
|
Boot log for the factory firmware. |
Beta Was this translation helpful? Give feedback.
-
|
See if we think this is correct. Slight variations from @lylavoie google sheet
|
Beta Was this translation helpful? Give feedback.
-
|
I bought a breakout and ribbon, and a couple of these displays (https://www.amazon.com/dp/B0CTTW3YMB?ref=ppx_yo2ov_dt_b_fed_asin_title) which plugin and work on the L9. I've double checked the wiring described in the google sheet and that all matches and aligns with the pinout on the displays from Amazon. I was also able to trace the backlight, through transistor labeled MT1 and to GPIO42 as well. However, I have not yet had any luck getting TFT_ESPI to drive the display through a parallel interface. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I ordered a display to experiment. Maybe try the LovyanGFX library instead of TFT_eSPI. |
Beta Was this translation helpful? Give feedback.
-
|
Any update on this driver? I purchased one of these today and it's a really nice little screen! I don't think I have seen any other screen that fits in a standard decora plate. |
Beta Was this translation helpful? Give feedback.
-
|
I am interested in this as well! This would be an awesome option as a display! Unfortunately there aren’t many options for making displays work that are any more than single gang and this could help solve that. It would be especially useful where there is a separate light switch and fan switch. |
Beta Was this translation helpful? Give feedback.
-
|
I pushed a commit b55efe0 which adds a configuration for the Lanbon L9. I don't own this device and it is purely created for testing and verification of the information we gathered so far... Please backup your original firmware before compiling and uploading the firmware. If you find issues with pins or settings please post here or create a Pull Request. Hopefully we can create a working config together... |
Beta Was this translation helpful? Give feedback.
-
|
Hey @fvanroie, I just purchased an L9-HS and I'm encountering an issue loading up OpenHASP based on your most recent commit above. After flashing, I get an infinite boot loop on regular power-up, backlight comes on but no picture. Happy to help troubleshoot things to get this working for the community as a whole, I've put the serial log output that occurs after flashing below. I did esptool erase_flash prior to flashing the L9 bin that I compiled and have written the bin probably 3-4 times (erasing between each flash). Each time the error is the same. 'CONF: Failed to load /config.json' followed later by 'Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled.' on every loop. Any ideas what could be causing this? happy to provide more details if needed. [01:39:52]�ESP-ROM:esp32s3-20210``` |
Beta Was this translation helpful? Give feedback.
-
|
FWIW, I received similar results. |
Beta Was this translation helpful? Give feedback.
-
|
This configuration is a test configuration, based on the information gathered here. It is to be expected that it doesn't work from the first try. Since I don't own the device, I can't really assist or troubleshoot anything. Someone with access to the device really needs to put in the effort to verify, test and correct the driver/pin settings... It started out with a lively search for the pins, but now the real grunt work needs to done to fine-tune the information into a working config. |
Beta Was this translation helpful? Give feedback.
-
|
I'm more than happy to contribute since I have this device. Mainly, I just have no idea how to interpret the errors I mentioned above. Any pointers on where to begin with this thing? |
Beta Was this translation helpful? Give feedback.
-
|
That error doesn't tell me anything besides a crash while or after initializing the display driver. This can be a config issue, wrong pin, driver issue, ... etc. The best way to move forward is to test a demo sketch from ArguinoGFX, LovyanGFX or TFT_eSPI to validate the pins and driver settings. Once you have a minimal working sketch, it will be easier to integrate that into openHASP. Now we're still punching in the dark and the chance of getting it working will be low. |
Beta Was this translation helpful? Give feedback.
-
|
My apologies, I realized after posting that it was entirely unhelpful. My intent was only to point out that I was unable to get it to work, but unfortunately I didn't save my terminal logs. I was able to flash my device with Tasmota-lvgl and get the device to boot, but wasn't able to get much further as it was just a bit over my head. I'm happy to reflash my device with this version and post logs if that would be helpful. I can try to turn up logs as well if that would be helpful. I spent a couple of hours reading through things and look over documentation, but it was still quite a bit over my head. I'm sorry if it sounded like I was just pitching something over the fence. I'm going to continue to tinker with mine, but I'm really just brute-forcing it by changing values and seeing what sticks. If there is anything I can provide to anyone more qualified than myself, just LMK. |
Beta Was this translation helpful? Give feedback.
-
|
Good news everyone, I can confirm I have the screen of the L9 working, using the Arduino GFX library, so we know the pinouts are working. Below are the important initialization lines, you can use to setup for the hello world program (example below). Remember, to work on bench, via the J4 header, we need to supply both 3.3 and 5V. For a video of this running, see: https://photos.app.goo.gl/Gu993TwHhs34Zios8 #include <Arduino.h>
#include <Arduino_GFX_Library.h>
/* More data bus class: https://github.com/moononournation/Arduino_GFX/wiki/Data-Bus-Class */
Arduino_DataBus *bus = new Arduino_ESP32LCD8(17 /* DC */, 21 /* CS */, 13 /* WR */, 18 /* RD */,
6 /* D0 */, 7 /* D1 */, 15 /* D2 */, 16 /* D3 */, 10 /* D4 */, 9 /* D5 */, 46 /* D6 */, 3 /* D7 */);
/* More display class: https://github.com/moononournation/Arduino_GFX/wiki/Display-Class */
Arduino_GFX *gfx = new Arduino_ST7789(bus, 4 /* RST */, 0 /* rotation */, true /* IPS */,
170 /* width */, 320 /* height */, 35 /* col offset 1 */, 0 /* row offset 1 */ );
void setup(void)
{
Serial.begin(9600);
Serial.println("Arduino_GFX Hello World example");
// Enable Blacklight
pinMode(42, OUTPUT);
digitalWrite(42, HIGH);
// Init Display
if (!gfx->begin(16000000UL))
{
Serial.println("gfx->begin() failed!");
}
gfx->fillScreen(BLACK);
gfx->setCursor(10, 10);
gfx->setTextColor(RED);
gfx->println("Hello World!");
delay(5000); // 5 seconds
gfx->fillScreen(BLACK);
gfx->drawRect(10, 10, gfx->width()-20, gfx->height()-20, RED);
delay(5000);
Serial.println("Done with setup ...");
}
void loop()
{
gfx->fillScreen(BLACK);
gfx->setCursor(random(gfx->width()), random(gfx->height()));
gfx->setTextColor(random(0xffff), random(0xffff));
gfx->setTextSize(random(6) /* x scale */, random(6) /* y scale */, random(2) /* pixel_margin */);
gfx->println("Hello World!");
delay(1000); // 1 second
Serial.println("Looping...");
} |
Beta Was this translation helpful? Give feedback.
-
|
This branch has the changes for openHASP get the display working, https://github.com/lylavoie/openHASP/tree/Lanbon_L9 Still has some bug, where, once the touch driver starts up, it seem like the system freezes, even after it looks like it finished booting all the way. |
Beta Was this translation helpful? Give feedback.
-
|
That branch should be working now, touch screen is responding. |
Beta Was this translation helpful? Give feedback.
-
|
Wow, that's awesome work! Thanks so much for the PR, it is now merged and building. |
Beta Was this translation helpful? Give feedback.
-
|
Working on the RF presence sensor. Ended up pulling off the board and it looks like it's actually this: MoreSense 10G Hand Sweeping Series MS10-3007D26M4 (https://en.moresense-tech.com/product_details/75.html) Anyone worked with these yet. Trying to find a datasheet. |
Beta Was this translation helpful? Give feedback.
-
|
The ZIP file looks like it has what I need in the C-code examples, assuming it works for this module. I didn't yet have success getting the module seen by an I2C scan, but I will play with this some more and see if I can mock something up that works. On the relay and the FAN module, it should just be a matter of driving the GPIO pins on the J4 connector. The FAN module might have more of those connected, the Light Switch only has the single relay. There is also the power sensor, which I think is based on the HLW8012, but I have also not yet played with this either in the L9, but I've used them before in ESPhome stuff. @fvanroie as we get closer to a final working solution for all of the L9, how do we define the GPIO and things like the HLW8012 power sensor "from code" so there are there when the firmware is built? I admit, I have not gone looking for that level of depth yet in the code base, but I think it's possible, from loading one of the example builds for other hardware. |
Beta Was this translation helpful? Give feedback.
-
|
So, the radar definitely works, in that is drives the output pin high when it detects something and will reset it once the detection event ends. However, I have not been able to get the I2C interface work, using either the actual I2C libraries, or the bit-banging approach they provided in the code example. |
Beta Was this translation helpful? Give feedback.
-
|
How are the default detection settings on it? Would it generally be usable as-is just with the high/low reading? |
Beta Was this translation helpful? Give feedback.
-
|
It would likely work, but I don't know if that is because I booted up the Lanbon software at least once and it "programmed" that chip, and those settings are saved, or these are the default settings, etc. The output pin of the radar is GPIO11, and can just be an input to OpenHASP. The bare radar module (i.e. no plastic case) was sensing about 2m away. Without the working interface, we can't chance the sensitivity. For where I wanted to install the L9, I was hoping for more of a 0.5m sensing, so the screen doesn't turn on every time someone walks by, compared to approaching the switch. Maybe I'll purchase a second unit, so I can install it and still have one to develop against, that might be a winter break project. |
Beta Was this translation helpful? Give feedback.
-
|
Ok thanks for all that info, I'll be off of work starting next week so I'll spend some time testing with my devices as well. Did you ever figure out how to add pre-configured output pins for the device specific firmware? I played around with trying to manually assign the pins in the web UI but I think the pin for the relay is disabled/hidden right now. I haven't taken a multimeter to the device to confirm which pin it is yet (was going off of the diagram in this discussion). This weekend I'll do that and post relevant pinouts for both the regular L9 and the CF version |
Beta Was this translation helpful? Give feedback.
-
|
I'm able to get it to trip reliably at about 4 feet. Also, in case it helps, it has never booted to the factory firmware. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, That's good to know! Unfortunately I don't have much experience with IC2 to be able to talk to the sensor and modify that range. Would be very cool to have that piece working since 4ft would be way to far for my use case haha |
Beta Was this translation helpful? Give feedback.
-
|
Hey @lylavoie, did you have any luck getting the relay GPIO pre-configured in the firmware? I'm still struggling with it :/ I also confirmed that IO 4 and 5 are connected to the J4 connector (continuity test with my multimeter), but even when manually configuring them as power (or light) relays I can't seem to control it. Tried setting 4 and 5 as output relays because I wasn't sure which one was the relay and which was the mmwave. |
Beta Was this translation helpful? Give feedback.
-
|
No, I dug for a little bit, but I couldn't find where the pins are restricted, or the correct format to set the GPIO template from the header file. @fvanroie can you give some pointers into the code base for how this is handled for the automatically built images that come with the GPIO already configured. |
Beta Was this translation helpful? Give feedback.
-
|
I have a couple of these switches, and I'm working on experimenting with them, but I am pretty new to working with microcontroller hardware. I've done a couple of Arduino projects, but am relatively new to this (I do have decades of software dev experience though). I am currently able to boot the low voltage part of the switch (the front part) using a serial to usb converter, and powering the 3v3 and 5v (and ground) pins on the J4 connector. Are you all using the 32 pin connector to flash this thing, or are you able to rx/tx with the J4, and if so, how are you setting up those connections. The J1 on high voltage side of the switch doesn't have very helpful descriptors of the pins, most of them reading NC (No connection, right?) and a K1 and a CF. The power wires are pretty self explanatory, but I'm not sure where to go from there. Using the L8 openHASP tutorial doesn't seem to be much help given the differences in the connection. If there's documentation I should look at, please steer me in the right direction if my inquiry is not appropriate in this discussion. |
Beta Was this translation helpful? Give feedback.
-
|
Oh never mind, I definitely had my pin wrong. Set it to 36 as a light relay output in the GPIO settings and now it works! A second issue I had was that I initially didn't realize that restarting the device was necessary to catch config changes in the GPIO menu. |
Beta Was this translation helpful? Give feedback.
-
|
Awesome you got the GPIO setup working! I'm looking forward to giving it a try. First though, I'm not sure if this is a setup issue I'm having, or if it's related to this build specifically. On the L9, I'm showing MQTT as Disabled. I'm able to setup the plate in HA, but nothing can communicate. From what I've read, if I leave the MQTT settings defaulted, it should work out of the box with Mosquitto, but all I see is disabled. If I set the MQTT settings to use my HA server's ip as the broker it is not disabled, but says Disconnected. As someone new to all of this, I assume this is something I'm doing wrong on my end... but I'm also not sure what else to try. Given that were kind of still in a bit of a test it out phase with the L9, I hope it's alright if I start my inquiry here. Please feel free to direct me somewhere else too. |
Beta Was this translation helpful? Give feedback.
-
|
I've got MQTT set up on my L9 which is running lylavoie's latest version. Getting the MQTT settings configured was a bit of a pain however (more so on the Home Assistant side of things). I had to configure the MQTT settings on the L9 itself to match my HA server, I'd guess that it's probably a config issue that's causing it to say Disconnected for you, but I'm by no means an MQTT expert so take that with a grain of salt. I ended up using a program called MQTT Explorer to see what was being posted to the HA MQTT server. That way I could watch various events on the L9 and figure out what to set my HA automation triggers to. I'm not at the house at the moment, but if you're still having issues when I'm back I can try to see if your configs look any different than what I'm doing. On the latest build of the L9 I was able to write some HA automatons to automatically turn the display on when I get close to the device using the mmwave sensor and that involves both sending & receiving MQTT data between HA and the L9. |
Beta Was this translation helpful? Give feedback.
-
|
Sounds great, let me know on your configuration of you get a chance; I can try to get mine posted in the morning. I'm calling it for the night on this one. I'll look into MQTT Explorer too. Sound like this might be a little more involved than I'd originally thought. |
Beta Was this translation helpful? Give feedback.
-
|
Just a friendly follow up. I've got everything working. First issue was needing to use a HA user and password, the MQTT default user/pw does not work. After that apparently the homeassistant.toggle service doesn't work on scenes. homeassistant.turn_on does though. First pass is now good to go. Going to push the updated BIN, and hopefully get installed soon. Thanks for all your help! |
Beta Was this translation helpful? Give feedback.
-
|
I only used the 5v and not the 3v and was able to flash. I struggled for a really long time trying to use pins inserted into the header and eventually just soldered 30awg wires to 5v, gnd, tx, Rx, and io0 where the header connected to the board. |
Beta Was this translation helpful? Give feedback.
-
|
I made a set of "pin" wires using the leads trimmed from resistors. That's a 1.25 mm pitch connector, so they wont' fit a the more typically seen 2.54 mm pitch. |
Beta Was this translation helpful? Give feedback.
-
|
I did something similar, except I ended up cutting up an old Ethernet cable. Solid core wires on Ethernet cable are thinner than standard DuPont wires and worked good since I had some laying around. |
Beta Was this translation helpful? Give feedback.
-
I followed this advice, worked like a charm. I put the ethernet wires into a breadboard, then used standard connector wires to connect to the serial adapter. This gave me some freedom to double ground connections, etc. without having to get too janky or solder anything. |
Beta Was this translation helpful? Give feedback.
-
|
I complied it locally and flashed, but i cannot find the pin 36 listed in the GPIO configuration, tried "-D RELAY_1=36" in "lanbon_l9.ini" and "#define HASP_GPIO_TEMPLATE "[]" also in the user_config_override.h still cannot set the GPIO to 36. Please Help !! |
Beta Was this translation helpful? Give feedback.
-
|
You should have two .bin files, one OTA on full. Both are always built, as far as I know. You have to flash the full one using esptool, similar to esptool.py write_flash 0x0 FULL_FIRMWARE_FILE.bin |
Beta Was this translation helpful? Give feedback.
-
|
Ah, then there's some significant user error on my side trying to compile this. Like I said it's not building that file for me at all, but it does show build successful. Any suggestions? |
Beta Was this translation helpful? Give feedback.
-
|
Please open a Pull Request with the required changes for this device, so it can be integrated in the main repository, thanks. |
Beta Was this translation helpful? Give feedback.
-
|
@fvanroie the changes really should require a rework of how you handle the pin differences between ESP32 / ESP8266, to account for the other ESP32 variants, like S3 WROOM modules, and if they include the on-module PSRAM as quad or octal. That is more work than I can put into it right now, which is why I haven't made a PR for the hacked up code. |
Beta Was this translation helpful? Give feedback.
-
|
I was able to get this working, there was something up with my VScode environment. Thanks for the help and work you all have put into this so far! |
Beta Was this translation helpful? Give feedback.
-
|
@lylavoie @Poisonite Thank you both for your work on the L9! I just received my switch this weekend, and will get around to programming it soon (or at least as soon as my schedule allows). A couple questions, if you have the time to answer:
Thank you again! |
Beta Was this translation helpful? Give feedback.
-
|
@Nick2253 if you do not need the relay, the main branch should work, since it will just ignore the GPIO pin used to control the relay. It proximity sensor does also work within openHASP. But, to control the state of the display, i.e. wake it up when you walk near it, you actually need a combination of both openHASP and Home Assistant to drive that "automation," which does add a bit of round trip time. The "control" of the proximity chip means we can't change any of the sensitivity of the chip, i.e. the distance where things "happen." I have the switch installed now, but running ESPhome, and it wakes up when I'm about 4 ft (1 m) to it, and it has a pretty "wide angle" of view (i.e. you don't need to be be directly in front of the switch). |
Beta Was this translation helpful? Give feedback.
-
|
@lylavoie Can you clarify what you mean here:
Does that mean that openHASP doesn't have the ability to automatically wake the screen, but provides sensors and controls for "proximity sensor" and "screen on", so you have to manually activate (through Home Assistant) "screen on" when "proximity sensor" goes high? Can you share your ESPhome config for the switch? I think my preference would be to use ESPhome, but I'm concerned about getting the screen to look nice, which is what attracted me to openHASP. If I can use ESPhome, that's how I'd prefer to use it. Any tricks about getting ESPhome working on the L9? |
Beta Was this translation helpful? Give feedback.
-
|
I did some more searching, and it looks like you're way ahead of me. Home Assistant community thread: https://community.home-assistant.io/t/lanbon-l9-lcd-smart-light-switch-with-motion-sensor/810428/10 lylavoie's fork which includes L9 example config and how-to: https://github.com/lylavoie/esphome-devices/tree/lanbon-l9 |
Beta Was this translation helpful? Give feedback.
-
|
@Nick2253 Correct, as far as I can tell, OpenHASP doesn't have support for "local" automations in the same way that ESPhome does, since it's a different architecture / approach. What you describe is correct, where Home Assistant has the automation, triggered by the binary sensor (proximity sensors), that can then "wake up" openHASP. This is also similar for anti-burnin for the screen as well (see the openHASP guides). For ESPhome, I have an open PR for the devices site. Note, this does depend on updates to either the ili9xxx device or a proposed i8080 display device. esphome/esphome-devices#1020 |
Beta Was this translation helpful? Give feedback.
-
|
This is an openHASP discussion, please use the appropriate forum for other firmware. |
Beta Was this translation helpful? Give feedback.
-
|
Im sorry to be that guy, but I've been racking my head trying to figure out how to get this little guy going. I have an l8 with openhasp and got this l9 now. Is there a pre build bin file available for this? |
Beta Was this translation helpful? Give feedback.
-
|
So far no PR has been submitted for this device. Feel free to test and submit your findings in this discussion thread. The L9 is a US form factor and I don't own this device. We're dependent on users sharing their experience and configuration to support it. Once a working configuration is available, I'll add it to the build workflow. |
Beta Was this translation helpful? Give feedback.
-
|
Okay, so I merged changes from the external fork into the master code repository. You can download Please test and report back if it works.... |
Beta Was this translation helpful? Give feedback.
-
|
Unsure if this is the appropriate place. Seems like my hardware is different than the shared ones I've found thus far. I was excited to try this out but wondering if it wouldn't work the same. Thoughts if it would still be compatible?
|
Beta Was this translation helpful? Give feedback.
-
|
Yeah, that's definitely a new hardware iteration. While it's hard to tell for sure, Lanbon has been good at making their PCB revisions backwards compatible on the L8... so my guess would be that it should work. But there is only on way to know for sure, give it a try. |
Beta Was this translation helpful? Give feedback.
-
|
Most critical is what display chipset is used on this one, and how is that connected to the ESP32 module. Is there anyway you can identify that? You probably need to pull the board with the ESP32 out of the plastic to see more details about the display. |
Beta Was this translation helpful? Give feedback.
-
|
Well this is a coincidence, I too just picked up this hardware and was looking to flash ESPHome (or openHASP) on it but was having trouble compiling the example ESPHome config. What's really interesting is I have an even newer version than @lilmansplace -- it appears they have v3.2 of the board, I have v3.3 which critically changes over from the WROOM-1U to a WROVER-IE. That means the pinouts are not compatible since the WROVER-IE only goes up to 39 GPIO pins. Maybe they only swapped the backlit (42) and two of the display pins (41 and 46) to some of the available pins? Any tips on how to trace that? I have an oscilloscope available but I'm not very experienced in tracing like this otherwise. Is there anything we can glean from the OEM firmware if I dump it? I'm not sure if decompilers can do much with a firmware dump like that. Interestingly mine still came with v3.2 of the power board, so that's the same at least. Conveniently the display and touch controller seem to be the same as well.
|
Beta Was this translation helpful? Give feedback.
-
|
Ahh I think they are going to be totally different mappings... the easy things to trace are the radar module pins and that seems to be:
where as the WROOM version was according to this spreadsheet:
|
Beta Was this translation helpful? Give feedback.
-
|
So, going only from your pictures, I'm going to caution a guess, they changed how they are driving the display from parallel to serial. The image of the display connector (CON 1 I think) on the board seems to only show about 7 or 8 pins connected. While the parallel input requires 8, just for the data lines. So, unfortunately, you are going to have to trace all of those, and reverse engineer this again, to get back to a working display. |
Beta Was this translation helpful? Give feedback.
-
|
Bummer, I seemed to have gotten the new revision (L9_HS_CB_V3.3) with the WROVER-IE as well. I dissembled a bit and found this is the screen being used, in case it helps anyone: https://www.alibaba.com/product-detail/1-9-inch-tft-lcd-display_1600108664434.html I'll get out the multimeter in a bit and see if I can trace back anything. Assuming we find the pins, what would the YAML be to use this screen? |
Beta Was this translation helpful? Give feedback.
-
|
Are you able to list out what pins those are on the screen, that should make it pretty clear if they are now driving it as a serial interface. I didn't get to follow your link (only on a phone for now), but does that doc list what display chip is used? |
Beta Was this translation helpful? Give feedback.
-
|
Kudos @revnelson -- I was able to trace and confirm and get a working ESPHome build compiled/running. Relevant info: I was not able to figure out the J4 K1-3 mappings so I can't use the relay, but I was only intending to use it as a touchscreen input anyway. Here's the ESPHome config. (Edited after posting initially to add sensor + fix display config) |
Beta Was this translation helpful? Give feedback.
-
|
This is fantastic, thanks @pharris2411 for such a detailed config to use. Unfortunately when I flash this (with the redacted pieces replaced appropriately) I get the following error about a dozen times a second on an infinite loop: I'm pretty new to ESPHome so if anyone has info on why I'm getting this or how to fix, I'd greatly appreciate it. |
Beta Was this translation helpful? Give feedback.
-
|
Weird! Do you have the latest ESPHome version installed? |
Beta Was this translation helpful? Give feedback.
-
|
Ahh, I just flashed my second device and it's working. I think the issue was because my first device I had dissected so far and not reconnected the touch panel. I'll keep following along here as well as trying things on my own, as I would really like to get the relay working to use this for my bathroom light. Thanks again @pharris2411, you've been a huge help! |
Beta Was this translation helpful? Give feedback.
-
|
I've had the v3.3 board (ESP32-based) working under ESPHome for a couple of months. I've been meaning to submit it to devices.esphome.io but I wanted to take some photos and differentiate it from the ESP32-S3 based version. In the meantime, though, here's my ESPHome yaml file. You'll have to remove the AQI code and |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Does anyone have experience or insight into the Lanbon L9 switch https://a.co/d/cO7q0Fp
Things like chipset, display and touch and display resolution? And potentially whether openHASP could work on that switch?
Beta Was this translation helpful? Give feedback.
All reactions