Python plugin: Sonoff-Tasmota + Other devices supporting MQTT Discovery

[emontnemery]

Fixed now.

[effinG]

I have the same settings, and no devices are found.

Setup: RPi3, latest beta Domoticz, done the setoption19 1 thingy, MQTT up and running.

Sonoff setup:
MQTT Host 192.168.0.124
MQTT Port 1883
MQTT Client & Fallback Topic DVES_AF76EE
MQTT User
MQTT Topic sonoff35 (every Sonoff has it's own Topic)
MQTT Group Topic sonoffs
MQTT Full Topic cmnd/sonoff35/

Full topic: %prefix%/%topic%/


Domoticz setup:
MQTT Server address:localhost
Port: 1883
Username:
Password:
Discovery topic: sonoffs
Ignored device topics (comma separated): tasmota/sonoff

What is wrong with this setup?

Edit:

I also have this error message in the log:

2018-06-03 11:30:25.656 (MQTT discovery) Warning: could not load plugin options '' as JSON object

What could this mean ? How can I solve this ?

Hi - I have the exact same issue but can't find a solution - what did you do to get it working? Or can anyone else advise what causes the error above?

[emontnemery]

effing: You need to update to the latest version of the plugin where this should be fixed

[peterenderest]

I installed this plugin last week with the latest beta release
Initially I connected my sonoff devices via the standard way using dummy/virtual devices, but I now switched everything to the new plugin
The plugin is working very good but I noticed that for a specific sonoff device you see an entry in the logging of that device every 5 minutes. So if the device is off, it is reported every 5 minutes as off
For other plugins/devices you only see a logging when the state has changed, eg if the device is off for 5 hours and then turned on, you see 1 logging only at the time the device turned on (until it is switched off again ofcourse)
How can I remove the multiple entries every 5 minutes with same state?

[BrianMayPT]

Hi,

Installed latest version of the plugin 1hour ago, latest domoticz version (4.10717) and I'm getting the "2019-05-12 23:12:33.758 (espscsgate) Warning: could not load plugin options '' as JSON object" message...tips?

[joostnl]

Your plugin is working great for my sonoff/blitzwolf powerplug.
The on/off device is added auto.

Only the power devices not, any hint?
Sorry do you mean with no sensors supported in the op that it doesn't work

Code: Select all

2019-07-15 21:59:30.300 (Discovery) updateDeviceSettings: Did not find device with key='devicename', value = '238EF1_RL_1'
2019-07-15 21:59:30.300 (Discovery) updateDeviceSettings: TypeName: 'Switch' Type: 244
2019-07-15 21:59:30.300 (Discovery) Creating device with unit: 1
2019-07-15 21:59:30.359 (Discovery) 001/Discovery - Sonoff: Setting TimedOut: '0'
2019-07-15 21:59:30.417 (Discovery) updateDeviceSettings: Did not find device with key='devicename', value = '238EF1_ENERGY_TotalStartTime'
2019-07-15 21:59:30.417 (Discovery) updateDeviceSettings: TypeName: '' Type: 0
2019-07-15 21:59:30.417 (Discovery) updateDeviceSettings: Did not find device with key='devicename', value = '238EF1_ENERGY_Total'
2019-07-15 21:59:30.418 (Discovery) updateDeviceSettings: TypeName: '' Type: 0
2019-07-15 21:59:30.469 (Discovery) updateDeviceSettings: Did not find device with key='devicename', value = '238EF1_ENERGY_Yesterday'
2019-07-15 21:59:30.469 (Discovery) updateDeviceSettings: TypeName: '' Type: 0
2019-07-15 21:59:30.470 (Discovery) updateDeviceSettings: Did not find device with key='devicename', value = '238EF1_ENERGY_Today'
2019-07-15 21:59:30.470 (Discovery) updateDeviceSettings: TypeName: '' Type: 0
2019-07-15 21:59:30.521 (Discovery) updateDeviceSettings: Did not find device with key='devicename', value = '238EF1_ENERGY_Power'
2019-07-15 21:59:30.521 (Discovery) updateDeviceSettings: TypeName: '' Type: 0
2019-07-15 21:59:30.522 (Discovery) updateDeviceSettings: Did not find device with key='devicename', value = '238EF1_ENERGY_ApparentPower'
2019-07-15 21:59:30.522 (Discovery) updateDeviceSettings: TypeName: '' Type: 0
2019-07-15 21:59:30.573 (Discovery) updateDeviceSettings: Did not find device with key='devicename', value = '238EF1_ENERGY_ReactivePower'
2019-07-15 21:59:30.573 (Discovery) updateDeviceSettings: TypeName: '' Type: 0
2019-07-15 21:59:30.624 (Discovery) updateDeviceSettings: Did not find device with key='devicename', value = '238EF1_ENERGY_Factor'
2019-07-15 21:59:30.624 (Discovery) updateDeviceSettings: TypeName: '' Type: 0
2019-07-15 21:59:30.625 (Discovery) updateDeviceSettings: Did not find device with key='devicename', value = '238EF1_ENERGY_Voltage'
2019-07-15 21:59:30.625 (Discovery) updateDeviceSettings: TypeName: '' Type: 0
2019-07-15 21:59:30.676 (Discovery) updateDeviceSettings: Did not find device with key='devicename', value = '238EF1_ENERGY_Current'
2019-07-15 21:59:30.676 (Discovery) updateDeviceSettings: TypeName: '' Type: 0
2019-07-15 21:59:30.677 (Discovery) updateDeviceSettings: Did not find device with key='devicename', value = '238EF1_status'
2019-07-15 21:59:30.678 (Discovery) updateDeviceSettings: TypeName: '' Type: 0
2019-07-15 21:59:37.498 (Discovery) 001/Discovery - Sonoff: Topic: 'sonoff1/tele/STATE 'Setting nValue: 0->1, sValue: ''->''
2019-07-15 21:59:58.149 (Discovery) onCommand 001/Discovery - Sonoff: Command: 'Off', Level: 0, Color:
2019-07-15 21:59:58.149 (Discovery) MqttClient::Publish sonoff1/cmnd/POWER (OFF)
2019-07-15 21:59:58.201 (Discovery) 001/Discovery - Sonoff: Topic: 'sonoff1/tele/STATE 'Setting nValue: 1->0, sValue: ''->''
2019-07-15 21:59:58.117 Status: User: Admin initiated a switch command (32/Discovery - Sonoff/Off)
2019-07-15 21:59:59.870 (Discovery) onCommand 001/Discovery - Sonoff: Command: 'On', Level: 0, Color:
2019-07-15 21:59:59.871 (Discovery) MqttClient::Publish sonoff1/cmnd/POWER (ON)

[mvveelen]

With the latest version of the plugin and Tasmota version 6.7.1 there are extra 'switches' discovered. For instance, I have already a discovered switch with the name "Lamp" and then it discovers an extra switch with the name "Lamp Button" which will do....nothing when you switch it.
Any idea? I now deleted them, but I suppose they will be discovered again when I restart Domoticz.

[apatrid]

Hi all,

I am trying to tackle the issue of setting my first LSC Smart Filament Bulb in Domoticz. I would appreciate if someone points me towards error in configuration (i've tried multiple combinations of naming the topic and device itself); I am not sure whether I am configuring it wrong, or should I look for older versions of Tasmota, as it seems it worked for others previously? I can control device fine from it's own IP address; my only problem is that I can't add it to DOmoticz - yet I seem to see device in logs.

I have flashed the bulb with Tasmota 7.0.0.3:

Code: Select all

Generic Module
standing_pixar_lamp
Program Version	7.0.0.3(tasmota)
Build Date & Time	2019-11-06T23:07:19
Core/SDK Version	STAGE/2.2.2-dev(38a443e)
Uptime	0T00:03:28
Flash write Count	82 at 0xF7000
Boot Count	24
Restart Reason	Software/System restart
Friendly Name 1	standing_pixar_lamp
	 
AP1 SSId (RSSI)	maybe (90%)
Hostname	pixar_standing_lamp-6999
IP Address	10.1.1.22
Gateway	10.1.1.1
Subnet Mask	255.255.255.0
DNS Server	10.1.1.1
MAC Address	84:0D:8E:6B:3B:52
	 
MQTT Host	10.1.1.2
MQTT Port	1883
MQTT User	mqtt
MQTT Client	DVES_6B3B57
MQTT Topic	pixar_standing_lamp
MQTT Group Topic	tasmotas/cmnd/
MQTT Full Topic	pixar_standing_lamp/cmnd/
MQTT Fallback Topic	cmnd/DVES_6B3B57_fb/
	 
Emulation	Disabled
mDNS Discovery	Disabled
	 
ESP Chip Id	7027543
Flash Chip Id	0x144051
Flash Size	1024kB
Program Flash Size	1024kB
Program Size	446kB
Free Program Space	556kB
Free Memory	30kB

I am seeing following logs (hidden in spoiler not to overflow topic):

Spoiler: show

Code: Select all

2019-12-04 20:10:17.791 Status: (Ams MQTT Discoverer) Exiting work loop.
2019-12-04 20:10:17.994 Status: (Ams MQTT Discoverer) Stopping threads.
2019-12-04 20:10:17.995 Status: (Ams MQTT Discoverer) Stopped.
2019-12-04 20:10:17.995 Status: (Ams MQTT Discoverer) Started.
2019-12-04 20:10:18.123 (Ams MQTT Discoverer) 'HardwareID':'14'
2019-12-04 20:10:17.790 Status: (Ams MQTT Discoverer) Stop directive received.
2019-12-04 20:10:18.123 (Ams MQTT Discoverer) 'HomeFolder':'/config/plugins/domoticz_mqtt_discovery-development/'
2019-12-04 20:10:18.124 (Ams MQTT Discoverer) 'StartupFolder':'/var/lib/domoticz/'
2019-12-04 20:10:18.124 (Ams MQTT Discoverer) 'UserDataFolder':'/config/'
2019-12-04 20:10:18.124 (Ams MQTT Discoverer) 'Database':'/config/domoticz.db'
2019-12-04 20:10:18.124 (Ams MQTT Discoverer) 'Language':'en'
2019-12-04 20:10:18.124 (Ams MQTT Discoverer) 'Version':'0.0.4'
2019-12-04 20:10:18.124 (Ams MQTT Discoverer) 'Name':'MQTT Discoverer'
2019-12-04 20:10:18.124 (Ams MQTT Discoverer) 'Address':'10.17.1.2'
2019-12-04 20:10:18.124 (Ams MQTT Discoverer) 'Port':'1883'
2019-12-04 20:10:18.124 (Ams MQTT Discoverer) 'Username':'mqtt'
2019-12-04 20:10:18.124 (Ams MQTT Discoverer) 'Password':'something'
2019-12-04 20:10:18.124 (Ams MQTT Discoverer) 'Key':'MQTTDiscovery'
2019-12-04 20:10:18.124 (Ams MQTT Discoverer) 'Mode2':'tasmota'
2019-12-04 20:10:18.124 (Ams MQTT Discoverer) 'Mode6':'Verbose'
2019-12-04 20:10:18.124 (Ams MQTT Discoverer) 'DomoticzVersion':'4.11533'
2019-12-04 20:10:18.124 (Ams MQTT Discoverer) 'DomoticzHash':'90106db09'
2019-12-04 20:10:18.124 (Ams MQTT Discoverer) 'DomoticzBuildTime':'2019-11-25 13:02:18'
2019-12-04 20:10:18.124 (Ams MQTT Discoverer) Device count: 0
2019-12-04 20:10:18.124 (Ams MQTT Discoverer) Debug logging mask set to: PYTHON PLUGIN DEVICE CONNECTION MESSAGE
2019-12-04 20:10:18.124 (Ams MQTT Discoverer) Warning: could not load plugin options '' as JSON object
2019-12-04 20:10:18.125 (Ams MQTT Discoverer) Plugin options: {'addDiscoveredDeviceUsed': True, 'updateRSSI': False, 'updateVCC': False}
2019-12-04 20:10:18.125 (Ams MQTT Discoverer) MqttClient::__init__
2019-12-04 20:10:18.125 (Ams MQTT Discoverer) MqttClient::Open
2019-12-04 20:10:18.125 (Ams MQTT Discoverer) Heartbeat interval set to: 10.
2019-12-04 20:10:18.125 (Ams MQTT Discoverer) Protocol set to: 'MQTT'.
2019-12-04 20:10:18.125 (Ams MQTT Discoverer) Transport set to: 'TCP/IP', 10.1.1.2:1883.
2019-12-04 20:10:18.125 (Ams MQTT Discoverer) Connect directive received, action initiated successfully.
2019-12-04 20:10:18.176 (Ams MQTT Discoverer) MqttClient::onConnect
2019-12-04 20:10:18.176 (Ams MQTT Discoverer) Successful connect to: 10.1.1.2:1883
2019-12-04 20:10:18.176 (Ams MQTT Discoverer) MqttClient::Connect
2019-12-04 20:10:18.177 (Ams MQTT Discoverer) MQTT CONNECT ID: 'Domoticz_MQTTDiscovery_14_1575486618'
2019-12-04 20:10:18.179 (Ams MQTT Discoverer) Sending 68 bytes of data
2019-12-04 20:10:18.179 (Ams MQTT Discoverer) 10 42 00 04 4d 51 54 54 04 c2 00 3c 00 24 44 6f 6d 6f 74 69 .B..MQTT.®<.$Domoti
2019-12-04 20:10:18.179 (Ams MQTT Discoverer) 63 7a 5f 4d 51 54 54 44 69 73 63 6f 76 65 72 79 5f 31 34 5f cz_MQTTDiscovery_14_
2019-12-04 20:10:18.180 (Ams MQTT Discoverer) 31 35 37 35 34 38 36 36 31 38 00 04 6d 71 74 74 00 0a 83 91 1575486618..mqtt..so
2019-12-04 20:10:18.180 (Ams MQTT Discoverer) 81 63 6c 75 86 9f 52 52 .. .. .. .. .. .. .. .. .. .. .. .. mething
2019-12-04 20:10:18.231 (Ams MQTT Discoverer) Received 4 bytes of data
2019-12-04 20:10:18.231 (Ams MQTT Discoverer) 20 02 00 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ....
2019-12-04 20:10:18.231 (Ams MQTT Discoverer) onMQTTConnected
2019-12-04 20:10:18.232 (Ams MQTT Discoverer) getTopics: '{'tasmota/#'}'
2019-12-04 20:10:18.232 (Ams MQTT Discoverer) MqttClient::Subscribe
2019-12-04 20:10:18.232 (Ams MQTT Discoverer) Sending 16 bytes of data
2019-12-04 20:10:18.232 (Ams MQTT Discoverer) 82 0e 00 01 00 09 74 61 73 6d 6f 74 61 2f 23 00 .. .. .. .. ®....tasmota/#.
2019-12-04 20:10:18.283 (Ams MQTT Discoverer) Received 5 bytes of data
2019-12-04 20:10:18.283 (Ams MQTT Discoverer) 90 03 00 01 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ю...
2019-12-04 20:10:18.284 (Ams MQTT Discoverer) Received 46 bytes of data
2019-12-04 20:10:18.284 (Ams MQTT Discoverer) 31 2c 00 24 74 61 73 6d 6f 74 61 2f 74 65 6c 65 2f 70 69 78 1,.$tasmota/tele/pix
2019-12-04 20:10:18.284 (Ams MQTT Discoverer) 61 72 5f 73 74 61 6e 64 69 6e 67 5f 6c 61 6d 70 2f 4c 57 54 ar_standing_lamp/LWT
2019-12-04 20:10:18.285 (Ams MQTT Discoverer) 4f 6e 6c 69 6e 65 .. .. .. .. .. .. .. .. .. .. .. .. .. .. Online
2019-12-04 20:10:18.285 (Ams MQTT Discoverer) onMQTTSubscribed
2019-12-04 20:10:18.285 (Ams MQTT Discoverer) getDevices key: '' configkey: '' hasconfigkey: 'tasmota_tele_topic' value: '' config: '' topic: ''
2019-12-04 20:10:18.286 (Ams MQTT Discoverer) getDevices found 0 devices
2019-12-04 20:10:18.291 (Ams MQTT Discoverer) onMQTTPublish: tasmota/tele/pixar_standing_lamp/LWT:b'Online'
2019-12-04 20:10:18.122 Status: (Ams MQTT Discoverer) Initialized version 0.0.4
2019-12-04 20:10:18.122 Status: (Ams MQTT Discoverer) Entering work loop.
2019-12-04 20:10:28.155 (Ams MQTT Discoverer) Heartbeating...
2019-12-04 20:10:28.155 (Ams MQTT Discoverer) MqttClient::Ping
2019-12-04 20:10:28.155 (Ams MQTT Discoverer) Sending 2 bytes of data
2019-12-04 20:10:28.155 (Ams MQTT Discoverer) c0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �
2019-12-04 20:10:28.206 (Ams MQTT Discoverer) Received 2 bytes of data
2019-12-04 20:10:28.206 (Ams MQTT Discoverer) d0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ю
2019-12-04 20:10:38.162 (Ams MQTT Discoverer) Heartbeating... 

I also saw it before like this:

Code: Select all

2019-12-04 19:53:59.102 (Ams MQTT Discoverer) Received 131 bytes of data
2019-12-04 19:53:59.102 (Ams MQTT Discoverer) 30 80 01 00 26 74 61 73 6d 6f 74 61 2f 74 65 6c 65 2f 70 69 0�.&tasmota/tele/pi
2019-12-04 19:53:59.102 (Ams MQTT Discoverer) 78 61 72 5f 73 74 61 6e 64 69 6e 67 5f 6c 61 6d 70 2f 49 4e xar_standing_lamp/IN
2019-12-04 19:53:59.103 (Ams MQTT Discoverer) 46 4f 32 7b 22 57 65 62 53 65 72 76 65 72 4d 6f 64 65 22 3a FO2{"WebServerMode":
2019-12-04 19:53:59.103 (Ams MQTT Discoverer) 22 41 64 6d 69 6e 22 2c 22 48 6f 73 74 6e 61 6d 65 22 3a 22 "Admin","Hostname":"
2019-12-04 19:53:59.103 (Ams MQTT Discoverer) 70 69 78 61 72 5f 73 74 61 6e 64 69 6e 67 5f 6c 61 6d 70 2d pixar_standing_lamp-
2019-12-04 19:53:59.103 (Ams MQTT Discoverer) 36 39 39 39 22 2c 22 49 50 41 64 64 72 65 73 73 22 3a 22 31 6999","IPAddress":"1
2019-12-04 19:53:59.103 (Ams MQTT Discoverer) 20 2e 31 37 2e 31 2e 32 32 22 7d .. .. .. .. .. .. .. .. .. 0.1.1.22"}
2019-12-04 19:53:59.104 (Ams MQTT Discoverer) Received 85 bytes of data
2019-12-04 19:53:59.104 (Ams MQTT Discoverer) 30 53 00 26 74 61 73 6d 6f 74 61 2f 74 65 6c 65 2f 70 69 78 0S.&tasmota/tele/pix
2019-12-04 19:53:59.104 (Ams MQTT Discoverer) 61 72 5f 73 74 61 6e 64 69 6e 67 5f 6c 61 6d 70 2f 49 4e 46 ar_standing_lamp/INF
2019-12-04 19:53:59.104 (Ams MQTT Discoverer) 4f 33 7b 22 52 65 73 74 61 72 74 52 65 61 73 6f 6e 22 3a 22 O3{"RestartReason":"
2019-12-04 19:53:59.104 (Ams MQTT Discoverer) 53 6f 66 74 77 61 72 65 2f 53 79 73 74 65 6d 20 72 65 73 74 Software/System.rest
2019-12-04 19:53:59.105 (Ams MQTT Discoverer) 61 72 74 22 7d .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. art"}
2019-12-04 19:53:59.105 (Ams MQTT Discoverer) Received 57 bytes of data
2019-12-04 19:53:59.105 (Ams MQTT Discoverer) 30 37 00 27 74 61 73 6d 6f 74 61 2f 73 74 61 74 2f 70 69 78 07.'tasmota/stat/pix
2019-12-04 19:53:59.105 (Ams MQTT Discoverer) 61 72 5f 73 74 61 6e 64 69 6e 67 5f 6c 61 6d 70 2f 52 45 53 ar_standing_lamp/RES
2019-12-04 19:53:59.106 (Ams MQTT Discoverer) 55 4c 54 7b 22 50 4f 57 45 52 22 3a 22 4f 4e 22 7d .. .. .. ULT{"POWER":"ON"}
2019-12-04 19:53:59.106 (Ams MQTT Discoverer) Received 44 bytes of data
2019-12-04 19:53:59.106 (Ams MQTT Discoverer) 30 2a 00 26 74 61 73 6d 6f 74 61 2f 73 74 61 74 2f 70 69 78 0*.&tasmota/stat/pix
2019-12-04 19:53:59.107 (Ams MQTT Discoverer) 61 72 5f 73 74 61 6e 64 69 6e 67 5f 6c 61 6d 70 2f 50 4f 57 ar_standing_lamp/POW
2019-12-04 19:53:59.107 (Ams MQTT Discoverer) 45 52 4f 4e .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ERON
2019-12-04 19:53:59.107 (Ams MQTT Discoverer) onMQTTPublish: tasmota/tele/pixar_standing_lamp/INFO1:b'{"Module":"Generic","Version":"7.0.0.3(tasmota)","FallbackTopic":"cmnd/DVES_6B3B57_fb/","GroupTopic":"tasmota/cmnd/tasmotas/"}'
2019-12-04 19:53:59.108 (Ams MQTT Discoverer) onMQTTPublish: tasmota/tele/pixar_standing_lamp/INFO2:b'{"WebServerMode":"Admin","Hostname":"pixar_standing_lamp-6999","IPAddress":"10.1.1.22"}'
2019-12-04 19:53:59.109 (Ams MQTT Discoverer) onMQTTPublish: tasmota/tele/pixar_standing_lamp/INFO3:b'{"RestartReason":"Software/System restart"}'
2019-12-04 19:53:59.109 (Ams MQTT Discoverer) onMQTTPublish: tasmota/stat/pixar_standing_lamp/RESULT:b'{"POWER":"ON"}'
2019-12-04 19:53:59.110 (Ams MQTT Discoverer) onMQTTPublish: tasmota/stat/pixar_standing_lamp/POWER:b'ON'
2019-12-04 19:54:07.859 (Ams MQTT Discoverer) Heartbeating...
2019-12-04 19:54:07.860 (Ams MQTT Discoverer) MqttClient::Ping
2019-12-04 19:54:07.860 (Ams MQTT Discoverer) Sending 2 bytes of data
2019-12-04 19:54:07.860 (Ams MQTT Discoverer) c0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �
2019-12-04 19:54:07.911 (Ams MQTT Discoverer) Received 2 bytes of data
2019-12-04 19:54:07.912 (Ams MQTT Discoverer) d0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ю
2019-12-04 19:54:08.065 (Ams MQTT Discoverer) Received 423 bytes of data
2019-12-04 19:54:08.065 (Ams MQTT Discoverer) 30 a4 03 00 26 74 61 73 6d 6f 74 61 2f 74 65 6c 65 2f 70 69 0Į.&tasmota/tele/pi
2019-12-04 19:54:08.067 (Ams MQTT Discoverer) 78 61 72 5f 73 74 61 6e 64 69 6e 67 5f 6c 61 6d 70 2f 53 54 xar_standing_lamp/ST
2019-12-04 19:54:08.067 (Ams MQTT Discoverer) 41 54 45 7b 22 54 69 6d 65 22 3a 22 31 39 37 30 2d 30 31 2d ATE{"Time":"1970-01-
2019-12-04 19:54:08.067 (Ams MQTT Discoverer) 30 31 54 30 30 3a 30 30 3a 31 34 22 2c 22 55 70 74 69 6d 65 01T00:00:14","Uptime
2019-12-04 19:54:08.068 (Ams MQTT Discoverer) 22 3a 22 30 54 30 30 3a 30 30 3a 31 36 22 2c 22 55 70 74 69 ":"0T00:00:16","Upti
2019-12-04 19:54:08.069 (Ams MQTT Discoverer) 6d 65 53 65 63 22 3a 31 36 2c 22 48 65 61 70 22 3a 33 31 2c meSec":16,"Heap":31,
2019-12-04 19:54:08.069 (Ams MQTT Discoverer) 22 53 6c 65 65 70 4d 6f 64 65 22 3a 22 44 79 6e 61 6d 69 63 "SleepMode":"Dynamic
2019-12-04 19:54:08.069 (Ams MQTT Discoverer) 22 2c 22 53 6c 65 65 70 22 3a 30 2c 22 4c 6f 61 64 41 76 67 ","Sleep":0,"LoadAvg
2019-12-04 19:54:08.069 (Ams MQTT Discoverer) 22 3a 37 32 2c 22 4d 71 74 74 43 6f 75 6e 74 22 3a 31 2c 22 ":72,"MqttCount":1,"
2019-12-04 19:54:08.069 (Ams MQTT Discoverer) 50 4f 57 45 52 22 3a 22 4f 4e 22 2c 22 44 69 6d 6d 65 72 22 POWER":"ON","Dimmer"
2019-12-04 19:54:08.069 (Ams MQTT Discoverer) 3a 35 35 2c 22 43 6f 6c 6f 72 22 3a 22 30 30 38 43 22 2c 22 :55,"Color":"008C","
2019-12-04 19:54:08.069 (Ams MQTT Discoverer) 48 53 42 43 6f 6c 6f 72 22 3a 22 30 2c 30 2c 30 22 2c 22 43 HSBColor":"0,0,0","C
2019-12-04 19:54:08.069 (Ams MQTT Discoverer) 68 61 6e 6e 65 6c 22 3a 5b 30 2c 35 35 5d 2c 22 43 54 22 3a hannel":[0,55],"CT":
2019-12-04 19:54:08.070 (Ams MQTT Discoverer) 35 30 30 2c 22 46 61 64 65 22 3a 22 4f 46 46 22 2c 22 53 70 500,"Fade":"OFF","Sp
2019-12-04 19:54:08.070 (Ams MQTT Discoverer) 65 65 64 22 3a 31 2c 22 4c 65 64 54 61 62 6c 65 22 3a 22 4f eed":1,"LedTable":"O
2019-12-04 19:54:08.070 (Ams MQTT Discoverer) 4e 22 2c 22 57 69 66 69 22 3a 7b 22 41 50 22 3a 31 2c 22 53 N","Wifi":{"AP":1,"S
2019-12-04 19:54:08.070 (Ams MQTT Discoverer) 53 49 64 22 3a 22 6d 61 79 62 65 22 2c 22 42 53 53 49 64 22 SId":"maybe","BSSId"
2019-12-04 19:54:08.070 (Ams MQTT Discoverer) 3a 22 34 41 3a 44 39 3a 45 37 3a 43 37 3a 34 37 3a 44 46 22 :"4A:D9:E7:C7:47:DF"
2019-12-04 19:54:08.070 (Ams MQTT Discoverer) 2c 22 43 68 61 6e 6e 65 6c 22 3a 31 31 2c 22 52 53 53 49 22 ,"Channel":11,"RSSI"
2019-12-04 19:54:08.070 (Ams MQTT Discoverer) 3a 39 36 2c 22 4c 69 6e 6b 43 6f 75 6e 74 22 3a 31 2c 22 44 :96,"LinkCount":1,"D
2019-12-04 19:54:08.070 (Ams MQTT Discoverer) 6f 77 6e 74 69 6d 65 22 3a 22 30 54 30 30 3a 30 30 3a 30 35 owntime":"0T00:00:05

I appreciate your help.

[Geitje]

@apatrid: did you look in Domoticz device database? (Setup > devices)

[apatrid]

yes, sure. I managed to add them via old method, but mqtt discovery failed. i also managed to brick one of them with attempting to upload sonoff 6.1.1 firmware; now it briefly flashes some esp32 wifi hotspot but it won't turn on nor it will allow me to really connect to wifi; seems bricked. oh well

i managed to add other two only after updating with OTAto tasmota 7.1.1 and getting domoticz menu.

[mosjonathan]

hello,

i installed and configured this plugin and it is working.

devices are discovered and the status is updating.

now i'm trying to switch a rgbww device(action lsc gu10) with tasmota 7.1.2.6 with dzvents but that is not working.

can u tell me how to do that in dzvents?

[johansson]

I got into testing a Sonoff Basic switch with Tasmota firmware, but my Domoticz doesn't detect any devices - any ideas what might be the issue?

I installed the plugin as per the instructions on the first page and added MQTT discovery into the hardware page. So far so good, but no devices are visible in devices list, nor is the MQTT discovery seen in the hardware list of the device page sidebar:

Screen Shot 2020-01-16 at 11.58.13.png (71.38 KiB) Viewed 2660 times

Screen Shot 2020-01-16 at 11.59.17.png (26.33 KiB) Viewed 2660 times

In log there's something related to this, not sure if that's correct amount of data:

Code: Select all

2020-01-16 11:51:32.397 (mqtt) MqttClient::Ping
2020-01-16 11:51:32.397 (mqtt) Sending 2 bytes of data
2020-01-16 11:51:32.397 (mqtt) c0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �.
2020-01-16 11:51:32.448 (mqtt) Received 2 bytes of data
2020-01-16 11:51:32.448 (mqtt) d0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �.

The Sonoff switch itself can be controlled and configured through browser, ie it's in the same network and so on:

Screen Shot 2020-01-16 at 12.02.35.png (34.38 KiB) Viewed 2660 times

Any pointers how to get this up & running?

[jake]

I got into testing a Sonoff Basic switch with Tasmota firmware, but my Domoticz doesn't detect any devices - any ideas what might be the issue?

I installed the plugin as per the instructions on the first page and added MQTT discovery into the hardware page. So far so good, but no devices are visible in devices list, nor is the MQTT discovery seen in the hardware list of the device page sidebar:

Screen Shot 2020-01-16 at 11.58.13.png

Screen Shot 2020-01-16 at 11.59.17.png

In log there's something related to this, not sure if that's correct amount of data:

Code: Select all

2020-01-16 11:51:32.397 (mqtt) MqttClient::Ping
2020-01-16 11:51:32.397 (mqtt) Sending 2 bytes of data
2020-01-16 11:51:32.397 (mqtt) c0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �.
2020-01-16 11:51:32.448 (mqtt) Received 2 bytes of data
2020-01-16 11:51:32.448 (mqtt) d0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �.

The Sonoff switch itself can be controlled and configured through browser, ie it's in the same network and so on:

Screen Shot 2020-01-16 at 12.02.35.png

Any pointers how to get this up & running?

Which firmware of the sonoff did you install? Make sure you select a bin version that supports the mqttdiscovery.
https://github.com/arendst/Tasmota/blob ... /BUILDS.md

At first I didn't realize that I needed a full version to get this to work. In the mean time I found an alternative that works for all binary files. Recovery in domoticz with this plugin is excellent: Tasmoticz
https://github.com/joba-1/Tasmoticz
I added 6 temperature sensors to the basic switch and they were immediately recognized within domoticz

[johansson]

Perfect, that was it - thanks Jake! I got the Sonoff pre-flashed, so didn't pay any attention to the firmware: downloaded tasmota.bin from http://thehackbox.org/tasmota/, uploaded it to switch and immediately it shows up in Domoticz. Case closed.

[deennoo]

I have an issue with this plugin who makes my re-use my sonoff 1st gen and flash action wifi plug.

This plugin update again and again device status even if there is no change.

Not very usefull and this use log for nothing

[mvveelen]

I'm using the latest version of the plugin and sometimes after a restart / update of Domoticz I get new Sonoff devices discovered.

2020-02-02 12:02:23.592 Status: (MQTT discovery) Entering work loop.
2020-02-02 12:02:23.592 Status: (MQTT discovery) Initialized version 0.0.4

Devices that were already discovered and are being used for a while now get found again. So then I delete these new discovered (double) devices.

How is this possible? Or do I have to delete the old devices and use the new devices to get rid of this "problem" ?

[loicZ0R]

Hello fellow Domoticz'ers

Im running into some issues aswell, i have a bunch of Sonofss DIY mini which i flashed with the tasmota-lite.bin since it only allows max 500kb.

Im a complete newbie, but managed to do this following those youtube guides: https://www.youtube.com/watch?v=w7QhsFqBr30 https://www.youtube.com/watch?v=t1yHmKZTsgE and https://www.youtube.com/watch?v=fzEDFmB0UYU Big up to their comprehencive vids!

I am running the latest Domoticz version on a Raspberry pi 3, i have flashed the sonoffs DIY mini's with tasmota, installed mousquitto MQTT broker with latest updates/upgrades.

My devices appear in domoticz, but only like 1 out of 15 try's to switch my lights on/of from domoticz does come trough, when connecting directly to the tasmota trough browser ip i can switch on/off without any hassle.

In my opinion there is somthing going on with my MQTT broker, since i dont see anything unusual in the tasmota logs, i havent managed yet to get a view of the MQTT broker logs.

Some help or advice would be much apreciated!

[rolandtwilt]

Good morning smart people,

I get the error message below and I'm looking for a solution but can't find an explanation.
Anyone know what's going on here?
logbook Domoticz:

2022-03-28 10:10:17.717 Error: MQTT Discovery: Call to function 'onMessage' failed, exception details:
2022-03-28 10:10:17.720 Error: MQTT Discovery: Traceback (most recent call last):
2022-03-28 10:10:17.720 Error: MQTT Discovery: File "/home/pi/domoticz/plugins/domoticz_mqtt_discovery/plugin.py", line 392, in onMQTTPublish
2022-03-28 10:10:17.720 Error: MQTT Discovery: message = json.loads(rawmessage.decode('utf8'))
2022-03-28 10:10:17.720 Error: MQTT Discovery: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb5 in position 264: invalid start byte
2022-03-28 10:10:17.720 Error: MQTT Discovery:
2022-03-28 10:10:17.720 Error: MQTT Discovery: During handling of the above exception, another exception occurred:
2022-03-28 10:10:17.720 Error: MQTT Discovery:
2022-03-28 10:10:17.720 Error: MQTT Discovery: Traceback (most recent call last):
2022-03-28 10:10:17.720 Error: MQTT Discovery: File "/home/pi/domoticz/plugins/domoticz_mqtt_discovery/plugin.py", line 1116, in onMessage
2022-03-28 10:10:17.720 Error: MQTT Discovery: _plugin.onMessage(Connection, Data)
2022-03-28 10:10:17.720 Error: MQTT Discovery: File "/home/pi/domoticz/plugins/domoticz_mqtt_discovery/plugin.py", line 379, in onMessage
2022-03-28 10:10:17.720 Error: MQTT Discovery: self.mqttClient.onMessage(Connection, Data)
2022-03-28 10:10:17.720 Error: MQTT Discovery: File "/home/pi/domoticz/plugins/domoticz_mqtt_discovery/plugin.py", line 151, in onMessage
2022-03-28 10:10:17.720 Error: MQTT Discovery: self.mqttPublishCb(topic, Data['Payload'])
2022-03-28 10:10:17.720 Error: MQTT Discovery: File "/home/pi/domoticz/plugins/domoticz_mqtt_discovery/plugin.py", line 395, in onMQTTPublish
2022-03-28 10:10:17.720 Error: MQTT Discovery: message = rawmessage.decode('utf8')
2022-03-28 10:10:17.720 Error: MQTT Discovery: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb5 in position 264: invalid start byte

please help