Let's Control It

chunter1 wrote: Suggestion:
1) After 30 failed connection retries - change to AP mode
2) If in AP mode and if there is no client connected for more than 1 minute, change back to client mode and try to reconnect to the specified WLAN AP
3) goto 1

5ko wrote: In this sense, the most commonly used NTC thermistor perfectly described:

https://learn.adafruit.com/thermistor/u ... thermistor

If it can not be included in the collection/list would need any help with the integration of these sensors in the ESP Easy whether I should make a change in the A1115 analog IC plug in, but which sends only int. not float... or should I add somewhere more complex analog formula...
Any help would welcome Thanks.
Regards
5ko

NietGiftig wrote:

chunter1 wrote: Suggestion:
1) After 30 failed connection retries - change to AP mode
2) If in AP mode and if there is no client connected for more than 1 minute, change back to client mode and try to reconnect to the specified WLAN AP
3) goto 1

How long does it take to get 30 connection retries.
So I have to wait for 30 retries staring at my computer until I see the access-point appear and then I have 1 minute to connect the AP?
How many modules you have?
The question is, why does it go to the AP mode if it is a working configuration?
If your network is changed (other name/password/...) there must be a better way then sitting at your computer waiting till all your modules have gone to 30 retries, and please do not miss the one minute AP period, else you have to wait another round.
The situation now is that you have to do walk around the house to do an off/on switch if your network has not changed but disappeared for too long.

I personally rather have no change to AP once defined
Possibly an small switch to force the ESP in AP mode.
I know, if you have an ESP-01 you do have not got one pin free, but lets face it, there are more and more ESP12 in use.
You can always go back to the serial for a change of the IP settings.

chunter1 wrote: As you can read, it was just a suggestion - not an attack at you

Feel free to change the 30 to 1 retries, and the 1 minute to 1 hour.
Using a switch is no good idea since the alternative - a power cycle - costs nothing.

I personally rather have no change to AP once defined

Feel free to change the 30 to 1 retries, and the 1 minute to 1 hour.

chunter1 wrote: Please read the argument i gave before again carefully and you'll understand why my suggestion makes sense.
And if it makes you happy, go and attach a button to it - that's ok - just unnecessary.
However i don't have time discussing bad ideas, sorry

5ko wrote:Dear costo,
maybe I was not clear enough, or you may missed the point ...
.

nonflammable wrote:1) toggle - set selected GPIO to 0 when is 1 or set to 1 when is 0

Code: Select all

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

2) read status of selected GPIO, and return 1, 0, PWM=xxxx, etc.

Code: Select all

http://<ESP IP address>/status?cmd=GPIO,<pin>,READ

3) timer switch (when NTP is enabled) (yes, I know it can be set by Rules - Clock#Time)

Code: Select all

http://<ESP IP address>/control?cmd=GPIO,<pin>,1,14:30 //set timer switch ON at 14:30
http://<ESP IP address>/control?cmd=GPIO,<pin>,0,15:00 //set timer switch OFF at 15:00

rajbadri wrote:Notifications for Pushbullet, Pushover or Ifttt directly without domoticz server.

chunter1 wrote:I really miss an optionally selectable periodic input/output-pin status transmit timer.
Also not beeing able to select "Send Boot state" for PCF8574 IO expanders is problematic.

The reason why is, that when there is a communication failure or a server/switch... reboot and the status of an input/output changes in that moment, the server will hold the obsolete status until the next espeasy-reboot or status change.
This can get very "inconvenient".

The feature should be available for all I/Os (internal GPIOs and external extensions like PCF8574...)

Thanks

BertB wrote: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

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

chunter1 wrote:Here another feature Request:
When connection to the WLAN-AP fails, the ESPEasy node shall periodically toggle between connection retry and AP-mode.

Suggestion:
1) After 30 failed connection retries - change to AP mode
2) If in AP mode and if there is no client connected for more than 1 minute, change back to client mode and try to reconnect to the specified WLAN AP
3) goto 1

fiets wrote:I would like the following features:

Turn a gio port on for a certain time (by value). This way I am not depending on a server for switching off. This is usefull for switching on a valve which has to close after a certian time. If the server hangs the esp switches off the port itself.

Also I would like an alarmmode, so a lamp can be switched on and of with 3 flashes after eachother.
From a server this is not possible.

I wonder if someone else also like these features…

Thanks in advance…

chunter1 wrote:I really miss an optionally selectable periodic input/output-pin status transmit timer.
Also not beeing able to select "Send Boot state" for PCF8574 IO expanders is problematic.

The reason why is, that when there is a communication failure or a server/switch... reboot and the status of an input/output changes in that moment, the server will hold the obsolete status until the next espeasy-reboot or status change.
This can get very "inconvenient".

The feature should be available for all I/Os (internal GPIOs and external extensions like PCF8574...)

Thanks

dduley wrote:Hi again,

Loving the new features!

Can the current I/O state be used in rules?
Example:
on Button#Value do
if [PCFGPIO,4]=0
pcfgpio,4,1
else
pcfgpio,4,0
endif
endon

this would allow the use of a momentary push button to control an output in a Push-on/Push-off style

on Button#Value do
 pcfgpio,4,[Button#Value]
endon

Martinus wrote:

dduley wrote:Hi again,

Sorry, but that will not work. The [..#..] will be substituted with a value if it can find a matching taskname/taskvalue pair.

This might work however:

Code: Select all

on Button#Value do
 pcfgpio,4,[Button#Value]
endon

chunter1 wrote:.
Feature requested: ON/OFF button on webinterface device-page to test GPIOs

For setup test and remote control purpose, it would be very convenient if there were small ON/OFF buttons next to I/O GPIOs on the webinterface to immediately test functionality.

How about an option to support dual protocols. It would be useful to send data via MQTT to OpenHab or other but also push values to Thingspeak

JR01 wrote:Use Node-Red for this, write MQTT to Node-Red (I have it on RasPi - works like a charm), the n create flows to take MQTT message out to all places, like ThingSpeak, MySQL, OpenHab, etc.

Martinus wrote:

dduley wrote:Hi again,

Loving the new features!

Can the current I/O state be used in rules?
Example:
on Button#Value do
if [PCFGPIO,4]=0
pcfgpio,4,1
else
pcfgpio,4,0
endif
endon

this would allow the use of a momentary push button to control an output in a Push-on/Push-off style

Sorry, but that will not work. The [..#..] will be substituted with a value if it can find a matching taskname/taskvalue pair.

This might work however:

Code: Select all

on Button#Value do
 pcfgpio,4,[Button#Value]
endon

timsson wrote:

tozett wrote:i am on r105, did you implement the LWT with rules? could you post your working example?

I use also r105, fantastic projekt! but for lwt i take my one ino file with exactly this syntax and it works fine:

Code: Select all

#define MQTT_TOPIC_LAST_WILL "/ESP_02/lwt"
mqttClient.connect("ESP_02", MQTT_TOPIC_LAST_WILL, 1, true, "disconnected");
mqttClient.publish(MQTT_TOPIC_LAST_WILL, "connected", true);

or do you need the complete ino?
and i use this library:
PubSubClient by Nick O'Leary Version 2.6.0 mqtt3.1.1