Let's Control It

Ath

That smells like a bug, can you report this on Github, so it doesn't get lost? https://github.com/letscontrolit/ESPEasy/issues

Ath

Well, the bug is probably that "&para" is replaced, instead of the actual html code "¶".

Ath

The simplest would be to add a rule for acting on a change of your sensor value: (DHT11 is the name of the sensor in the Devices list) on DHT11#Temperature do 7dt,[DHT11#Temperature] endon This requires you to enable the Rules engine in the Tools/Advanced page (Leave Old Engine enabled as well)

Ath

TD-er wrote: ↑12 Aug 2020, 11:27 I added a reminder for me on Github: https://github.com/letscontrolit/ESPEasy/issues/3207

And I PR'd https://github.com/letscontrolit/ESPEasy/pull/3208 to implement suggestion a) from my list above.

Other options are still viable, IMHO, but this one seems eminent.

Ath

In that case there are a few ways to resolve this: a) Remove the Wire.setClock(700000) setting and let it run at the configured speed (though that may influence the screen-update speed). It is only set on initial setup of the display. Already in PR #3208 or b) Reset Wire.setClock(Settings.I2C_clockS...

Ath

I hope you got the latest sources from github? When using a Normal build of ESPEasy, both plugins P024 and P036 are included, so no need to make a custom build for that :o Latest releases (compiled binaries and matching source code) can always be found here: https://github.com/letscontrolit/ESPEasy/...

Ath

... i did a factory reset and reentered every single setting. Now it is working again... That is to be expected, as the flash is 'formatted' during the factory reset, you started with a clean slate :) ... I'm testing your espeasy software very hard at the moment (i'm a developer too) trying to find...

Ath

Looking at the log you posted, it seems you may have some kind of networking issues, as the MQTT host can't be reached. Or is that enabled and not configured properly?
If the networking/WiFi interface is quite busy, all kinds of weird stuff may happen.

Ath

What exact release of ESPEasy (name of the .bin file please) do you have installed on your ESP?

Ath

buzzger0815 wrote: ↑10 Aug 2020, 13:07 By the way, im on "20109 - Mega" on a esp8266-01.

Most clear version to report is the name of the .bin file installed on your board, as '20109' is the version of the internal settings structure, and that doesn't change for every released version.

Ath

Well, it shouldn't matter what type of ESP8266 board you are running for this type of action, as they are all based on the ESP8266EX chip, that (usually) runs at 80 MHz. (ESP32 is a different beast, with dual cores at 240 MHz) A bit weird though that the first rule execution isn't completed before t...

Ath

There are (at least) 2 ways you can try to resolve this: 1) Allow for some background processing during rules (unsure if this will actually work though) Publish,"leinwand/status","going-down" Delay,0 // The delay command is advised not to be used, thought the exception seems to b...

Ath

Good day! I still couldn't find your driver on the forum. I hope to start a plugin (or extend an existing one) for ST7735 (128x128px/128x160px/80x160px) soon (a.o. waiting for hardware from Ali), and I'll investigate if ST7789 (240x240px/320x240px) can also be supported (but often that last resolut...

Ath

TD-er added a pull-request implementing a timer with milliseconds resolution, and 2 repeating (loop) timers (no need to restart after the timer fired, with seconds and milliseconds resolutions). It can be found here: https://github.com/letscontrolit/ESPEasy/pull/3204 There are downloads available fr...

Ath

TD-er added a pull-request implementing a timer with milliseconds resolution, and 2 repeating (loop) timers (no need to restart after the timer fired, with seconds and milliseconds resolutions). It can be found here: https://github.com/letscontrolit/ESPEasy/pull/3204 There are downloads available fr...

Ath

Adding an 'eventlog' line in the script is often quite helpful:

Code: Select all

On Rules#Timer=1 Do
EventLog,"%sysname%/%unit%/IP,%ip%" // removed some quotes!
Publish,"%sysname%/%unit%/IP","%ip%"
timerSet,1,30 //Resets the Timer 1 for another 30 seconds
EndOn

Ath

But are you (also) starting the timer in the on mqtt#connected rule? It doesn't start by itself...

Ath

Those very compact plugs are usually quite hard to disassemble in a way they can be safely re-assembled later. It seems to suggest in the picture it is tuya based, meaning that alternative firmware is possible, but I've never tried to flash ESPEasy in that way. (A tuya update tool can be found by th...

Ath

And you seem to have gpio0 hard-wired to gnd? I ground it during reset, hold it down for a few more seconds, then release it.

You already have a nice breadboard in use, you could easily add a couple of buttons for reset and 'pgm'

Ath

P095 is meant to drive a ILI9341, not the ST7735s, and I'm not sure how compatible these chips are.

The TS_CS should be a chip-select signal, to be able to have multiple displays on the same SPI bus, but I don't know if that is supported by ESPEasy (don't own that type of display, so can't test)

Ath

Are you using a SysLog server? That seems to cause issues with some ESP's or configurations. You could try switching that off.

Ath

If you could connect the LED on a standard GPIO port, then you could use the

Code: Select all

longpulse_ms,<GPIO>,<state>,<duration>

command to turn it on for a number of milliseconds, using a higher resolution timer.

Ath

After installing the latest release from https://github.com/letscontrolit/ESPEasy/releases on your device, you might also read this thread about the 'accuracy' of the timers: https://www.letscontrolit.com/forum/vie ... f=2&t=7849

Ath

Time problem for Presence simulation on Light#Lux do if [Light#Lux] < 25 and %systime% < 23:15:00 and %systime% > 16:30:00 GPIO,2,0 elseif [Light#Lux] < 35 and %systime% < 7:30:00 and %systime% > 6:30:00 GPIO,2.0 else GPIO,2,1 endif endon on dummy#switch=0 do event,lightoff on dummy#switch=1 do eve...

Ath

Have you tried swapping RX and TX?
Some tend to document it as a 1:1 connection, instead of a TX -> RX and RX -> TX (crossed) connection.

It doesn't hurt the unit if you had them connected in the wrong way, AFAIK

Ath

We would appreciate if you could share the details, please.

Ath

SendToHTTP 172.19.0.63,80,/json.htm?type=command&param=udevice&idx=1009&nvalue=0&svalue=[SI1145#UV] That smells like you are using Domoticz, right? You should be able to use the Domoticz HTTP or MQTT controllers to send that data there. After setting up the controller, you should on...

Ath

Ehm, since release mega-20200426, the ILI9341 plugin has been included as P095, but I'm not sure if it is included in any of the standard builds (it's quite large when all libraries are linked in). You could suffice with just enabling it in define_plugin_sets.h for the PLUGIN_SET_TESTING or add it t...

Ath

Have you added #define USE_CUSTOM_H somewhere in your source or in your build environment?

Ath

Then don't worry! I just won't be using these displays with espeasy. I will attach them to arduino. The advantage of these displays over the OLed displays is that they are a bit larger, thus easier to read from some 'distance' (~1 meter), while an average OLed requires me to be within ~60 cm to be ...

Ath

I have two such displays. I would like to use them in ESPeasy. Maybe someone will give me a fresh build, including a plugin for NOKIA5110? Well, it's a bit hard (for me at least) to create a build, for a couple of reasons. a) It is an older plugin, and uses no longer supported functions and objects...

Ath

What version of ESPEasy is installed on your board?

Ath

Any time sofar that I encountered issues like that, my wiring was broken (I tend to use patch wires for that), so you might want to check or replace your wiring.

Ath

Have you read this support issue: https://github.com/letscontrolit/ESPEasy/issues/2724 ? You have your quotes mixed up, no need to combine ' and " around a single token. something like this, copied from your post and quoted as intended Publish homebridge/to/set,'{"name":"ESP62.Le...

Ath

A few more questions:
- What version (.bin filename is the most informative) of ESPEasy do you have installed on your ESP's?
- What type of ESP's do you have, ESP8266 or ESP32?

Ath

Due to the nature of the sensor it seems appropriate to ask if you cleaned it, before putting it back to use?
These kind of sensors seem quite sensitive, and excessive dust inside the sensor sounds like a plausible cause of malfunctioning.

Ath

You can go 3 ways to have the temperatures sent from the TempEsp to the OLedEsp: Use SendToHttp ( the most generic and independent* ) Use the Inter-ESPEasy network ( the easiest to use* ) Use the ESPEasy P2P Networking controller ( a bit finicky but quite doable* ) (* that is my opinion , not a verd...

Ath

Well, as said, I mostly took up this project to try and apply the hardware 'patch' on the shelly, and even though I still can't measure voltage and current, the original challenge succeeded for most part. Voltage and current would have been 'nice to have', but I can live without it :) I haven't been...

Ath

When looking at the shunt (first photo, above) it most likely has a 1 mOhm resistance, at least the print on R20 can be read as '0.1'. That is also the defined value in the source, and should result in the correct factor. My multimeter isn't accurate enough to effectively measure that kind of resist...

Ath

I'm pretty confident the bulb doesn't have a switching powersupply, but I don't think it's halogen either, that may be from my imagination, or some text on the box it came in, I can't recall that, and the box went down the paper 'archive'.
It's this closeup:

: 20200719_095212.jpg (1.71 MiB) Viewed 21807 times

Ath

Are you certain about the correct factor for the power? Well, with a 53 watt 'eco' bulb (halogen) I got a power value of around 180, so I corrected for that. The other values are the sensor defaults. Quite often those power measurement chips only output the VA and not the power in Watt. So they don...

Ath

I recently bought me a Shelly 1 PM WiFi switch with the intention of using the Power, Voltage and Current measurements. After receiving the aparatus, I realized I didn't do my due diligence properly, as this specific device doesn't actually support Voltage and Current measuring :o Luckily, a user of...

Ath

Well, you can open an extra browser-tab with the log, and do your action(s) in the initial tab, the log-update should continue

Ath

TD-er wrote down a procedure to flash ESP32 boards here: https://www.letscontrolit.com/forum/viewtopic.php?f=5&t=7697&p=44667&hilit=esp32+flash#p44622 You shouldn't use the download from that post, as they are a bit 'old' now, you'd better get the latest from the releases page I linked a...

Ath

momo3000 wrote: ↑25 Jun 2020, 12:28 Where i can find default factory bin files?

They are included in recent builds of ESPEasy, in the bin directory. Latest releases can be found here: https://github.com/letscontrolit/ESPEasy/releases

Ath

Hi, welcome to the forum! Most ESP32 boards have 2 buttons, one usually labeled Boot or B and one Reset or EN. To go into flash mode, press and hold the Boot button, and then press the Reset button shortly (about half a second is fine). I usually hold the Boot button for a few more seconds, and then...

Ath

How do you think it can be configured so that if there is no change of state then there is only one record in the log? Well, that is completely against the nature of logging. Logging is to be sent out of, and away from, a system or application, to prevent being compromised when that system/applicat...

Ath

First a warning: Don't make ESP devices running ESPEasy directly accessible from the internet (you have probably read that before on this forum, I just want to emphasize it again). At lease include some type of VPN or other secure remote control option. The limited security that is available in ESPE...

Ath

With the newer ESPEasy versions, you might want to uncheck the 'Append Unit Number to hostname' option on the Config page.

Ath

You say you changed the ip-address, does that mean you sent data to a non-existing ip with the sendtohttp command? If so, it could explain the reboots, as sendtohttp waits for an ack from the destination, but as that doesn't respond, the watchdog timer forces a reboot as the unit is not responding d...

Search found 3526 matches