Let's Control It

TD-er

Do you have a link to those boards?
Then I can get some to test why it doesn't work.

Or maybe can you send me one via the mail?

TD-er

Ah the new feature added yesterday is already being used

(the 0x hex notation)

Better to use a comma instead of a space, since using > 2 spaces may cause issues (or a tab) to determine what parameter it is.

TD-er

If the code is already known, you can program it in the rules running on the IRsend node.
Then you simply must trigger an event on that node to execute that part of the code.

Events can be sent via lots of ways, like HTTP, MQTT or the p2p protocol.

TD-er

I don't know how much of it is already present in the ESP32 core libraries. (or maybe even ESP8266)
If it is already supported, then it will not be that hard to implement and it may be a nice addition as SPI does use a lot less GPIO pins compared to RMII based chips like the LAN8710A/LAN8720A etc.

TD-er

Hmm never heard of Windows rejecting to connect to the AP of the ESP. Can you try to connect to the ESP via (USB) serial? For example using some terminal program like Putty with 115200 baud (default for other serial settings) When connected, the ESP is likely to reboot (if the board uses one of thos...

TD-er

Welcome

Good to have some "oude rot in het vak" among the users

TD-er

invalid conversion from 'boolean* {aka unsigned char*}' to 'boolean {aka unsigned char}' [-fpermissive] boolean* is indeed not the same as boolean (without the asterisk). boolean* is a pointer to a bool. (or actually an unsigned char according to the error, as the "boolean" type does not ...

TD-er

It happens to me a lot (also in C++), so it is one of those things I check as one of the first things in debugging.
So maybe it should also be done in the rules parsing to help via the logs to indicate mismatch in if/endif etc.

TD-er

Code: Select all

on wave#State do
  if [wave#state]=1
   gpio,2,0
   timerSet 1,10
  endif // Missed this one
endon

on Rules#Timer=1 do
   gpio,2,1
endon

You missed an "endif"

TD-er

You should use another pin since GPIO-16 doesn't support interrupts.

TD-er

See here for more info on the controller parameters: https://espeasy.readthedocs.io/en/lates ... parameters

TD-er

Wifi#connected will happen before Mqtt#connected.
Maybe that's the difference here, Domoticz will be updated before Home Assistant?

TD-er

Hmm good to know.
I will think of how we can extend the Domoticz controllers to support those and maybe add extra types for the Dummy plugin to select it.
Or maybe even automatically detect it.

TD-er

The line above states it is not possible right now. The check for "2-step OTA needed" is simply this: const bool otaPossible = freeSketchSpace >= smallestOtaImageSizeNeeded; use2step = freeSketchSpace < currentSketchSize; // Assume the new image has the same size. On 4M units, the free ske...

TD-er

Why diving into RC networks for timing (which also needs 2 pins, one for the motion detection, one for the timer), while you can do it all in rules? For example a motion sensor can trigger a signal on a GPIO pin, which triggers an event in the rules. This event then sets a timer (each time again if ...

TD-er

What exactly do you want to achieve?

Is it going to be a RC timer circuit?
Then you must also know what the charging voltage is and what voltage will be enough to be considered "high" or "low" (depending how you connect it)

TD-er

You could use the rules to act on the System#boot event and then use the commands ControllerDisable and ControllerEnable. See: https://espeasy.readthedocs.io/en/latest/Reference/Command.html For example, set a timer at boot and disable the controller. Then, when the timer expires, you can enable the...

TD-er

Check

TD-er

Can you add an issue for it on Github?
Issues here are always hard to find back.

TD-er

Yep.
But please remind me later this evening to reply, as I now have to go and the forum doesn't have a "mark as unread"

TD-er

I've seen a number of similar frustrations... ehh features on pro grade devices, so I know what you mean.

Really strange to see prosumer/enterprise products often also means it is a lot harder to configure right.

TD-er

Yep, indeed you need to change the event to use "#All" in the rules block handling the event. I'm glad we had this discussion, as it gave me an idea for a very simple optimization which also makes the rules a lot less complex in the end. Especially on plugins like the pulse counter which c...

TD-er

The ESPEasy flasher (the one with GUI) is indeed not compatible with ESP32.
I recently documented flashing the ESP32 here: https://espeasy.readthedocs.io/en/lates ... html#esp32

TD-er

What is the size of the currently flashed 'sketch' ?
You can see it on the sysinfo page at the bottom.
If it is > 600 kB, you cannot update via OTA, not even when using the 2-step OTA.

TD-er

See for test build:
https://github.com/letscontrolit/ESPEas ... -758278897

This allows you to set the checkbox to combine all values of a task in a single event.

TD-er

I can't see your images.

TD-er

Hmm that means this interruption is longer then "short" as the timeout for a reconnect fail is like 20 seconds.

TD-er

Based on this discussion I added a new feature and will now make a test build for you.

See the last commit on this PR: https://github.com/letscontrolit/ESPEasy/pull/3439

TD-er

See: https://github.com/letscontrolit/ESPEasy/issues/2724 The message you try to send do have normal quotes and commas. So you must wrap it in commas not used in the parameter, like a single quote. publish milight/0x8233/rgbw/4,'{"state":"ON","brightness":143,"bulb...

TD-er

Are you sure the URL is using "vvalue" ? I thought Domoticz only used "nvalue" (integer) or "svalue" (string). Also I guess this part can be slightly simpler: on System#Boot do Monitor GPIO,12 SendToHTTP,192.168.68.29,8080,/json.htm?type=command&param=updateuservari...

TD-er

When looking at your rules, I notice you have 2 entries for the "Watermeter" When handling the Watermeter#Count event, you also look at the [Watermeter#Time] value. However, the order of values of the pulse plugin is: - Count - Total - Time That's also the order in which the events are sen...

TD-er

You should always use the %eventvalue% notation in handling events. The reason is very simple; Events may be queued and processed one at a time. So if you handle an event, the event values were stored at the time the event was created and added to the queue, but the task values they reflect may have...

TD-er

We do have the serial gateway and Serial proxy.

The last one is still very experimental and essentially does read an ASCII line from serial (until newline) and sends it to a configured MQTT controller.
You can also use a command of that plugin to send an ASCII line to the serial port.

TD-er

I think this is going to be somewhat of an endless exercise as the code of that plugin is over 4 years old, so I think there will be other things that may need additional includes or small prefix changes. So I can try to compile it later this evening, to see what else is needed. But it seems quite a...

TD-er

If you need the fading, we can help you to call this function in the PLUGIN_FIFTY_PER_SECOND loop.

TD-er

Why does it need the Ticker library? We do have a number of timer options that can be used to for example perform the next fade step as it tries to do here: https://github.com/ddtlabs/ESPEasy-Plugin-Lights/blob/1b2069fac1bf3c829a1c6c243c30a81aa1b70033/_P123_LIGHTS.ino#L274-L278 // disable Timer if d...

TD-er

Hmm I don't think so. We could set the "TimerOptional" value of the plugin in the code, but I don't know whether that may cause issues for people who never set the value. (This is a remark meant for Ton, who is probably also reading this ;) ) For now you could set the interval to an extrem...

TD-er

I don't have either of the Somfy blinds, nor a RFlink, so maybe it doesn't have to do with this issue at all. My first idea when reading your post is that one of the remotes or some other device in the neighborhood running on the same frequency has a low battery and is now jamming the ether with pac...

TD-er

Maybe you can also add a separate feature request issue on Github for this?
Requests like these are later next to impossible to find when I want to work on them. (and also to remind me to work on them)

TD-er

Also keep in mind that the "calculate" function (to do computations) is not yet done on all commands in the rules. (this is something I'm looking into for a pending PR, so not yet fixed) The Let command does call all kinds of calculate functions, so that's the safest one for doing computat...

TD-er

Yep, I could add a check for matching frequencies when assigning a channel. Just have to check/test if frequency is the only limiting factor. I also added a wrapper for this check to the Servo calls, so have to check what will happen if I mess with channels for another pin, which is a shared channel...

TD-er

@Ton:
Maybe log the incorrect read value? That's more useful in debugging.

TD-er

Ah you got a bit carried away I see

TD-er

Well we've got you covered on those topics here, so be welcome

TD-er

Ath wrote: ↑07 Jan 2021, 16:01
TD-er wrote: ↑07 Jan 2021, 15:48 0x52 >> 1 = 0x29
My hex calculations aren't that trained to see that immediately, thnx

Would you say it is a bit shifted?

TD-er

After many researched, I found that my sensor uses the 0x39 I2C address instead of 0X29. Strange, according to the chip documentation, a VL53L0X has an I2C address of 0x52 , not 0x29, 0x30 or 0x39, at wat address is it found by the ESPEasy I2C Scanner (Tools page)? Can you provide a link to the act...

TD-er

The way I programmed it, is so it will keep track of pins that are assigned for a "channel" (maybe not the "channel" as used in the ESP32 definition) so they will at least not interfere with each other as long as you keep the frequency the same. So you have to test whether it may...

TD-er

Hello, this thread is pretty old but I get a try :) So I bought the same Sensor and I cannot manage to use it with (EspEasy or else). After many researched, I found that my sensor uses the 0x39 I2C address instead of 0X29. Is there a solution to edit this address used by the plugin without full rec...

TD-er

Just keep in mind when chosing the touch pins, that you're using the ones connected to the ADC which is not used by the WiFi. See: https://espeasy.readthedocs.io/en/latest/Plugin/P002.html?highlight=adc#wifi-activity-and-adc And before building it, please test using something like a NodeMCU board (w...

TD-er

It is correct that the recent builds of the ESP32 now use the hardware PWM for constant frequencies. (hardware fade is not yet used) The ESP32 does have 2 PWM circuits: - One based on 80 MHz clock - One based on 1 MHz clock To me it is not entirely clear when the 80 MHz clock version cannot be used,...

Search found 8755 matches