Feature Request collection/list

[tozett]

ok. seems to be software configurable. riddle solved.
https://github.com/esp8266/Arduino/issu ... -167515482

[beic]

ok. seems to be software configurable. riddle solved.
https://github.com/esp8266/Arduino/issu ... -167515482

So, what will happen if in the future someone uses more ESPEasy and some devices will get the same MAC address?

[Drum]

No 2 devices should ever have the same MAC they are hard coded by the manufacturer. Because Espressif has more than 1 set of MAC addresses for the ESP8266 ( I have both 5C/5E and 60/62) it is possible to have 2 devices running ESPEasy with the same chipID. The chances are less than 1 in 281,474,976,710,656. ( feel free to check my math, I am not perfect ). I think you have better odds for winning the lottery, even the Italian lottery.

Where you may have a problem is your router may not be able to handle the number of IP addresses. A lot of carrier provided routers limit the number of connected devices, and really limit the number of manually assigned IP Addresses. If I remember correctly my current router(vodafone) is limited to 27 devices, and about 10 assigned addresses. Not enough, but the ESP devices do not need internet access so they can be on a separate network.

[beic]

No 2 devices should ever have the same MAC they are hard coded by the manufacturer. Because Espressif has more than 1 set of MAC addresses for the ESP8266 ( I have both 5C/5E and 60/62) it is possible to have 2 devices running ESPEasy with the same chipID. The chances are less than 1 in 281,474,976,710,656. ( feel free to check my math, I am not perfect ). I think you have better odds for winning the lottery, even the Italian lottery.

Where you may have a problem is your router may not be able to handle the number of IP addresses. A lot of carrier provided routers limit the number of connected devices, and really limit the number of manually assigned IP Addresses. If I remember correctly my current router(vodafone) is limited to 27 devices, and about 10 assigned addresses. Not enough, but the ESP devices do not need internet access so they can be on a separate network.

Thanks for clarifying it all!

[tozett]

this (bug-)fix didnt jumped onto the devs-feature-list by itself,
so i like to promote it again:

NTP code is blocking 1500ms in while-loop. please change!
http://www.esp8266.nu/forum/viewtopic.p ... =ntp#p9271

[Wallebalboa]

Feature request: Output-device (binary) and disable of "commands" to not defined GPIO.. (only MQTT actions)
too easy to make mistakes and to remember wich GPIO is connected to what HW.
ability to report configured output GPIO status to MQTT.
disable change of state on non configured GPIOs/devices. (to easy to turn on HW by mistake)
checkbox for inverted I/O (ex. opencollector)
ability to set names for states (1=on,up,open.. 0= off,down,closed)

example: carheater is connected to GPIO4 on node01 thru relay and opencollector driver.
reducing risk of mistakes..
* 0 = ON
* nothing but MQTT topic "node01/carheater/set/ "ON" would turn it on
* publishing "node01/carheater/state/ "ON"

easy to monitor in MQTT logs (compared to xxx/gpio04/1 wher you dont know if 0=ON)

[Wallebalboa]

more then 32 espeasy?
possibility to disable all communication exept MQTT (no need for unique unit #.) (same unitnumber crasch espeasy)
alternativly increase number of units to >32 (the old 640k problem? )

[id001]

Feature request: DS2423 support - 4kbit 1-Wire RAM with Counter https://www.maximintegrated.com/en/prod ... S2423.html

There is already support for 1-wire temperature sensors, but I would like to read my counter via ESP. Thank you!

[BertB]

You know, this is a discontinued chip?

[StephenF]

Feature Request; Day/Time Dummy (or Variable)

Hi, I will appreciate the addition of a Day/Time Dummy device. I would like to send a Day/Time for the rules at a specific time via MQTT preferably.

E.g.

On Clock#Time=[Dummy1#DayTime1] do // Irrigation starts at the defined time, e.g. "Mon,08:00"
gpio,14,1
endon

[beic]

Feature Request; Day/Time Dummy (or Variable)

Hi, I will appreciate the addition of a Day/Time Dummy device. I would like to send a Day/Time for the rules at a specific time via MQTT preferably.

E.g.

On Clock#Time=[Dummy1#DayTime1] do // Irrigation starts at the defined time, e.g. "Mon,08:00"
gpio,14,1
endon

Wrong category to request!

[reddo]

Feature request :

A PID controller with a PWM output, where also a minimal 'on' time can be set for the PWM so it can be used also for controlling boilers for heating (with normal unrestricted PWM it will pulse very quickly, which is fine for an electric heater but not for a gas fired one)

If implementend, an ESP8266 can be a very simple and flexible smart thermostat using a DS18B20 !

[loicwyn]

Hello guys,
Do you plan to support video & audio record on ESPEasy ? I think it might be a chalenge in term of HW capabilities to support that.
I would love to have this feature on ESP8266.

[hvdwolf]

Flexible programmable deep sleep possible?
(This is a rewrite of another post, which I now deleted, as I had not seen this collection list)

what I would like is the following: deep sleep from 07:00-23:00, active from 23:00 to 07:00 (of course time frame adjustable).
I want to use this for a PIR motion sensor system which shouldn't do anything during daytime. I can leave the ESP "on" during daytime but I prefer to have it to sleep to use as little energy as possible.

I have already found that deep sleep on the ESP is held by a uint32_t, with a max value of 4,294,967,295 microseconds which is slightly over 1 hour. Some people/posts report it sometimes doesn't work like a uint but like an int being 31 bits, so slightly over half an hour. I assume that's an error in software or hardware implementations, but actually I don't know.
So a direct option for "my demands" is not possible. I have seen posts on using an external RTC, or something like having the esp wake up every 60 minutes, update a counter, and go back to sleep.

What I am thinking off is more in the rules section.

There are time based rules so I wanted to know if something is possible like :

Code: Select all

On Clock#Time=All,07:00 do // every day at 07:00 hours do ...
 "set esp easy to deep sleep and wake up every 30 minutes to check the time"
endon

On Clock#Time=All,23:00 do // every day at 23:00 hours do ...
 "get esp easy from deep sleep and switch on necessary functions"
endon

But that would also require a flexible programmable deep sleep. Is that possible?

As a reference: Espimatic, another ESP8266 ino, uses a variable "backdoor" that can be checked and read/set. On every wakeup this value is checked/read in pimatic from a variable but could be initiated to other controllers using the protocols, or via rules on "this" or another espeasy. It will also help preventing you from "bricking" an espeasy: simply toggle the variable on your controller and the esp stays awake. This specific code can be found here.

[Elektrofreak]

Flexible programmable deep sleep possible?
(This is a rewrite of another post, which I now deleted, as I had not seen this collection list)

what I would like is the following: deep sleep from 07:00-23:00, active from 23:00 to 07:00 (of course time frame adjustable).
I want to use this for a PIR motion sensor system which shouldn't do anything during daytime. I can leave the ESP "on" during daytime but I prefer to have it to sleep to use as little energy as possible.

I have already found that deep sleep on the ESP is held by a uint32_t, with a max value of 4,294,967,295 microseconds which is slightly over 1 hour. Some people/posts report it sometimes doesn't work like a uint but like an int being 31 bits, so slightly over half an hour. I assume that's an error in software or hardware implementations, but actually I don't know.
So a direct option for "my demands" is not possible. I have seen posts on using an external RTC, or something like having the esp wake up every 60 minutes, update a counter, and go back to sleep.

What I am thinking off is more in the rules section.

There are time based rules so I wanted to know if something is possible like :

Code: Select all

On Clock#Time=All,07:00 do // every day at 07:00 hours do ...
 "set esp easy to deep sleep and wake up every 30 minutes to check the time"
endon

On Clock#Time=All,23:00 do // every day at 23:00 hours do ...
 "get esp easy from deep sleep and switch on necessary functions"
endon

But that would also require a flexible programmable deep sleep. Is that possible?

As a reference: Espimatic, another ESP8266 ino, uses a variable "backdoor" that can be checked and read/set. On every wakeup this value is checked/read in pimatic from a variable but could be initiated to other controllers using the protocols, or via rules on "this" or another espeasy. It will also help preventing you from "bricking" an espeasy: simply toggle the variable on your controller and the esp stays awake. This specific code can be found here.

This is what I need too! In my case it would be okay to manually trigger the deep sleep from external (e.g. via Plugin or HTTP) or to dis-/enable it with a command.

[wrbrower]

In the ESP Easy firmware it would be nice if the IP address of the ESP was dumped out the serial port on boot up after the IP address is assigned.
I am stuck with a cable modem router and it takes a long time to look up the IP address of a newly configured ESP Easy device after doing the initial 192.168.4.1 set up.

Thanks!

[paxi]

Typing "settings" doesn't do that? I don't use serial that much...

Also after the initial setup in AP mode you see the new IP in a link that takes you right to the "full" webinterface. Assign a fixed IP from there and you'll never have to touch you router.

[pwassink]

Typing "settings" doesn't do that? I don't use serial that much...

Also after the initial setup in AP mode you see the new IP in a link that takes you right to the "full" webinterface. Assign a fixed IP from there and you'll never have to touch you router.

Yes, but only when typed with a capital : Settings as input within the Serial connection from the Arduino IDE
it will tell you the most things you were looking for ..

[paxi]

I still don't see the need for your request.

You need that information only once, right?
Why should a (admittedly small) delay be introduced in the boot process that isn't needed in 99.9% of cases?
Just to save you typing a single word while sitting at the console anyways - to get something that's shown in the web UI also?

[psy0rz]

In the ESP Easy firmware it would be nice if the IP address of the ESP was dumped out the serial port on boot up after the IP address is assigned.
I am stuck with a cable modem router and it takes a long time to look up the IP address of a newly configured ESP Easy device after doing the initial 192.168.4.1 set up.

Thanks!

this is already implemented in espeasy version 2.

[Shardan]

In the ESP Easy firmware it would be nice if the IP address of the ESP was dumped out the serial port on boot up after the IP address is assigned.
I am stuck with a cable modem router and it takes a long time to look up the IP address of a newly configured ESP Easy device after doing the initial 192.168.4.1 set up.

Thanks!

This is implemented in ESPEasy V2

Anyways if you need to look up the IP addresses in your network you
may use an IP scanner. Here the "Angry IP Scanner" is used for that.
Maybe give it a try under http://angryip.org

Regards
Shardan

[AndrewZ]

Hope this is the right place to ask.
Will be great to have version number available via MQTT, the same way as RSSI and Uptime.
Many thanks to psy0rz for v2!

[Domosapiens]

I kindly request support for the A4988 stepper motor driver module.
https://www.pololu.com/product/1182

Simple control:
- select direction (DIR pin)
- give a number of pulses (STEP pin)

(also applicable for DRV8825, DRV8834 and generic two-pin (DIR/STEP) stepper motor drivers)



Cost €0.73, bought here:
https://nl.aliexpress.com/item/5pcs-lot ... Title=true

- the A4988 has a translator for step modes: one pulse,one step.
- select 1 out of 5 step modes (I suggest a hardwired choice: selector inputs pin MS1, MS2, and MS3)
- the Vreff adjustment enables Voltage/Current limitation to adapt to different stepper motors.

There is an AccelStepper library for Arduino
with automatic acceleration and de-acceleration capabilities.

This would be a great contribution to the ESPEasy Actuators capability !
Thank in advance,
Domosapiens

Reference:
https://www.letscontrolit.com/forum/vie ... per#p12052
https://www.letscontrolit.com/forum/vie ... per#p11668
https://github.com/laurb9/StepperDriver

[ohuf]

#1 - Please obfuscate ALL passwords on the config tab - not only the WiFiKey, but also the admin password and the "WPA AP mode key"

#2 - Make it possible to change the admin password from the console command line.

#3 - CONTINUE MAKING THE MOST INTERESTING CONFIG INTERFACES FOR THE ESP8266 !!!

Thank you !!!!!!

[beic]

#1 - Please obfuscate ALL passwords on the config tab - not only the WiFiKey, but also the admin password and the "WPA AP mode key"

#2 - Make it possible to change the admin password from the console command line.

#3 - CONTINUE MAKING THE MOST INTERESTING CONFIG INTERFACES FOR THE ESP8266 !!!

Thank you !!!!!!

Thumb for that and also obfuscate the Controller Password field too!

[NetEye]

I' am wondering if it is possible to get an formula field in the device edit page of the distance sensor HC-SR04 to correct the value a bit.
In my case I want to use it as an depth sensor.
Due to solfe the "20cm blind spot" by re-place the sensor and enter a formula to correct the height, for example with: %value%-25

[bobbybeans]

#1 - Please obfuscate ALL passwords on the config tab - not only the WiFiKey, but also the admin password and the "WPA AP mode key"

#2 - Make it possible to change the admin password from the console command line.

#3 - CONTINUE MAKING THE MOST INTERESTING CONFIG INTERFACES FOR THE ESP8266 !!!

Thank you !!!!!!

Thumb for that and also obfuscate the Controller Password field too!

thumbs up on this as well . this has been a glaring exploit and very bad as many peoples autofill save the non password fields which then saves this. now it can be scraped for passwords from an attacker

[JR01]

Today I saw a demo of the newish SAP IoT workbench on SAP Cloud Platform, (HCP renamed). They showed the creation of a sensor process, targeted for bus users, where an OAuth token is created for the thing, this then is cut and pasted into the thing's, setup, then communcates through mqtt to the sap platform.

Maybe we should have such a option to remove uid / pwd, but OAuth token based authentication for the thing to communcate to backend?

[bobbybeans]

#1 - Please obfuscate ALL passwords on the config tab - not only the WiFiKey, but also the admin password and the "WPA AP mode key"

#2 - Make it possible to change the admin password from the console command line.

#3 - CONTINUE MAKING THE MOST INTERESTING CONFIG INTERFACES FOR THE ESP8266 !!!

Thank you !!!!!!

Thumb for that and also obfuscate the Controller Password field too!

thumbs up on this as well . this has been a glaring exploit and very bad as many peoples autofill save the non password fields which then saves this. now it can be scraped for passwords from an attacker

Edit, I have build 147 and it now looks like its hidden in a standard password field however still not secure, if you go and inspect the element with any basic debugger it shows you the password [img][
Please see the picture the standard google inspect agent can get the password back

[psy0rz]

We COULD fix this, but then there are still countless other issues that need to be solved to make it really secure.

For example: We use http instead of https. Its possible to download the configfile, which contain the unhashed password as well. And there is a lot of functionality that is not password protected at all for various reasons.

If you're concerned about just the password, somebody should add a hash function to store the password securely. (but then still no https)

Otherwise just use a less important password.

I think the password protection is just there to prevent accidental modification by ignorant users that dont know whats going on. (family/co workers). Its not ment to be really secure.

Edwin

[bobbybeans]

lol touche
didn't even think of that as I was writing that however in the past I thought of that
but from what I read the https would increase the load on the tiny esp? right? as it has to decode /encode the certs

[BertB]

Is it possible to automate the setting of the DST bit?
It is not a secret when Daylight Saving Time starts and ends, so why not make the ESPEasy jump to summertime and back when the DST box is checked?

[paxi]

+1!

[AndrewJ]

+1

[wrbrower]

So appreciated!

In the ESP Easy firmware it would be nice if the IP address of the ESP was dumped out the serial port on boot up after the IP address is assigned.
I am stuck with a cable modem router and it takes a long time to look up the IP address of a newly configured ESP Easy device after doing the initial 192.168.4.1 set up.

Thanks!

This is implemented in ESPEasy V2

Anyways if you need to look up the IP addresses in your network you
may use an IP scanner. Here the "Angry IP Scanner" is used for that.
Maybe give it a try under http://angryip.org

Regards
Shardan

[Ton_vN]

At installation of the 'Mega-firmware' I have checked the box for DST, but starting 25th of March I don't see the expected 1hour-shift in time:
display in ESPEasy of Systemtime is still 'wintertime'.
Any additional action required, or need to wait a while till the default NTP-server switches time?

[Shardan]

At installation of the 'Mega-firmware' I have checked the box for DST, but starting 25th of March I don't see the expected 1hour-shift in time:
display in ESPEasy of Systemtime is still 'wintertime'.
Any additional action required, or need to wait a while till the default NTP-server switches time?

NTP servers usually do not send DST - they give the UTC only as they are usable worldwide.
So your device (ESP, PC, Laptop... whatever) has to take care of things like time zones and DST.

The advanced settings give you a possibility to adjust your time zone with "Timezone offset".
If you check the "DST" box it will simply add one hour (remember a display has a delay setting,
you have to wait until it refreshes to see the change).

I'd appreciate an automatic setting too - that's what this request is about.


Regards
Shardan

[Ton_vN]

My 'problem' is that the DST-box has been checked, but the extra hour is not added!
Local manipulation of time-offset should not be required to get the difference between Wintertime and Summertime.

[Shardan]

My 'problem' is that the DST-box has been checked, but the extra hour is not added!
Local manipulation of time-offset should not be required to get the difference between Wintertime and Summertime.

Which Version of ESPEasy do you run?

I've checked with R148 yesterday evening and it adds the hour when DST is checked, and vice versa.
On a LCD or OLED this change is visible with the next delay cycle so it may take a while.
On the main page of the ESP item it should be visible immediately.

Please note, that an automatic DST switching ist not built into ESPEasy at this time.
For changing between summertime and wintertime you have to check the DST box in summer and uncheck it for wintertime - manually.

Regards
Shardan

[JR01]

Hi, have a pool motor with ESP attached, some distance from my wifi point. I would like the ESP to switch motor on and off, under its own control, and not have the non-availability of the wifi, cause the ESP to reboot etc. What about a rule to switch wifi off, for say up to 6 hrs, and allow local rules based control only ?

[Ton_vN]

Related to DST.

My version is R146, at this moment just for experiments, not yet for 'serious' application.
Apperently need to upgrade ......

[papperone]

About DST I'd like to have the possibility to turn it on/off via rules, so it will be easy to have a global MQTT command sent from my server to all nodes to react on DST setting.

What I mean is that I'd like a way to turn DST ON or OFF on all my ESPEasy devices at same time, as it's pointless to have some only, and it's quite annoying to cycle trough all of them 2 times a year.
As well I'm puzzled how the DST should be changed in devices with Deep-Sleep enabled (I don't have any at the moment as I've only experiment with this feature a while ago but not yet used in my real setup)

[mrwee]

About DST I'd like to have the possibility to turn it on/off via rules, so it will be easy to have a global MQTT command sent from my server to all nodes to react on DST setting.

What I mean is that I'd like a way to turn DST ON or OFF on all my ESPEasy devices at same time, as it's pointless to have some only, and it's quite annoying to cycle trough all of them 2 times a year.
As well I'm puzzled how the DST should be changed in devices with Deep-Sleep enabled (I don't have any at the moment as I've only experiment with this feature a while ago but not yet used in my real setup)

To be honest, that seems like strange feature to me. In my mind NTP incl. DST should work automatically without any user-interaction just like any other NTP enabled device. When your device is in deep-sleep, it deep-sleeps and do not get any DST update. An NTP update should be performed when it takes up.

[papperone]

About DST I'd like to have the possibility to turn it on/off via rules, so it will be easy to have a global MQTT command sent from my server to all nodes to react on DST setting.

What I mean is that I'd like a way to turn DST ON or OFF on all my ESPEasy devices at same time, as it's pointless to have some only, and it's quite annoying to cycle trough all of them 2 times a year.
As well I'm puzzled how the DST should be changed in devices with Deep-Sleep enabled (I don't have any at the moment as I've only experiment with this feature a while ago but not yet used in my real setup)

To be honest, that seems like strange feature to me. In my mind NTP incl. DST should work automatically without any user-interaction just like any other NTP enabled device. When your device is in deep-sleep, it deep-sleeps and do not get any DST update. An NTP update should be performed when it takes up.

NTP does not carry DST info as these may vary depending on your country, as it's not starting/ending on the same day across the world and some countries does not even have the DST by law!
So I woudl prefer to control it as I described below as my MQTT Raspberry server is already setup with DST properly and thus I won't overload ESPEasy code to implement full world-wide DST code!

[grovkillen]

+1

[grovkillen]

I've now come to change my idea about this request with NTP with DST. I simply followed this guide:
https://www.interfacett.com/blogs/creat ... r-windows/
And I now have my MQTT broker and NTP server locally as the same computer and this will work with the DST built into Windows. Problem solved. Just to be sure to have my Windows computer sync with a internet NTP server (I do this with http://www.timesynctool.com/).

[neykov_t]

I kindly request support for the A4988 stepper motor driver module.
https://www.pololu.com/product/1182

Simple control:
- select direction (DIR pin)
- give a number of pulses (STEP pin)

(also applicable for DRV8825, DRV8834 and generic two-pin (DIR/STEP) stepper motor drivers)



Cost €0.73, bought here:
https://nl.aliexpress.com/item/5pcs-lot ... Title=true

- the A4988 has a translator for step modes: one pulse,one step.
- select 1 out of 5 step modes (I suggest a hardwired choice: selector inputs pin MS1, MS2, and MS3)
- the Vreff adjustment enables Voltage/Current limitation to adapt to different stepper motors.

There is an AccelStepper library for Arduino
with automatic acceleration and de-acceleration capabilities.

This would be a great contribution to the ESPEasy Actuators capability !
Thank in advance,
Domosapiens

Reference:
https://www.letscontrolit.com/forum/vie ... per#p12052
https://www.letscontrolit.com/forum/vie ... per#p11668
https://github.com/laurb9/StepperDriver

+ 1 +1

[houk008]

Feature-Request: Bridge betwen atmega/arduino/other microcontroller to domoticz via espeasy reading from uart.

Sending from microcontroller named values like
wind=value,gust=value,winddir=value\n
rain=vaule\n
lux=value\n
uv=value\n
lightning=value\n
or any other named value defined by field name and parsed from uart to domoticz idx device.
Of course with ability to deepsleep for minute or more, source device will send values over and over again every one second and esp will wake, read values and send it to domo and go to sleep.

This feature have great potential, from weather stations based on sensor like this https://www.sparkfun.com/products/8942 to complex usage with hand made custom solutions.

Or simply please add sparcfun weather station based on documentation to this sensors provided from sparcfun .
With esp going to deepsleep to save battery power there is no option for counting gust or rain properly and for that is my idea to read it from uart.

[nonflammable]

bump for GPIO toggle

Code: Select all

http://<ESP IP address>/control?cmd=GPIO,<pin>,TOGGLE

#57: https://www.letscontrolit.com/forum/vie ... ?f=2&t=736

[bobbybeans]

+1 for toggle