-
-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
m5 Stack Config Failing: "Unable to find action with the name 'homething_menu.scroll_counter_clockwise'." #136
Comments
sorry for the delay common/m5stack-fire/binary_sensor.yaml, # used for button controls
common/m5stack-fire/binary_sensor_rotary.yaml, # used for rotary controller https://shop.m5stack.com/products/encoder-unit
|
Thanks for the reply!
Makes sense. I removed
This is my own private base config - it just configures WiFi and sets the API Encryption key. I removed it and moved these into the config for debugging simplicity.
No. if I remove
|
Seems like I missed a lot of components, really. I was trying to base this off of this wiki (https://github.com/landonr/homeThing/wiki/m5stack-fire) but it contains a mix of what seem like required components and references to your own setup. Let me spend some time and try to figure out an "empty" m5stack config and maybe I can submit in a PR or something. |
That wiki page is pretty out of date, i'm going to remote it! this is my personal M5Stack Fire config that I use to control my cat's auto feeder https://github.com/landonr/esphome-devices/blob/main/fireremote.yaml |
I'm trying to install homeThing to a brand new m5Stack FIRE device. When I try to validate the configuration in ESPHome Dashboard, I'm getting a failure: "Unable to find action with the name 'homething_menu.scroll_counter_clockwise'."
Here is my config, heavily based on your wiki and samples:
Here is what I get from validate using ESPHome 2024.6.6 Dashboard:
I don't think this particular error can be caused by something on my side, but maybe I am missing something...
The text was updated successfully, but these errors were encountered: