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

---

@koffienl said:

@Harry-van-der-Wolf Can you point me to one of your projects with the time.h function?

Actually it is not my project but a minimally changed project from @okadesde where I replaced the DHT with a ds18b20 functionality. And I used the time function (here) which is based upon the default esp8266 repository. The same can be done for an initial year-date-time.
Something like

string InitDate = year() + mon() + day()

Preparing 0.1.26 right now. Few bugs fixed,KwH interrupt meter added and changed the root page. You only see sensors and devices that are configure:

guess the kwh meter is for S0 pulse counting via flashing led?
maybe for later you might consider to also implement a hall sensor for gas meters smilar like @Yves911 has done here https://forum.pimatic.org/topic/662/energy-and-gas-monitor-with-esp8266. would be hilarous

@leader21 said:

guess the kwh meter is for S0 pulse counting via flashing led?
maybe for later you might consider to also implement a hall sensor for gas meters smilar like @Yves911 has done here https://forum.pimatic.org/topic/662/energy-and-gas-monitor-with-esp8266. would be hilarous

Jup pulse (interrupt) meter only right now. Perhaps later other sensors, but I don’t have a hal sensor (or gas )

Finishing deep sleep now. It’s working and functional, just have to buildin the backdoor function and then it’s finished

Released : https://github.com/koffienl/ESPimatic/wiki/Release-notes#0126

Since DeepSleep was requested, please let me know it there are any strange behaviour or bugs. Read the releasenotes regarding DeepSleep,

I can’t wait for some esp’s to be delivered… Postnl hurry up please…

Thanks for all the effort so far!

Currently no much time for testing, but some quick thoughts about deep sleep. In the wiki you should mention that it is not absolutly necessary to connect GPIO16 to RESET. Any external logic with or without GPIO16 can deliver the reset pulse. Also to mention is that if you set sleep time to zero the ESP will not trigger the GPIO16 and will sleep until manual reset. Last one question: Is backdoor open if Pimatic server is off or not reachable. In some of my older experiments a had a hardware solution by pressing a button which connects GPIO0 and GPIO2 during reset which signals to boot in AP-Mode to have the chance to reconfigure which is better for battery saving as trying a connection setup on each wakeup.

@Heizelmann said:

Currently no much time for testing, but some quick thoughts about deep sleep. In the wiki you should mention that it is not absolutly necessary to connect GPIO16 to RESET. Any external logic with or without GPIO16 can deliver the reset pulse. Also to mention is that if you set sleep time to zero the ESP will not trigger the GPIO16 and will sleep until manual reset. Last one question: Is backdoor open if Pimatic server is off or not reachable. In some of my older experiments a had a hardware solution by pressing a button which connects GPIO0 and GPIO2 during reset which signals to boot in AP-Mode to have the chance to reconfigure which is better for battery saving as trying a connection setup on each wakeup.

How DeepSleep is implementend in the current version, there is no need / use for triggering external. That’s why there is a timer in the config Smallest time to choose is 1 minute.

It will only stop sleeping if it can reach Pimatic, find the backdoor variable and if that variable is set to 1. If Pimatic is down, the var doesn’t exist or the value is something else it will go back to sleep.

@koffienl Thanks for the explanation. Now I think the currrent behaviour is mostly clear but my question is not answered yet.

First my current understanding:
If backdoor variable is set to 1 the ESP config server is reachable again at the next wakeup (depending on wake up interval might be long) or manual reset. This will last until variable is set back to zero or deep sleep mode is set to false in config web page.

Lets asume you have a preconfigured ESP with deep sleep and you would use it in a new environment (other pimatic server other network) and the old Pimatic server isn’t available anymore.
How to come out of deep sleep mode then? My idea was to have a hardware button on the ESP. Hold this button and repower and ESP will back in AP-Mode to be able to reconfigure. On an ESP-01 with limited GPIOs the solution would be a switch between GPIO 0 and GPIO 2 where the sensor is connected on GPIO 2. (http://www.forward.com.au/pfod/ESP8266/GPIOpins/ESP8266_01_pin_magic.html Chapter ‘Detecting Config Mode’)

@Heizelmann said:

@koffienl Thanks for the explanation. Now I think the currrent behaviour is mostly clear but my question is not answered yet.

First my current understanding:
If backdoor variable is set to 1 the ESP config server is reachable again at the next wakeup (depending on wake up interval might be long) or manual reset. This will last until variable is set back to zero or deep sleep mode is set to false in config web page.

Lets asume you have a preconfigured ESP with deep sleep and you would use it in a new environment (other pimatic server other network) and the old Pimatic server isn’t available anymore.
How to come out of deep sleep mode then? My idea was to have a hardware button on the ESP. Hold this button and repower and ESP will back in AP-Mode to be able to reconfigure. On an ESP-01 with limited GPIOs the solution would be a switch between GPIO 0 and GPIO 2 where the sensor is connected on GPIO 2. (http://www.forward.com.au/pfod/ESP8266/GPIOpins/ESP8266_01_pin_magic.html Chapter ‘Detecting Config Mode’)

Aha, now I understand your question. It wasn’t clear for me why one would have trouble with waking up, but if Pimatic is not there your ESPimatic will be a deadloop.
Shouldn’t be difficult to add a hardware override. Simply detect if a certain GPIO is HIGH before going to sleep. You even wouldn’t need a push button, just add a jumperwire between a (configurable) GPIO and GND.

Now I have the software running both on my ESP01 en Nodemcu. Although the Spiffs of the ESP01 needs to be changed to 128k.
I now have the following question. How do I add a dummy? temperature sensor to Pimatic. I have added the parameter and this is nicely updated by the ESP but I would like to have the same display as the DHT connected to the homeduino?
Second question is, would it also be possible to connect to the https:// connection of pimatic?

For now secure connections are not possible, the library consumes way to much memory when setting up SSL connections.

Why would you want to add a dummy temperature sensor? Just make a VariablesDevice for the updatet var and set unit to temperature:

@koffienl thanks for the quick update. I was looking for this device but could not find it.

@koffienl I just have tested the new firmware on my ESP-01, especially the deep sleep option. Realy a great work!

Now I can think only of three small improvements:

• Action on wakeup should be the same as without deep sleep, means no extra configuration necessary. Currently it is restricted to only one sensor, which is insufficient in my mind.
• Sleep time is currently limit to 1…60 minutes. Should be possible to enter larger values, lets guess up to 24 hours
• A hardware based backdoor like described in an earlier post

It would be very cool to control some neopixel or IRFZ44n with this

@Heizelmann said:

@koffienl I just have tested the new firmware on my ESP-01, especially the deep sleep option. Realy a great work!

Now I can think only of three small improvements:

• Action on wakeup should be the same as without deep sleep, means no extra configuration necessary. Currently it is restricted to only one sensor, which is insufficient in my mind.
• Sleep time is currently limit to 1…60 minutes. Should be possible to enter larger values, lets guess up to 24 hours
• A hardware based backdoor like described in an earlier post

Can you explain what it should do on wakeup? I don’t undestand what you are asking.
The maximum sleeptime for an ESP is 71 minutes, longer is not possible.
Hardware backdoor will be in future version.

@n3ro said:

It would be very cool to control some neopixel or IRFZ44n with this

I don’t have both of these devices, sou could take while

@koffienl

The maximum sleeptime for an ESP is 71 minutes

Didn’t kow that, thanks! Is Ok.

Can you explain what it should do on wakeup? I don’t undestand what you are asking.

Not sure if I am right: In the System config page on the deep sleep part you can select which sensor should be operated in deep sleep mode. You can only select one.

In non-deep-sleep mode multi sensors can be operated. What I would like to have is that in deep sleep mode also multiple sensors can be operated. Best would be the same as configured in non-deep.sleep mode. (If this would be possible the config of which sensor should report in deep sleep config could be omitted.)

In my senario I would like to have a DHT sensor, ADC (for battery level) and a PIR sensor working in deep sleep mode.

PIR would be a total different part, we should build a ESP ‘device’ where the PIR is seperate powered and able to wake the ESP.
Other devices on wakup could be implemented, but have to investigate further.
Currently I’m working on a redesign on how stuff is stored in EEPROM, also allowing more relays and DS18B20’s. When that part is finished, I can take a look on how to handle Deep Sleep actions.

Sorry to interrupt, but why does some1 want to use the ESP for sensors like a PIR with batteries? How long does the ESP last? For this kind of stuff MySensors is much and much better and lasts for more than a year on 2 AA batteries.

For actuators is a different story ofc, because you don’t need batteries.