[ESPimatic]ESPimatic : ESP8266 modular sensor for Pimatic [v0.1.26]

---

maybe powering with a simple powerbank with 18659 lithium accus could be an option.

I also thought about having an Attiny that “wakes” the ESP8266 every 5 minutes or so by pulling CH_PD high, ESP8266 sets a Pullup on CH_PD on startup, gathers Measurements, sends them and sets CH_PD to Low state. The Tiny also could go to sleep and be wake up by the Watchdog Timer.

Would be worth a test how long it runs with a pair of AA’s. I mean temp and humidyt etc. does not change that fast so 5min would be a decent timeframe.

info about power consumption… http://bbs.espressif.com/viewtopic.php?t=133

but… please… be back on topic… this is a thread for ESPimatic… not for ESP8266 module in general…
also there are complete forums out there dedicated to just this module… for example: http://bbs.espressif.com

with google you will also find MANY informations… project websites, IRC Chats, forums, tutorials, etc… etc…

@demlak : Yep know most of the resources, but have not tested it by myself till now.

@leader21 : Would be a solution with a suitable 3,3V voltage regulator.

But now back to topic.

@demlak said:

• After Reboot of ESPimatic, state of Relay (for example) could differ from State in Pimatic

(added this to my list above)

I have a shell-switch in Pimatic with a refresh every1 minute. When the ESPimatic restarts, the situation is adopted in pimatic within a minute.

Regarding the power : I use a ESP8266-12 development board that comes with a batteryholder for 3 AA batterys. A onboard power regulator converts it to 3.3v
I cut of the wores to the batteryholder and attach a 5 volt USB cable for power.
For my particulair board, I have seen a test where someone made a sketch to powerup, read temperature from DHT, send to a website and go to deepsleep for 10 minutes. On 3 AA batterys this sketch would run for about 3 months before the batterys came to low.
I have seen with my own board that you get random crashes when the batterys are to low in juice.

@koffienl said:

@demlak said:

• After Reboot of ESPimatic, state of Relay (for example) could differ from State in Pimatic

(added this to my list above)

I have a shell-switch in Pimatic with a refresh every1 minute. When the ESPimatic restarts, the situation is adopted in pimatic within a minute.

my fault… i did not wait long enough to see this
whatabout option to store last state in ESPimatic, on reboot/power failure?

Thought about that, but u find it a bit danger to automaticly turn on relays after power loss. Will think about it

btw… it seems, the updateinterval is not working correct… im using DS18B20 sensor… and put an 1 minute interval… but pimatic says, it gets the update every 5 minutes (nearby)

Should work? I have the same setup/config and get new temp every minute. Do you use the latest pimatic version?

sorry… seems to be my fault… again…
the events log trims down to 5 min on reload… but if you look constantly on the log… then you are able to see the 1 min. update…

it´s a trap

Playing with basic authentication for next release now. Looks cool

New feature request:
Config option to switch off DHCP and enter fixed IP, subnetmask and gateway
(Edited my list above)

@Heizelmann said:

New feature request:
Config option to switch off DHCP and enter fixed IP, subnetmask and gateway
(Edited my list above)

Not sure if I will implement that request
I think making a static reservation in yout DHCP/router is a lot easier and safer.
All my ESP’s have a static IP in my router (and a own FQDN on my domain name).

what are the plans for the future?
espimatic can only control wired devices, or?
or is it possible to 433mhz devices, intertechno?

@noxx said:

what are the plans for the future?
espimatic can only control wired devices, or?
or is it possible to 433mhz devices, intertechno?

I’m working and testing with sending/receiving 433 Mhz from and to pimatic, but at this point I’m having trouble receiving KaKu (the protcol I use most).
Not sure how this will be implemented in ESPimatic.

ok, you write
ESP8266 (highly recommende a version with 4mb flash size)

which ESP have 4MB, i found only devices like this here:
http://www.amazon.de/dp/B00P2KDTEC

there is no info about the flash size (or i dont see it)

NodeMCU 1.0 should have 4Mb , check ebay

Working on the basic authentication tight now.
In a nutshell :

• all HTML from SPIFFS is behind password
• all ajax feedback pages should be behind password
• Some internal pages should be behind password (like format, upload files)
• The api page is not behind a password but when authentication is enabled you should send a API key
• You can turn authentication on and off

Am I missing something ?

thx

i found diffent versions of the NodeMCU.
can i use all of them ?

http://de.aliexpress.com/item/D1-mini-Mini-NodeMcu-4M-bytes-Lua-WIFI-Internet-of-Things-development-board-based-ESP8266/32529101036.html?isOrigTitle=true

http://de.aliexpress.com/item/NodeMcu-Lua-WIFI-development-board-based-on-the-ESP8266-Internet-of-things/32339203041.html?isOrigTitle=true

http://de.aliexpress.com/item/New-Wireless-Module-NodeMcu-Lua-WIFI-Internet-of-Things-Development-Board-Based-ESP8266-with-Pcb-Antenna/32453467385.html?isOrigTitle=true

@noxx
i’m using the wemos d1 mini without issues. even flashing was easy after the ide was set up correctly.

@noxx
I ordered this one http://www.ebay.com/itm/181924392878?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT

For what I understand, the nodemcu with CH340 chip is the old version(v1) and with CP2102 chip is the newer version (v2 and v3)
The wemos that @leader21 is talking about looks to be almost the same.
Comparison:
http://frightanic.com/iot/comparison-of-esp8266-nodemcu-development-boards/