Recent content by 123

  I'm still using Premise as well but together with Home Assistant which now handles most of the automation chores as well as the frontend. The two communicate via MQTT.   I use Premise to control two "legacy" devices via native drivers and custom modules that I created a long time ago:  ...

???   It publishes (sends) and subscribes (receives).   Example:   If KitchenLight's PowerState changes from true to false, a payload of 0 is published to: premise/home/kitchenlight/powerstate   It is also subscribed to: premise/command/kitchenlight/powerstate   So if I publish a payload...

  FWIW, the standard model is a subset of the Pro model. They basically do the same thing with the key difference being the Pro version provides a Telnet interface. That's what allows third-party software to access it locally.  ...

  Quite the avid endorsement. How many ELK integrations did you research to arrive at this glowing conclusion?     ELK integrations have been around for over ten years. I can state that with confidence because I developed one for Premise a decade ago. It supports: Areas Zones Outputs PLC...

  Sorry but I don't know.    You want to write code for MiniBroker that subscribes to an MQTT topic. Effectively, you want to use an MQTT Client service but Premise doesn't have one.   Even SyseventBroker isn't an MQTT Client. It farms out that function to Node-Red. The two communicate via a TCP...

  I'm using Home Assistant to generate a UI.   For example, I have the following light in Premise: Home.House.First.Foyer.FoyerLight   In Home Assistant, I define an MQTT Light:   - platform: mqtt     name: "Foyer"         state_topic: "premise/home/house/first/foyer/foyerlight/powerstate"    ...

@pete_c   In state_topic you have a leading slash: state_topic: "/GarageDoor1/SENSOR"   whereas later you show the topic used in MQTT Explorer does not have a leading slash:  

Go to Devices > CustomDevices > Syseventbroker, scroll to the very bottom of the Properties pane, and there you'll find a section called ExportOpenHAB. Click Reset first and then check the contents of the section above called ExportParameters. This is where it identifies the host name of your...

  Whatever I said that gave you that impression, it wasn't my intention. It's entirely possible to create an attractive UI with openHAB's HABpanel (see examples here). Mapping a widget's elements in HABpanel is no more onerous than in Home Remote. Both lack complex abstractions so you'll be...

  Yes, I used it for awhile almost a year ago (discussed its use here: A fresh new face for Premise).   Based on my experiences at the time, the developer provided excellent support and frequent product updates. The reason why I abandoned it is because even creating a basic UI requires a fair...

  I checked out the docs for ELK M1 integration. Without a doubt, Hubitat rules supreme … in installation complexity; that's a lot of individual copy/paste steps to get full ELK M1 functionality. I think that aspect could use some streamlining.    Where's the list of supported devices and...

Our household has been using VOIP service for about 8 years now. We use voip.ms and have no complaints; service is top-notch. We use the cheapest plan (pay as you go) and, based on our rather limited usage of it, it ends up costing about $11/month. VOIP interface is an Obihai Obi110 and we have...

The article about Lifx is dated February 2019 and, at its very end, it states the security flaw was corrected. The other article mentions bulbs that can be controlled via IR. I'm not aware of any IR control for Lifx bulbs (nor Philips Hue). It uses Wi-Fi (and the other uses ZigBee). FWIW, I...

You're welcome!     A few thoughts: Home Assistant's scripts provide more flexibility than its scenes. The same is true for Premise. A scene is strictly 'set this thing to on, this other thing to 50%, yet another to off, etc' whereas a script also allows you to do some conditional logic (if this...

Pete,   With all due respect, this thread is about using MQTT with Premise. Your question is about Omnistat/Omnilink/climate integration is off-topic (and there's a dedicated thread for it elsewhere … where you are currently participating). I don't own an Omni panel nor use the Omnilink...