Let's Control It

psy0rz

Jotoc wrote: ↑05 Jun 2017, 21:38 Hello all,

i miss the Checkbox "Send to Controller" for the Device Ina219.
Is this planned?

Greetings
Jotoc

we know: https://github.com/letscontrolit/ESPEasy/issues/321

it might be fixed already, try compiling the current github sources. if its fixed i can release dev11.

psy0rz

Wouldn't it be possible if we had a dump variable that let you use Deep Sleep Delay X seconds (maximum 4294) and let the ESP wake up after y number of Deep Sleep Delay Cycles. If deep sleep delay is 3600 seconds and deep sleep delay cycle is 24 then the wake up would happen once every 24 hours? Jus...

psy0rz

yellowsky wrote: ↑05 Jun 2017, 20:14 Indeed, i found some information about rtc memory but to be honest i won't be able to program it.
How is it possible to ask this feature? Of course, it is dedicated for low power usage (to boot without wifi and check if the sleep is stillpending or not).

Post an feature request on github for it.

psy0rz

Wouldn't it be possible if we had a dump variable that let you use Deep Sleep Delay X seconds (maximum 4294) and let the ESP wake up after y number of Deep Sleep Delay Cycles. If deep sleep delay is 3600 seconds and deep sleep delay cycle is 24 then the wake up would happen once every 24 hours? Jus...

psy0rz

I'm created a little project that notifies my by email when I have actual paper mail.

The ESP will always be in deep sleep and will be waked by a magnetic switch.

Look here for details: https://www.letscontrolit.com/wiki/inde ... ifications

psy0rz

You could also wake it up manually by pulling RST to GND, and using a deepsleep time of 0. Then it will never wakeup automaticly.

Dont know if this is feasible for your project.

psy0rz

sounds awesome! any pictures of your setup?

psy0rz

I created a practical example for notifications: https://www.letscontrolit.com/wiki/inde ... ifications

psy0rz

I started working on the rig: First i'm building scripts to do things like compiling/erasing flash/flashing/wifi setup/serial connections. I will try to make scripts reusable and build a clean modular rig. Eventually the scripts are able to do everything automaticly on as many ESP's as we have. So, ...

psy0rz

perhals we should do that. when we're finally at 20900 (v2.0.9) or something, it might be ok to break compatibilty and fix it properly. by that time everyone should be running version 2.

psy0rz

its more like we kept hanging too long at step 1. but im new here and it takes a few months to get "settled" in a new project an community, so to speak

now its time for step 2 indeed.

psy0rz

I agree, we should focus on fixing bugs the coming month so we can move on and finally release a beta of v2.0. :) Having all all the devs help with the awesome new features is like giving free candy to a kid. Its just too good not to take. ;) jkdesign, krikk, can you put the new features on hold for...

psy0rz

vader wrote: ↑30 May 2017, 11:27 Ok.... Must it be numeric? And when you make it alphanumeric? So it is a text variable....

If we change it, the older nodes wouldn't be able to display it correctly.

psy0rz

i would love to..but that number is only 16 bits. so it can be 65535 max. maybe its better if we change it to the builddate instead of version. we cant just make it more bits since that is part of the protocol. (wouldnt be backwards compatible)

psy0rz

Should we add an option that activates the internal pullup for the DHT?

psy0rz

I just released dev10 (its still compiling) to fix a regression with the DHT sensors in dev9. But also some enhancements with the ADC module.

It will be available for download here: https://github.com/letscontrolit/ESPEas ... .0.0-dev10

psy0rz

the DHT issue is reverted. i'll release dev10 now.

psy0rz

nice

psy0rz

Martinus that looks awesome! It pure art. :) Regarding donations: Might be a good idea. But there are multiple people involved. For example Remco is paying/sponsoring/hosting our forum , wiki and other stuff. So i cant just decide this. Ill discuss it with remco and martinus to figure out how to do ...

psy0rz

i asked krikk if he could take a look at it.

psy0rz

The discussion is going really nice ;) The question is not : do we want support for the SonoffPOW in ESPEasy? we do not support dedicated hardware devices from certain manufacturers in ESPEasy there is only support for certain hardware chips or these chips on a breakoutboard. So the real question i...

psy0rz

i'll update my own dht22 tomorrow to see whats going on.

i hope that in the future we can prevent regressions like these with The Rig: https://www.letscontrolit.com/forum/vie ... =18&t=3141

psy0rz

Which standard ESP setup's are planned? I wouldn't make much sense to have multiple setup around ESP-01 and other simular setup around the ESP8266. It would make sense to choose a standard ESP core processor like the ESP-12F and different periferal chipsets like memory (1M/4M), serial (F330) or pow...

psy0rz

We've just released v2.0.0-dev9. This time we've solved a lot of the stability issues. Jochen Krapf and krikk made huge improvements to all the static HTML code. They've replaced most of the mess with nice functions. This makes the code a lot cleaner, smaller and easier to debug. Also creating new p...

psy0rz

those serial commands are easy to implement. can you create a feature request for it?

also we already have a windows flasher gui. maybe you extent it and make a pull request. sources should be somewhere i think.

psy0rz

I use this shell script (in linux) to quickly connect my ESPEasy to the wifi, without using the wizard:

Code: Select all

#!/bin/bash

echo "
wifissid YourSSID
wifikey YourWIFIpassword
ip 192.168.1.123
save
reboot
" > /dev/ttyUSB0

psy0rz

The biggest problem I currently have is that it's difficult to test hardware and controllers after we've made changes or improvements. A possible solution for this is to create a test-setup that contains a lot of common sensors. Because I might get a financial grant to support ESPEasy (more on this ...

psy0rz

nice, thanks

psy0rz

starfish, can you make a feature request for this on github?

psy0rz

we should just re-add that feature, but never save to flash. thats not necessary for most applications that use the oled i think?

psy0rz

yeah in a later version we might have an option to import/export json format.

psy0rz

thanks for starting this guys!

psy0rz

indeed Arduino IDE should still work, and i've did make a few changes to the Arduino IDE instruction, because we've changed the directory layout.

maybe someone should update the wiki so that page is easier to find.

psy0rz

indeed, indeed. thank for reporting.

psy0rz

i could just make a config file in which you can enable/disable plugins?

psy0rz

yea that needs to be on the wiki indeed.

perhaps in the future we also can have some automatic online update option as well.

psy0rz

someone has been working on a java program that allows the end user to enable and disable plugins. i didnt have time to look at it so far.

psy0rz

Yeah we need to fix a lot of MQTT stuff still. I dont know if we have enough memory for SSL/TLS.

But making MQTT more robust and more complete is certainly something we will do in the near future.

psy0rz

as for mass upgrading, if you use the curl commandline tool, you can script an update like this:

Code: Select all

curl -v -F update=@firmware.bin http://1.2.3.4/update

psy0rz

I've added checks to prevent crashes when someone uses invalid timer values. However that check was off-by-one. Latest commit fixes it. Valid timers are 1 through 8 (inclusive). Also setting a timer to 0 sec disables it. This is usefull to create events that start and stop repeating timers: I use t...

psy0rz

lol..i've clicked your name to see what you asked, and i found this:

https://www.letscontrolit.com/forum/vie ... 481#p15481

You asked something, I saw it was a bug, and i fixed it immediately and answered you.

psy0rz

I'm a developer and i agree with the last few answers above. For developers its even a bit different: we're focussing on developing ESPEasy, fixing issues and adding features. I sometimes scan the forum, and I ignore the support questions that can be answered by one of the many competent people on o...

psy0rz

is doesnt have versioning, you can just flash any version you like.

keep in mind you cannot upgrade downgrade between ESPEasy v2 (mega) and the "classic" ESPEasy. (the ones that where numbered R1...R148)

well you can upgrade, but the unit will reset to factory defaults.

psy0rz

Last month we made some great progress with ESPEasy version 2.0. If you look at this link you can see many things have happend: https://github.com/letscontrolit/ESPEasy/pulse/monthly We've merged 33 pull requests containing 100's of improvements and fixes. Also we've closed 20 issues on the issue tr...

psy0rz

I will ask remco to fix that

psy0rz

I've added checks to prevent crashes when someone uses invalid timer values. However that check was off-by-one. Latest commit fixes it. Valid timers are 1 through 8 (inclusive). Also setting a timer to 0 sec disables it. This is usefull to create events that start and stop repeating timers: I use th...

psy0rz

Can you increase the serial log level to 10 (to get more debugging) and try again with the latest commit?

Could you also paste that log output somewhere?

psy0rz

Shardan, can you try again with the latest commit? I've fixed https://github.com/letscontrolit/ESPEasy/issues/253

Note that you can also just download the zip file from github now, without any of the previous isseus (submodules ) https://github.com/letscontrolit/ESPEas ... e/mega.zip

psy0rz

Note that this only seems to be the case for OpenHAB MQTT?

The other two MQTT controllers work differently.

psy0rz

fixed in 5c9d00c0a978d4d3137b90842f092dccd7391c85

if it doesnt work or you have problems, reopen this issue: https://github.com/letscontrolit/ESPEasy/issues/246

Search found 230 matches