Proddy
Proddy
@mheyse - I'm getting compile errors when compiling with `-DEMSESP_TEST`. It happens here: ``` #if defined(EMSESP_STANDALONE) || defined(EMSESP_TEST) #include #endif ``` perhaps a namespace clash with `Error`
Ok. This was an idea from @bbqkees so I'll wait until we have clear requirements.
Still not sure what this would look like (UI wise) or whether it's practical. What does the community think? Let me know....
the error code is fetched on EMS-ESP startup and when there's a change. You can try and force the fetch yourself using the scheduler, and send a read request to...
@MichaelDvP as a possible new addition, we could add a new command called 'read' to each device, so you can 'boiler/read' with value '12' (for example) from the Scheduler. Not...
Probably bad mapping indeed. Do you see any errors or warnings in the log? Can you trace the telegrams when you change it manually? https://emsesp.github.io/docs/Troubleshooting/#changing-a-value-on-an-ems-device-doesnt-work
> Thanks, the first command is same as `boiler/reset maintenance`, I'll add `history` option to the `boiler/reset` command. @proddy Should we change the text from `maintenance` to `message` or add...
> > yes, let's rename! > > Hmm, i see that maintenance reset also verifies the reset by reading the maintenance message, that is not nessesery for message reset, so...
@sciurius could you find out?
fixed by Michael in dev