Serialsend6 - comma-separated decimal send as binary #8937
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Alternative to #8920 (i.e. one or the other). Same use case - allowing sending of parameters using rules to binary serial devices e.g. #5737. I've noted that the mqtt response formats in HEX when serial is received after a binary message is sent - I don't think this should change so it's treated the same.
example:
serialsend6 255,85,5,5,220,10
An example rule that (should) allow the above device to work with vanilla tasmota + this PR:
rule1
on dimmer#state=0 do event setdimmer=5 endon
on dimmer#state>0 do backlog scale1 %value%,1,100,16,255; event udimmer endon
on dimmer#boot do backlog baudrate 9600; scale1 %value%,1,100,16,255; event udimmer endon
on event#udimmer do event setdimmer=%var1% endon
on event#setdimmer do serialsend6 255,85,%value%,5,220,10 endon
on power1#state=0 do event setdimmer=5 endon
on power1#state=1 do event setdimmer=%var1% endon
Checklist:
NOTE: The code change must pass CI tests. Your PR cannot be merged unless tests pass