Let's Control It

Ath

Well, the value read from the board is an int32 (32 bit integer), that can hold a max value between -2147483648 and +2147483647, so you're not yet close to that limit. The value read from this sensor should be seen as a relative value, and as you have proven, is (mostly) related to the board, not so...

Ath

You mean calibrate from raw value to real units or something else ? I just compare now raw value bettwen two identical constructions. Yes, as said, the analog voltages can be very low, so amplification has to be high to get measurable values with enough resolution, so calibration is required to mat...

Ath

Problem is new HX711+D1. But i try 10pcs of hx711 and still overlimit Ok, reduced to a hardware/board issue, that's unfortunate, but not much ESPEasy can do about that :? Edit: NB: You always have to calibrate the board and the sensor using real world weights, as there are analog parts involved, th...

Ath

Have you checked your wiring? Don't make that too long, (triple)check the soldering/connections, the sensor-side is really low voltages, so quite sensitive to external influences.

Ath

We're not using the library from BeFlE, (and looking at that code makes me really unhappy, seeing f.e. the inconsistent method naming and the many spelling errors :(). When will that sensor be available? as it looks best & easiest to me to have it added as a new/extra model to the plugin, and in...

Ath

I found only 1 Failure in the actual Firmware but i dont know if this is for every S2 version. In the "Hardware" section of the ESPEasy FW the LED is not GPIO-4 (D4) it is GPIO-15 (D?). A couple of issues here: The manufacturer can decide to provide a LED on any GPIO they desire. The GPIO...

Ath

Are you running ESPEasy on your board, or 'plain' Arduino, or IDF?

Ath

Your MQTT broker is returning a 'Relay....' command to your unit, when you publish to the Relay topic.
This implies your configuration issue is in the MQTT broker, not on the ESPEasy side. ESPEasy doesn't have a 'relay' command, AFAIK.

Ath

kniazio wrote: ↑03 May 2024, 10:12 Has anything changed regarding RF Switch?

Well, no, still too much going on

but I do have the intention to implement these plugins.

Ath

As usual in IT, "It depends" :lol: - ESP8266: Skip that, as it's (IMHO) outdated, and really limited, in both RAM and max. bin size (The amount of work to make ESPEasy fit is increasing with every useful feature we try to add) - ESP32 (Classic): Fine for most tasks, great if you need Ether...

Ath

@knighToFdemonS The PR has been merged, and will be in the next ESPEasy release.

Ath

@oisisi The PR has been merged, and will be in the next ESPEasy release.
I originally started working on ESPEasy code, because of the poor configurability of this plugin...

most likely you need to tweak the settings, indeed

Ath

@jgrad The PR has been merged, and will be in the next ESPEasy release.
It also now has the added feature of sending events for P2P Nodes when they 'join' or get 'out of sight', for you to respond on.

Ath

@damiak The PR has been merged, and will be in the next ESPEasy release.

Ath

Thats why I was asking how the reset-pin works in ESPEasy and about the "try to clear i2c bus if stuck" option. Currently iam trying to have this option disabled and see what ESPEasy will do in case of a bad sensor. I can see the "clearing i2c stack..." in the log but it pops up...

Ath

Any particular device you use that requires this? As the only I2C sensors I know that are causing I2C bus-issues are the ATH10 & AHT15 temperature/humidity sensors, but those are of mediocre quality anyway, out of production by the original manufacturer, and have properly working replacements in...

Ath

antro31 wrote: ↑29 Apr 2024, 20:37 Even if available only through rules, it would be fine.

That's what I was thinking of, as it's the easiest, and probably most compact, way of adding it.

Ath

This data is currently not available, other than via the web UI. It can however be made available, after a little coding effort

I'll see if that can be added without adding too much code, as this plugin is included in many builds, and some are really cramped for binary size issues

Ath

The actually esp2688 is still build in a small housing, to change the hardware, I think I have to build a new housing. The smallest ESP32 I own are the same size and pinout as an ESP01S (using an ESP32-C3 ), so 'quite small'... a little larger are these C3/S3 units , still smaller than a Wemos D1 o...

Ath

Can you test using the neopixel, with LittleFS enabled, build I mentioned before? That uses the latest IDF 5.1 framework, that solves many issues still present in the IDF 4.4 used by non-LittleFS ESP32* builds.

Ath

The neopixel_ESP32s3_4M316k_LittleFS_CDC build should do the trick here. Be aware that the storage is not migrated from the default SPIFFS to LittleFS, so while you can do an in-place upgrade, then all configuration (except WiFi) will be gone! Or just grab an unused board, then you'll loose nothing ;)

Ath

Well, the simplest way to get that going is to use an ESP32 Collection B build (or MAX if you have an ESP32 with 16 MB Flash).

AFAICS, the Custom ESP8266 builds currently also get LIMIT_BUILD_SIZE set, causing the statistics/graphs options to be excluded

Ath

The build you're using doesn't include the statistics collection, so no average values are available

(it's missing the checkboxes to enable that for the Values)

Ath

Definitely! And as soon as you jumped in, it was a little Apple marketing like: „it just works”. 😉 Thanks again to everyone involved! Thanks for the compliments 8-) Well, now I could think about a PCB to make it nice and neat. 🤔 No idea if more people would be interested, but maybe wrap it up this ...

Ath

So this turns out to be a successful project

Ath

What GPIO pin are you using, and does your board have PSRAM on-board? (H4R2 indicates it has 2MB PSRAM, so pins 26..32 should not be used, and also, there is a warning about using ADC2 pins)

Ath

A few check questions:
- Is your NeoPixel powered at 5V?
- Do you have a 3.3V/5V level converter installed between the ESP and NeoPixel?

Ath

Here is ESP Room SmartMonitor V3. This design may give you a reference. https://www.pcbway.com/project/shareproject/ESP_Room_SmartMonitor_V3_8a9e5a39.html It uses DHT22 (Temperature and humidity sensor) and BH1750 light sensor. For dust sensor, you can use PMSx003 modules. https://espeasy.readthedo...

Ath

AndyZZ wrote: ↑27 Apr 2024, 14:17 What is info#update ?

A small typo, should be "on info#uptime do", the rest of the script is ok.

Ath

And having "SendToHTTP wait for ack" enabled will cause similar slowdowns with poor WiFi connections.

Ath

Something like this: on system#boot do LoopTimerSet,1,5 // Perpetual repeating timer endon on rules#timer=1 do let,1,%v1%+1 if %v1% > 4 let,1,1 endif if %v1%=1 DotMatrix,txt,1,"Value1: [MQTT#Value1]" elseif %v1%=2 DotMatrix,txt,1,"Out 2: [MQTT#Value2]" elseif %v1%=3 DotMatrix,txt...

Ath

It seems that those who use p2p a lot care little about the reliability of the parameters used. Well, we seem to differ in opinion on that then, but that's no problem. Using the P2P connected sensors without issues for a long time, and actively developing on ESPEasy, so if there would have been an ...

Ath

We already have 3 Light/Lux sensors supported, P010 - BH1750, P015 - TSL2561 and P074 - TSL2591. Only P015 has RTD documentation available, and P010 has the old Wiki docs available. They don't have a max. lux range comparable to the VEML6030/VEML7700 but are fine sensors, and are available in nearly...

Ath

Are you working on a new plugin with ID P168? As I'm about to assign a number to another planned plugin, but if you are already using that I can also register yours and select the next ID to my planned plugin. Just provide a name and purpose for your plugin.

Ath

ESPEasy supports only 1 MQTT controller to be active at 1 time for sending out data (the first one is used). Simplest alternative is to switch your sensors sending all data to Domoticz from rules, so the Domoticz controller can be disabled, then configure HA Controller configuration during the trans...

Ath

Ah, I got the impression you could calculate the lux from available values, but that's not the case. I've ordered a VEML7700, that appears to be compatible in lux range with the VEML6030 but is quite a bit cheaper :?, and have to check specs if they are also (fully) software-compatible. Any reason f...

Ath

Then try:

Code: Select all

DotMatrix,settxt,1,'Pool: [Sens#TEmp]║C'

Ath

bison00 wrote: ↑24 Apr 2024, 21:02 How can I do this in Rules?

Code: Select all

DotMatrix,settxt,1,'Pool: [Sens#TEmp]{D}C'

Ath

Well, "&deg" is not the way to get that degree symbol shown, you should put the ASCII character 186 there: º
Possibly using {D} could work, don't have a display at hand to test, ATM.

Ath

Of the available fonts, only the Extended ASCII font supports the degree symbol. Depending on the build you're using, this font may or may not be included, you can check that in the Font dropdown list.
The font overview shows what ASCII character to use for making it visible.

Ath

What's special about this sensor that you can't get from either the already supported VEML6040, VEML6070 or VEML6075 ?

Ath

BartSr wrote: ↑23 Apr 2024, 20:52 I looked into https://td-er.nl/ESPEasy/
but from there I might have overlooked but anyway, couldnot find a binfile .

It's there:

: Screenshot - 23-04-2024 , 20_59_28.png (7.47 KiB) Viewed 281 times

Ath

In the list of plugins you can see that this plugin is in the Normal plugin set, implying it's available in nearly all builds. For 1MB ESP8266 units, like the ESP01, there is a Normal 1M (_not_ 4M1M !) build available that you can upload.

Ath

You could make that dependent on a GPIO pin (with a switch connected), so it doesn't 'waste' all that energy keeping the AP active, as that uses more energy, also when not needed, as that remote site you won't be visiting often, I assume

Ath

bastler11 wrote: ↑18 Apr 2024, 11:51 I had a look on this board:

https://www.amazon.de/dp/B0CRYJC3NW/

Have you seen the real-world dimensions of that display? (the images are somewhat misleading, IMHO) It's only 44mm wide, and 56mm high. And with that 480x600 resolution could result in very small text being displayed

Ath

Can you also add possibility to fetch load of selected node? Well, I wasn't sure if that would be useful, but as you're asking for it I've added it. And I also added the Type column value, both numeric and string-converted, that shows the type of chip in the remote unit (not only ESP's... ;)) A new...

Ath

For uploading files onto the local file system, there is a button "File browser" (near the bottom of the Tools tab), that has an "Upload" button to add files there. The files have to be on the device where you run the webbrowser. There is a little snag in your intended setup: Aft...

Ath

The temperature offset seems consistent for this sensor, as I see a similar delta. The intended use of the sensor is for temperature compensation of the measurements, not to supply the ambient temperature value :? when configured for Ikea Vindstyrka, an additional compensation is applied in the code...

Ath

@jgrad I've created pull request #5039 to add the request conversions. The names are somewhat different then requested, as conversions are required to start with "%c_". Quick documentation available in the PR. (Documentation is also updated, and will be deployed on ESPEasy RTD when the PR ...

Ath

It seems your browser doesn't download additional files from the cdn (content delivery network) implying that access to the internet (by the browser) is required, sometimes it's enough to do a forced refresh in the browser, if that won't work, you can also upload the .js and .css files to the filesy...

Search found 3549 matches