Error Device created after MQTT AD

[McMelloW]

Raspberry Pi 3B+ Buster
Domoticz build 13949
Shelly 2.5 flashed with Tasmota v10.1.0

After Auto creation of the Device, the following errors

Code: Select all

2021-12-18 18:48:08.096 Error: MQTT: Unhandled state received '{"Time":"2021-12-18T18:48:08","Uptime":"0T01:04:38","UptimeSec":3878,"Heap":27,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"MyNetwork","BSSId":"28:FF:3E:1A:53:CB","Channel":6,"Mode":"11n","RSSI":78,"Signal":-61,"LinkCount":1,"Downtime":"0T00:00:03"}}' (692E91_SHT_1/Shelly-01U)
2021-12-18 18:48:08.220 Error: MQTT: Exception: in Json::Value::resolveReference(key, end): requires objectValue!
2021-12-18 18:48:08.221 Error: MQTT: Exception: in Json::Value::resolveReference(key, end): requires objectValue!
2021-12-18 18:48:08.221 Error: MQTT: Exception: in Json::Value::resolveReference(key, end): requires objectValue!
2021-12-18 18:48:08.221 Error: MQTT: Exception: in Json::Value::resolveReference(key, end): requires objectValue!
2021-12-18 18:48:08.222 Error: MQTT: Exception: in Json::Value::resolveReference(key, end): requires objectValue!
2021-12-18 18:48:08.222 Error: MQTT: Exception: in Json::Value::resolveReference(key, end): requires objectValue!
2021-12-18 18:48:08.245 Error: MQTT: Exception: in Json::Value::resolveReference(key, end): requires objectValue!
2021-12-18 18:48:08.245 Error: MQTT: Exception: in Json::Value::resolveReference(key, end): requires objectValue!
2021-12-18 18:48:08.245 Error: MQTT: Exception: in Json::Value::resolveReference(key, end): requires objectValue!
2021-12-18 18:48:08.246 Error: MQTT: Exception: in Json::Value::resolveReference(key, end): requires objectValue!

Anybody a clue where this comes from and how to handle this?

[jvdz]

The First one will be fixed in the next version. Is that an TASMOTA device?
For the other errors we will need the offending MQTT TOPIC and PAYLOAD messages to be able to check what is happening. In case they aren't CONFIG topic, we also likely need the CONFIG MQTT message for the offending device.

Jos

[McMelloW]

The First one will be fixed in the next version. Is that an TASMOTA device?
For the other errors we will need the offending MQTT TOPIC and PAYLOAD messages to be able to check what is happening. In case they aren't CONFIG topic, we also likely need the CONFIG MQTT message for the offending device.

Jos

Thanks for your reply.
Yes it is a Shelly 2.5 flashed with Tasmota v10.1.0 - Domoticz is at build 13949.
The Shelly is the first device created with auto detection after (Setoption19 1) on the Tasmota console. At this moment only this error message every 5-6 min.

Code: Select all

2021-12-18 21:03:08.326 Error: MQTT: Unhandled state received '{"Time":"2021-12-18T21:03:08","Uptime":"0T03:19:38","UptimeSec":11978,"Heap":27,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"VGV751954873C","BSSId":"28:FF:3E:1A:53:CB","Channel":6,"Mode":"11n","RSSI":74,"Signal":-63,"LinkCount":1,"Downtime":"0T00:00:03"}}' (692E91_SHT_1/Shelly-01U)

In which next version will this be fixed? Domoticz or Tasmota

[jvdz]

Yes the "Unhandled state received" error from TASMOTA will soon (probably in a couple of days) be fixed. Just need to finish the 3 line mod and make a PR.
..But what about the other errors you get? I do not recognize them.

Code: Select all

2021-12-18 18:48:08.220 Error: MQTT: Exception: in Json::Value::resolveReference(key, end): requires objectValue!

[McMelloW]

Yes the "Unhandled state received" error from TASMOTA will soon (probably in a couple of days) be fixed. Just need to finish the 3 line mod and make a PR.
..But what about the other errors you get? I do not recognize them.

Code: Select all

2021-12-18 18:48:08.220 Error: MQTT: Exception: in Json::Value::resolveReference(key, end): requires objectValue!

OK, I will watch Tasmota for the update.
The other messages were gone when did a (setoption19 0) on the device. Set it again to 1 the messages appear again.

[jvdz]

PR is made for issue #5072 .

[McMelloW]

PR is made for issue #5072 .

Thanks, disabled debug in the MQTT hardware to avoid all the extra messages.

[McMelloW]

PR is made for issue #5072.

Hi jvdz, I see PR #5072 is gone or done. But when this will be available in a compiled version?

[jvdz]

I don't know as that only happens when @gizmocuz pushes the right buttons...

[McMelloW]

PR is made for issue #5072 .

Hallo Jos,

At this moment I am on build 14052. When I change the loglevel of the MQTT Auto Discovery Client Gateway with LAN interface enabled Error the following error messages still appear again. Disabling Error in the loglevel stops this messages.

Code: Select all

2022-01-15 12:06:36.773 Error: MQTT: Exception: in Json::Value::resolveReference(key, end): requires objectValue!
2022-01-15 12:06:36.774 Error: MQTT: Exception: in Json::Value::resolveReference(key, end): requires objectValue!
2022-01-15 12:06:36.774 Error: MQTT: Exception: in Json::Value::resolveReference(key, end): requires objectValue!
2022-01-15 12:06:56.678 Error: MQTT: Exception: in Json::Value::resolveReference(key, end): requires objectValue!
2022-01-15 12:06:56.678 Error: MQTT: Exception: in Json::Value::resolveReference(key, end): requires objectValue!
2022-01-15 12:06:56.678 Error: MQTT: Exception: in Json::Value::resolveReference(key, end): requires objectValue!
2022-01-15 12:06:56.679 Error: MQTT: Exception: in Json::Value::resolveReference(key, end): requires objectValue!

I am not sure, but I guess after split og MQTT and MQTT AD hardware the PR #5072 is not done on both hardware objects. Any clue or solution.

[gizmocuz]

@McMellowW Please do not cross post on the forum and github, use either of the two
Lets continue on github

[McMelloW]

@McMellowW Please do not cross post on the forum and github, use either of the two
Lets continue on github

OK, I will