ndfan77

The Production Store version (3.15) doesn't have a pre-defined configuration setting for API key. Is it a custom configuration parameter we can enter if we know the right text to use for the key? Or does the Non-production Store version (dated today) have API key as a new configuration parameter?

FWIW -- My Ecobee HA HomeKit integration doesn't allow setting fan hold duration when overriding a preset, unless I'm seriously missing something. It always uses "Until the next scheduled activity". This doesn't work for my use case. I need to set fan hold with a duration of "Until I change it". If the HA HomeKit integration actually let me set hold durations properly I'd be using it right now. @Jimbo.Automates: do you still think you could resuscitate the existing plugin with reduced polling if you had access to a different Ecobee API key?

FWIW, I just spent some time talking with Ecobee tech support and politely but firmly let them know this particular customer wasn't very happy with how they handled this (and that I wasn't the only one).

Not using forecasts here. Wouldn't miss it. (But certainly do miss not being able to control the thermostat!) If Ecobee is incurring a cost to provide the forecast, I could understand their position, but otherwise, this seems pretty boneheaded on their part. If forecasts is the main issue, and if it can be enabled/disabled on Ecobee's end for each key, then maybe split the plug-in up into two versions. One with forecasts that has a higher or recurring cost, and one without that just supports device control. But like others have said, this may get me looking at other thermostats.

The Home Assistant integration with my Ecobee seems to still be working fine. I sure hope Ecobee recognizes the significant value add from supporting integration with other home automation platforms! After you log into Ecobee, click the user profile icon (top right) and then click My Apps. You should have an app named "UDI Polyglot (PIN)" registered in the list.

An issue for this has been opened on Github, but I'm not holding my breath. The last time the author posted any activity on Github was the start of June in last year.

And here. Is Jimbo still listening??

I have the same problem too. Seems like maybe the refresh instructions should be public. (So everyone with this problem doesn't have to submit a ticket and wait!)

Ah, and so it does. Thanks!

I'm trying to setup a Caddy reverse proxy (which does automatic certificates) in front Polyglot. What's the right/supported method to configure Polyglot to use http instead of https? TIA...

I might be missing something, but I'd like my mini remote to toggle the *current* state of a scene (not toggle whatever state the mini controller last sent). From what I can tell, the mini remote has three modes: 4 button (the two buttons in each row act as absolute on or off -- which seems like a waste of a button). 8 button -- toggle (sends codes that are opposite whatever state the mini remote last issued -- which may not coincide with the state the scene is actually in) 8 button (always send the on code, which won't work to turn off a scene when directly linked as a controller) So how do you get a single button on a mini remote to toggle the *current* state of the scene? Say for instance, I have some backyard floods already controlled by an on/off switch, and a button on a 8-button dimmer. If the flood light has been turned on by the 8-button dimmer, how do I toggle them off with a button on the mini-remote (or vice-versa) reliably with just one button push? Seems like this has to be done with an ISY994i program (in order to know real time status of the scene), because when the mini remote is a controller for a scene it has no way to know what has happened to the scene other than whatever codes it has sent -- which may not be accurate when other devices are also controllers, right? Or am I missing something? Thanks in advance!

Is this still the case?

Wouldn't the net effect of that logic be to only send one notification (after the first 25 hour period expired without a heartbeat), but then nothing more after another 25 hours, etc. ? And, also, isn't it dependent on the heartbeat firing at least once to start the 25 hour wait? I switched to a "two-part" approach. Instead of the two lines above in the "Then" section I'm simply resetting a watchdog variable ($Int_1), and then using another program (Leak Sensor HB Monitor) that has the Run at Startup flag set and runs continuously (incrementing the watchdog variable every hour; if it exceeds 26 send a notification, reset the variable, wait an hour, and start over; otherwise increment the variable, wait an hour, and start over): Program: Leak Sensor Heartbeat If Control 'Leak Sensor-Heartbeat' is switched On Or Control 'Leak Sensor-Heartbeat' is switched Off Then $Int_1 = 0 Else - No Actions - (To add one, press 'Action') Program: Leak Sensor HB Monitor If $Int_1 > 26 Then $Int_1 = 0 Send Notification to 'HeartbeatMissing' Wait 1 hour Run Program 'Leak Sensor HB Monitor' (If) Else $Int_1 += 1 Wait 1 hour Run Program 'Leak Sensor HB Monitor' (If)