Releases, Bugs, Issues, Requests

P.S. Do you prefer we request additions to the MQTT plugins directly through GitHub or should we initiate them on the forum first?

If it's a simple bug report or enhancement request, just put it in GitHub. I think the forums are best suited for Q&A type stuff. Sometimes a question leads to a bug or an enhancement, so if there's any doubt, go ahead and post it here.

Release 0.2.0 - OpenDXL support

https://github.com/FlyingDiver/Indigo-M ... /tag/0.2.0

Now supports OpenDXL Brokers. DXL is a off-shoot of MQTT.

https://www.opendxl.com

OpenDXL is an initiative to create adaptive systems of interconnected services that communicate and share information for real-time, accurate security decisions and actions.

Just installed the latest version from the Plugin Store and got this error:

1 Oct 2019 at 12:22:39
Stopping plugin MQTT Connector (pid 31524)
MQTT Connector Flying Diver MQTT: Stopping Device
MQTT Connector Shutting down MQTT
Stopped plugin MQTT Connector
Upgrading plugin MQTT Connector to newer version 0.2.0 (previous version moved to trash)
Loading plugin "MQTT Connector 0.2.0"
Starting plugin "MQTT Connector 0.2.0" (pid 37358)
MQTT Connector Error Error in plugin execution InitializeMain:

Traceback (most recent call last):
File "plugin.py", line 17, in <module>
File "/Library/Application Support/Perceptive Automation/Indigo 7.4/Plugins/MQTT Connector.indigoPlugin/Contents/Server Plugin/dxl_broker.py", line 9, in <module>
ImportError: No module named dxlclient.client

Stopping plugin "MQTT Connector 0.2.0" (pid 37358)
Stopped plugin "MQTT Connector 0.2.0"

I am not using OpenDXL but just wanted to update to the latest version as it was showing update available in the plugin store in the Indigo 7.4 Plugins Menu.

I am not using OpenDXL but just wanted to update to the latest version as it was showing update available in the plugin store in the Indigo 7.4 Plugins Menu.

Huh. Shouldn't do that unless you try to create a DXL device. I'll look into that today.

Joe

Fixed in 0.2.1 (I hope). Now available.

Fixed in 0.2.1 (I hope). Now available.

Yes - just installed 0.2.1 and it is working fine - thanks for the quick fix.

MQTT Shims - Release 0.1.2

Added ability to specify “on” value
Fixed sensor on images
added error checking for Multi-states key.

I had a typo in my Policy. It works now! Yay

Thanks Joe! Can I donate somewhere? You've made my day.

Matt

MQTT Shims plugin updated to 0.2.5 in the Plugin Store. Changes since last store release:

Added support for battery level in Indigo UI.
Added support for Energy and Power usage in Indigo UI.
Added multi-state support to all device types. Fix to allow top-level multi-state dictionary.
Added payload templates for Indigo actions.
Added Generic Shim device for things that aren't really sensors, switches, dimmers, etc. Like keypads.
Added Event triggers for capturing updates to Shim devices when none of the states change. Like a repeated button press on a keypad.

1)

Code: Select all

Traceback (most recent call last):
  File "plugin.py", line 111, in runConcurrentThread
  File "plugin.py", line 136, in processMessages
  File "plugin.py", line 212, in update
AttributeError: type object 'kStateImageSel' has no attribute 'Sensorn'


Changed Line 212 to SensorOn and now OK

2)
Tick the 3 new UI options, battery level, Energy and Power usage and they all appear, untick all 3 and Battery level remains, only the Energy and Power disappear as expected.

1)

Code: Select all

Traceback (most recent call last):
  File "plugin.py", line 111, in runConcurrentThread
  File "plugin.py", line 136, in processMessages
  File "plugin.py", line 212, in update
AttributeError: type object 'kStateImageSel' has no attribute 'Sensorn'


Changed Line 212 to SensorOn and now OK

Fixed for next release.

2)
Tick the 3 new UI options, battery level, Energy and Power usage and they all appear, untick all 3 and Battery level remains, only the Energy and Power disappear as expected.

Cannot reproduce. Worked for all device types I tried it with. What was the specific device type you saw this with?

It was a Shelly 1PM, I thought I was in the Shelly DW and hit the battery tick box.
Just duplicated the Shelly Dimmer and that acts the same and if I untick the Shelly DW battery it still show in the UI even after reloading Shims or Indigo.

It was a Shelly 1PM, I thought I was in the Shelly DW and hit the battery tick box.
Just duplicated the Shelly Dimmer and that acts the same and if I untick the Shelly DW battery it still show in the UI even after reloading Shims or Indigo.

What's the exact sequence of actions again?

It was a Shelly 1PM, I thought I was in the Shelly DW and hit the battery tick box.
Just duplicated the Shelly Dimmer and that acts the same and if I untick the Shelly DW battery it still show in the UI even after reloading Shims or Indigo.

What's the exact sequence of actions again?

Screenshot 2020-02-24 at 17.07.57.png (120.29 KiB) Viewed 2240 times

Screenshot 2020-02-24 at 17.09.27.png (128.53 KiB) Viewed 2240 times

Screenshot 2020-02-24 at 17.10.10.png (115.93 KiB) Viewed 2240 times

D'oh. I thought you said the UI entry field (for the payload key) wasn't going away.

Hmmm.