Maybe I was unclear. I have this installed on my HE "Server":
HubConnect-Server.groovy -- App Code
HubConnect-Server-Instance.groovy -- App Code
HubConnect-Remote-Hub.groovy -- Driver Code
On ST, I have the following installed:
HubConnect-Remote-Client.groovy -- ST SmartApp
Prior to the update this morning, everything worked. Now, I am getting the error described in my earlier post and devices are not showing in HE at all.
I think I'm making progress. I was able to successfully add a custom driver. It took a complete remove/re-install though. No amount of clicking done before re-installing worked/helped.
OK. Now... For attributes all I have selected is "thermostat" as attribute 1.
Q: Do I need to manually enter all thermostat attributes (coolingSetpoint, heatingSetpoint, temperature, etc) in attributes 2-8, or do those come along for free with attribute #1?
I completely uninstalled the app and resinstalled. I am not getting the error described earlier.
However, I am not getting any of the devices from ST to show up in HE at all. It has been almost 10 minutes since install.
I have two devices I am testing. Ring Doorbell Pro and ST Presence Sensor. Both devices have the Universal drivers in the HE drivers code. As info, both showed up in HE devices prior to the 1.1 update.
I am seeing the following in the logs: [trace](http://192.168.86.5/installedapp/configure/829)Received ping from ST V3.
ST V3 is the name of my ST hub in your app. It appears to be communicating and shows Online in the App menu.
Anything else to try?
UPDATE:
It appears that when I connect to HE HubCOnnect Server from ST, it is not creating the driver in HE for HubConnect.
It also appears that HubConnect is not properly installing the generic driver in HE for the ST devices. For example, my Ring Doorbell just tried to send an event to HE and received the following warning:
[warn](http://192.168.86.5/installedapp/configure/829)Ignoring Received event from ST V3: Device Not Found!
However, the HubConnect-Ring-Doorbell.groovy driver is installed in HE drivers code.
You can certainly press it as many times as you want It's grabbing what the "real device" knows.. I've had real devices add attributes over time.. I have a recessed door sensor that has a tamper switch.. but it did not expose that til I caused a tamper event. A sync before is not going to know MORE than the device itself.
Sigh .... If the Thermostat setting in attribute slot #1 doesn't actually transfer anything automatically, then I don't have enough attribute fields to get what I need. There are 8 attributes I need.
@srwhite Any possibility of getting a few more attribute slots on custom drivers?
Or make the "thermostat" attribute pull across one of them by default - like temperature?
I really need all 7 standard thermostat attributes PLUS one more - 8 total.
I have a ST Arrival Sensor V4. Also, a Ring Doorbell Pro. Both generic drivers are in the HE drivers code section.
Here's the deal. Prior to the update this morning to Version 1.1, it worked perfectly. Something in 1.1 seems to have broken the ST to HE process.At least for these two devices.
I'm getting an "unsubscribe" error at line 291 in ST when I tried to remove something and save it:
groovy.lang.MissingMethodException: No signature of method: script_app_12345averylongstringofcharactersandnumbers12345.unsubscribe() is applicable for argument types:
(physicalgraph.app.DeviceWrapperList, java.lang.String, java.lang.String) values: [[Bedroom TV Iris (ZBr), Crawlspace Plug (ZBr), Entry Closet (ZBr), ...], ...]
Possible solutions: unsubscribe(), unsubscribe(java.lang.String), subscribe(physicalgraph.app.InstalledSmartAppWrapper, java.lang.String, java.lang.String), subscribe(physicalgraph.app.DeviceWrapper, java.lang.String, java.lang.String), subscribe(java.util.Collection, java.lang.String, java.lang.String), subscribe(physicalgraph.app.HubWrapper, java.lang.String, java.lang.String) @line 291 (subscribeLocalEvents)
Any idea what thats about? I have seen things show up from Hubitat on ST, but not the reverse (pretty sure I did something out of order, so I'm not too worried about it - might start over later)
Custom thermostat driver just doesn't seem to work 100%. Attributes that are specified don't seem to show up in Current States. Numbers come across, enumerations/text don't seem to (at least not reliably).
And I have debug logging turned on at both ends, nothing in the logs. I see EVENTS on the replicated device for some parameters (like "thermostatFanState" mentioned below), but there is no Current State for it... don't know why.
For instance, I bring across the attribute "thermostatFanState".
Here it is on the actual device:
Notice no "thermostatFanState" on the replicated device (note, thermostatOperatingMode wasn't there either until I hit sync, but it doesn't actually update automatically):