That sensor is using a rather weird technique of 2 I2c addresses to read different parts of the data. Haven't seen that before, this sensor isn't yet supported by ESPEasy. For developing an ESPEasy plugin, there's sort of a standard procedure: - Request a new plugin ID at https://github.com/letscont...
@antro31 I've changed the argument separator for this plugin from comma to dot (period), so after you update to this GH Actions run, you'll have to update your rules!
So you'd have to use like this: [Pool#sensorstats.1.success]
This will go into the release version, so no reason not to update
I2C Scan should at least list the address, the device names may be excluded, not sure if these names are included in the Custom build. You can enter the found address in the I2C Address field, but I assume you already tried that. Adding a 10k pull-up to 3V3 on both SDA/SCL should fix the pull-up sta...
A few questions: - How long are the wires to your sensor? - Do you have pull-up resistors installed on the SDA and SCL lines? - You didn't swap the SDA and SCL wires? (no harm, but won't work) - Was the sensor used by someone else before you got it, and reprogrammed it to I2C Address 0x01? - I assum...
Ah nope, saw what Ton did: https://github.com/letscontrolit/ESPEasy/pull/5051 A bit strange to use a comma here, as we don't do that anywhere else. Why not a dot, Ton? Well, I did that also in other plugins, like P011 and P087, and in AdafruitGFX_Helper (for all supported Display plugins P095, P096...
That plugin has the plugin statistics enabled, but that entire feature is disabled for the Collection, Minimal and 1M (like the ESP01S) builds (and other 'bin-size limited' ESP8266 builds)... :shock: When buying new ESP's go for an ESP32 (dual-core, stable workhorse), ESP32-S3 (dual-core, many GPIO'...
Ah, that's because of the limitations for binary size, then the later added sensors (Adafruit and the new BeFlE v3) are excluded :o I'll create a custom build for you, and upload it here later today (I'm not near my ESPEasy development system ATM :?) Are there other plugins required for your build t...
According to this page the DHT22 should be quite OK, but maybe it suffers condensation where it is currently located, and is disturbed by that. Reading that list above, it seems the ATH20 is a better choice, as it has a range of 0..100%RH, where the DHT22 only allows 5..95%RH In another story I read...
@Dick60 I've added a PR that should resolve your issues, it adds an event <taskname>#Address,<state>[,<address_high>,<address_low>] when the new option Event with iButton address is enabled and the Device Address is set to None. A test-build can be obtained from this GH Actions run Please report you...
I've created pull request #5049 to add support for the new BeFlE v3.x hardware, based on the updated code in the BeFlE SoMoSe repository @sptotal I haven't planned to order the new sensor, but I assume you are ordering one. Can you test the code from the PR on the actual hardware? Download binaries ...
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...
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...
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...
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.
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...
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...
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.
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...
@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
@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.
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...
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...
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
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...
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.
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 ;)
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)
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 ...
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)
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...
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...
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 ...
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...