Feature Request collection/list

Moderators: grovkillen, Stuntteam, TD-er

Message
Author
tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Feature Request collection/list

#1 Post by tozett » 27 Jan 2016, 09:18

i am experimenting with ESPeasy, i am on R072, wounderful piece of code.

in the last days i made loosely around the forum some feature requests.
to see the ESPeasy going on from best to super-best, maybe there can be a sortet list of from the developer,
whitch features are considered to be realised in coming versions/milestone?

at the moment i will do like before an post feature-wishes loosely into the forum. ok?

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#2 Post by tozett » 28 Jan 2016, 20:31


tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#3 Post by tozett » 29 Jan 2016, 21:30

as the list is locked :o
i put it here?

i can configure general http request with IP and PORT,
i have log-level 6 (on all logs), but i dont have these details in the log.
the port is missing. maybe a good thing to put it also there in the log, if one wants to check like me ...

Code: Select all

Jan 29 21:22:53 ESP Unit: 0 : HTTP : closing connection
Jan 29 21:22:53 ESP Unit: 0 : PN532: Tag: 2227488915 25
Jan 29 21:22:53 ESP Unit: 0 : HTTP : Delay 1000 ms
Jan 29 21:22:54 ESP Unit: 0 : HTTP : connecting to 192.168.14.253
Jan 29 21:22:54 ESP Unit: 0 : /esp01?device=sw13?device=rfid1&param=rfid&value=2227489024.00
another one: some more variables for general https request?
like the formfields from the config page? to differentiate a bunch of ESPs by their names in the http-string..

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#4 Post by tozett » 30 Jan 2016, 08:54

Feature-Request: Date-Time-Stamp in the Config-name

my config stayed in flash while upgrading from R072 to R073,
but was deleted by downgrade vom R072 to R048 (i was experimenting with PN532).

so now i save my config. but the name stays the same. it would be helpful it he name would contain date+time, or a UUID instead, or device-name-UUID
(i have a NTP configurred an running)

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#5 Post by tozett » 01 Feb 2016, 18:57

i saw some request jumped over the sticky-list. fantastic. therefore, another for more easy ESPeasy:

Feature-Request for a change with the IDX-Field (?!)

Explanation:
some people (like myself) did not see, that a Zero in the device-IDX field (default) blocks the device from sending.
http://www.esp8266.nu/forum/viewtopic.p ... =755#p3685

maybe a checkbox could help, like
[ ] send immediatey
or some other default, or some hints?:
idx : 1 (send) / 0 (no send)

kr0815
Normal user
Posts: 132
Joined: 18 Nov 2015, 18:24

Re: Feature Request collection/list

#6 Post by kr0815 » 01 Feb 2016, 19:08

I made the same fault and wondered, maybe just pre-fill it with something like 99 ?

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#7 Post by tozett » 01 Feb 2016, 19:57

Feature-Wish: TSL2591

the TSL2561 Lux-sensor is already in, but i own a TSL2591
https://learn.adafruit.com/adafruit-tsl2591/overview

maybe sometime it will be supported in the source :roll:

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#8 Post by tozett » 01 Feb 2016, 21:30

Feature-Request: Output-Device (LED),
means: every connected GPIO (can) defined in the device section

as i found the LED as Output device on the wiki, i tried this.

but it was confusing that i did not have to create a device and define the GPIO on wich the LED was connected.

so mabye to be more logical, even if one can control GPIOs via HTTP without any defines,
that it would be more logical to have _every_ GPIO connection in the device section.
so one has there GPIO connections list

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#9 Post by tozett » 01 Feb 2016, 23:04

sorry to make this list longer, but the ESPeasy is most of the best i have ever seen in HomeAutomation
:D
So another Feature-Request for the list: "Level-Control" transformation to something like "IFTTT"
means: expand "level control" to control the GPIOS on rules, react on Level or events.
maybe rename to "rules engine", or something similar

my example was the LED on GPIO. i liked to led it flicker every second of the runtime. (a typo with the led/let, a joke in a second reading!)
so i could configure level-control to react on a Hysteresis, but if all conditions were more general, or other events on the system,
i could set rules to control GPIOs with on/off, PWM, and the like... that would be great!

can grow to a complex and powerful system. a lot of coding, i guess :geek:

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#10 Post by tozett » 01 Feb 2016, 23:19

Feature-Request: HTML Meta-Tag on the main-Page with the runtime.

i did not look longer, but it seems the pages does not refresh itself.
but a (configurable) refreshtime via a meta-tag in the html/css would be nice.
to get the updated realtime runtime. wouldnt it?

http://www.w3schools.com/tags/att_meta_http_equiv.asp

edit 2016.02.02: seems to be there already somehow on /setup Page in R076

Code: Select all

// if Wifi setup, launch setup wizard
  if (wifiSetup)
  {
    WebServer.send(200, "text/html", "<meta HTTP-EQUIV='REFRESH' content='0; url=http://192.168.4.1/setup'>");
    //WebServer.send(200, "text/html", "<a class=\"button-menu\" href=\"setup\">Setup</a>");
    return;
  }
https://github.com/ESP8266nu/ESPEasy/bl ... Server.ino

edit: i found the log page already self-refreshing with javascript:

Code: Select all

<script language='JavaScript'>function RefreshMe(){window.location = window.location}setTimeout('RefreshMe()', 3000);</script>
Last edited by tozett on 04 Feb 2016, 19:22, edited 2 times in total.

dannybloe
Normal user
Posts: 36
Joined: 16 Dec 2015, 16:29

Re: Feature Request collection/list

#11 Post by dannybloe » 02 Feb 2016, 08:14

And set it to the same interval as the sensor delay setting :)

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#12 Post by tozett » 02 Feb 2016, 12:00

as long as the admin is not stopping me, (and my time is not running out)
i will try to collect useful ideas for the ESPeasy from around the forum at this single place here.. 8-)

Feature-Request: PWMFADE, pin, target, time in seconds
http://www.esp8266.nu/forum/viewtopic.p ... f383#p3723

(is there a negative effect of PWMFADE if one would control some motors, not only LIGHT with that?)
Last edited by tozett on 02 Feb 2016, 12:02, edited 1 time in total.

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#13 Post by tozett » 02 Feb 2016, 12:01

Feature-Request: Store state of GPIO in Flash, to be retrievable after (cold-)reboot
Was thinking it would be worth adding code to write the gpio levels to flash and retrieving them on boot too?
http://www.esp8266.nu/forum/viewtopic.p ... 3723#p3723

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#14 Post by tozett » 02 Feb 2016, 14:59

Development-Idea (far ahead a Feature-Request):

Store of ESP-"Swarm"-parameters/configs on a central unit

the interesting idea is working here: http://jeelabs.org/article/1604f/
(the JET-Database is it called)

The idea is, to send all configs via MQTT into a central HUB (Raspberry, ESP32...??) and store it there.
like in a usual it-infrastructure with a central server, somehow. So one could manage a lot of devices from one place.. :ugeek:

interesting reading, the concept/source here:
http://jeelabs.net/projects/housemon/wiki

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#15 Post by tozett » 03 Feb 2016, 19:51

While fiddling with Infrared IR:
http://www.esp8266.nu/forum/viewtopic.p ... =763#p3772

+1 Feature-Request: give out the recognized remote (sony/sanyo/technics..)
+1 Feature-Request: IR-Send (sometime?)

https://github.com/juanpintom/Souliss_E ... Receiver.h
http://internetofhomethings.com/homethings/?p=899

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#16 Post by tozett » 04 Feb 2016, 07:54

Feature-Request: show WIFI Strength

the AT-Firmware has RSSI values for the connected and the list of receivable WIFI networks.
think it is a informational value to show the RSSI value on the main status page, like my openwrt does on the AP side.. (maybe channel+bitrate, too?)
Attachments
rssi.png
rssi.png (34.39 KiB) Viewed 4767 times

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#17 Post by tozett » 04 Feb 2016, 19:16

Feature-Request: Set Individual address in the device-section on i2c for multiple devices on I2C bus

http://www.esp8266.nu/forum/viewtopic.php?f=6&t=771

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#18 Post by tozett » 04 Feb 2016, 19:30

i was wondering today, why it is not already in:

Feature-Request: Return-Object for (System-) GPIO-States.

i need to now, whats coming from the sensors. at the moment i get this RETURN via the publish-template (http/mqtt). And Syslog. good.
but if i switch a LED on an GPIO, i only have a http-String as command to turn it on/off, and _NOT_ any return,
or am i wrong?
so i would be helpful, to get (at least in this scenario) somehow a return over the status from the GPIO..

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#19 Post by tozett » 06 Feb 2016, 16:07

MQTT syslog channel/topic
MQTT boot-log channel/topic

i played with MQTT,
so i am missing a device "System Info", as an MQTT-syslog-channel.
would like to have a "LOGging" ind in the "System Info"-Device,
so everthing what is send to syslog is also published via MQTT

dduley
Normal user
Posts: 93
Joined: 06 Feb 2016, 17:56

Re: Feature Request collection/list

#20 Post by dduley » 06 Feb 2016, 18:09

How about extending the gpio pulse output (i.e. http://<ESP IP address>/control?cmd=Pulse,<pin>,<state>,<duration>) to work with PCFGPIO outputs as well. This would be useful for relay control of garage doors and entry gates etc.

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#21 Post by tozett » 06 Feb 2016, 22:11

Big Wish: MQTT commands!

If ESPs had only inputs on GPIOs,
it would only be a sensor-node (only), collects information and publishes them to backends.
actually in R078 we have only one central MQTT-publish-template to send it to one single backend ...

BUT

ESPeasy knows Outputs/Actuators (see wiki),

BUT

i cannot control them via MQTT (or do i miss something?)

so, most logical,a per DEVICE MQTT-Subscribe-Template (or per DEVICE general receive-Template) would make sense,
to control each output individually with a individual per device method (MQTT, http, UDP, ...?).
(as the outputs could also be controlled otherwise in parallel, i.e. on the ESP, i.e. Level-Control, Action,...)

on a big scene this could be an architetural decision for a matrix:
to have only sensor-nodes, small-nodes (in/out, in+out), function-nodes (with rules on them),
function-nodes as Actuators/with outputs with control from backends, ...

but a least minimal: receive of commands to set GPIO outputs (per device=per GPIO + via MQTT) :mrgreen:

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#22 Post by tozett » 07 Feb 2016, 13:26

esp and wired ethernet.

seems possible,
https://github.com/esp8266/Arduino/issu ... -176710920
so dont you want to give it at try?

+1 ESPxx and wiznet (ethernet-lan)

edit: found a link here:
http://forum.espruino.com/conversations ... ?offset=25
some more info here:
http://www.esp8266.com/viewtopic.php?f=6&t=6910

espruino with wiznet (ethernet), cool!! 8-) :
https://www.tindie.com/products/gfwilli ... rnet-shim/

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#23 Post by tozett » 07 Feb 2016, 22:37

log to google spreadsheet.

cool example here:
https://docs.google.com/spreadsheets/d/ ... P0/pubhtml

done with (little) code here:
http://www.espruino.com/Logging+to+Google+Sheets

:mrgreen:

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#24 Post by tozett » 10 Feb 2016, 08:21

more/individual i2c adresses for devices

from a forum thread ;
http://www.esp8266.nu/forum/viewtopic.p ... 3973#p3973

dynode
Normal user
Posts: 4
Joined: 11 Feb 2016, 01:56

Re: Feature Request collection/list

#25 Post by dynode » 11 Feb 2016, 03:05

Some kind of timed GPIO switching. I see NTP support in firmware, this means ESP Easy can do timekeeping? If so, timed GPIO switching should be possible. I would like to have this independent of large and complex domotics software solutions.

chunter1
Normal user
Posts: 82
Joined: 22 Jan 2016, 22:40

Re: Feature Request collection/list

#26 Post by chunter1 » 13 Feb 2016, 00:02

My wishes...

1) Sending GPIO input and output states not only on changes but also in regular intervals and at startup.
2) Selecting sending intervals for each task individually
3) manually selectable I2C address for each device
4) pulse output time increase to 1h or more
Last edited by chunter1 on 14 Feb 2016, 18:21, edited 2 times in total.

msev
Normal user
Posts: 33
Joined: 13 Feb 2016, 18:24

Re: Feature Request collection/list

#27 Post by msev » 13 Feb 2016, 23:33

My wish would be to add to the protocols another one - Souliss protocol. I'm gonna probably create a separate thread for discussing that :)

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#28 Post by tozett » 14 Feb 2016, 21:21

use the CHIP id to identify more startup SSIDs...

they are all equal ESP_0...
but why not ESPeasy_xxx =CHIPID ?

CHIPID could also identify Nodes/MQTT, but nice if it would be changeable via webGUI ...

ambassadoro
Normal user
Posts: 40
Joined: 17 Nov 2015, 15:58

Re: Feature Request collection/list

#29 Post by ambassadoro » 15 Feb 2016, 18:20

My wish:

Rock stable MQTT. It works already very well for sensors and simple actors like a relay on a GPIO. Other outputs like PWM, the minipro-extender and other extra IO are not supported or at least not documented.
If you need help for documentation, I like to get involved (I tried to login to the wiki, but it said that I am already registered since 2013 :? )

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#30 Post by tozett » 18 Feb 2016, 19:21

rock stable ESPs on hidden places in homeautomation :geek:

WATCHDOG for COLD-RESET (somehow)

i posted elsewhere, but it should be a feature-wish here:
for having "reliable" ESP-nodes at some unusual places in home automation i would be good to
cold-restart the ESP. Anybody doing this?

i read here:
http://tech.scargill.net/esp8266-reset/#comment-4735
I send an MQTT "heartbeat" message to the boards from a central "controller" which is a battery backed-up Raspberry Pi2 - the ESPs have a flashing light on them that alternates every second. If that heartbeat does not arrive, I stop the flashing lights, try again to get the message and if that fails, reboot the board.
which seems a good idea for an _internal_ watchdog. maybe a wishlist feature?
for an external watchdog i dont know how, but maybe connect something to the reset pin..

i did not understand everything, but may points to consider:
It seems that module Reset can be done with CH_PD line (pulling it low) leaving Reset alone with pull-up. And leaving Reset alone seems to be better for sleep/wake up mode (when GPIO16 connected to Reset) and avoid some problems in this case.
http://hallard.me/esp8266-autoreset/

Another good idea:
I use a variation of the normal reset whereby the first trigger of the watchdog calls a routine to log the error in EEPROM then immediately resets the board - so I know the difference between a power off and a watchdog reset).
http://tech.scargill.net/esp8266-and-lo ... mment-1147

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#31 Post by tozett » 18 Feb 2016, 20:42

WATCHDOG with SOFT-RESET (for an embedded device like the esp)

Code: Select all

Sometime back I faced a strange issue where after ESP.reset() used to perform soft reset did not worked perfectly. The ESP was not able connect to the same router reliably. So I tied GPIO16 to RESET pin. I found this in one of the Blogs on tech.scargill Blog itself. Whenever a reset was required I used the following:

RESET_PIN = GPIO16;
pinMode(RESET_PIN, OUTPUT);
digitalWrite(RESET_PIN, LOW);

The code above will ensure a complete reset done by the software. This has worked for me with 100% results.

I have seen ESP hanging in software loops where we wait till content is available:
while (!client.available()) {
}

http://tech.scargill.net/esp8266-and-lo ... ment-13335

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#32 Post by tozett » 25 Feb 2016, 08:09

Support of 1-wire (OneWire) variants of

DS18B20
DS18S20 - Please note there appears to be an issue with this series.
DS1822
DS1820

from: http://www.esp8266.nu/forum/viewtopic.p ... =277#p4514
links to code: https://github.com/milesburton/Arduino- ... ol-Library

chunter1
Normal user
Posts: 82
Joined: 22 Jan 2016, 22:40

Re: Feature Request collection/list

#33 Post by chunter1 » 05 Mar 2016, 09:39

1.) really STABLE PWM output
2.) Timed dimmer command e.g. ".../control?cmd=DIM,14,0,60" (dimms GPIO14 to 0% in 60 seconds)

Am using timed dimmer function with homematic devices already as wakeup-light ;)

User avatar
nonflammable
Normal user
Posts: 42
Joined: 09 Mar 2016, 22:19
Location: Poland

Re: Feature Request collection/list

#34 Post by nonflammable » 09 Mar 2016, 22:41

WOL - receive magic packet and set selected GPIO to HIGH for defined time.
Last edited by nonflammable on 01 Apr 2016, 19:39, edited 7 times in total.

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#35 Post by tozett » 10 Mar 2016, 07:30

WoL must be: "Wake on Wireless LAN" !!??
is this possible?
https://technet.microsoft.com/de-de/lib ... s.10).aspx

Wake on Lan: explained here:
http://www.howtogeek.com/70374/how-to-g ... enable-it/

VasilijHCN
Normal user
Posts: 18
Joined: 08 Oct 2015, 18:02

Re: Feature Request collection/list

#36 Post by VasilijHCN » 10 Mar 2016, 12:00

Add SI1145 UV IR Visible Sensor I2C, this is a ultraviolet sensor, give result in UV index. Also measure infrared and visible light, 3 in one sensor.
http://www.ebay.com/itm/SI1145-UV-IR-Vi ... OSwQoFWPHi~
Arduino libary https://github.com/adafruit/Adafruit_SI1145_Library

User avatar
nonflammable
Normal user
Posts: 42
Joined: 09 Mar 2016, 22:19
Location: Poland

Re: Feature Request collection/list

#37 Post by nonflammable » 10 Mar 2016, 12:59

tozett wrote:WoL must be: "Wake on Wireless LAN" !!??
is this possible?
https://technet.microsoft.com/de-de/lib ... s.10).aspx

Wake on Lan: explained here:
http://www.howtogeek.com/70374/how-to-g ... enable-it/
WOL - i meen - receive magic packet when ESP is working - not wake ESP
https://en.wikipedia.org/wiki/Wake-on-LAN#Magic_packet
i think it's posible to receive that by working ESP
I have Synology NAS without WOL, but i can wake it by ESP GPIO set to HIGH for "half second". ESP could receive magic packet and set GPIO HIGH for while. You can turn on any device without build-in WOL eg. from router.

Martinus

Re: Feature Request collection/list

#38 Post by Martinus » 11 Mar 2016, 13:48

nonflammable wrote:i think it's posible to receive that by working ESP
I have Synology NAS without WOL, but i can wake it by ESP GPIO set to HIGH for "half second". ESP could receive magic packet and set GPIO HIGH for while. You can turn on any device without build-in WOL eg. from router.
Nice idea. I happen to have multiple Synology systems without WOL and a router capable of sending WOL. Indeed this could bring WOL to systems that do not support it (as long as you have 3V3 or 5V available to feed the ESP...)

Have to create a plugin for this.

Martinus

Re: Feature Request collection/list

#39 Post by Martinus » 11 Mar 2016, 15:59

WOL plugin is pushed to the plugin playground:
https://github.com/ESP8266nu/ESPEasyPluginPlayground

tozett
Normal user
Posts: 733
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Feature Request collection/list

#40 Post by tozett » 11 Mar 2016, 16:54

nonflammable wrote: I have Synology NAS without WOL, but i can wake it by ESP GPIO set to HIGH for "half second".
could you please provide some wiring information _with_ the plugin,
how to start the synology nas with the GPIO high (if i got this right)?
tankx, great idea for more like this... :D

msev
Normal user
Posts: 33
Joined: 13 Feb 2016, 18:24

Re: Feature Request collection/list

#41 Post by msev » 15 Mar 2016, 09:59

RC522 Rfid reader support would be cool :) (https://github.com/Jorgen-VikingGod/ESP8266-MFRC522)

sommers9
Normal user
Posts: 3
Joined: 16 Mar 2016, 16:44

Re: Feature Request collection/list

#42 Post by sommers9 » 16 Mar 2016, 16:57

ETHERNET all-in-one connector.

I'm dying to get an ESP8266 but with ethernet connection.
Please make it an all-in-one type with magnetics and RJ-45 jack (and PHY and MAC nonsense).

The WiFi version isn't going to cut it for a lot of projects.
Personally, I would pay €40+ for such an device. (Given it's programmable with GPIO, which would only be a concurrent of the €50 XPort. (Others can't do I/O))
But if I look at the ESP8266, you guys could make it for around €10,- which would give quite an return on investment...
(Bet you could even let some enthusiasts develop it, without a lot of additional (single time) costs.)
Seeing how much of a succes the ESP8266 is an ethernet version would probably hit hard.

There are too much people trying to use the annoying ENC28J60 or WIZ5500 or expensive/overpowered XPort.
We need an ethernet version of the ESP8266!

No, serious: Is such a product in development? If not, please do so.

highroller
Normal user
Posts: 31
Joined: 09 Feb 2016, 22:16

Re: Feature Request collection/list

#43 Post by highroller » 16 Mar 2016, 19:38

sommers9 wrote:ETHERNET all-in-one connector.

I'm dying to get an ESP8266 but with ethernet connection.
Please make it an all-in-one type with magnetics and RJ-45 jack (and PHY and MAC nonsense).

The WiFi version isn't going to cut it for a lot of projects.
Personally, I would pay €40+ for such an device. (Given it's programmable with GPIO, which would only be a concurrent of the €50 XPort. (Others can't do I/O))
But if I look at the ESP8266, you guys could make it for around €10,- which would give quite an return on investment...
(Bet you could even let some enthusiasts develop it, without a lot of additional (single time) costs.)
Seeing how much of a succes the ESP8266 is an ethernet version would probably hit hard.

There are too much people trying to use the annoying ENC28J60 or WIZ5500 or expensive/overpowered XPort.
We need an ethernet version of the ESP8266!

No, serious: Is such a product in development? If not, please do so.
Why not use an older rasperry if ethernet connection is essential?

costo
Normal user
Posts: 490
Joined: 21 Nov 2015, 15:03

Re: Feature Request collection/list

#44 Post by costo » 17 Mar 2016, 00:55

sommers9 wrote:ETHERNET all-in-one connector.

No, serious: Is such a product in development? If not, please do so.
I don't think this is realistic.
ESPEasy is a software project not a hardware project.
ESP8266 is developed just for wireless connection because people want to get rid off the UTP wires.
There is nothing on the ESP-chip that makes it suitable for wired ethernet.

Use a Arduino (Uno/Mega) with the wiznet W5100 board, that is exactly what you want https://www.arduino.cc/en/Main/ArduinoEthernetShield

Barb232
Normal user
Posts: 40
Joined: 12 Mar 2016, 16:40
Location: Earth
Contact:

Re: Feature Request collection/list

#45 Post by Barb232 » 17 Mar 2016, 10:16

is it possible to build a button?

Switch on via MQTT: on / off or off / on .. hold n - seconds.
i used a switch for my project and i have to program via fhem the on / off feature:
https://blog.moneybag.de/erfahrungsberi ... -diffuser/
https://blog.moneybag.de/espeasy-admini ... -und-fhem/


it it possible to build a LED stripe like this?

https://blog.moneybag.de/fhem-mit-led-s ... ertragung/
transmit data via a hex code to light up the LEDs in several colors

sommers9
Normal user
Posts: 3
Joined: 16 Mar 2016, 16:44

Re: Feature Request collection/list

#46 Post by sommers9 » 17 Mar 2016, 16:39

highroller wrote: Why not use an older rasperry if ethernet connection is essential?
That would be the most bulky solution yet xD

An raspberry Pi uses a lot more power.
An raspberry Pi needs an OS (which should be kept up to date).
An raspberry Pi is quite big for embedded solutions.
An raspberry Pi is not easily mountable on a breadboard.
An raspberry Pi is not easily programmed through it's pins.
An raspberry Pi has to be shut down in a proper way.

You could indeed use an Arduino Nano + Nano Ethernet shield.
But that still is much more bulky that an all-in-one device as the ESP8266 and would require a separate controller.

I would like to simply attach a small ethernet port to a shift register. And be able to control these over ethernet.
But it shouldn't be over WiFi, since it would be in an industrial setting.
(But that's just one of the applications)

sommers9
Normal user
Posts: 3
Joined: 16 Mar 2016, 16:44

Re: Feature Request collection/list

#47 Post by sommers9 » 17 Mar 2016, 16:44

costo wrote:Use a Arduino (Uno/Mega) with the wiznet W5100 board, that is exactly what you want https://www.arduino.cc/en/Main/ArduinoEthernetShield
Than I could aswell go with an Arduino Ethernet Board (https://www.arduino.cc/en/Main/ArduinoBoardEthernet).
But it should be possible in a small form-factor. If you would say someone could make such an tiny Wi-Fi device (as the ESP8266) also nobody would believe you.

If you have an 10BASE-T converter (or basically an IC that can convert ethernet signaling to TTL serial) you could feed it in the ESP8266 protocol stack/processing and it would somewhat work? :)
Hmm, but you're probably right, I should annoy WizNet or Microchip for such a device/implementation.

highroller
Normal user
Posts: 31
Joined: 09 Feb 2016, 22:16

Re: Feature Request collection/list

#48 Post by highroller » 17 Mar 2016, 19:12

sommers9 wrote:
highroller wrote: Why not use an older rasperry if ethernet connection is essential?
That would be the most bulky solution yet xD

An raspberry Pi uses a lot more power.
An raspberry Pi needs an OS (which should be kept up to date).
An raspberry Pi is quite big for embedded solutions.
An raspberry Pi is not easily mountable on a breadboard.
An raspberry Pi is not easily programmed through it's pins.
An raspberry Pi has to be shut down in a proper way.

You could indeed use an Arduino Nano + Nano Ethernet shield.
But that still is much more bulky that an all-in-one device as the ESP8266 and would require a separate controller.

I would like to simply attach a small ethernet port to a shift register. And be able to control these over ethernet.
But it shouldn't be over WiFi, since it would be in an industrial setting.
(But that's just one of the applications)
Raspberry is just as easy to program as an esp. Actually it would be easier since you have a lot more hardware (ram, cpu) and programing languages.
About the size you could go for a pi zero with usb to rj45 adapter.

Martinus

Re: Feature Request collection/list

#49 Post by Martinus » 19 Mar 2016, 13:37

sommers9 wrote:ETHERNET all-in-one connector.

I'm dying to get an ESP8266 but with ethernet connection.
Please make it an all-in-one type with magnetics and RJ-45 jack (and PHY and MAC nonsense).

The WiFi version isn't going to cut it for a lot of projects.
Personally, I would pay €40+ for such an device. (Given it's programmable with GPIO, which would only be a concurrent of the €50 XPort. (Others can't do I/O))
But if I look at the ESP8266, you guys could make it for around €10,- which would give quite an return on investment...
(Bet you could even let some enthusiasts develop it, without a lot of additional (single time) costs.)
Seeing how much of a succes the ESP8266 is an ethernet version would probably hit hard.

There are too much people trying to use the annoying ENC28J60 or WIZ5500 or expensive/overpowered XPort.
We need an ethernet version of the ESP8266!

No, serious: Is such a product in development? If not, please do so.
We only do software here and only the 'application layer', not even the SDK or libraries.
You need to ask Expressif if they are interested in this kind of chip development. Doubt this because the whole world wants the convenience of wireless...
But I agree that having a tiny SOC module like ESP12E with build in wired Ethernet for less than 3 dollar and easy code portability from Arduino would also be fun for some applications.

BertB
Normal user
Posts: 1019
Joined: 25 Apr 2015, 14:39

Re: Feature Request collection/list

#50 Post by BertB » 23 Mar 2016, 21:22

Is it possible to enhance the Settings Save routine so that the Unit number becomes part of the standard name. Something like:
config_unit1.txt

Post Reply

Who is online

Users browsing this forum: No registered users and 17 guests