How to configure everything

Can you post a screen grab of MQTT Explorer showing the homie node with all sub-nodes expanded?
I will then more likley be able to see why the device isn't being detected.

I am in the eprocess of doing some major design changes to the plugin. I am also working with Kevin (Hubitat MQTT App author) to get the plugin and his MQTT App working better together. More detailed documentation will follow once that is complete.

Here a screenshot, but I did not expanded all the nodes (do not fit in the screen )
If you need something in particular let me know.

Hi Marco,

Here a screenshot, but I did not expanded all the nodes (do not fit in the screen )
If you need something in particular let me know.

I was actually replying to the @mclass post above as I need to figure out why @mclass can't see the device.

Support for colour bulbs is in the process of being further refined and will be availble in the next major release.

Color bulbs are working nicely to be honest.
What would it be nice is the ramp control

Wow! That was quick, thanks!

Can you post a screen grab of MQTT Explorer showing the homie node with all sub-nodes expanded?
I will then more likley be able to see why the device isn't being detected.

Screen grab attached. I have not fully expanded the Sonos device, as it's the Aeotec Smart 6 test device ("Aeotec") I've been concentrating on.

Thanks again for being so responsive.

mclass

Hi @mclass,
Thanks for the screengrab

Looking at the $properties, they seem to have a space after the commas which is what I think is throwing the plugin?

The easiest thing to do is to:

1. Update the $properties in MQTT Explorer by publishing a topic of homie/qualia/aeotec/$properties with a payload of measure-voltage,measure-power,measure-energy,onoff - Note the removal of dim which isn't appropriate for an outlet
2. Once you have done, reload the plugin and try again.

I will make a change in the plugin in due course to handle the spaces.

Looking at the $properties, they seem to have a space after the commas which is what I think is throwing the plugin?

There are no discernible (to me!) spaces after the commas. However I did what you suggested to no avail

This is the log with debug logging on during restart of the plugin:

Code: Select all

================================================== Initialising Hubitat Plugin ===================================================
Plugin Name:                    Hubitat Bridge
Plugin Version:                 0.5.14
Plugin ID:                      com.autologplugin.indigoplugin.hubitat
Indigo Version:                 2021.2.0
Indigo License:                 ActiveSubscription
Indigo API Version:             2.6
Python Version:                 2.7.16 (default, Jan 26 2020, 23:50:38) [GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.31)]
Mac OS Version:                 10.13.6
==================================================================================================================================

   Hubitat Bridge                  Logging to Indigo Event Log at the 'Debugging' level
   Hubitat Bridge                  Logging to Plugin Event Log at the 'Debugging' level
   Hubitat Bridge Warning          MQTT Topic Filtering active for the following Hubitat device(s):
                        Hubitat Device: 'Qualia | hub'

   Started plugin "Hubitat Bridge 0.5.14"
   Hubitat Bridge Debug            getDeviceStateList invoked for 'Qualia'
   Hubitat Bridge Debug            State List [Amended]: States : (list)
     Item : (dict)
          Disabled : false (bool)
          Key : heartbeat (string)
          StateLabel : MQTT Heartbeat (string)
          TriggerLabel : MQTT Heartbeat changed (string)
          Type : 100 (integer)
     Item : (dict)
          Disabled : false (bool)
          Key : lastPayload (string)
          StateLabel : Last Payload (string)
          TriggerLabel : Last Payload changed (string)
          Type : 150 (integer)
     Item : (dict)
          Disabled : false (bool)
          Key : lastTopic (string)
          StateLabel : Last Topic (string)
          TriggerLabel : Last Topic changed (string)
          Type : 150 (integer)
     Item : (dict)
          Disabled : false (bool)
          Key : status (string)
          StateLabel : Status (string)
          TriggerLabel : Status changed (string)
          Type : 150 (integer)
   Hubitat Bridge Debug            MQTT CLIENT ID: HOMIE-INDIGO-HUBITAT-QUALIA
   Hubitat Bridge Debug            Debugging Hub Handler Thread
   Hubitat Bridge                  Device 'Qualia' Started
   Hubitat Bridge Debug            Hub Handler Thread initialised for 'Qualia'
   Hubitat Bridge Debug            HE-HUB Details:/n{39: 1343082442, 12: {}, 16: <threading._Event object at 0x107bb7950>, 18: u'10.10.15.207', 19: 1883, 20: None, 21: u'HOMIE-INDIGO-HUBITAT-QUALIA', 22: False, 23: 0, 24: u'homie/Qualia/#', 25: <ThreadHubHandler(Thread-1, started 123145371770880)>, 31: []}
   Hubitat Bridge Debug            Autolog Hubitat Hub Qualia now started


What is mystifying me is that despite the Hubitat plugin "HE Hub device" showing connected, the other custom states are vacant (see screen shot 1). If, however, I subscribe to the "homie" topic in the MQTT Connector app, these states are reflected (see screen shot 2). This would suggest that the Hubitat Indigo plugin is not subscribing to the homie topic?

Any suggestions at this stage would be welcome!!

mclass

Change the device driver in Hubitat to Generic zwave switch or smart switch, tick the boxes in MQTT app and see if that works as I cannot understand why you are getting a “$type = shade “ for a smart switch. It should be “$type = sensor”.

Hi @mclass,

I have spent sometime this afternoon trying to recreate and resolve the issue you are experiencing, so far without success.

I setup topics in MQTT Explorer, like this:

mclass_aeotec_mqtt_explorer.png (160.14 KiB) Viewed 2919 times

I setup all topics as retained with a QOS of 1.

I then setup a Hub based on qualia and then went to add a device and can do so successfully:

mclass_aeotec_indigo_device.png (352.91 KiB) Viewed 2919 times

So, your definitions seem to work on my system.

I am beginning to clutch at straws, but here are some things I would check:

• make sure the qualia name in the Indigo Hub settings is in lowercase
• make sure that topics listed in MQTT Explorer show as retained (see image). You can normally test this by quitting MQTT Explorer and then launching MQTT Explorer again to check everything is still there and hasn't disappeared.
• In HE make sure that in the MQTT App > MQTT Publish Formats that Complete & compliant homie topics is on

I am obviously missing something in your mix but can't put my finger on it at the moment.

I am currently doing some major changes to the plugin but once these are relatively stable, I can PM you a link to the revised plugin for you to try. It will be a few days yet before I finish these changes.

Bingo!!

make sure the qualia name in the Indigo Hub settings is in lowercase

It was that "undocumented feature" requiring a lower case "q" that trapped me - together with a minimal understanding of MQTT!!

Many thanks for your patience and tolerance - and even more thanks for the plugin!!

mclass

Very good news to hear you have got it working.

I will update the next version of the plugin to ensure lower-case is enforced.
It's something I should have done for the current version.

Hey Hubitat users, advice requested. It feels like something is wrong with the MQTT Broker or the Hubitat MQTT App, but I can't get a connection between the two platforms. Appreciate any thoughts, thanks.

- Installed Hubitat Hub - check
- installed (and enabled) MQTT app and drivers - check
- installed Mosquitto via Brew on Indigo MacOS platform - check
- tested Mosquitto MQTT messaging (locally) - check
- modified Mosquitto.conf - listener 1883 0.0.0.0 [and] allow_anonymous true - check
- disabled firewall on Indigo MacOS - check
- installed Hubitat Indigo plugin - check
- created Mosquitto Broker in Indigo, and status is connected - check
- created Hubitat Hub in Indigo, and status is disconnected - fail

Hi @7rdr7,

I think I have information overload!

Can I suggest that you use the App MQTT Explorer to see what is being published to the MQTT broker.
Note that you can also get this App from the Mac App Store.

Have you selected the devices to publish in the MQTT App.

What version of the Hubitat MQTT App are you running?

Apologies for the overload

I figured that I was just missing something obvious, and I was......

Opened MQTT Explorer and noticed immediately that the MQTT app had converted underscores to dashes..... change them all to dashes, and everything works.

Thanks Jon!

No problem with theoverload - better to have too much info, than too little.

Pleased to hear it is now working OK for you.