Look in
Modules > SyseventBroker > Macrosd > MacroFolder. There should be two Macros:
ListSupportedObjects,
ListUnsupportedObjects.
Basically, SyseventBroker doesn't handle MediaZones, Keypads and maybe one other thing I can no longer recall. It also won't handle any custom Home objects (Modules) you may have created (but it's possible to support them).
I may be wrong but the last time I was in touch with etc, he had been working on extending SyseventBroker to include MediaZones.
I can't comment on the issue with MQTT Explorer. After establishing a connection to my MQTT broker, the connection box goes away and displays a list of all topics currently being managed by the broker.
The UI piece is handled by another system of your choosing. All that SyseventBroker does is enable Premise to 'speak MQTT':
If
Home.Kitchen.CeilingLight.PowerState changes to true, Syseventbroker will automatically publish a "1" to this topic:
premise/home/kitchen/ceilinglight/powerstate
If you publish a "0" to:
premise/command/home/kitchen/ceilinglight/powerstate
SyseventBroker will turn off
Home.Kitchen.CeilingLight.PowerState
What you use to subscribe/publish to those two topics is your choice. An MQTT client like MQTT Explorer is adequate for confirming all the 'plumbing' is functional. For day-to-day control via a UI, you'll want something with greater flexibility and better presentation options.
- I started with The Home Remote but eventually abandoned it because I found it laborious to create even a simple UI.
- I then moved to openHAB. It's a full-blown home automation solution but all I wanted was its ability to create a UI. Ultimately, I abandoned it as well because I ran into a few limitations (and it involved more work than I wanted to invest).
- I now use Home Assistant. Like openHAB, it's a complete home automation solution but I largely use it to render a UI for Premise. I also take advantage of the things it offers that aren't available in Premise (and probably never will be) like HomeKit integration (for example, I can use Siri to control my UPB lights).
Home Assistant has a few similarities to Premise including the ability to automatically render a UI widget for a Home object (although in Home Assistant it's called an 'entity'). So what I've done is define a matching Home Assistant entity for each Home object I have in Premise. Each one of these entities communicates via MQTT. The configuration for a light entity would look something like this:
light:
- platform: mqtt
name: "Kitchen"
state_topic: "premise/home/kitchen/powerstate"
command_topic: "premise/command/home/kitchen/powerstate"
brightness_state_topic: "premise/home/kitchen/brightness"
brightness_command_topic: "premise/command/home/kitchen/powerstate"
brightness_scale: 100
payload_on: "1"
payload_off: "0"
That configuration tells Home Assistant to create a light called
light.kitchen, using MQTT, with instructions for both receiving status and sending commands for power and brightness via the appropriate MQTT topics. It also explains how to convert the incoming/outgoing values (Premise SyseventBroker's 1 and 0) to its own format (Home Assistant uses ON and OFF). It also states that the received brightness values use a scale from 0 to 100 (which Home Assistant converts to its own scale of 0 to 255).
Once it creates the entity, it automatically renders a UI widget for it (like in Premise). Unlike Premise, if you don't like the widget's appearance or its placement, you can change it. You can either change it graphically right in the browser (relatively recent enhancement so it currently has some limitations but is always getting better) or by editing a UI configuration file which offers greater freedom. There's a library of standard widgets ('cards') available and an ever-expanding library of custom cards created by the user-community.
Standard cards:
https://www.home-assistant.io/lovelace
