You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 24, 2022. It is now read-only.
I tried the rf file today with a remote here and I had a couple of issues. I was able to fix them myself and would like to upload a pull request. or I can just send you my changes.
last brightness and last binary don't seem to be filled and used. This causes problems when turning off with the remote so it wouldn't update esp and HA.
the brightness value that is sent over serial is a hex percentage. Hex 64 = 100 which I can see the confusion. So the line that is round (brightness/64) should be just brighness/100 since esphome is looking for a number between 0 and 1.
I set a variable called isReceivedBrightness when receiving a value from the dimming/rf chip. This way I don't send it back over serial to the same chip that sent it to esp.
Yaml should have default_transition_length: 0s as transitions are handled by the dimming chip on the D1.
I tried the rf file today with a remote here and I had a couple of issues. I was able to fix them myself and would like to upload a pull request. or I can just send you my changes.
last brightness and last binary don't seem to be filled and used. This causes problems when turning off with the remote so it wouldn't update esp and HA.
the brightness value that is sent over serial is a hex percentage. Hex 64 = 100 which I can see the confusion. So the line that is round (brightness/64) should be just brighness/100 since esphome is looking for a number between 0 and 1.
I set a variable called isReceivedBrightness when receiving a value from the dimming/rf chip. This way I don't send it back over serial to the same chip that sent it to esp.
Yaml should have default_transition_length: 0s as transitions are handled by the dimming chip on the D1.