Enable multiple Digital & Events

[pilotak]

I know that there is going to be support for specifying all the things dynamically through browser but before that here is enhancement to support it now. This would also help for anyone finding #1815 as there is no code provided, only guidance

[pilotak]

The only thing i don't know is how to set pwrRatioE and pwrResetE in web-config for each sensor separately

[mcspr]

pwrRatioE<index>? where index is just a _sensors position
Reset & calibration are a strange ones. Wouldn't it be easier to use direct action calls instead of going through settings and then purging keyvalues?

You might want to also add mapping from the old ..._PIN to the ...1_PIN

[pilotak]

pwrRatioE<index> is not a problem to add but how to hide the unused in browser - there is only section hiding (in html there will be all 8 listed but lets say you have only two setup which would need display: inherit).
How do i do "direct action calls"?

[mcspr]

Append html settings section programmatically?

By direct actions I meant ws actions:

espurna/code/espurna/relay.ino

Line 698 in fbf2b71

void _relayWebSocketOnAction(uint32_t client_id, const char * action, JsonObject& data) {

espurna/code/html/custom.js

Line 430 in fbf2b71

function sendAction(action, data) {

(thus directly requesting required actions instead of using one-shot settings)

[pilotak]

ok, what if i remove pulse-meter from this PR and create a separate once it's done?

[mcspr]

sure, that will work

[mcspr]

You might want to also add mapping from the old ..._PIN to the ...1_PIN

Btw, by that I meant to add something here https://github.com/xoseperez/espurna/blob/dev/code/espurna/config/deprecated.h
to remap old defines into the new one + show a warning. Release notice will be there too, but at least VSCode / Atom with PlatformIO will track those messages and show them after build completes if someone uses those in custom header

[pilotak]

@mcspr any other request? i think it can be changed otherwise

[mcspr]

Don't think so. Any other changes can be made in bulk with other sensors (and maybe even move sensor init to sensor classes themselves)
Sorry for the delay, was I bit busy past 2 weeks.

Also, cc @lbdroid mentioned this #1529 (comment)

[pilotak]

That's ok, can this be merged?

[mcspr]

Done.
I have noticed some pulsemeter changes left over, but they just chain back into themselves and don't change the existing behaviour

[pilotak]

I know let's call them preparation for future