-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
updateDeviceSettings: Did not find device with key='devicename', value = '9198D2_ENERGY_Total' #41
Comments
I also have these messages on start-up and these also:
Running Domoticz 2021.1 plug-in version 0.0.4 |
I think I'm seeing the same issue with Tasmota Sensors 9.4.0.4 running on a D1 mini in combination with a BH1750 lux sensor. 2021-06-02 10:12:34.074 MQTT discovery: (MQTT discovery) Heartbeating... |
I think it has to do with something a change in Domoticz 2021.1, I am currently trying to find a fix for the problem. The error exist in this part of the code. Does anyone experience the issue that a Tasmota device is flipping very quick on and off when it was trigger a on, off, on to quickly?
|
I don't believe that the existing devices are having any issues... Can you explain in more detail what you're looking for? |
I am trying to lean the structure of the code to fix the boot message. |
Hello, I just downgraded to the version as per your link. 2021-06-07 11:38:01.072 MQTT discovery: (MQTT discovery) MqttClient::Ping My Domoticz version is: Version: 2021.1 (build 13256) Build Hash: ab915f0a4 Any ideas how to solve this? Best regards, Bart |
@BartdaMan I removed comment I notes that it was not the solution, but I think on the run it is better. |
Nice! will try your build. |
I am trying to add my first Tasmota device with power metering to the Domoticz I have running. (There's over ten other Tasmota devices, but none do power metering)
I've set it up pretty much identical to all others, with the exception of the name and template settings...
When I do 'setOption19 1', no devices get added, and instead the module logs a lot of messages like the one in the title...
Here's a section of log I see as soon as I enable homeassistant autodiscovery mode:
The text was updated successfully, but these errors were encountered: