Page 3 of 4
Re: Feature Request collection/list
Posted: 12 May 2016, 09:49
by tozett
SendtoUDP in Rules:
i wish a function/explanation how to use
special-characters in SendToUDP strings.
i have an example here:
http://www.esp8266.nu/forum/viewtopic.php?f=4&t=1518
in the rules window, the string is not enclosed in ""/'' or something like this.
so (if it is possible) how do i send \n\r or hex-codes?
Re: Feature Request collection/list
Posted: 29 May 2016, 09:01
by msev
KY-40 rotary encoder. Would be super nice for a thermostat setpoint project. Like here:
https://mydiyelectronics.wordpress.com/ ... y-encoder/
Re: Feature Request collection/list
Posted: 29 May 2016, 10:05
by manjh
Re: Feature Request collection/list
Posted: 29 May 2016, 10:33
by tozett
i want nice graphs from my temp values,
so i wanted to send http to influxdb (and grafana for graphs)
as far as i can see up to r107, i cannot use "sendToHTTP" in the rules section for the needed string:
example string to push values via http to influxdb (directly from espeasy, without curl):
Code: Select all
curl -i -XPOST 'http://localhost:8086/write?db=mydb' --data-binary 'cpu_load_short,host=server01,region=us-west value=0.64 1434055562000000000'
but EspEasy R107 says, only this is possible:
Code: Select all
// SendToUDP <ip>,<port>,<message> sample: SendToUDP 192.168.0.123,65500,Hello 15
// SendToHTTP <ip>,<port>,<path> sample: SendToHTTP 192.168.0.8,8080,/json.htm
maybe the dev are interest to put the influxdb option into ESPeasy?
here i found a lib:
https://hwwong168.wordpress.com/2015/11 ... -influxdb/
https://github.com/hwwong/ESP8266Influxdb
and this is one example
graph from grafana, cool?
Re: Feature Request collection/list
Posted: 29 May 2016, 12:20
by JR01
@tozett, you can do this with nodered?
Re: Feature Request collection/list
Posted: 29 May 2016, 14:30
by tozett
actually, as the ESPeasy firmware seems some lack to publish values with the sendtohttp to the influxdb,
i searched for other ways to get the grafana -graphs.
as is set most of the espeasy-modules to mqtt publish their values and experimented before with node-red,
my data-flow now comes from the espeasy-modules via mqtt to node-red, and there i push it to influxdb, and have nice graphs in grafana.
i am working on it, but it runs basically fine...
to push the device-values directly via http-send to the database would be more stable...as i dont need node-red all the time ...
or have a look here:
https://github.com/shirou/mqforward
https://github.com/sguilly/mqtt-influxdb
https://github.com/hobbyquaker/influx4mqtt
https://github.com/mqtt-smarthome/mqtt- ... oftware.md
Re: Feature Request collection/list
Posted: 01 Jun 2016, 07:55
by tozett
BACKEND: Rules designer
Wow, if anybody ever implements a GUI-backend for the rules: come up here, please...
like this:
https://community.openhab.org/t/visual- ... gner/11072
Re: Feature Request collection/list
Posted: 01 Jun 2016, 12:46
by Drum
It has been a while since I have had time to update the firmware, and noticed the new mandatory WiFi selection when starting after initial flash.
I noticed it is not possible to select a open network (NO PASSWORD) and there is no way I see to bypass the WiFi selection initially to do basic some basic configuration, like assign the name. I set up 5 last night and it would be nice to be able to set the name before I move them to the live network rather than having to keep logging in to different WiFi APs to configure. Yes, it does give me the new IP of the ESP when it connects to the WiFi AP (which is a neat trick, by the way), but I still have to keep switching APs to change the names so I can find them later, and I usually don't configure on the production network so I have to change it anyway.
Re: Feature Request collection/list
Posted: 01 Jun 2016, 22:45
by dduley
Hi All,
I have a suggested addition to the SWITCH Task. Currently the SWITCH task supports "Normal", "Pushbutton active low" and "Pushbutton active hi". How about another state as "Event on change"? This would generate an SWITCH event whenever a switch position changed. This could be used for 3-way switch action and to allow a switch to control a light (for example) for local control but also allow for remote control of the light. Currently if you use a toggle switch to control a light and the position is in the off state when you try to remotely turn the light on it will com on for a few seconds, then a switch event is generated and the light goes back off.
Just a thought.
Dave
SI1145 - anybody for pretty coded implementation ?!
Posted: 24 Jun 2016, 15:22
by milan.gsm
Hello ... is here anybody interested in developing pretty coded SI1145 (UV sensor) plugin for ESPEasy ??? I think, that I am able to do it mysqlf (I have already made the NEXA 433RF plugin for ESPEasy), but I am not sure how to include the avialable library (
https://github.com/adafruit/Adafruit_SI1145_Library) into the plugin to need NOT include as external library. If nobody avialable for make the SI1145 plugin then I will do it the dirty way - need to include external library to your Arduino. Thank you.
Re: Feature Request collection/list
Posted: 14 Jul 2016, 20:14
by nonflammable
Re: Feature Request collection/list
Posted: 15 Jul 2016, 11:46
by pmayer
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
Re: Feature Request collection/list
Posted: 23 Jul 2016, 09:38
by tozett
Re: Feature Request collection/list
Posted: 15 Aug 2016, 14:24
by tozett
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...)
Re: Feature Request collection/list
Posted: 15 Aug 2016, 18:22
by happytm
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
Re: Feature Request collection/list
Posted: 17 Aug 2016, 09:36
by tozett
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...
Re: Feature Request collection/list
Posted: 19 Aug 2016, 09:51
by tozett
look. isnt that nearly wonderful ?
(espeasy still missing as "home of control" )
Re: Feature Request collection/list
Posted: 22 Aug 2016, 09:27
by tozett
Re: Feature Request collection/list
Posted: 23 Aug 2016, 15:25
by poe
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
Re: Feature Request collection/list
Posted: 28 Aug 2016, 11:09
by Drum
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.
Re: Feature Request collection/list
Posted: 28 Aug 2016, 11:16
by Drum
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.
Re: Feature Request collection/list
Posted: 28 Aug 2016, 12:00
by Drum
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.
Re: Feature Request collection/list
Posted: 29 Aug 2016, 09:43
by anarro
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
Re: Feature Request collection/list
Posted: 03 Sep 2016, 12:45
by big_alex
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.
Re: Feature Request collection/list
Posted: 04 Sep 2016, 15:36
by fluppie
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
Re: Feature Request collection/list
Posted: 05 Sep 2016, 10:29
by jgrad
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.
Re: Feature Request collection/list
Posted: 06 Sep 2016, 11:42
by daxkamala
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.
Re: Feature Request collection/list
Posted: 06 Sep 2016, 17:07
by guz
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
Re: Feature Request collection/list
Posted: 08 Sep 2016, 13:14
by overdrive
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.
Re: Feature Request collection/list
Posted: 08 Sep 2016, 14:37
by shubell
what about the ability to control the little led on the esp?
Re: Feature Request collection/list
Posted: 08 Sep 2016, 20:39
by tozett
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
Re: Feature Request collection/list
Posted: 17 Sep 2016, 13:55
by costo
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.
Re: Feature Request collection/list
Posted: 26 Sep 2016, 12:59
by tozett
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..
Re: Feature Request collection/list
Posted: 26 Sep 2016, 13:16
by beic
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?!
Re: Feature Request collection/list
Posted: 26 Sep 2016, 15:19
by Martinus
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
Re: Feature Request collection/list
Posted: 26 Sep 2016, 15:22
by beic
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!
Re: Feature Request collection/list
Posted: 28 Sep 2016, 09:31
by tozett
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)
Re: Feature Request collection/list
Posted: 28 Sep 2016, 10:38
by beic
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.
Re: Feature Request collection/list
Posted: 29 Sep 2016, 10:12
by tozett
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:
Re: Feature Request collection/list
Posted: 29 Sep 2016, 10:58
by beic
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
Re: Feature Request collection/list
Posted: 29 Sep 2016, 11:09
by tozett
ok. seems to be software configurable. riddle solved.
https://github.com/esp8266/Arduino/issu ... -167515482
Re: Feature Request collection/list
Posted: 29 Sep 2016, 11:16
by beic
So, what will happen if in the future someone uses more ESPEasy and some devices will get the same MAC address?
Re: Feature Request collection/list
Posted: 29 Sep 2016, 14:07
by 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.
Re: Feature Request collection/list
Posted: 29 Sep 2016, 14:31
by beic
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!
Re: Feature Request collection/list
Posted: 03 Oct 2016, 13:56
by 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
Re: Feature Request collection/list
Posted: 11 Oct 2016, 16:11
by 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)
Re: Feature Request collection/list
Posted: 11 Oct 2016, 16:16
by 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?
)
Re: Feature Request collection/list
Posted: 06 Nov 2016, 19:46
by 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!
Re: Feature Request collection/list
Posted: 06 Nov 2016, 22:00
by BertB
You know, this is a discontinued chip?
Re: Feature Request collection/list
Posted: 14 Nov 2016, 20:35
by 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