MrBill

I've never tried from my iPad until now, but I can confirm this behavior. Also hold true using Firefox and Chrome on iOS.

hmmm I wonder why you have to do that? Are they old switches? I don't have issues that require me to intervene after a power failure. But yes, you can set backlight in a program too: If you're going to do this at startup I'd add a wait to the top of the program, just to get it away from all the things that happen at startup. For Run at Startup you can leave the If body blank and then after Saving the program, switch to the Summary Tab of Programs, find the program and right click it then pick Run at Startup from right click menu.

I suspect all is well today? Amazon had a major AWS failure yesterday. They resolved the incident this morning at 4AM PST. Most of Alexa worked yesterday but things that didn't all seemed to revolve around Streaming, and API calls to other related services.

Backlight is what you're looking for. You need to set the value and then click the button to the left or click the word "backlight" itself. There's also a minor GUI bug when you select the next device it will claim it's at whatever you set for the last device... just click the "backlight" button if you want to set it to the same thing.

AWS is having a bad day. Many of Alexa's services aren't working today. Started about 8AM PST, didn't get declared a major event until about 10AM PST. Many services are finally starting to go back to green, a couple of hours ago the status page looked about double worse.

There's a number of threads. click here for a google search limited to this forum.

Are you are pushing the "Save" button at the bottom of the Network Settings box before rebooting?

I'm not sure if you caught in my post: disable the skill using the app, then re-enable the skill using the Alexa web interface and not the app. For some unknown reason that caused something different to happen than when my son disabled then re-enabled using the app only.

I agree. I've almost ridded myself with Feit, when I started changing to LED circa 2013 that was actually the best choice in terms of price/performance. Today I only purchase Phillips Warm Glow for white colored light bulbs. (and a few Phillips Hue where we actually wanted color.)

For replacing two of your remotes you will want to use Replace Device, which in effect just changes the address of the devices in question. The step by step instructions in the wiki are here: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing_a_Device Two things to note: As mentioned in the instructions you can't have the devices in a folder they must be at the root level. Second, your working with battery devices so you'll have the extra step of needing both devices to be in linking mode. Essentionally on a high level: add the new device to the ISY using new Insteon device, then stop don't add it to scenes or programs. Now use the Replacing a Device instructions, when that's complete your new device address will have replaced the old. You won't need to update any scenes or programs.

Different Skill in play, but my son uses an Insteon Hub rather than an ISY at his house. I don't remember the exact issue he was having but it was a bit weird and partial. I suggested disabling the skill and logging back in which he did and it didn't help. The next day he got a callback from Insteon Support... they told him to disable skill from the Alexa app... then switch to a computer and full browser and log into the Alexa web interface at https://alexa.amazon.com and re-enable the skill from there. That in fact solved the issue. (he doesn't have the same technical mind I do, so he didn't as why that worked, I wish I knew what the difference was tho...)

As I mentioned your path of least resistance is upgrade to 5.x on the ISY, convert any remaining climate module subscription to ISY portal subscription and use the polyglot cloud nodesevers. Unfortunately in all cases you or someone will have to tweak the programs using climate data to obtain it from a new source. If you're already a portal subscriber you're just that much closer, in that case just get the ISY upgraded, and start using one of the cloud node servers, and tweak your programs. Does your current system use Z-wave? do you see Z-wave as an option on the top row of the admin console? If so based on the fact that you're using v4.x ISY firmware that likely means you have a 300 series z-wave board. In that case Z-wave > Advanced > Z-wave Version will return Zwave version 4.55.... If it does say 6.81 that means you already have a newer z-wave board. As far as just writing a check, I know UDI offers remote programming, you'd have to contact them for an estimate. There may or may not be other forum members that might take on a paid project.

Back last February it was announced the climate module was being Sunset'd : https://www.universal-devices.com/byebyeclimatemodule/ The deadline was extended several times and it didn't actually go offline until sometime over the summer. There were also emails sent, although I can't give details of such. The replacement is via nodeservers, and there are in fact quite a number of weather/climate related nodeservers to choose from. It does require upgrading to the 5.x firmware branch. From there with a portal subscription there are several weather related nodeservers that can be run from Polyglot cloud, or via a local raspberry pi, or a local Polisy device. Polisy is available for purchase from UDI and will someday also be your ISY. Right now you have 3 options for climate data, I would not recommend the raspberry pi option unless you already have one, know how to use it, and are ready to install polyglot.... the reason to steer away tho is it appears newest unreleased Polyglot version 3 won't run on a raspberry pi. At one point, and I assume they still are, UDI was giving credit for the climate module based on when it was purchased towards a portal subscription. That's probably your path of least resistance at this point. No additional hardware needed just nodeservers running in UDI's cloud space. ((It should also be noted: How far you should upgrade in the 5.x firmware branch also depends on if you have an older 300 series z-wave dongle. Everyone can use v5.0.16c, or v5.3 requires that a 500 series z-wave board or no z-wave board be installed, in other words 300 series boards are no longer supported past v5.0.16c. Upgrade from 4.x to 5.x usually requires some manual intervention, some people like myself had minimal adjusts to make, a few people report it was alot of work... there are threads here that review these things.))

Question, is that true when including an INTEGER variable? Would it not need to be a STATE variable changing to cause the program to trigger? Using in integer variable in combination with AND (as OP has done) can have logical usage, however using integer variables alone of in conjunction with OR don't seem to have value in an IF statement. I'm guessing on OP's variable naming convention that it's an integer variable, but that is not stated and I'm in fact guessing.

They're just variables set to 0 and 1, makes code reading easier. I used to do it, but now I tend have a lot of Flags rather than just true/false... like my away mode for example is no longer just false or true, instead -1=Off without Auto enable, 0= Off with auto enable, 1=On, with auto disable, 2=On won't auto disable.

I ended up with the second so I could delay it a few seconds. I once a problem where too many things ran at "sunset" and created the dreaded queue full errors in the error log, and ever since I've always tried to be aware of spacing things just slightly. this is a great set of programs!

I'm implementing this. I don't have much that gets confused, but I do have some heartbeats, an uptime timer, and a few other run time timers that appear to get thrown off. Great idea. I wonder which technique is best for restarting heartbeats, including the full list as run program ____ (then) or just including 'if $sDST_Alert = $cTrue' in the If body of each heartbeat program? Or even yet another "restart heartbeat" program that adds a few seconds of time between the restarts? (I have like 18 heartbeat programs but actually need to add a few more too). It seems like this would also make a great nodeserver, or addition to one of the existing dealing with holidays or sun-data.

Yep that's it. Try the Query, Re-discover buttons at the bottom of that page... it should be populated.

It's a node in the admin console named "ISY Inventory". If the admin console was open when you installed the nodeserver close it and reopen.

it appears you can do so on this page: https://www.universal-devices.com/my-account/

Z-Wave does waste some nodes.... I seem to remember that you have a Polisy, if so add the ISY Inventory nodeserver. then Compare the totals to this chart which shows max nodes of 254 and max programs of 300 for the non-pro ISY versions. As others have mentioned to upgrade to pro just purchase the upgrade thought the admin console/UDI website... the upgrade is instant.

If you mean a portal account at https://my.isy.io and log in. Once logged in look for "My Profile" in the top left corner and click it. There you can change your login email address.

As has been noted you need to post the program. The easy way to do that is right click the program in the program tree and select Copy to Clipboard, then you can simply paste it into a reply.

support@universal-devices.com Include your UUID# with your portal userid.

If button B is the controller for a scene, include button C as a responder and set it to off for scene B. Not this just sets the button to Off, it doesn't set scene C off. Likewise for the scene that button C is the controller include Button B and set the button to off. yep... i was typing as you were.