You can find esp32 wifi sniffer on github, it can display all nearby wifi units.

as I recall there is a size limit when using Preference lib, so suggest you only use that for things like ssid and passwords. You can save your web pages in SPIFFS memory, try look here: https://randomnerdtutorials.com/esp32-vs-code-platformio-spiffs/

Hello @dstaley Correct, that is what should happen. But yes, when I run your code I can see that the screen gets cleared but no time is shown. Here is why: the ePaper needs some time to actually do the writing on screen. When the pushCanvas() call returns, the actual writing is still ongoing, but in your case the system is shutdown immediately after and before the ePaper had a chance to finish. Therefore the time is not shown. The trick is to add a delay before the shutdown. I tried with a delay(1000) and now the time shows. Cheers Felix

Hello, Core2 and Core have different API thus cannot work together, you must work with the core2 API library and not the core API library. the hardware between the devices is different.

Sorry, full documentation is way behind schedule.

@dimi Congratulations ! Thank you very much.

Hello @HausBusDe exactly why this is happening I cannot say, but it seems to be related to the double initialisation of Serial.begin() which is already happening through M5.begin(). As soon as I remove the Serial.begin() your code then works w/ or w/o the 'not working line'. Thanks Felix

Thanks Felix, That helped. I guess from the documentation I thought that just adding the M5StickCPlus library would work. I have verified that some other programs do work (Display, TFT_Clock, PowerWake) with adjustments for the larger display size. The AXP192 and I2C_Tester programs work with your changes although I left Wire.begin() at default because I was checking the bus on the Grove port and that now is working. I did notice that on the Plus there is a small current draw on the battery (-0.5 mA) when I am running on USB power but it is 0mA on the StickC. Ralph

Just to close the loop for anyone from the future... Here's the steps I took to resolve this: Uninstall / Cleanup / Restore to macos Mojave default python installation. (Which is v2.7.16 as noted above.) This was a pretty intensive step. The short breadcrumb for anyone else: Dont touch the mac system python installs located at: /System/Library or /usr/bin helpful stack overflow post for uninstalling python But in the end, from what I could find Mojave doesn't include pip by default, and easy_install is depreciated so we had to go to step 2. brew install python Today in Dec 2020 this will install 3.9.0. ((Python 2.7 has been long depreciated))[Also note pip is currently installed with this version of python] At this point if you type python --version you will still get: 2.7.16 While reading the ESP-IDF toolchain instructions, I noticed the following command: ln -s /usr/local/bin/python3 /usr/local/bin/python This setup a symlink to the python3 symlink also installed by brew. (Seems kind of hacky, but technically works...) I also had to do: ln -s /usr/local/bin/pip3 /usr/local/bin/pip which cleaned up any remaining issues making pip work. (Biggest issue being me forgetting to type pip3) After restarting my terminal, running python --version I now get: 3.9.0 With my new python env working as expected, I fired up ardunio IDE and one of the Core2 examples, and went to verify to see if my issues went away... And I still had the issues above in my original post. 6b. At this point I tried a ton of other things, most notably redoing everything by installing pyenv and trying to set the global env to 3.9, but none of those steps worked... I went back through the troubleshooting steps above, had the expected correct outcomes. Even ran the esp-tools.py directly and didnt have any issues importing serial or anything else. I believe the actual issue is the first line in the esp-tools.py: #!/usr/bin/env python Which I believe is what is forcing the ardunio IDE to use the default MacOS python version. (See note in #1 about this being the protected default python that we shouldnt touch.) 9. Just as a test, I changed that line to be: #!/usr/bin/env python3 Once I reopened Ardunio, this worked and verified without any issues. However, I feared that if I ever updated the board definitions I would forget about this change and it would all break again. So I followed @lydericc instructions above. (Thank you!) You really shouldnt do this, but it's the only way to make it "work" with everything else out of the box. Specifically the following line (Step 2 in the post above): sudo pip3 install --target /Library/Python/2.7/site-packages pyserial This installed the required serial module and fixed the remaining issues. I'm not sure I like the solution, but it is the only thing that has made it work. The "correct" fix would be to have esp-tool.py use the installed default python version instead of the specific one installed at /usr/bin. Finally, as with all things in life, there is already an xkcd for this: https://xkcd.com/1987/ Maybe I'll open an issue with the esp-tool or Ardunio IDE and see what happens, but I dont believe this has anything to do with M5stack tools. Thanks for all who helped! (@Zontex & @lydericc )

Hello, could you please share the code you were trying to compile and how did you try to compile it, using arduino IDE?

Hello @wadoadi I am glad to hear you got it working. And thanks for reporting back. Happy Stacking! Felix

Doesn't the Atom matrix and atom lite normally come with UIFlow installed. All mine have. Yes, in arduino the fastled library works great.