Feature Request collection/list

Message

nonflammable · #111 Post by **nonflammable** » 14 Jul 2016, 20:14

add HT16K33 support
eg.
https://learn.adafruit.com/adafruit-led ... t-backpack
or
https://learn.adafruit.com/adafruit-led ... 8x8-matrix

arduino library sources:
https://github.com/adafruit/Adafruit_LED_Backpack
https://github.com/adafruit/Adafruit-GFX-Library

datasheet:
https://cdn-shop.adafruit.com/datasheet ... 33v110.pdf

pmayer · #112 Post by **pmayer** » 15 Jul 2016, 11:46

Hi guys,

maybe I've overread it but is it possible to let espeasy drop the current IP/MAC and maybe the configured device number to mqtt? As the number of espeasy nodes rises it would be nice to know which device id's are already taken and which sensor has which IP. As I run the esp's in deep-sleep most of the time it also is possible, that they will get new IP's on reconnect.

Would be a very nice feature in my eyes, maybe inside the SystemInfo-Plugin?

regards,
Patrik

tozett · #113 Post by **tozett** » 23 Jul 2016, 09:38

make webserver port configurable: http://www.esp8266.nu/forum/viewtopic.p ... 8132#p8128

tozett · #114 Post by **tozett** » 15 Aug 2016, 14:24

i am missing a config-variable/field where i can set/mark the room and place, where the device is located.
i.e. LOCATION: _______

(i am alread on r121)...

(also for the further development, you made wiki-pages and supergood suggestions,
a debug/feature roadmap at one promiment place would be good, to check all the good work which is running over the time into ESPeasy by the devs...)

happytm · #115 Post by **happytm** » 15 Aug 2016, 18:22

Requesting support for :

Adafruit 12-Key Capacitive Touch Sensor Breakout - MPR121

It is I2C interface and good option to save pins on ESP8266.

https://www.adafruit.com/product/1982

tozett · #116 Post by **tozett** » 17 Aug 2016, 09:36

request support for 8-dot display with max7219 (SPI)

https://github.com/squix78/MAX7219LedMatrix

---update: there is room for improvement in the lib,
but it is running somehow. it would be WONDERFUL !!!!!!!!!!!!!!!
if i could attach the matrix (via SPI possible?) to the espeasy firmware as a device
to use all the wonderful features of ESPeasy with the matrix-display...

tozett · #117 Post by **tozett** » 19 Aug 2016, 09:51

look. isnt that nearly wonderful ?
(espeasy still missing as "home of control" )

tozett · #118 Post by **tozett** » 22 Aug 2016, 09:27

Bluetooth enable / Presence detection

http://www.esp8266.nu/forum/viewtopic.php?f=2&t=1886
https://www.happybubbles.tech/presence/detector
http://www.aliexpress.com/wholesale?cat ... E+breakout

poe · #119 Post by **poe** » 23 Aug 2016, 15:25

A PID Device.
Device needs 6 parameters P, I, D, setpoint, Device(actual value) and GPIO for output. A checkbox to determine if it is for heating or cooling would also be nice.
I am aware of the limited power of the processor, but for many purposes a cycle time of 5-10 seconds would be sufficient.

I think it could be done with rules and a couple of dummy devices. But would be nice to have room for DS18B20 (actual value) Switch(to monitor output) and Display.

I'm not ready to make it myself yet, but i'm more than willing to help testing.

Later a simple on/off device would be nice. Source device, Setpoint, hysteresis, GPIO for output and a heat/cool switch should be enough.

/Preben

Drum · #120 Post by **Drum** » 28 Aug 2016, 11:09

pmayer wrote:Hi guys,

maybe I've overread it but is it possible to let espeasy drop the current IP/MAC and maybe the configured device number to mqtt? As the number of espeasy nodes rises it would be nice to know which device id's are already taken and which sensor has which IP. As I run the esp's in deep-sleep most of the time it also is possible, that they will get new IP's on reconnect.

Would be a very nice feature in my eyes, maybe inside the SystemInfo-Plugin?

regards,
Patrik

IP address posted in mqtt would save a lot of time fixing problems.

Drum · #121 Post by **Drum** » 28 Aug 2016, 11:16

when you are using deep sleep the uptime function does not work. Perhaps a counter which shows how many times the unit has slept since the last hard boot/watchdog reset is possible? or some other indication of how long it has been running. I think this would make it easier to identify problems with units using deep sleep.

Drum · #122 Post by **Drum** » 28 Aug 2016, 12:00

Option to rather than browse for file to upload, have a preset location and file name on the controller. There would probably need to be a request / response message especailly when using deep sleep. For example, Node-red can monitor a folder for file changes. When it sees a change and receives a check for update request, it sends back a command to update firmware, or a no update msg if there is no change. peolle would have to be careful with this, as they have to when uploading firmware to 1 unit. The difference is one of scale. Yes they can update all units of 1 type at once, they can screw them all up at once as well. I think the file name check would help too. File must be in the correct folder with correct name.

Along with this, a version option in the system plugin would be useful if not critical, perhaps unit sends version, controller checks if it is the preset current version and sends upgrade or noupgrade back. If there is a problem the controller can easily identify units which continue to have old versions for further troubleshooting.

I think the automatic or semi-automatic upgrade function is necessary to move into a production environment.

anarro · #123 Post by **anarro** » 29 Aug 2016, 09:43

Hi,

If your like the idea and want to add... the option to send http PUT commands, please.

I use it with this funcition in Connand.ini file.

Code: Select all

  if (strcasecmp_P(Command, PSTR("SendToPUT")) == 0)    //ANTONI
  {
    success = true;
    String strLine = Line;
    String host = parseString(strLine,2);
    String port = parseString(strLine,3);
    int pathinipos = getParamStartPos(strLine,4);
    int pathfinpos = getParamStartPos(strLine,5);
    String path = strLine.substring(pathinipos,(pathfinpos-1));
    String msgs = parseString(strLine,5);
    WiFiClient client;
    if (client.connect(host.c_str(), port.toInt()))
    {
        client.println("PUT " + path + " HTTP/1.1");
        client.println("Connection: keep-alive");
        client.println("Host: " + host);
        client.println("Content-Type: text/plain;charset=UTF-8");
        client.print("Content-Length: ");
        client.println(msgs.length());
        client.println();
        client.println(msgs);

        unsigned long timer = millis() + 200;
        while (!client.available() && millis() < timer)
          delay(1);
  
        while (client.available()) {
          String line = client.readStringUntil('\n');
          if (line.substring(0, 15) == "HTTP/1.1 200 OK")
            addLog(LOG_LEVEL_DEBUG, line);
          delay(1);
        }
        client.flush();
        client.stop();
    }
  }

Thank you,
Antoni

big_alex · #124 Post by **big_alex** » 03 Sep 2016, 12:45

There have already mentioned, I wish to join the request. PID function allows you to save up to 30% of electricity when the heater control.

fluppie · #125 Post by **fluppie** » 04 Sep 2016, 15:36

poe wrote:A PID Device.
Device needs 6 parameters P, I, D, setpoint, Device(actual value) and GPIO for output. A checkbox to determine if it is for heating or cooling would also be nice.
I am aware of the limited power of the processor, but for many purposes a cycle time of 5-10 seconds would be sufficient.

I think it could be done with rules and a couple of dummy devices. But would be nice to have room for DS18B20 (actual value) Switch(to monitor output) and Display.

I'm not ready to make it myself yet, but i'm more than willing to help testing.

Later a simple on/off device would be nice. Source device, Setpoint, hysteresis, GPIO for output and a heat/cool switch should be enough.

/Preben

Maybe you need to check the thermostat function of this ESP8266 board: https://github.com/openenergymonitor/ES ... elay_Board

And also this code: https://github.com/mhaas/Coffee-Arduino ... CP3208_PID

jgrad · #126 Post by **jgrad** » 05 Sep 2016, 10:29

Feature-Request: support for multiple access-points

Currently only one WIFI accesspoint can be defined in ESPeasy configuration. New feature is to support multiple pairs (SSID+pass).
Where it is usable:
-at deployment: you can configure ESPeasy units on one location with WIFI parameters which are available on target deployment location
-support for backup: in case one WIFI network is down, ESPeasy can switch to alternative WIFI network.

daxkamala · #127 Post by **daxkamala** » 06 Sep 2016, 11:42

I would like to be able to set Dummy Device variables from MQTT / HTTP.
This would allow for rules that can be changed externally.
I'm thinking specially of timers but pwm or servo could be useful too.

As a kludge, is it possible to read a level set for pwm or servo motor control?
The docs only show how to set but not to read.

guz · #128 Post by **guz** » 06 Sep 2016, 17:07

I'd like a new function in rules to put espeasy in deep sleep for x seconds.

On Clock#Time=All,01:00 do // every day at 01:00 hours put esp in deepsleep for 3 ours
deepsleep,10800
endon

overdrive · #129 Post by **overdrive** » 08 Sep 2016, 13:14

Hello,
I think i would be helpful, if you use more the one device, to Include the device name in the Node Liste table in the main menu.

shubell · #130 Post by **shubell** » 08 Sep 2016, 14:37

what about the ability to control the little led on the esp?

tozett · #131 Post by **tozett** » 08 Sep 2016, 20:39

SPifFS DATA Folder (in source) for upload files with arduino-ide or fs-explorer

like explained here:
http://www.esp8266.com/viewtopic.php?f=32&t=10081

costo · #132 Post by **costo** » 17 Sep 2016, 13:55

As we use NTP time servers to sync the ESPEasy time we already have all the information for Date and Time in the FEATURE_TIME definitions, though only %systime% variable is used and implemented. I think it would just use a relatively small amount of extra memory to add the %sysdate% variable and a %sysdow% variable.

This makes it not only possible to use the OLED display as a real clock with Time, Date and Day-Of-Week information, this variable could probably also be used in the rules section to do actions only on specific days of the week.

I pledge for adding the %sysdate% (and %sysdow%) variable(s) to the tools of ESPEasy.

tozett · #133 Post by **tozett** » 26 Sep 2016, 12:59

Chip-id is the last 3 doubles of the MAC-Adress,
but shown on web-gui as integer. makes this doubling somehow invisible..

https://github.com/esp8266/Arduino/issues/921

for me i would be helpful, if the chip-id on the homepage of ESPeasy is
not only shown as integer, but also as HEX-Mac-portion.

this way i could see the analogy of the ID and more easy identify my devices.

as small wish on a long grown list..hope the dev still reads here..

beic · #134 Post by **beic** » 26 Sep 2016, 13:16

tozett wrote:Chip-id is the last 3 doubles of the MAC-Adress,
but shown on web-gui as integer. makes this doubling somehow invisible..

https://github.com/esp8266/Arduino/issues/921

for me i would be helpful, if the chip-id on the homepage of ESPeasy is
not only shown as integer, but also as HEX-Mac-portion.

this way i could see the analogy of the ID and more easy identify my devices.

as small wish on a long grown list..hope the dev still reads here..

There are two MAC address shown, Client and AP Mode...so, the ChipID would come from?!

Martinus · #135 Post by **Martinus** » 26 Sep 2016, 15:19

tozett wrote:hope the dev still reads here..

I do, but available time is sometimes an issue.

Currently trying to investigate, build and test some ways to migrate my existing Nodo Small units to 'shared ESP solutions'. Lot's of ideas, so little time...

So i've launched my very own private 'Nodo Small revival project' some weeks ago. I'll launch a new topic today and see if someone else shares some interest. Likely only dutch or belgium citizens as the Nodo Project was a dutch project only. Checkout http://www.nodo-domotica.nl

beic · #136 Post by **beic** » 26 Sep 2016, 15:22

Martinus wrote:
tozett wrote:hope the dev still reads here..
I do, but available time is sometimes an issue.

Currently trying to investigate, build and test some ways to migrate my existing Nodo Small units to 'shared ESP solutions'. Lot's of ideas, so little time...

So i've launched my very own private 'Nodo Small revival project' some weeks ago. I'll launch a new topic today and see if someone else shares some interest. Likely only dutch or belgium citizens as the Nodo Project was a dutch project only. Checkout http://www.nodo-domotica.nl

Is there any chance to give users the compiled binary releases like in previous versions (R108 and R120) as on Wiki page is?

Thank you!

tozett · #137 Post by **tozett** » 28 Sep 2016, 09:31

beic wrote: There are two MAC address shown, Client and AP Mode...so, the ChipID would come from?!

on my esps, the last 3 segments are identical on both, CLIENT ant AP. (only the first parts are different)

beic · #138 Post by **beic** » 28 Sep 2016, 10:38

tozett wrote:
beic wrote: There are two MAC address shown, Client and AP Mode...so, the ChipID would come from?!
on my esps, the last 3 segments are identical on both, CLIENT ant AP. (only the first parts are different)

In my case, only the first part (first two characters) are different the rest of them are all identical.

tozett · #139 Post by **tozett** » 29 Sep 2016, 10:12

i checked all my 8 wemos-boards. all the same.
only first part different, everything the same.
means: the same last 3 parts of the mac for STA+AP.
look:

beic · #140 Post by **beic** » 29 Sep 2016, 10:58

tozett wrote:i checked all my 8 wemos-boards. all the same.
only first part different, everything the same.
means: the same last 3 parts of the mac for STA+AP.
look:

Similar looking here too...

Code: Select all

STA MAC:	5c:xx:xx:xx:xx:f8
AP MAC:	5e:xx:xx:xx:xx:f8

tozett · #141 Post by **tozett** » 29 Sep 2016, 11:09

ok. seems to be software configurable. riddle solved.

https://github.com/esp8266/Arduino/issu ... -167515482

beic · #142 Post by **beic** » 29 Sep 2016, 11:16

tozett wrote: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 · #143 Post by **Drum** » 29 Sep 2016, 14:07

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 · #144 Post by **beic** » 29 Sep 2016, 14:31

Drum wrote: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 · #145 Post by **tozett** » 03 Oct 2016, 13:56

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 · #146 Post by **Wallebalboa** » 11 Oct 2016, 16:11

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 · #147 Post by **Wallebalboa** » 11 Oct 2016, 16:16

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 · #148 Post by **id001** » 06 Nov 2016, 19:46

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 · #149 Post by **BertB** » 06 Nov 2016, 22:00

You know, this is a discontinued chip?

StephenF · #150 Post by **StephenF** » 14 Nov 2016, 20:35

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 · #151 Post by **beic** » 14 Nov 2016, 22:51

StephenF wrote: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 · #152 Post by **reddo** » 27 Nov 2016, 00:56

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 · #153 Post by **loicwyn** » 30 Nov 2016, 17:48

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 · #154 Post by **hvdwolf** » 02 Dec 2016, 16:04

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 · #155 Post by **Elektrofreak** » 03 Jan 2017, 08:14

hvdwolf wrote: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 · #156 Post by **wrbrower** » 26 Feb 2017, 16:24

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 · #157 Post by **paxi** » 26 Feb 2017, 18:37

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 · #158 Post by **pwassink** » 02 Mar 2017, 00:13

paxi wrote: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 · #159 Post by **paxi** » 02 Mar 2017, 08:13

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 · #160 Post by **psy0rz** » 04 Mar 2017, 13:38

wrbrower wrote: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.

Who is online