-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
support for AW50011 non dimmer #12
Comments
I will be ordering a new switch soon. so i don't have to remove the one i got mounted in my kitchen lol then ill get you the pictures ect |
If i give you the 12 bucks can you do the port for it |
tossed you 15 eur |
I flashed your firmware to my AW50011 non dimmer and it connects to MQTT server just fine. The only issue is that The physical push button no longer controls the internal relay. When I send it a 1 it responds by turning on the WIFI light, 0 turns the WIFI led off. I believe adjusting the pin mapping may be all that is needed to make it completely compatible. Of course, I could be way off too. |
@zmesser , you are correct. All that's needed is to fin the correct pin mapping. |
Of Course. I'll post them soon. Thank you for your work! |
@ljalves will these images work? I'm sure you are busy, just wondering if there is anything else I can do to help. |
First, I love the work Luis has put into this! I didn't realize how much until I started digging around. I had a few on the non dimmer ones and finally had time to get the compiler up and running and was able to get them to work, mostly. I could not get the wifi LED to work. I tried to handle it while using mostly the plug code but ended up soft bricking my switch where I had to hook into the serial port and send a new image over with xmodem. That was fun! I did modify the MQTT code slightly. For Home Assistant, I wanted a way to get the status on startup and for it not to get hung if trying to switch to the value the switch was already at. So now, it will send back the status regardless if the switch changed or not. Also, if you send it anything other than your defined OFF and ON commands, it will just return the current status via MQTT so you can query it's current state. So, for what it's worth, below is a link to the one I compiled. If you don't mind the wifi LED not working it should work fine for you, however use at your own risk, don't blame me if your switch explodes after you install it. For reference, here are the pins used: |
Nice work. |
That pin mapping you posted doesn't seem right.
In your post this translates: |
I'm glad you're looking at adding the switch. I've had it working great for a few months now except for that green wifi LED. I did not know where to really put it in the code, but I thought I could toggle it on and off having 10 defined in the relay position. From seeing the mapping above, that makes no sense. These do work, for sure, though.
At least, the button does turn on/off the relay as expected and the orange power light lights up as it should. I really wasn't sure where to put the WiFi LED though. It will go into the "recovery" mode though if you hold the button in, just like the dimmers do. |
I'm going to recompile with pin 9 instead of 19 for the LED and see what that does.. |
Ok, my apologies, 9 as well as, for whatever reason, 19 controls the power LED. |
Ok, I was assuming it was the power LED that used the LED field and not the WiFi led function.
Thanks for figuring that out! With those values everything works perfectly. |
That makes sense! :) |
That will be awesome! I really didn't know what I was doing, just started from one and worked my way up until it did something. |
Whenever you can please test latest release (https://github.com/ljalves/hfeasy/releases/tag/0v9). |
The switch works great. Even the WiFi LED changes according to the setting!! :) I think you can officially call this one supported! |
Thanks for testing |
https://www.amazon.com/dp/B00N0S47NK/ref=twister_B07WPT7TTW?_encoding=UTF8&psc=1
I'm pretty sure it's using the same controller as the dimmer module
The text was updated successfully, but these errors were encountered: