Domoticz

Posted: **Friday 30 August 2019 0:14**

Hey!
I have got problem with shelly RGBW2 in domoticz. When I change state in shelly's http page, it works fine and i can see change in domoticz. When I try to on/off switch in domoticz, it doesnt work.

Any idea what could be the reason ?

Posted: **Friday 30 August 2019 6:59**

damyano wrote: ↑Friday 30 August 2019 0:14 Hey!
I have got problem with shelly RGBW2 in domoticz. When I change state in shelly's http page, it works fine and i can see change in domoticz. When I try to on/off switch in domoticz, it doesnt work.

Any idea what could be the reason ?

Make sure, that the appropriate shelly device is enabled in the Domoticz device page, as status updates works in its disabled state, but sending commands do not.
If this is not the problem, please post a verbose event log, when you try to change i from Domoticz, which contains the sent commands and mqtt lines.

Posted: **Friday 30 August 2019 8:10**

Thanks for answear. I have only one shelly device, so it must be this one.
When I try to on/off in domoticz , the logs look like that:

2019-08-29 23:57:15.645 Status: (Shelly RGBW2) Entering work loop.
2019-08-29 23:57:15.645 Status: (Shelly RGBW2) Initialized version 0.3.6
2019-08-29 23:57:15.965 Status: MQTT: Connecting to 192.168.10.1:1883
2019-08-29 23:57:16.066 Status: MQTT: connected to: 192.168.10.1:1883
2019-08-29 23:57:16.167 Status: MQTT: Subscribed
2019-08-29 23:57:21.089 Status: User: Admin initiated a switch command (8/Shelly RGBW2 - shellyrgbw2-66174C-3-w/Off)
2019-08-29 23:57:24.761 Status: User: Admin initiated a switch command (8/Shelly RGBW2 - shellyrgbw2-66174C-3-w/Off)
2019-08-29 23:57:26.352 Status: User: Admin initiated a switch command (8/Shelly RGBW2 - shellyrgbw2-66174C-3-w/Off)

And nothing is going on.

Posted: **Friday 30 August 2019 18:05**

damyano wrote: ↑Friday 30 August 2019 8:10 2019-08-29 23:57:26.352 Status: User: Admin initiated a switch command (8/Shelly RGBW2 - shellyrgbw2-66174C-3-w/Off)

I have learned from the above line that:
1. You are using 4xWhite channel mode
2. Only the last Channel 3 is not working, Channel 0-1-2 works fine. (You do not specifically write it, but i tried out and this is the case...)

In todays commit this bug is fixed.

Posted: **Friday 30 August 2019 19:56**

That's true

Now it works well! Thanks!

Posted: **Wednesday 11 September 2019 13:25**

SHelly just publish a new API through their cloud. Could be interesting to have the plugin using it instead of MQTT (which work great) in order to keep the cloud available on the app (with MQTT, you lose cloud access)
https://www.facebook.com/notes/shelly-s ... 673078719/

Posted: **Wednesday 11 September 2019 18:10**

darrepac wrote: ↑Wednesday 11 September 2019 13:25 ... (with MQTT, you lose cloud access)

Noted, and I am very happy without cloud-things in my home.

Posted: **Wednesday 11 September 2019 19:32**

lwolf wrote: ↑Wednesday 11 September 2019 18:10
darrepac wrote: ↑Wednesday 11 September 2019 13:25 ... (with MQTT, you lose cloud access)
Noted, and I am very happy without cloud-things in my home.

I do agree, I am just afraid that they do not continue MQTT in the future

Posted: **Wednesday 11 September 2019 21:14**

darrepac wrote: ↑Wednesday 11 September 2019 19:32 I do agree, I am just afraid that they do not continue MQTT in the future

I do not afraid of that, MQTT is the only thing that makes Shelly a viable option instead a Sonoff.
If they ever drop MQTT, most users will flash Tasmota onto Shelly devices... and the sales will drop favoring the Sonoff.

Posted: **Saturday 14 September 2019 17:25**

Strange thing going on.
Stopped Domoticz
Cloned the repository in my domoticz/plugins folder.
Started Domoticz.

No trace of the Shelly_MQTT in the hardware. Other plugins show up just fine.
My log at startup:

Code: Select all

 2019-09-14 17:06:10.634 Status: Domoticz V4.10717 (c)2012-2019 GizMoCuz
2019-09-14 17:06:10.634 Status: Build Hash: b38b49e5, Date: 2019-05-09 13:04:08
2019-09-14 17:06:10.654 Status: Startup Path: /home/wim/domoticz/
2019-09-14 17:06:10.722 Status: PluginSystem: Started, Python version '3.6.8'.
2019-09-14 17:06:10.726 Status: WebServer(HTTP) started on address: :: with port 9080
2019-09-14 17:06:10.731 Status: TCPServer: shared server started...
2019-09-14 17:06:10.731 Status: RxQueue: queue worker started...
2019-09-14 17:06:10.730 Error: WebServer(SSL) startup failed on address 0.0.0.0 with port: 443: bind: Address already in use
2019-09-14 17:06:10.730 Error: WebServer(SSL) check privileges for opening ports below 1024
2019-09-14 17:06:12.732 Status: AppLamp: Worker Started...
2019-09-14 17:06:12.732 Status: Harmony Hub: Worker thread started...
2019-09-14 17:06:12.733 Status: AppLamp: Worker Started...
2019-09-14 17:06:12.733 Status: (GBridge) Started.
2019-09-14 17:06:12.734 Status: EventSystem: reset all events...
2019-09-14 17:06:12.735 Status: dzVents: Write file: /home/wim/domoticz/scripts/dzVents/generated_scripts/onMorning.lua
2019-09-14 17:06:12.735 Status: dzVents: Write file: /home/wim/domoticz/scripts/dzVents/generated_scripts/sunrise.lua
2019-09-14 17:06:12.735 Status: dzVents: Write file: /home/wim/domoticz/scripts/dzVents/generated_scripts/sunset.lua
2019-09-14 17:06:12.735 Status: dzVents: Write file: /home/wim/domoticz/scripts/dzVents/generated_scripts/sunset2.lua
2019-09-14 17:06:12.735 Status: dzVents: Write file: /home/wim/domoticz/scripts/dzVents/generated_scripts/Radio bureau.lua
2019-09-14 17:06:12.735 Status: dzVents: Write file: /home/wim/domoticz/scripts/dzVents/generated_scripts/Beweging bureau.lua
2019-09-14 17:06:12.735 Status: dzVents: Write file: /home/wim/domoticz/scripts/dzVents/generated_scripts/Achterdeur open.lua
2019-09-14 17:06:12.735 Status: dzVents: Write file: /home/wim/domoticz/scripts/dzVents/generated_scripts/offEvening.lua
2019-09-14 17:06:12.735 Status: dzVents: Write file: /home/wim/domoticz/scripts/dzVents/generated_scripts/MultiMedia Off.lua
2019-09-14 17:06:12.736 Status: dzVents: Write file: /home/wim/domoticz/scripts/dzVents/generated_scripts/TV On.lua
2019-09-14 17:06:12.736 Status: dzVents: Write file: /home/wim/domoticz/scripts/dzVents/generated_scripts/Netflix on.lua
2019-09-14 17:06:12.736 Status: dzVents: Write file: /home/wim/domoticz/scripts/dzVents/generated_scripts/WII on.lua
2019-09-14 17:06:12.736 Status: dzVents: Write file: /home/wim/domoticz/scripts/dzVents/generated_scripts/Retropie on.lua
2019-09-14 17:06:12.736 Status: dzVents: Write file: /home/wim/domoticz/scripts/dzVents/generated_scripts/Rolluiken Living.lua
2019-09-14 17:06:12.736 Status: dzVents: Write file: /home/wim/domoticz/scripts/dzVents/generated_scripts/Rolluiken Xander.lua
2019-09-14 17:06:12.736 Status: EventSystem: reset all device statuses...
2019-09-14 17:06:12.796 Status: Python EventSystem: Initalizing event module.
2019-09-14 17:06:12.796 Status: EventSystem: Started
2019-09-14 17:06:12.796 Status: EventSystem: Queue thread started...
2019-09-14 17:06:12.934 Status: RFLink: Using serial port: /dev/ttyACM0
2019-09-14 17:06:12.934 Status: RFLink: Using serial port: /dev/ttyACM1
2019-09-14 17:06:13.179 Status: PluginSystem: Entering work loop.
2019-09-14 17:06:13.372 Status: (GBridge) Entering work loop.
2019-09-14 17:06:13.372 Status: (GBridge) Initialized version 0.0.14
2019-09-14 17:06:13.636 Status: Incoming connection from: 127.0.0.1
2019-09-14 17:06:13.733 Status: MQTT: Connecting to 127.0.0.1:1883
2019-09-14 17:06:13.834 Status: MQTT: connected to: 127.0.0.1:1883
2019-09-14 17:06:13.855 Status: RFLink: Controller Initialized!...
2019-09-14 17:06:13.857 Status: AppLamp: Bridge found!...
2019-09-14 17:06:13.860 Status: RFLink: Controller Initialized!...
2019-09-14 17:06:13.908 Status: AppLamp: Bridge found!...
2019-09-14 17:06:13.930 Status: RFLink Detected, Version: 1.1 Revision: 48 Build: 4
2019-09-14 17:06:13.934 Status: MQTT: Subscribed
2019-09-14 17:06:13.935 Status: RFLink Detected, Version: 1.1 Revision: 48 Build: 4
2019-09-14 17:06:16.706 Status: Harmony Hub: Connected to Hub.

Any help would be appreciated.

Thank you

Posted: **Saturday 14 September 2019 18:18**

lwolf wrote: ↑Wednesday 11 September 2019 21:14
darrepac wrote: ↑Wednesday 11 September 2019 19:32 I do agree, I am just afraid that they do not continue MQTT in the future
I do not afraid of that, MQTT is the only thing that makes Shelly a viable option instead a Sonoff.
If they ever drop MQTT, most users will flash Tasmota onto Shelly devices... and the sales will drop favoring the Sonoff.

Very happy with my Shellys flashed with Tasmota - solid (so far!)
- they are then consistent with my Sonoffs.

Posted: **Saturday 14 September 2019 21:21**

any signs of the new shelly devices being implemented in the plugin?

Posted: **Monday 23 September 2019 13:07**

I have an issue with a Plug S and the last day graph. It should come from the plugin as it is plug and play: https://www.domoticz.com/forum/viewtopi ... =6&t=29496

everything was working well but now, nothing work good (bad energy display)

Edit: Everything is working now ok, I think it is due to the reset of the device once you unplug it

Posted: **Wednesday 02 October 2019 15:45**

On my fresh installed domoticz on Debian 9.9 with python3.5 installed as per domoticz pyhton installation guide, when i add the Shelly MQTT hardware, domoticz stops working with the following error

Error: (ShellyMQTT) failed to load 'plugin.py', Python Path used was ':/usr/lib/python35.zip:/usr/lib/python3.5:/usr/lib/python3.5/plat-x86_64-linux-gnu:/usr/lib/python3.5/lib-dynload:/usr/local/lib/python3.5/dist-packages:/usr/lib/python3/dist-packages:/usr/lib/python3.5/dist-packages'.
2019-10-02 15:43:35.136 Error: (Shelly) Module Import failed, exception: 'ImportError'
2019-10-02 15:43:35.136 Error: (Shelly) Module Import failed: ' Name: plugin'
2019-10-02 15:43:35.136 Error: (Shelly) Error Line details not available.

Posted: **Wednesday 02 October 2019 18:30**

Hello everyone
a strange thing happens to me, I created a Scene group that turns on and off some of the lights switches it works normally but in the log of each switch it is reported (date is time and on) for switching on, but for switching off it is reported (date is time " empty field).
This does not affect web domoticz, but on the Domoticz App the lights that should be turned off remain on.
I would say that the devices used for the lights are shellys managed by the Shelly_MQTT plugin, which, however, by acting directly on a single device on domoticz in the log is written on and off regularly.
Other dummy devices do not have this problem.
Do you have an idea how you can solve it?

The version of domoticz I am using is Beta 4.11333 on raspberry Pi,

Posted: **Sunday 06 October 2019 19:37**

scsmloni wrote: ↑Wednesday 02 October 2019 15:45 On my fresh installed domoticz on Debian 9.9 with python3.5 installed as per domoticz pyhton installation guide, when i add the Shelly MQTT hardware, domoticz stops working with the following error

Error: (ShellyMQTT) failed to load 'plugin.py', Python Path used was ':/usr/lib/python35.zip:/usr/lib/python3.5:/usr/lib/python3.5/plat-x86_64-linux-gnu:/usr/lib/python3.5/lib-dynload:/usr/local/lib/python3.5/dist-packages:/usr/lib/python3/dist-packages:/usr/lib/python3.5/dist-packages'.
2019-10-02 15:43:35.136 Error: (Shelly) Module Import failed, exception: 'ImportError'
2019-10-02 15:43:35.136 Error: (Shelly) Module Import failed: ' Name: plugin'
2019-10-02 15:43:35.136 Error: (Shelly) Error Line details not available.

Then try to install any other Python plugin for testing your python environment. There are several exception handling lines in my plugin.py and this error messages not coming from it. "ImportError" suggests that maybe some core python library is not available.

Posted: **Sunday 06 October 2019 19:43**

mattley30 wrote: ↑Wednesday 02 October 2019 18:30 a strange thing happens to me, I created a Scene group that turns on and off some of the lights switches it works normally but in the log of each switch it is reported (date is time and on) for switching on, but for switching off it is reported (date is time " empty field).

A verbose log would be very helpful about what is happening in the background. I can only guess that shellymqtt waits "on" or "off" commands only from Domoticz, and something else arrives...

Posted: **Sunday 06 October 2019 19:52**

snellejellep wrote: ↑Saturday 14 September 2019 21:21 any signs of the new shelly devices being implemented in the plugin?

I can only implement shelly devices that i own. But as it is open source everyone has the freedom to implement it.. or send me one device to implement it!

https://bitekmindenhol.blog.hu/2019/05/02/support_236

Posted: **Monday 14 October 2019 10:22**

lwolf wrote: ↑Sunday 06 October 2019 19:43
mattley30 wrote: ↑Wednesday 02 October 2019 18:30 a strange thing happens to me, I created a Scene group that turns on and off some of the lights switches it works normally but in the log of each switch it is reported (date is time and on) for switching on, but for switching off it is reported (date is time " empty field).
A verbose log would be very helpful about what is happening in the background. I can only guess that shellymqtt waits "on" or "off" commands only from Domoticz, and something else arrives...

2019-10-14 10:15:42.600 Activating Scene/Group: [Luci Magazzino Pesca]
2019-10-14 10:15:42.605 Activating Scene/Group Device: Pesca Magazzino 1 (On)
2019-10-14 10:15:42.657 Activating Scene/Group Device: Pesca Magazzino 2 (On)
2019-10-14 10:15:42.708 Activating Scene/Group Device: Produzione 1 (On)
2019-10-14 10:15:42.759 Activating Scene/Group Device: Produzione 2 (On)
2019-10-14 10:15:42.810 Activating Scene/Group Device: Produzione 3 (On)
2019-10-14 10:15:42.861 Activating Scene/Group Device: Produzione 4 (On)
2019-10-14 10:15:42.598 Status: User: Admin initiated a scene/group command
2019-10-14 10:16:10.751 Activating Scene/Group: [Luci Magazzino Pesca]
2019-10-14 10:16:10.756 Activating Scene/Group Device: Pesca Magazzino 1 (Off)
2019-10-14 10:16:10.807 Activating Scene/Group Device: Pesca Magazzino 2 (Off)
2019-10-14 10:16:10.858 Activating Scene/Group Device: Produzione 1 (Off)
2019-10-14 10:16:10.909 Activating Scene/Group Device: Produzione 2 (Off)
2019-10-14 10:16:10.960 Activating Scene/Group Device: Produzione 3 (Off)
2019-10-14 10:16:10.750 Status: User: Admin initiated a scene/group command
2019-10-14 10:16:11.010 Activating Scene/Group Device: Produzione 4 (Off)

HI,Iwolf
I send you the log on and off of the group / scene, the commands send them regularly, I hope this log helps
thanks

Posted: **Monday 14 October 2019 22:44**

mattley30 wrote: ↑Monday 14 October 2019 10:22 2019-10-14 10:15:42.600 Activating Scene/Group: [Luci Magazzino Pesca]
2019-10-14 10:15:42.605 Activating Scene/Group Device: Pesca Magazzino 1 (On)
2019-10-14 10:15:42.657 Activating Scene/Group Device: Pesca Magazzino 2 (On)
2019-10-14 10:15:42.708 Activating Scene/Group Device: Produzione 1 (On)
2019-10-14 10:15:42.759 Activating Scene/Group Device: Produzione 2 (On)
2019-10-14 10:15:42.810 Activating Scene/Group Device: Produzione 3 (On)
2019-10-14 10:15:42.861 Activating Scene/Group Device: Produzione 4 (On)
2019-10-14 10:15:42.598 Status: User: Admin initiated a scene/group command
2019-10-14 10:16:10.751 Activating Scene/Group: [Luci Magazzino Pesca]
2019-10-14 10:16:10.756 Activating Scene/Group Device: Pesca Magazzino 1 (Off)
2019-10-14 10:16:10.807 Activating Scene/Group Device: Pesca Magazzino 2 (Off)
2019-10-14 10:16:10.858 Activating Scene/Group Device: Produzione 1 (Off)
2019-10-14 10:16:10.909 Activating Scene/Group Device: Produzione 2 (Off)
2019-10-14 10:16:10.960 Activating Scene/Group Device: Produzione 3 (Off)
2019-10-14 10:16:10.750 Status: User: Admin initiated a scene/group command
2019-10-14 10:16:11.010 Activating Scene/Group Device: Produzione 4 (Off)

Sorry the standard logs has no informations for me.
Please set "Debug: Verbose" at ShellyMQTT settings. I will show you a sample of the verbose log, which i can use:

2019-08-10 10:36:00.643 (shelly) Received 194 bytes of data
2019-08-10 10:36:00.643 (shelly) 30 31 00 2b 73 68 65 6c 6c 69 65 73 2f 73 68 65 6c 6c 79 73 01.+shellies/shellys
2019-08-10 10:36:00.644 (shelly) 77 69 74 63 68 2d 33 32 42 46 38 37 2f 72 6f 6c 6c 65 72 2f witch-32BF87/roller/
2019-08-10 10:36:00.644 (shelly) 30 2f 70 6f 77 65 72 30 2e 30 30 30 2e 00 28 73 68 65 6c 6c 0/power0.000..(shell
2019-08-10 10:36:00.644 (shelly) 69 65 73 2f 73 68 65 6c 6c 79 73 77 69 74 63 68 2d 33 32 42 ies/shellyswitch-32B
2019-08-10 10:36:00.644 (shelly) 46 38 37 2f 72 65 6c 61 79 2f 70 6f 77 65 72 30 2e 30 30 30 F87/relay/power0.000
2019-08-10 10:36:00.644 (shelly) 2f 00 2c 73 68 65 6c 6c 69 65 73 2f 73 68 65 6c 6c 79 73 77 /.,shellies/shellysw
2019-08-10 10:36:00.644 (shelly) 69 74 63 68 2d 33 32 42 46 38 37 2f 72 6f 6c 6c 65 72 2f 30 itch-32BF87/roller/0
2019-08-10 10:36:00.644 (shelly) 2f 65 6e 65 72 67 79 30 30 2c 00 29 73 68 65 6c 6c 69 65 73 /energy00,.)shellies
2019-08-10 10:36:00.644 (shelly) 2f 73 68 65 6c 6c 79 73 77 69 74 63 68 2d 33 32 42 46 38 37 /shellyswitch-32BF87
2019-08-10 10:36:00.644 (shelly) 2f 72 65 6c 61 79 2f 65 6e 65 72 67 79 30 .. .. .. .. .. .. /relay/energy0
2019-08-10 10:36:00.644 (shelly) MQTT message: shellies/shellyswitch-32BF87/roller/0/power 0.0
2019-08-10 10:36:00.644 (shelly) MQTT message: shellies/shellyswitch-32BF87/relay/power 0.0
2019-08-10 10:36:00.644 (shelly - shellyswitch-32BF87-energy) Updating device from 0:'1.31;0.0' to have values 0:'0.0;0.0'.
2019-08-10 10:36:00.647 (shelly) MQTT message: shellies/shellyswitch-32BF87/roller/0/energy 0
2019-08-10 10:36:00.647 (shelly) MQTT message: shellies/shellyswitch-32BF87/relay/energy 0
2019-08-10 10:36:00.647 (shelly - shellyswitch-32BF87-energy) Updating device from 0:'0.0;0.0' to have values 0:'0.0;0.0'.
2019-08-10 10:36:00.225 Status: LUA: Time based event fired
2019-08-10 10:36:00.543 Status: LUA: Device based event fired on 'shelly - shellyswitch-32BF87-0-pos', value 'Open'
2019-08-10 10:36:00.544 Status: LUA: Device based event fired on 'shelly - shellyswitch-32BF87-0-roller', value 'Stop'
2019-08-10 10:36:00.649 Status: LUA: Device based event fired on 'shelly - shellyswitch-32BF87-energy', value '0.0;0.0'
2019-08-10 10:36:00.650 Status: LUA: Device based event fired on 'shelly - shellyswitch-32BF87-energy', value '0.0;0.0'
2019-08-10 10:36:03.712 (shelly) Command: Off (0) Color:
2019-08-10 10:36:03.712 (shelly) MqttClient::publish shellies/shellyswitch-32BF87/roller/0/command (close)
2019-08-10 10:36:03.712 (shelly) Sending 54 bytes of data
2019-08-10 10:36:03.712 (shelly) 30 34 00 2d 73 68 65 6c 6c 69 65 73 2f 73 68 65 6c 6c 79 73 04.-shellies/shellys
2019-08-10 10:36:03.712 (shelly) 77 69 74 63 68 2d 33 32 42 46 38 37 2f 72 6f 6c 6c 65 72 2f witch-32BF87/roller/
2019-08-10 10:36:03.712 (shelly) 30 2f 63 6f 6d 6d 61 6e 64 63 6c 6f 73 65 .. .. .. .. .. .. 0/commandclose
2019-08-10 10:36:03.712 (shelly) Received 54 bytes of data
2019-08-10 10:36:03.712 (shelly) 30 34 00 2d 73 68 65 6c 6c 69 65 73 2f 73 68 65 6c 6c 79 73 04.-shellies/shellys
2019-08-10 10:36:03.712 (shelly) 77 69 74 63 68 2d 33 32 42 46 38 37 2f 72 6f 6c 6c 65 72 2f witch-32BF87/roller/
2019-08-10 10:36:03.712 (shelly) 30 2f 63 6f 6d 6d 61 6e 64 63 6c 6f 73 65 .. .. .. .. .. .. 0/commandclose
2019-08-10 10:36:03.712 (shelly) MQTT message: shellies/shellyswitch-32BF87/roller/0/command close
2019-08-10 10:36:03.963 (shelly) Received 47 bytes of data
2019-08-10 10:36:03.963 (shelly) 30 2d 00 29 73 68 65 6c 6c 69 65 73 2f 73 68 65 6c 6c 79 73 0-.)shellies/shellys
2019-08-10 10:36:03.963 (shelly) 77 69 74 63 68 2d 33 32 42 46 38 37 2f 72 6f 6c 6c 65 72 2f witch-32BF87/roller/
2019-08-10 10:36:03.963 (shelly) 30 2f 70 6f 73 2d 31 .. .. .. .. .. .. .. .. .. .. .. .. .. 0/pos-1
2019-08-10 10:36:03.963 (shelly) Received 46 bytes of data
2019-08-10 10:36:03.963 (shelly) 30 2c 00 25 73 68 65 6c 6c 69 65 73 2f 73 68 65 6c 6c 79 73 0,.%shellies/shellys
2019-08-10 10:36:03.963 (shelly) 77 69 74 63 68 2d 33 32 42 46 38 37 2f 72 6f 6c 6c 65 72 2f witch-32BF87/roller/
2019-08-10 10:36:03.963 (shelly) 30 63 6c 6f 73 65 .. .. .. .. .. .. .. .. .. .. .. .. .. .. 0close
2019-08-10 10:36:03.963 (shelly) MQTT message: shellies/shellyswitch-32BF87/roller/0/pos -1
2019-08-10 10:36:03.963 (shelly) 0:1 0:101
2019-08-10 10:36:03.963 (shelly - shellyswitch-32BF87-0-pos) Updating device from 0:'0' to have values 1:'101'.
2019-08-10 10:36:03.968 (shelly) MQTT message: shellies/shellyswitch-32BF87/roller/0 close
2019-08-10 10:36:03.968 (shelly - shellyswitch-32BF87-0-roller) Updating device from 17:'Stop' to have values 1:'On'.
2019-08-10 10:36:03.690 Status: User: Admin initiated a switch command (86/shelly - shellyswitch-32BF87-0-roller/Off)
2019-08-10 10:36:03.970 Status: LUA: Device based event fired on 'shelly - shellyswitch-32BF87-0-pos', value 'Closed'
2019-08-10 10:36:03.971 Status: LUA: Device based event fired on 'shelly - shellyswitch-32BF87-0-roller', value 'On'

Domoticz

Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT

Re: Python Plugin: Shelly MQTT