Max Prokhorov

Results 502 comments of Max Prokhorov

Interval is there based on the SDK docs and some feedback at the esp8266/Arduino repo. We can't continuously read ADC, WiFi driver will lose its mind and break since we...

https://github.com/xoseperez/espurna/commit/5f6df82110573f25ca0a15003ff4e22efcee9a94 solves the logging part with the use of terminal command WebUI may use some kind of API for that

> Alternativ you could have a look at ESPHome, which I have been using: https://esphome.io/components/sun.html > > Implementation here: https://github.com/esphome/esphome/blob/dev/esphome/components/sun/sun.cpp thanks for link, I do remember looking at that too...

> The idea is still to not re-write the schedule, but to create a new event type that will replace the time of day one. btw I have scrapped that...

+1, for the float instead of int for measurements and calibration but, version bump should probably for other number than just the patch (either 2.0.0 or 1.2.0) > They're not...

Let me rephrase - you don't *have to use volatile* nor does it use mean operation will be in sync / atomic. In ESP case, we just end up with...

'volatile' in language meant to signify two things - order of operations (aka serialization) and explicitly tell the compiler it *should not* optimize reads or writes. When you access global...

Based on: https://www.espressif.com/sites/default/files/documentation/2c-esp8266_non_os_sdk_api_reference_en.pdf **3.5.52.** *wifi_set_macaddr* And https://github.com/esp8266/Arduino/issues/413#issuecomment-458551253 Settings are driven through a C++ class, so some adjustments need to happen there so it could work without it (or at least...

Follow-up for the above https://github.com/esp8266/Arduino/issues/8554#issuecomment-1162376481 https://github.com/xoseperez/espurna/blob/4f22960a90408ebce1f4a38530a290818172ceab/code/espurna/wifi.cpp#L1532 At least for now, modifying the source is the way. Meaning here, just before the connection happens where we definitely know interface is UP...

> So I assuming this issue is maybe related to low quality copy sensors. Closing? This, plus unexpected behaviour with parasite / non-parasite power modes as it turns out. Or,...