-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Any Way to disable switching on / off Device via MQTT without disabling MQTT? #18164
Replies: 14 comments · 23 replies
-
Beta Was this translation helpful? Give feedback.
All reactions
-
Beta Was this translation helpful? Give feedback.
All reactions
-
OK so your config doesn't seem to be the problem What are the logs of the tasmotas (in level 3)? And your ticks for the logs are in the wrong direction 😊 |
Beta Was this translation helpful? Give feedback.
All reactions
-
Beta Was this translation helpful? Give feedback.
All reactions
-
I just tried to figure out if Problems are exisiting while stopping SAE Service again. I will now switch to WebLog 3 in Console, but....... If that "Reset" or however you will call the "Reboot" or "off / on" Switch happens, weblog is gone in Console and starts like I posted at my 1st Post. Just to tell... Here is my mosquitto.conf
and here the smartapplianceenabler.conf which is placed in /etc/mosquitto/conf.d
EDIT After stopping smartapplianceenabler Service, the disconnect, new connect, closing old connection msg are gone... |
Beta Was this translation helpful? Give feedback.
All reactions
-
Ok, like Britney would say, oops, he did it again.... Weblog from POW:
Log from Mosquitto:
And here the Log from Syslog Server:
Whats the Meaning of ESP-CSE: ? Any Ideas why that only happens, if SAE Service is running? |
Beta Was this translation helpful? Give feedback.
All reactions
-
It's going to explode 🙄
Definitively somehting went wrong and the ESP got stuck into a dead loop which triggered the watchdog What would be interresting are the logs before that happens |
Beta Was this translation helpful? Give feedback.
All reactions
-
Well...
This was the 1st life Signal in Weblog (weblog 3) after the Reset / off on switching... I can show you the syslog from 1 Minute before, whole with all Devices but....
Thats all the syslog tells...... :(
Any Idea? All i can say is, if i stop SAE all is fine.... EDIT: I have another log not, fun fact, FHEM service is stopped...... I would say, hey ok, so one POW has a Hardware Demage and that causes the random off / on switching but...... Here the log without FHEM:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
From the Java crash log it looks like Tasmota crashes while/before (presumably) SAE is polling it through web requests on STATUS8 Do you have only 1 device that is crashing this way ? |
Beta Was this translation helpful? Give feedback.
All reactions
-
Hello! Yes, like I said, I have 12 POW Devices. 10 POW2 and 2 POW1 from Itead. Past night I only let run 3 of them and 2 had same off / on / Reset Issue. Here the crashlog from SAE for my Wasserbett: (POW Gen.1)
And here 2 Crashlogs from a POW2:
and
As far i can see the Error Msg from SAE are all same on differen POW Devices. I am getting desperate.... Here the Syslog from Syslog Server from my POW Gen.1 Device "Wasserbett"
There is nothing happening before.... |
Beta Was this translation helpful? Give feedback.
All reactions
-
This feature has not been implemented yet (but is planned). |
Beta Was this translation helpful? Give feedback.
All reactions
-
I'm the developer behind this project and use 7 Tasmota devices myself with SAE for some years already. One of them is even a Sonoff Pow R2.
Running SAE and Tasmota devices I never experienced any "Ghost Switching".
Recently during some testing I got the same error when I run a Web browser on Tasmota Web-UI and SAE was accessing the same Tasmota device via HTTP. Most times it works but about 10-20 percent of the calls result in an error. Looks like Tasmota does not support concurrent HTTP requests. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Hello @barbudor
Its set to Value 3
Its set default "on"
Its also set to Default Value "off" Maybe the Power State scanning do the quick toggle at the Relais ? |
Beta Was this translation helpful? Give feedback.
All reactions
-
Update to v12.4.0.2 and see if the spikes are gone. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Thank you a lot @arendst for your Information. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Sadly Error still existing :(
|
Beta Was this translation helpful? Give feedback.
All reactions
-
Sad to say, that its still same :(
|
Beta Was this translation helpful? Give feedback.
All reactions
-
This feature has not been implemented yet (but is planned). |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
Ok Guys! I have a sleepless Night behind me, to get things clear and exclude Error maybe of my running System. All whats installed at the VM is Mosquitto and SAE + needed Files for SAE... No FHEM not nothing! I can trace this sudden off/on "spike" Switching at all the POWs connected to SAE! @camueller If you only have one POW this Fault happend maybe one time in 24 Hours, maybe in 48 Hours. So most of the Users of SAE wont realize that. The Error Messages in Syslog, Weblog and SAE are still same, so I dont attach them here again. Only a Screenshot with
to show, that those random off / on Thing still happens at all connected POW Devices Maybe @arendst is able to fix the toggeling at SAE Error restart, that would help a lot. So I think I have done all I can to find the Error. Hope we can terminate whats the Reason for it. |
Beta Was this translation helpful? Give feedback.
All reactions
-
EDIT: |
Beta Was this translation helpful? Give feedback.
All reactions
-
I'm using a Sonoff Pow R2 to monitor the power consumption of a water pump. This Tasmota device is only polled for power consumption but not controlled by any kind of software. If it would be switched off ("ghost switching") I would surely notice since the toilets would run without water :-)
It may happening for a long time in your installation but so far I did not receive any similar bug reports. |
Beta Was this translation helpful? Give feedback.
All reactions
-
In my test with Sonoff Pow R2 no relay clicking is noticed during a normal restart. The exceptions you encounter may lead to a relay click but then you shouldn't see exceptions at all. Using HTTP for monitoring Tasmota devices (like TasmoAdmin) is known to lead to unwanted restarts due to used HTTP library. As said before Tasmota was never meant to be monitored by HTTP. |
Beta Was this translation helpful? Give feedback.
All reactions
-
It is running Tasmota 7.2.0 with MQTT enabled but not used. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Version 7.2 is very old, I'd recommend upgrading to current before asking about how things can get different. While I don't remember when, a long time ago Tasmota was improved to allow restarts reliably without relay clicking, since then I've had my main desktop computer behind a Sonoff Pow R2 with lots of restarts/upgrades, without issues. |
Beta Was this translation helpful? Give feedback.
All reactions
-
I'm not asking for anything. The Sonoff Pow R2 running Version 7.2.0 runs without problems. No need to upgrade. |
Beta Was this translation helpful? Give feedback.
All reactions
-
To lower network traffic (decoding) you might also want to consider to disable (WeMo) emulation. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Well OK... I will do 2 last Tests, else i will uninstall SAE. As I understand @arendst right, HTTP requests or HTTP Communication of SAE causes the Reset off / on switching thing.
Just to say: And also as I said, I ran only SAE at a VM, without anything else and same Issue. @camueller |
Beta Was this translation helpful? Give feedback.
All reactions
-
You should downgrade yous to 7.2.0 instead if you want to have a similar setup. I don't think the problem is relates to the Tasmota version. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Hello Guys! SAE and Tasmota wont like each other at newer Versions. In Case you think its about flashing. I had a new Gosund Plug flashed 1st time with Tasmota 12.xxx and had same Issues and Error Messages in Mosquitto.log, SAE log and Syslog. To me its OK to solve the Problem like this. I am sure if other Users who use SAE and have Tasmota 12.xxx Firmware on their Devices will have same Issues. |
Beta Was this translation helpful? Give feedback.
All reactions
-
If this is true and although MQTT is preferable over HTTP when getting data from Tasmota device I'm really suprised that newer versions of Tasmota are not as stable as older versions. I wouldn't have expected that! |
Beta Was this translation helpful? Give feedback.
All reactions
-
Yes silly, its what I witness and it also would explain, why you cant trace my explained Errors because your POW is also on older Firmware. |
Beta Was this translation helpful? Give feedback.
All reactions
-
It seems since later versions stack is low on energy monitoring devices leading to unexplainable restarts and exceptions and watchdogs. Working on a possible solution. |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
Give latest dev branch a try. It reduces stack usage which when becoming to low could lead to all kind of issues. |
Beta Was this translation helpful? Give feedback.
-
Hello!
I have huge problems with Ghost Switiching with my Tasmota sOnOff POW Devices.
I spent a lot of Time Reading, switched on / off powerretain, buttonretain, switchretain etc.
nothing really worked
My Configuration is special and not as easy in connection with Mosquitto.
I have installed Mosquitto on an Ubuntu 20.04 LTS Server. persistence is set to false in the mosquitto.conf
I have a FHEM Server with MQTT1 (no MQTT Server) to switch and visualize the POW Devices
I use Smart Appliance Enabler to monitor the POWs Power at SMA Sunny Portal.
If I disable Smart Appliance Enabler, "Ghost Switching" is gone.
The Developer of SAE uses sOnOff POWs too, but no FHEM and has no Problems with Ghost Switching.
If I only use FHEM the Devices wont switch random....
It looks like the POWs "overrun" and Reset?
The POW Devices makes a short off / on switching and runs normal till next time same happens...
The log looks like this:
Does Tasmota have Problems with multiple Apps that are using MQTT, like in my Case SAE and FHEM?
Somebody any Idea?
At Mosquitto I have such Messages in log:
At SAE it looks like this:
But why the Heck the POW does a quick off / on switching after that all?
Is there a way to disable the Relais and just leave it on?
Its important for Devices like my Freezer for example. Its on 24/7
But sure no Solution for the Main Problem...
I dont think it is a ratain Message from MQTT because i disabled the db.......
It looks like the POW has an electric short for some milliseconds.
But I have 12 POWs and all do the same while connected to SAE and FHEM
If i stop SAE Service the POWs run as expected without any Problems...
Devil is a Squirrel ?
I would be happy if somebody could help me with my Problem
Beta Was this translation helpful? Give feedback.
All reactions