Ouput test branch to increase resolution of actor output

[avollkopf]

@brackendalebrewing, although, no new issue has been created, I am working on a feasibility version for your request on the actor output resolution.

There is one branch for the server and another for the UI

A variable self.output and self.outputmax has to be used in a new sensor if this feature is used. There is an example in the mqtt folder -> MQTT actor (output).

It has an action to set power or / and output and you can define the max output value.

-> I have not yet tested a logic, but a modified / new logic plugin needs to set the output instead of the power if you want to use this feature.

The UI is also modified -> As powerslider you can define power or output.

Please try and give feedback, if this is something you can work with.

Server
UI

Alex

[brackendalebrewing]

Hi Thank you for the update. I will review/try as soon as I can. Work/business is keeping me very busy at the moment. Thanks Andy

…

On Sun, 11 Aug 2024 at 21:58, Alexander Vollkopf ***@***.***> wrote: @brackendalebrewing <https://github.com/brackendalebrewing>, although, no new issue has been created, I am working on a feasibility version for your request on the actor output resolution. There is one branch for the server and another for the UI A variable self.output and self.outputmax has to be used in a new sensor if this feature is used. There is an example in the mqtt folder -> MQTT actor (output). It has an action to set power or / and output and you can define the max output value. -> I have not yet tested a logic, but a modified / new logic plugin needs to set the output instead of the power if you want to use this feature. The UI is also modified -> As powerslider you can define power or output. Please try and give feedback, if this is something you can work with. Server <https://github.com/PiBrewing/craftbeerpi4/tree/outputtest> UI <https://github.com/PiBrewing/craftbeerpi4-ui/tree/outputtest> Alex — Reply to this email directly, view it on GitHub <#145>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJUAW6U6A4MHBI6DSE4O3ULZRA6HNAVCNFSM6AAAAABMLNL2P2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ3DAMBUGE4DANY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[brackendalebrewing]

Subject: Re: Update on Actor Output Resolution Feature Hi Alex, Thanks for the update and for working on this feature. I think the modification you've made will work well for what I need. I'll update you as soon as I modify and test my plugins with this new setup. I appreciate your efforts and will keep you posted on how it goes. Best regards, Andy

…

On Mon, 12 Aug 2024 at 12:06, a Coop ***@***.***> wrote: Hi Thank you for the update. I will review/try as soon as I can. Work/business is keeping me very busy at the moment. Thanks Andy On Sun, 11 Aug 2024 at 21:58, Alexander Vollkopf ***@***.***> wrote: > @brackendalebrewing <https://github.com/brackendalebrewing>, although, > no new issue has been created, I am working on a feasibility version for > your request on the actor output resolution. > > There is one branch for the server and another for the UI > > A variable self.output and self.outputmax has to be used in a new sensor > if this feature is used. There is an example in the mqtt folder -> MQTT > actor (output). > > It has an action to set power or / and output and you can define the max > output value. > > -> I have not yet tested a logic, but a modified / new logic plugin needs > to set the output instead of the power if you want to use this feature. > > The UI is also modified -> As powerslider you can define power or output. > > Please try and give feedback, if this is something you can work with. > > Server <https://github.com/PiBrewing/craftbeerpi4/tree/outputtest> > UI <https://github.com/PiBrewing/craftbeerpi4-ui/tree/outputtest> > > Alex > > — > Reply to this email directly, view it on GitHub > <#145>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AJUAW6U6A4MHBI6DSE4O3ULZRA6HNAVCNFSM6AAAAABMLNL2P2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ3DAMBUGE4DANY> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[avollkopf]

Thanks for the reply. Witing for your feedback. I am sure, the code for server and UI needs a bit more finetuning, but this can be done, once you conform it is working for your application.

[avollkopf]

Since there is no feedback yet, I assume this is not relevant anymore. If there is no further action on this issue by the end of November, I will close the issue and 'retire' the corresponding branches.

[brackendalebrewing]

I have been very busy with work. I apologize for not following up. The system you devised works very well for me. I believe it it adds a flexibility that is valuable. Thank you for your work. If I can help in any way please let me know. Thanks Andrew

…

On Mon, Nov 25, 2024, 1:17 PM Alexander Vollkopf ***@***.***> wrote: Since there is no feedback yet, I assume this is not relevant anymore. If there is no further action on this issue by the end of November, I will close the issue and 'retire' the corresponding branches. — Reply to this email directly, view it on GitHub <#145 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJUAW6XC362FVY5O4QDQUKD2CNZWFAVCNFSM6AAAAABMLNL2P2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJYHA2DCMBUGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>