-
Notifications
You must be signed in to change notification settings - Fork 5
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
Pid branch to address issue #15 #16
base: pid_branch
Are you sure you want to change the base?
Conversation
That all looks ok, but I am not able to test it at the moment. Do you feel you have given it sufficient testing? |
From experience I can hardly answer "yes" to this question in general. Here's what I can say:
|
That's great. Have you been able to test setting parameters via MQTT? I don't think it is necessary to test them all, if you check a couple of them I will check the code changes carefully so the rest should be ok |
I'm only setting them via MQTT. That worked fine. |
OK, are you happy for me to merge it now or is there anything else you want to do? |
I think it's fine. I'll then also send the PR to arendst/development, as @ascillato suggested, right? |
Great, Thanks 👍 |
For the record: the PR against arendst/Tasmota is here: arendst#10412 |
I understand the confusion early on in the issue now, I didn't realise that the pid branch had been incorporated into the arendst code. When I initially attempted to get it merged it was ignored, if I remember correctly. |
I've had some discussion with Theo in the other PR, that I've submitted. I was not really sure about the Timeprop_Command in xdrv_91_timeprop.ino ( Sonoff-Tasmota/sonoff/xdrv_91_timeprop.ino Line 152 in 2fef64d
Functionality remained in place when I removed it. It looks like it was meant to receive commands for directly altering timeprop functionality. What shall I do about it? xdrv_92_pid.ino contains two lines to publish PID power: Sonoff-Tasmota/sonoff/xdrv_92_pid.ino Line 339 in 2fef64d
I've barred that behind an ifdef for backwards compatibility, as I've now managed to place the PID information into one JSON inside the /SENSOR topic (as I wanted to do years ago, but eventually had to face that I had no time). It probably be easier to discuss one sole line of patches in the other PR, right? |
Description:
Related issue (if applicable): fixes #
Checklist: