Weather - Look at developing built-In integrations for local weather stations and sensors, such as EcoWitt and others that offer local comm's
Lighting - Supporting Philips Hue push notifications in the built-in integration, like in Coco-Hue and Advanced Hue Bridge Integration
Energy - Start to expand into the energy space, interfacing with services / systems such as Solar and other energy monitoring systems. Of particular interest to me is Solar Edge. Admittedly a cloud service....
Home Automation Platforms - Develop a built-In integration with Home Assistant, building on the success of integrating with Apple Homekit
Obviously I would also like the UI enhancements many have requested as well, including expanding the capabilities of HE dashboards..... Just still allow CSS and other tweaks that we have so carefully crafted
If you want to develop a Mitsubishi Thermostat integration, that would also be good,
UI jumping around when selecting apps or devices... Keep me in the same spot in the drop down list as I make app & device selections, and don't let the drop-down jump around the screen as the text length changes
Can't select an app or device as a filter and then click Show more to show additional log entries
--
I'd like to be able to map a virtual motion sensor, contact, switch created in Hubitat to an MQTT topic to bring external devices in. I'm currently doing this with the only community MQTT app I can find, but it's in beta and was broken some time ago following a platform update. Most MQTT apps seem to be designed to publish Hubitat devices events for use elsewhere but I want the opposite. I think my only option at the moment is Node-Red but despite reading several threads I remain confused as to what I need for that (I can easily put Node-red on my Pi but what do I need to add in Hubitat?)
Create Hubitat virtual devices with the capabilities/attributes that your real device has - going to assume you have already brought your real device into Node-RED.
I briefly had it working for a single device, but I had the full path mapped in the topic. That means if I continue that way it'll be a complete mess as I'll have to create multiple instances of the MQTT link (as opposed to having one link and everything going through one Switch.
Could you possibly screenshot the config of your switch in that flow? I realise that the topic path will be completely different to mine. I'm just struggling to work out how much of the topic path to enter in 'Property' and what to use as the comparison beneath it.
There is no reason you can't have one link and one Switch. It if gets out of line, you can use Link Nodes. I have one node listening to my Alexas and use that method to keep the flows "clean".
You haven't said what kind of devices you have that are sending MQTT messages but mine are simply sending their ID; not status of off; on; LWT; etc.
That's a ST "new app" feature that I never used ... and I still can't think of a circumstance where that makes sense to me in anything I personally do on a day-to-day basis.
I can think back to my time on ST, where I used it mostly as a remote control and not an automation platform. I don't use an app or a dashboard with my day-to-day interaction with my smart home anymore. I automate it instead.
E.g., I enter a room; the lights go on. I leave the room; 2 minutes later the lights go out. I open a door; the lights go on. I close the door; the lights go out.
Yes, it is working for me again - as of 2.3.4.something changed and I have found Smartley to work as it did before. However, a few reported still having issues. Not sure why...
