Max Prokhorov
Max Prokhorov
Oops, this was missed in the relays update quite a while. Dummy relays are no longer used, and it is a different 'provider' for the specific relay. https://github.com/xoseperez/espurna/blob/9d4ef1a38690252ff3e2ead31b14689ee9cb3d7f/code/espurna/relay.cpp#L898-L945 STM's relay...
fwiw, current version *does* scan all declared schedules for the specified action target-id and launches the last one but, only when there's a schedule restore setting on https://github.com/xoseperez/espurna/blob/e22f67e5d61ce8c3c1eb1f9a50f2d6261b8b8d57/code/espurna/scheduler.cpp#L65 https://github.com/xoseperez/espurna/commit/e22f67e5d61ce8c3c1eb1f9a50f2d6261b8b8d57#diff-e8b9a5d04af16462e032b4ceb5900c29571415364a39b566b9ca03ac55749fcf
No. I also did a double-check, we don't have anything related to AT commands handling atm. Did you mean to make the port?
Most of the code is already there. SC-specific support consists of comms.ino + serial link helper functions that talk through the AT commands, everything else is *supposed* to be a...
> Can I set the DIGITAL_PIN to be inverted so it shows 0 even though the input is actually LOW and then shows 1 when HIGH? > > I did...
Could have another sensor modeling the button one. Previous EventSensor used digitalRead right from ISR function: https://github.com/xoseperez/espurna/blob/62ad7da332f3f904ad8241a2b738be9820b196e4/code/espurna/sensors/EventSensor.h#L159-L162 But, if the button model works, might re-do that with that one instead...
INVERT option for buttons would be setting a fixed LOW or HIGH default mode? Config above sets BOOT. And there is DIGITAL#\_DEFAULT_STATE (config says 1, but it is really means...
> So would setting the DEFAULT_STATE LOW mean that an input that was at 3V would actually represent OFF and taking the input to 0V would then represent ON? (If...
See https://github.com/xoseperez/espurna/pull/2116 (+ subsequent https://github.com/xoseperez/espurna/commit/2e891e3129133ea5025547d730682c1c4c162c26) This was discussed out of the issue tracker - https://gitter.im/tinkerman-cat/espurna?at=5e206b6d0dbd9379ed470747 Main culprits: - Arduino Core 2.3.0 only starts running initialization code at around 243msec after...
Likely the one after the next one.