Let's Control It

Ath

Have you tried to configure the counter in a Device slot other than 4? There has been a report here that the 4th device wasn't counting, for as of yet unknown reasons (AFAIR), maybe this is also the case here.

Ath

Well, we'll need a bit more info then. - What version of ESPEasy was initially installed? - What version of ESPEasy do you have installed now? - What short-circuited that made it stop working? - What plugins do you have active? - And how are the sensors for these plugins connected? (wiring-type + gp...

Ath

Koenig wrote: ↑24 May 2020, 16:03 The power supply is perfect, that cannot be the problem.

Well, to be really, really sure, can you try another power supply?, as, from where I'm looking, it seems it is not proving sufficient power to your ESP...

Ath

Well, I was trying to write that when a status change on one end (Domoticz) causes a status change on the other (ESP), that then is causing a status change on the first end again (Domoticz), you are causing an endless loop, by design. I have the example of my Sonoff S20 switch(es), that are keeping ...

Ath

Well, the documentation is quite easy to find using standard Google fu, this page is pretty clear: https://petergodwin.wordpress.com/2016/ ... 266-board/

I just hope you haven't waited (or held your breath) for an answer all these days...

Ath

Sorry to barge into this discussion, but IMHO this is not an issue of ESPEasy, but of the way it is configured. When both sides trigger the other side on a status change, then only an endless loop can be created. It is impossible for each side to know that only a status update was sent, instead of a...

Ath

TungstenE2 wrote: ↑20 May 2020, 22:22 Is this a bug or a feature?

Well, it's supposed to be a feature to create 1 rules file per event, but I'm not sure how to define a user-defined event here, as the # is a mandatory item in the name.

'Been there, done that' kinda situation (till I found that Old Engine checkbox

)

Ath

TungstenE2 wrote: ↑20 May 2020, 20:13 Only rules are gone. Also rules page looks strange.

Have you been using the Rules with 'Old Engine' option disabled? I think it was default off a couple of releases ago, but been (re-)enabled by default shortly after that. This setting is hiding in the Tools / Advanced Settings page.

Ath

You're almost there, something like this should work:

Code: Select all

On switch1#State do
  event,generalswitch
endon

On switch2#State do
  event,generalswitch
endon

On generalswitch do
  if [switch1#State]=1 or [switch2#State]=1
    gpio,0,1  // Turn on
  else
    gpio,0,0  // Turn off
  endif
endon

Ath

LeanzLatino wrote: ↑19 May 2020, 21:30 It doenst seem to change i have also tried.

Have you tried the example @dynamicdave gave? That uses the quotes around arguments containing spaces or commas, as required in current releases of ESPEasy

Your last examples have invalid JSON

Ath

I'm looking for a compiled file where TASKS_MAX is greater than 12? Currently, only the ESP32 builds support over 12 tasks, 32 to be exact. Downloads are available from the ESPEasy Github releases page You will need the Esspressif ESP32 flash tool to upload it to the device, or install the VSCode/p...

Ath

Today I completed my PV display project. It consists of a Wemos D1 clone, a 1.3" OLed display and a APDS-9960 gesture sensor. The PV data is sent to the fixed IP address of the Wemos, and the string that is displaying the Start and Update times is also formatted and sent externally. Data is gat...

Ath

According to the specs of the reed switch that should not happen. Or do i see that wrong? If all things in life happened according to specs, what would be the fun of that? :D So i just figured out that when i add a 1 Ohm resistor in series to the reed. It all works as i wish. But still... Not 100% ...

Ath

I suspect that the power that your Wemos is using is enough to make the reed-switch 'stick' once turned on. You probably need a simple circuit using a relay board to turn your Wemos on and off, where the relay-circuitry (not just a simple relay!) will draw significantly less power than the Wemos. So...

Ath

I thought of an alternative to your rules to extend to 16: (Because of the rather large number of script lines, the 1 second timer delay may be a bit extended, maybe subtract a few percent when using larger numbers like > 100?) NB: Untested code! on LongpulseGPIO do // usage: event,LongpulseGPIO,<gp...

Ath

I was going to try an ESP32 with a relayboard, but the optocouplers on mine are all powered with 3.3V, so no easy way to replay your situation.

Ath

Do you have a ESP8266 board available to check if that is able to 'longpulse' the relay? I'm a bit puzzled that your ESP32 isn't able to perform such basic functionality, so I suspect there is some incompatibility with that reley board. It could be related to the 5V supplied to the optocouplers, and...

Ath

Have you tried adding a pull-up resistor (10k should do fine) to that output pin?

What board are you using?

Ath

Is the voltage of the battery enough to get the motor turning? Possibly the voltage drops too low when it tries to turn...

Ath

What is your build environment? ArduinoIDE, VSCode or Atom?

What branch are you trying to compile?

Ath

Oefff, version 120 is over 2 years old, and not very up to date, so that's why you are missing the LongPulse_Ms command. As I suggested earlier, please upgrade to a more current release, there have been many after R120, the latest is always available from here: https://github.com/letscontrolit/ESPEa...

Ath

Well, I just built your scenario, but I'm not sure you have stuff set up right: - My led is on GPIO5, and it is active-low, not active-high as you seem to have (on high the GPIO doesn't deliver much current, though on low it can pull some current) - My switches are set up as Normal Switch, with inte...

Ath

How can I program the switch-on threshold in rules that Realis does not hear heard coming in and going out. Maybe with a timer? I'm don't fully understand what you are asking. Do you want to silence the sound of the relay when it turns on or off? I wouldn't know how to have a relay make less sound ...

Ath

publish command which is: device =% sysname% & taskid =% id% & cmd =% valname% & value =% value%, when i click on sumit it only keeps: device =% sysname% i don't know why. The spaces in your command are intentional for the forum? Or are they also in your settings? In that case: remove t...

Ath · Re: servo rules asuz wrote: ↑03 May 2020, 16:50 Perfect You're welcome

asuz wrote: ↑03 May 2020, 16:50 Perfect

You're welcome

Ath

Well, that's not a biggie, I can fix that :o I've used a Dummy device so I could monitor it in the Devices page, but we can also use a uservar (let,1,x and [Var#1], there are 16 available) as I've done below: on ServoAction do servo,1,4,180 timerset,8,1 // Extend as needed if the servo doesn't make ...

Ath

That WD log line is just the WatchDog that logs some of the current status in INFO log mode, nothing to worry about. Is your servo now moving as expected? If not, lets try some manual commands: (you'd find that on the Tools page, don't copy the quotes I used) entering the command "servo,1,4,180...

Ath

Hmm, this is getting a bit weird. A few questions: What type of servo are you using, because the code I shared is actually tested on a MG995R, that can move from 0 to ~180 degrees. What version of ESPEasy are you running? It should best be a 2020 made release (20200410 seems very stable atm), though...

Ath

Many moons ago, I experimented with 'aiming for the light' too, and built me this, now disassembled, tiny rig: IMG_20200503_103330a.jpg IMG_20200503_103417a.jpg IMG_20200503_103426a.jpg IMG_20200503_103512a.jpg (Dismantled it for easier storage) It consists of 3 TSL2561 I2C light sensors (3 only as ...

Ath

Ah, that's a very inconvenient shield, I've used loose components only, so I can connect them to any GPIO.

You could cut the connection to D2, and rewire to another GPIO to avoid this issue, but it will require a bit of soldering handyness

Ath

In the 'on ServoDone do' event the value has to be 9000 to turn off the servo, not 360. That 360 will bring the servo as close to 360 as it can, being 180...

Ath

mjdb wrote: ↑02 May 2020, 18:27 By the way... If someone has an idea to use more then twelve devices without compiling EspEasy I would like to hear it.

Well, that's quite easy, get an ESP32, ESPEasy allows 32 devices on that hardware

Ath

Have you tried changing the High DPI settings in the Compatibility tab of the shortcut's Properties page?

Ath

You can wait to put it into Flash-mode until it actually is trying to connect, it might be looking for the 'download' message to be sent before it starts to actually flash.

(I'm usually uploading from VSCode after a build, and just bring it into Flash-mode when it starts connecting...)

Ath

The DS18B20 Temperature Sensor Module voor Wemos D1 has hard-wiring for GPIO4, pin D2. What makes you think that? I haven't seen this behavior anywhere, except when you connect a sensor to a port already used/configured for something else, of course. Usually a Wemos has enough free ports so you can...

Ath

At first my ESP32's didn't want to flash either following your procedure, as it seems the UART method of bringing them into flash-mode doesn't work. My current procedure is to bring them into flash-mode by holding down the Boot button, shortly pressing the EN button, hold down for a few more seconds...

Ath

Did you add a pull-up resistor (4k7 or 10k work fine here) to the GPIO port?, that does seem to help. The internal pull-up is often too weak (80-100k)

Ath

Ath wrote: ↑02 May 2020, 13:13 I'd go for something along these lines:

What I was trying to say was: I didn't test that code

The servo command is a bit tricky, it seems, you need to give the servo command some time to move the actual servo, I ended up with this:

Code: Select all

final script is below...

Ath

I'd go for something along these lines:
Assumptions:
Action times: 08:00, 15:00, 22:00
GPIO: 15
Servo movement: 0-180 degrees, (some only support -90 to 90 or -135 to 135 degrees, as stated in the documentation)

Code: Select all

final script is below...

Ath

What value have you set for default_envs in your platformio.ini?

NB: I'm assuming you use VSCode with PlatformIO as a build environment, as you didn't mention anything about that... I'm not using, nor interested in, Arduino IDE

Ath

To disable other plugins, just add // in front of the #define USES_... lines for plugins you don't need.

Ath

asuz wrote: ↑01 May 2020, 12:05 I cannot make a rule is there any help?

Do you mean you have Rules still disabled (default setting on a cleanly installed device) in Advanced config, or you don't know how to write rules?

Ath

I think it should be added in define_plugin_sets.h, in the section that starts with #ifdef PLUGIN_SET_TESTING, but that's assuming that you have chosen a testing build in your platformio.ini (I'm using this one: default_envs = test_beta_ESP8266_4M1M for ESP8266 and test_ESP32_4M316k for ESP32) It is...

Ath

Have you added

Code: Select all

#define USES_P103

in your configuration somewhere?

Ath

This feels like a quiz :D A NodeMcu V1 board does have quite a couple of available GPIO's, and it looks like it even provides 13, and an ESP32 has even more, and ESPEasy also allows for 32 devices on that chip. Both boards allow for using GPIO extender boards via I2C like the MCP23017, that provide ...

Ath

I'm getting quite good results from BME-280 (not to be confused with BMP-280), though it may need some temperature calibration by applying a formula to the value (%value%-6), as in my situation (bought cheap clones from Aliexpress) they return a bit too high temperature values. Humidity and barometr...

Ath

(prototyping is fun, but what to do when it finally works???) put it in the back of a cupboard forget it for a couple of years :roll: find it again while searching for something totally different wonder yourself what the hack* it is, take it apart, and be amazed about the primitive parts found insi...

Ath

Not sure this belongs in the experimental forum, hardware seems more appropriate, but we'll see if a moderator moves it

Do you have any info on the lcd controller and possibly other ic's that are used? It is rather hard to find anything without that kind of information...

Ath

Close, but no cigar

Try something like this (air code...)

Code: Select all

on Analog#Value do
  if [Analog#Value]>448 and [Analog#Value]<554
    // first button pressed
  elseif [Analog#Value]>548 and [Analog#Value]<654
    // second button pressed
  elseif ...
    // etc.
  endif
endon

Ath

how i have to connect the pull-up resistor of 4,7k at every gpio that will used as input? Pull-ups are normally only needed on input ports, and most commonly, as the name suggests, they are connected between VCC (3.3v) and the input. And yes, each port should get its own pull-up. I always connect t...

Search found 3562 matches