Was a ticket opened for the broken URL processing.
I haven't opened a ticket about it since the page was marked "beta" in 1.5.408 I assumed (perhaps incorrectly) that the problem was obvious and would be fixed in a later firmware release. I have an open issue on this here:
https://github.com/watou/vera-nest-thermostat/issues/17For the second one, I have attached another png - the 2F device has no Fan wire. The Fan state for the 1F device is accurate. Not sure I understand what you mean by "currently accurate representation", I do understand that controls in Devices view are not real time but I think that's not what you mean.
For your 2F device, the plugin is probably not accounting for a system where there is no fan. (I added
https://github.com/watou/vera-nest-thermostat/issues/24 to remind me to include the fix in the v1.2 release.) Since I can't test that configuration here, I will scan the code to see if there is a proper way to detect that configuration in the JSON payload I get back, and at least not show the fan as being in either Auto or On mode. As for hiding the Fan label and Auto and On buttons, that was the ticket I had opened about selectively hiding dashboard controls based on device state, and got back a less than actionable response. I can hide controls using the
Commands variable from the HaDevice1 service type (a comma-separated list of control codes found in the .json file), but the controls will not correctly track the device configuration, leading to even more confusion. As in, setting the Commands variable to a different list of control IDs is not reflected in the UI until the UI is manually reloaded.
If you wanted to hide the fan Auto and On buttons yourself for the 2F thermostat device, you could add the
Commands variable to that device like this on the Advanced tab, and then reload the UI:
New service: urn:micasaverde-com:serviceId:HaDevice1
New variable: Commands
New value: hvac_off,hvac_auto,hvac_cool,hvac_heat,heating_setpoint,cooling_setpoint,hvac_state(The above value omitted the fan_auto and fan_on control codes, so that they won't be shown, but the "Fan" text label will still be there.)
Also, it seems very odd to me that your HOME and Nest devices show the correct icons but your thermostat and humidistat devices have the generic icons. I've never seen that before. Is there anything "non-standard" about how you access the UI, and what is your firmware, etc.? I would love to understand what's going on there.
watou