Replies: 19 comments 1 reply
-
|
Just for reference: Issue already reported at #11349 but was not solved. Adding the label Help Needed due to there is no active development for Tuya drivers in Tasmota at this moment. Sorry. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Frist. Thx for the reply. I looked into the topic #11349 but the problem is different. I cant turn of the light´s at all at this moment. Not in the gui or on the physical nob on the outside. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Since my topic was closed by issue still persists, I'll share some updates from my side. My config is setup with following changes to Tasmota default:
Behavior is still erratic and I have yet to find a pattern in the logging. I'm not a dev, just a power user :) Unsuccesful turning off with physical button: Successful turning of using physical button Successful turning off with MQTT |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi, if the range of the device is 0 to 255 please try: |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi @Tortue95 This enable the behavior of @Daddel15 not being able to shut down via webinterface. This is with SetOption20 turned off btw. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Even when having below config and the correct lower limit values of 10, the result is still not working. Setting the dimmer to 80% and then pressing off button does not work. The dimmer goes down and shuts off for as a second, but after that he send the original value before turning off. Even though SetOption20 should prevent this from triggering the power, it does and the light goes back on at 80%... Addition: The sending of the last value before shutting off is something that only happens when the button is pressed. Not when a power off command is sent via web/mqtt. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hello, I admit that I don't understand what is happening, because nothing is sent from tasmota except the heartbeat, and at the end of the dimming as you say "Suddenly dimmer update to previous value before turning off" but it comes from the device not from tasmota... (you can see the sended command form tasmota in log with: "TYA: Send ...") Just for information, if i look the code, SetOption20 is not used with Tuya but SetOption54: allows to save the value of the dimmer from MCU in tasmota even when the light is OFF (the current documentation is not clear about it) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
In fact, this comes from the beginning: your device performs its dimming routine when it goes off and only after it executes the received command |
Beta Was this translation helpful? Give feedback.
0 replies
-
No that's also what I see. This is not something that tasmota triggers, but it is something it is not processing correctly when received. The MCU seems to sent the previous dim value after shutting down when using the physical button to turn off. Tasmota receives this and sets the dimmer value, but incorrectly reactivates the power as well.
Hearing this I would believe that SetOption54 is not working as it should. Because like you see in the logs, I receive the dimmer update back to 80% after shutting down from the MCU, but this also triggers a power switch action on the side of tasmota it seems. Or am I reading the sequence of the last actions wrong? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Here is a new log, same settings (20,54,131 on). Dimmer was at 1% so I set it to 80% waited a bit to see the heartbeats and then turned it off using the physical button. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
in fact it would seem that it is your MCU which turns the lamp back ON when it receives a heartbeat... it's curious. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Nice "feature" tuya .... :( |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
yes each manufacturer does a little what he wants... and does not necessarily respect the tuya protocol... |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I have no idea why.... I just updated to the lasted dev build 2022.01.3 and my dimmer work perfectly now.... The config that works for me is really just this, without any SetOption20,54,131 turned on: I also tested this on previous builds and then it failed, so no idea what they updated? There was a rewrite of the tuyaMCU to support ESP32, but I thought that was already in the previous build as well... |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
probably following this problem that I had raised : #14157 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I've started a re-factor of the TyaMCU module - the intent to make sure we ALWAYS wait for an ack to each command when we expect one, and don't send anything outside of the (poor) state diagram in the tuya docs. If anyone knows of one, let me know. Else I'll create a Node-red flow to do a simple simulation to check operation before attempting anything with a real device. I have asked a supplier for a dev device, but donations accepted :). Don't wanna destroy my WAF factor any further by completely removing a device from the new kitchen!. Brief plan: thoughts/comments welcome. p.s. Athom have just confirmed they will send me two 3 way switches to replace my dimmers until the development is completed successfully. However, shipping from China whilst under strict lockdown means it may be a few weeks before I can bench test. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Also posted in Discord: Tuya Help wanted: Does anyone have a Tuya MCU setup which is easy to serial flash (i.e. on the bench in bits)? I have re-worked some of the TuyaMCU driver to better adhere to the official Tuya state machine (like not send commands during startup phase, only send a command if the previous has been replied to, improve the protocol state machine to account for byte timeout, not bomb if a 0x55 is in the data (only reset state of we get 55 followed by AA), etc. However, I don't have a serial flashable device with Tuya to test on at the moment.... What I'd really like is someone who could build & flash and confirm I'm not going to render my device inoperable :). i.e. an initial sanity check & review. PM me or open an issue in my repo if you can help? (code is here https://github.com/btsimonh/Tasmota/tree/Tuya - reviews and comments welcome). Effectively the rework is complete and building ready for initial tests, but I can't brick my device as I'm not sure I can serial program them easily, and they are installed :(. Update: |
Beta Was this translation helpful? Give feedback.
1 reply
-
Beta Was this translation helpful? Give feedback.
-
|
@Daddel15 - would you be able to test the version here: |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@Daddel15 @Tortue95 @mvanlijden Please, help testing the Tuya Driver -> #15281 (comment) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
PROBLEM DESCRIPTION
A clear and concise description of what the problem is.
When the dimmer is turned of in Tasmota, light is still on in full brightness. In addition the dimming range is reversed aswell (should be very bright but is pretty dark in reality).
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255:Backlog Rule1; Rule2; Rule3:Status 0:weblogto 4 and then, when you experience your issue, provide the output of the Console log:TO REPRODUCE
Steps to reproduce the behavior:
applied template
{"NAME":"EDM-1WAA-EU","GPIO":[1,1,1,1,1,1,0,0,1,1,1,1,1,0],"FLAG":0,"BASE":54}
SetOption97 1
TuyaMCU 11,1
TuyaMCU 21,2
DimmerRange 10,1000
setoption54 1
setoption20 1
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
Light off in tasmota
Lights off in reality
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
I use parts from to different dimmers. I fried the actual dimmer of an old Maxcio dimmer (since then they updated the daughterboard with the controler so it cant be flashed easily). Since my daughterboard with the tasmota flashed chip survived I tried pluging this into the new dimmer and got this result.
(Please, remember to close the issue when the problem has been addressed)
Beta Was this translation helpful? Give feedback.
All reactions