They're definitely types. Hubitat mostly follows the SmartThings model and they are types there. Also, even though it's not explicitly documented on the Hubitat side yet here is a glimpse from somebody official that this is the case:
If you don't provide a map of maps the single String or array of Strings is considered to be a type(s). You can prove this out by looking at the data types of the parameters passed to commands. For example, if you type it as "NUMBER" the parameter's type is BigInteger instead of String.
Ah OK - I did have a look at a few other custom drivers including the "Echo Speaks" app/drivers and they were just using it as a description, but taken on board for this project
Testing works for me and now been looking into the getConfig output as it lists some quite useful information. As much as I could create a list of commands that one might expect to be used, if for each device and activity we pull the commands available, it will be much more personalised to all users needs.
One thing I've picked up on...
We're using a deprecated method for the websocket https://docs.hubitat.com/index.php?title=Websocket_Interface
However, if we upgraded to the non-deprecated commands, it would rule out people running hubitat pre-2.1.2 when current minimum is 2.0.3.114 (I'm on 2.1.9.115)
Any way to pick which commands based on hubitat version, such that if the commands are dropped in a later release completely, system still works without forcing people on less that 2.1.2 to upgrade?
The deprecated methods and the non-deprecated methods for the websocket from what I remember about a post from Chuck use the same code underneath without any differences. Since we don't have to worry about compilation warnings or even deprecated annotations it's less complicated just to keep using the deprecated location of the client for now. I'm for crossing that bridge later.
My LG OLED TV (for some weird reason I'm still trying to figure out) has been turning on at 3am daily for the last week. I have a rule in Rule Machine that turns on a Harmony Activity when the TV's input changes to that activity's TV input. So as an example. if the TV is manually changed to HDMI4, the rule turns on the Harmony TiVo activity (as a delayed cancelable action after 15s). This way, the Harmony stays in sync even if the TV is controlled through another means. An example of the rule is below and it's worked very well.
Today, the TV came on at 3:02:55am and went to the TiVo input at 3:03:45am (50s even though it normally takes 500ms).
channelName
Tivo
LG TV channelName is Tivo
DEVICE
2020-03-08 03:03:45.650 AM EDT
power
on
LG TV is on
DEVICE
physical
2020-03-08 03:02:55.653 AM EDT
switch
on
LG TV is on
DEVICE
physical
2020-03-08 03:02:55.639 AM EDT
At 3:04:04am, the rule kicked in and turned on my "Living Room TiVo" Logitech Harmony activity.
RM
Triggered
2020-03-08 03:04:05.795 AM EDT
RM
LG TV channelName Tivo
2020-03-08 03:04:05.729 AM EDT
For some weird reason, my Living Room Tivo (child device) actually never turned on though.
switch
on
DEVICE
2020-03-08 01:00:04.388 PM EDT
switch
off
DEVICE
2020-03-07 10:08:23.244 PM EST
However, the parent device (Living Room TV) did turn on without updating the current activity
Activity
Watch Fire TV
DEVICE
2020-03-08 07:05:57.631 AM EDT
switch
on
DEVICE
2020-03-08 03:04:24.675 AM EDT
Activity
PowerOff
DEVICE
2020-03-07 10:08:23.335 PM EST
Please any idea why the parent device would have switched on but the child device didn't? Because it didn't, the parent device's switch was on but the current activity was "PowerOff" which should never be the case.
I have a Harmony Hub Elite with the home automation buttons. I know this [awesome] driver does not support those buttons yet. I migrated from Smarthings and this is the last of the Hubitat unsupported things I have. I am not sure what to do as I do want to use those buttons to control 2 dimmers (and rocker switch) and 2 scenes in Hubitat. What should I do?
Use Hub Connect to mirror scenes/devices from hubitat to smarthings and use the button/ST integration
Use webcore on Hubitat and ST to call a POST API to trigger the scenes? - boo no dimmer/rocker button support
If your lights are Lutron Caseta or Philips Hue, then you could use the Harmony Hub to Lutron/Philips integration directly, bypassing Hubitat and SmartThings altogether.
Yes. Each Harmony Activity will be represented as child “Switch” device within Hubitat. When you press OFF on the remote, the active Activity will turn off. The Parent Device will also be usable to know whether or not any Activity is on, or if they are all off. The Parent Device implements a Switch attribute that represents this. This can easily be used within RM, or any other App that can be triggered by a switch changing states.
Each of your Harmony Activities should have been created as a Switch device, named the same as each activity. If you’re not seeing those, did you add my Child Switch driver per the ReadMe instructions?
Ah! Switch... as I was reading that I realized I had seen them in switches when making another rule. Outstanding. Thank you. Still learning my around.... you guys are an amazing help and doing amazing stuff. This is a game changer for me.
Next step is to try and figure out how to start music off so it’s playing when I walk through the door.
Lots of options for this and most will depend on what speaker devices you have on hand. Off-topic for this thread so if you don't find your answers by using the search functionality start a thread specifically for that purpose. I'm sure there are threads out there about this though. I'm not sure how searchable they are.
So, those home automation buttons. Is it just technically complicated or impossible to get those integrated with Hubitat, or is it that noone has had the time to do it? I don't really want to go through the hassle of setting up Hub Connect just for these buttons...
Also, is there a way for me to activate a certain scene whenever the Pause button is pushed? I don't see how to set a trigger from rule machine?
Great work @ogiewon and @rebecca. This is exactly what I was looking for.
I've known about this for a long time, but haven't felt like messing with the Harmony since I screwed it up previously.
For whatever reason, I need to refresh, give a second delay, and then power on the activities otherwise it's not consistent. Same with power off. But as soon as I add that to my rule, it works without fail on my Aqara 6 button remote. But, it just might be because I put it on hub with the crazy Aeon v1 HEM that I'm still sending reports from at 1 second interval (not doctor recommended).
[Edit] Turns out this was an unrelated issue with the way my Aqara 6 button remote rule was functioning. No refresh or delay required. It's all working as expected with the child devices.
It is technically not possible. This integration uses the webSocket interface to communicate with the Harmony Hub. So, anything that occurs on the Harmony Hub, that results in data being sent out over the webSocket interface, can be 'read' by this integration. Unfortunately, when you press those 'home automation buttons' on the Harmony remote, nothing is sent via webSockets that this integration can receive (unless those buttons are already bound to a device via another existing Harmony Hub integration, like to SmartThings, Lutron Caseta, or Philips Hue.)
Unfortunately, individual button presses are not sent via the webSockets interface. Therefore, there is no way for this integration to be informed when a specific button is pressed to act as a trigger for RM.
Unfortunately Logitech hasn’t accepted any new integrations with harmony for a couple years now, which really limits our options.
But depending on what you want to do when pushing a button, as @ogiewon mentioned, it’s also possible to link a harmony remote to Caseta or hue devices, and probably even trigger an automation in rule machine (if you got creative with the trigger from a linked caseta/hue device).
Here’s the list of currently (and forever?) available harmony cloud-based integrations from the app:
I’m lost as to the reason anyone wanting to control Hue wouldn’t just use the HE Hue Integration?
Also, @JustinL, I don’t personally agree that setting up HubConnect is a “hassle”. The instructions are clear and easy to follow. You just need to take your time and it all just works when you’re done.
This is what most folks have done.
