FAQ & Getting Help
![[PLACEHOLDER: FAQ and Help]](images/troublefaq_01.jpg)
Before you open a GitHub issue or head to the discussions board, check these Frequently Asked Questions. Most “mysteries” have a simple explanation rooted in hardware limitations or configuration settings. Note that this is a “living” document that will be updated as common questions are brought to light. Initially, the list is pretty short!
Frequently Asked Questions
Can I use a different ESP32 board, different sensor type or different “X” component?
Short answer: Maybe…maybe not!
Long answer: The firmware is written and compiled with specific pin-mappings and hardware register commands for the components listed in the Build Guide. This guide includes a parts list that indicates which components can be substitued and those likely to require a firmware modficiation. While you can modify the code to work with other hardware, I cannot provide support for these versions.
ESP32’s/MCU: The firmware should work with any standard ESP32, regardless of form factor (30-pin, 38-pin, Mini, etc.). The firmware is compilied using the “ESP32_DEV” board, so any board that compiles under that definition should work. However, if you wish to use a different ESP32 variant, such as a -S3, -C6, etc., it is likely that the firmware will at least require recompilation using the specified board. Source code modifications may or may not be necessary.
Wired Sensors: In theory, you can substitute any wired sensor that uses a single GPIO pin andreturns a HIGH signal when triggered and LOW when clear. These would be configured as a “PIR” sensor in the settings. If you want to use other sensor types (I2C, SPI) or something like the HC-SR04 for distance, then source code modifications will be required as the libraries to read the sensors (and the syntax to interface with them) will be different than the VL53L0X.
Wireless Sensors: As covered in the topic on Sensor Types and Selection, it is possible to build your own custom wireless sensors, using any sensor type desired, as long as the sensor can send a wireless HTTP API signal via WiFi to the primary controller, or can post an MQTT payload to the correct topic.
⚠️ Support Only Offered for Listed Hardware
The system has only been fully tested using the components listed in the build guide. As much as I’d like, I simply do not have the capacity to support multiple builds of the firmware for various hardware variations. If you swap a component, you are officially the lead developer for your specific fork! I’ll try to answer questions as time allows, but please do not request firmware modifications for hardware other than listed in the Build Guide.
Can I control the system with Alexa or Google Home?
Not directly from the controller itself. The system is designed for local control to protect your privacy and eliminate the need for Internet connectivity. However, if you integrate the lamp into Home Assistant via Discovery, you can then expose those entities to Alexa or Google Home through the standard Home Assistant cloud or Nabu Casa integrations.
📢 “Hey Google. Turn on the Stair LEDs and set to 50% brightness”
Getting Additional Help
If your question isn’t answered above, don’t worry—the project has several avenues for support.
GitHub Discussions (Recommended)
This is the best place for “How do I…?” questions or “Is this normal?” concerns. Discussions allow for code snippets and images, making it much easier for me (and the community) to see what’s going on.
- Etiquette: Include your firmware version and a description of what you’ve already tried. “It won’t work” is a riddle; “My MQTT status is ‘Offline’ despite the correct IP” is a solvable problem!
GitHub Issues
Please reserve Issues for confirmed or suspected bugs in the official firmware.
- If you find a bug, please provide steps to reproduce it.
- If the issue is related to custom hardware or modified code, it will be moved to the Discussions area or closed.
Please don’t email me directly unless specifically requested. The volume of email received means your message will likely be lost in the “noise” and may not receive a response. The best way to initially reach out is via the Discussions area.
💡 A Final Note on Support
I’m an electronics hobbyist, just like you. I maintain these repos in my spare time between coffee refills and actual work. Please be patient—I’ll do my best to help you get your lamp shining bright!