Good to know multi-location installations are working!
Note, at the moment, if you change any of the SmartApp settings, it will re-authenticate and recreate the zone you don’t want, so you would need to delete it again. However I plan to improve this in the future to allow locations/controllers/zones to be explicitly included or excluded.
Regarding mode actions (i.e. off, economy, dayOff, etc), these are applied to a controller, and hence all zones associated with that controller. Therefore, if you apply a mode to your home controller it shouldn’t affect your remote zone, which will be associated with a different controller.
Re hot water zones, I’m making good progress and should have an update in the next few days.
Can someone using David’s code on Android please post post a screenshot of a zone, particularly the big tile at the top. It’s looking very different here on iOS and Android, but I don’t know whether that’s down to something dodgy at my end, or whether it affects all Android versions.
Currently there is a parity issue between Android and iOS platforms in regard to how multiAttribute tiles work. There is currently work being done on the Android platform to address this. In the meantime, some things stated here about multiAttributeTiles may not work as expected on the Android platform.
For the time-being I suggest using type:"generic" on the multiTile for Android users. And changing key: "OPERATING_STATE" to key: "SECONDARY_CONTROL" on the tileAttribute. However the background colour will no longer update based on the operatingState.
Looks like the latest Android App update has fixed the problem of the up and down buttons and humidity icons appearing in the main tile. But I’m not seeing the status line either - although perhaps I messed around with the code! I need to do a refresh against the latest release.
I’m trying to remove this app to have a play with the official one that was released to compare them, but I keep getting the message ‘An expected error has occurred’ whenever I try to remove the SmartApp, or the last heating zone.
@PailOckenden: hint taken. I’ll release an updated version with hot water support and a bunch of other stuff later this week.
@Roy_Donaldson: Failure to remove is usually down to other SmartApps being subscribed to the Evohome devices. The IDE will tell you if anything is using the devices. Note, there is no specific need to remove my SmartApp and devices, they will happily co-exist with the official ones.
I get this error when trying to remove the last zone:
groovy.lang.MissingMethodException: No signature of
method: script1462882558681699476382.removeChildDevices() is applicable
for argument types: (java.util.ArrayList) values: [[Study Heating Zone
(Evohome)]] @ line 105”
I tried to copy/paste the smart app (UK version does not support Github integration) and get following error:
No signature of method: script1462894237356116508522.metadata() is applicable for argument types: (script1462894237356116508522$_run_closure1) values: [script1462894237356116508522$_run_closure1@21b6aa07] Possible solutions: getMetadata(), getState(), setState(java.lang.Object), metaClass(groovy.lang.Closure)
SmartThings is happy to say that we’ve released our Honeywell evohome integration via the Marketplace in the SmartThings app! We apologise for the lengthy wait for this integration! This was due to OAuth stability issues that would cause occasional disconnects, forcing a manual re-authorisation. Honeywell has recently made improvements to their API to correct for this. Please contact SmartThings support if you notice any issues with the Honeywell evohome integration