Espeasy: Add proper checks and show warnings to users against incorrect configuration

Created on 15 Feb 2018 · 6Comments · Source: letscontrolit/ESPEasy

[x] Tell user that PulseCounter only works on task 1-4 if configured on task 5-12
[x] Do not use same name of tasks
[ ] When changing a name which is used in some rule, add a warning
[ ] Add a warning when a hostname cannot be resolved
[ ] Add a warning when a device cannot be detected in a plugin/task (e.g. I2C devices)
[ ] Add warning/error when delay is set to a too low value in a plugin/task
[ ] Max length on task namn, value name
[x] Check that task and value name is different
[x] Check for non valid chars in names
[ ] Validate unit number
[x] Show a warning when performing OTA on a 1MB flash device
[x] Set msg delay to 100 ms when using a switch
[x] Check IP settings for all values be filled or none (DHCP)

Frontend UX In Progress Feature Request

Source

tedenda

👍2

All 6 comments

Also good to check:

Do not use same name of tasks.
When changing a name which is used in some rule, add a warning.
Add a warning when a hostname cannot be resolved.
Add a warning when a device cannot be detected in a plugin/task (e.g. I2C devices)
Add warning/error when delay is set to a too low value in a plugin/task.

TD-er on 15 Feb 2018

👍1

Length of task name, value name should also be included in the scope. Also it's not recommended to have the same name for task and value. Spaces is names are also a no-go.