Let's Control It

TD-er

That's a quick fix

TD-er

It was a bit more complicated, but in essence it is still a bug that's not going to solve itself indeed.
It needs a firmware update to get it fixed.

TD-er

Ah you also mentioned it here...
Same questions though

What is needed to make it work again? Save the settings of the task again, or do you need a power cycle?

TD-er

chromo23 wrote: ↑19 Sep 2020, 13:38 and the dht22 became unavailable, again. always after around one day.

And what do you need to do to make it work again?
Is saving the settings again enough to get it to work again, or do you need a power cycle?

What error does it give in the logs?

TD-er

Have you already tried the test build?

TD-er

If you replace the current LEDs on the unit with the LEDs of the optocoupler, you don't need extra resistors. N.B. the same applies when you set the optocoupler LEDs parallel. There is however a big BUT here... Can you measure the voltage drop over the LED in the optocoupler? If this is a higher vol...

TD-er

What bus frequency are you now using? 100 kHz?

TD-er

Do you have some resistor voltage divider to lower the voltage you want to measure?
According to the datasheet the input voltage should be lower than the voltage powering the chip (absolute max is Vdd + 0.5V)

TD-er

kamly12 wrote: ↑17 Sep 2020, 13:24 hi, i am from Australia.wow great work, I was having this GPIO problem with deep sleep. thanks for the help. I will try this after taking some rest. I think my bed and bed sheets are calling me badly lol.

Make sure to have the correct pins connected before you go into deep sleep yourself

TD-er

Well the current builds are quite OK. Just found a few more issues you would only encounter with > 25 days uptime. And I recently changed all I2C plugins to allow to be used with the I2C multiplexer, so it would be nice if those can also be tested (not yet included in the last build, but merged to t...

TD-er

Ah found an issue which could explain it all. In the function bool WiFiConnected() if (validWiFi) { // Connected, thus disable any timer to start AP mode. (except when in WiFi setup mode) if (!wifiSetupConnect) { timerAPstart = 0; } STOP_TIMER(WIFI_ISCONNECTED_STATS); // Only return true after some ...

TD-er

The "Message interval" used to be a MQTT only setting (remember, Wiki documentation is dated, refer to ReadTheDocs for more up to date documentation) Currently the controllers all use a "controller queue", which has the "Minimum Send Interval", which does what this old ...

TD-er

Well the ESP will not query the NTP server very often, so all updates to the system time are done using the same timeDiff function. Meaning that if there is now somehow some bug in the timeDiff function, or the millis() function, then it could be something to look at. The (apparent) high CPU load an...

TD-er

The logic is flawed as it connects all transistors on the optocouplers together and their GPIO pins too. You should use a pull-up resistor per transistor. Also I guess it is wise to add a resistor in series with the transistor too, to make sure the GPIO pin is not drawing too much current if it by a...

TD-er

Is the time displayed correct on those nodes?
And the unixTime?

TD-er

Added it: https://github.com/letscontrolit/ESPEasy/pull/3257

TD-er

Well I can imagine the error would be something like this:

Code: Select all

int i = millis();
if (i > (some_prev_value + 100)) {
...
}

or maybe something like this:

Code: Select all

unsigned int i = timePassedSince(some_prev_value);
if (i < 1000) {
...
}

What controller(s) do you use?

TD-er

And another thing to keep in mind.
If you didn't change anything in the configuration but suddenly the double / was added.
Maybe it was caused by an update of Domoticz and then it would mean the same could have been changed in other places.

TD-er

I have seen the 'connected' time indeed reporting negative values. Not sure if it is related, but at least it is a good starting point to see what else may be wrong here. I guess it may be something simple as the timeDiff (returning a signed int) is assigned to an unsigned int. Those bugs were not m...

TD-er

Ah you're right.
I didn't look at the build date, even though that's the main reason I put the date stamp in there

TD-er

Can you change the url to not have the double // in the url?
It should only have the // at the begin (http://....)

TD-er

I do find the double '/' in the URL a bit strange.
What is giving this log error? Is it ESPEasy or Domoticz?

And are you 100% the ESP does have the same IP address? (e.g. what if your DHCP server suddenly changed IP assignments?)

TD-er

There is no "generic I2C plugin", but if you can use some UART protocol then maybe ser2net plugin may be useful here?

TD-er

Well it does seem to work stable now. Before you try to save a new setting, can you maybe reboot first? At reboot (before loading the settings) the filesystem garbage collector is called, which may clear blocks no longer used. I've seen strange things with small SPIFFS file systems and lots of edits...

TD-er

Hmm that sounds like it may have had a settings file that was not written fully.
Did you see a red error message when saving the settings?

Is there enough free space on the file system?
SPIFFS may act strange sometimes when it encounters a full or highly fragmented file system.

TD-er

If it is asking for authorization that often, then please also check to see if it is rebooting. It is for sure not normal :) Just a rule of thumb here, if it is annoying, it probably isn't intended nor normal :) GPIO5 is also the default of one of the I2C pins. So please check you did assign other p...

TD-er

Just another thing to try, regardless of the pull-up check.
You can also try to lower the I2C speeds.
The default is 400 kHz, but you could also try a lower speed like 100 kHz in the settings.

TD-er

Have you tried something like this?

Code: Select all

curl --user username:password http://<espeasyip>/control?cmd=<command>

It is just the "basic authorization". Nothing fancy.

TD-er

What tool do you use for the http command?
Command line tool like Curl, or is it from another ESP?

TD-er

Sending commands via MQTT should be done via the subscribed topic + /cmd
So if you subscribe to the topic

Code: Select all

ChickenBot_4/Chickenbot

you should publish the ESPEasy commands to

Code: Select all

ChickenBot_4/Chickenbot/cmd

TD-er

Is the serial port (and/or serial logging) still enabled in the settings?
Do you have a pull-up resistor between 3v3 and SCL and one between 3v3 and SDA?
If not, I would suggest to try a 4k7 resistor as pull-up resistors for the I2C bus.

TD-er

How do you activate the relay?
Via a transistor?

Do you have a diode over the relay spool to protect the transistor?
If not, please check with a new transistor.

TD-er

Can you try to send continuous pings from another node to that Shelly one and see if the problem is still occuring?

TD-er

See PR: https://github.com/letscontrolit/ESPEasy/pull/3255

TD-er

Can you try this test build? https://github.com/letscontrolit/ESPEasy/pull/3254

TD-er

It is the first parameter of this function in the NewPing library: unsigned long NewPingESP8266::ping_median(uint32_t it, unsigned int max_cm_distance) { unsigned int uS[it], last; uint32_t j, i = 0; unsigned long t; uS[0] = NO_ECHO; while (i < it) { t = micros(); // Start ping timestamp. last = pin...

TD-er

The MQTT import plugin does only yield values. The controllers themselves do also monitor their subscribe topics appended with "/cmd" So if you subscribe to "rl1c_0/relay/" you should publish a command to the topic "rl1c_0/relay/cmd/" Whatever is published there, is pic...

TD-er

Absolutely there is a reason for it... but I don't know it

Either there wasn't any when the Dallas plugin was written, or it wasn't working right or maybe the only one available back then was using the wrong license.
I simply don't know.

TD-er

Well as I am also working on a board design myself using ESP32, I guess I will also run into this quite soon.

TD-er

Well the SettingsStruct we use was not updated on all aspects before we started using ESP32 builds. ESP8266 only has GPIO 0 ..16, so there are no fields in the struct for more. See this in the source code: int8_t PinBootStates[17]; // FIXME TD-er: this is ESP8266 number of pins. ESP32 has double. It...

TD-er

Thanks, I will include it in the main repo, so it can also be incorporated when the Dallas code gets refactored into a central 1-wire handler.

TD-er

Hmm, I just looked for the transformations syntax in the docs: https://espeasy.readthedocs.io/en/lates ... red-values
But apparently there is none to output "true" and "false"

Very odd...

TD-er

Like I said, I haven't tried the commands via MQTT myself. According to the documentation, you should add "cmd" to the topic: https://espeasy.readthedocs.io/en/latest/Reference/Command.html?highlight=mqtt%20command#command-reference The command itself does work when you enter it in the com...

TD-er

2000 is not in the range of 1...255.

TD-er

Not sure whether it is a good idea at all, but at least I would suggest not to use multiple blocks acting on the same event only with different event values. So to just tackle that part: on pcfGPIO#0 do if [Plugin#pcfGPIO#Pinstate#1]=%eventvalue% Publish %sysname%/PCFGPIO/0,[Plugin#pcfGPIO#Pinstate#...

TD-er

Hmm 25 days sounds a lot like 2^31 msec, from the top of my head. A long time ago, I fixed a bug where we had a "Y2K-like" problem with the msec timer overflowing after 49.7 days But 25 days sounds just like a signed version of that. Are there other issues too, apart from the Dallas sensor...

TD-er

I also added the same info to the main documentation, to help others too.

https://espeasy.readthedocs.io/en/lates ... #p048-page

TD-er

Nope, the ESP32 build has 32 tasks

TD-er

Well regardless of changing it to 14 or 24, it would mean incompatible settings. And running at 24 tasks without using them is not going to take a lot of extra resources. My warning was more about if you increase the number of tasks, you are likely to use them and with more active tasks, you would c...

TD-er

Well sending via MQTT is not something I tried myself. But in general, the commands should be formatted just as if you sent them via the command field on the tools page. The options are almost all strings, so: - Command is MotorShieldCMD - Motor type = "DCMotor" or "Stepper" - Mo...

Search found 8750 matches