installed 2.0.0dev7 on a sonoff device. The device is connected to iobroker via a cloud mqtt-broker on a vps. Switching on/off setting LED on/off and attaching the original button using a rule works fine.
I noticed that a mqtt-topic devicename/status is created but it always shows "not connected" which cannot be true as the device connects to the broker and everything works as expected. Do I have to set this status manually or is it supposed to be generated by ESPEasy?
2.0.0dev7 mqtt status not set
Moderators: rtenklooster, Voyager, BertB, Stuntteam
Forum rules
You have entered the experimental forum, beware!!!
You have entered the experimental forum, beware!!!
Re: 2.0.0dev7 mqtt status not set
i assume you had espeasy installed in a previous version. this is a bit of an educated guess.
there is indication, that some info from the old version in the flash, leading to unexpected behaviour (in my case http connection to domoticz). the controller tab became unavailable and log showed connection errors. this only happened on a wemos that had 147 installed previously. the other "virgin" wemos that was flashed from the beginning with dev7 does not show the same behaviour =(works well)
the other indicator, that the is to do with residual info in flash is that when flashing back to 147, all my tasks and rules from the previous setup (147) came back.
try to erase flash with one of the "0" bin files (confirmed to work by user Shardan) . doing a hard reset (power off --> connect gpio 1 with 3 (rx and tx) then power up --> wait 3min) could also work, not sure though.
there is indication, that some info from the old version in the flash, leading to unexpected behaviour (in my case http connection to domoticz). the controller tab became unavailable and log showed connection errors. this only happened on a wemos that had 147 installed previously. the other "virgin" wemos that was flashed from the beginning with dev7 does not show the same behaviour =(works well)
the other indicator, that the is to do with residual info in flash is that when flashing back to 147, all my tasks and rules from the previous setup (147) came back.
try to erase flash with one of the "0" bin files (confirmed to work by user Shardan) . doing a hard reset (power off --> connect gpio 1 with 3 (rx and tx) then power up --> wait 3min) could also work, not sure though.
Domoticz on Raspi 2 -- 14 ESP units (hacked Sonoff,NodeMCUs, Wemos, self-built units) running with RC140- Mega 2.0.0 dev8
Re: 2.0.0dev7 mqtt status not set
thanks toffel969 - well I didnt have a previous ESPEasy version on it, but the original Sonoff software. But there must be another error - ESPEasy could not send disconnected while being disconnected ... that does not make sense.
Re: 2.0.0dev7 mqtt status not set
fixed in 5c9d00c0a978d4d3137b90842f092dccd7391c85
if it doesnt work or you have problems, reopen this issue: https://github.com/letscontrolit/ESPEasy/issues/246
if it doesnt work or you have problems, reopen this issue: https://github.com/letscontrolit/ESPEasy/issues/246
Who is online
Users browsing this forum: No registered users and 14 guests