larryllix

Yawn.

Many want a thermostat that is hard wired to the load for reliability with no wireless anything. However cloud monitoring or minor adjustments via the cloud are fine as along as the basic operation is hard wired.

I just had the same thing with one of five I just "rebuilt". After a power cycle and a closer to the router retry, it linked together OK and now is working well at a larger distance on 5GHz. It seems if certain parts fail the Dot gets hung and only a cold boot will release it from the hang. The only thing I can see of benefit is local weather is available. Of course amazon needs this so you can accidentally enable ordering features and have toilet paper arrive at your door for $40 shipping fees.

Some assumptions are made in the setup that you are on a mobile phone that will automatically reconnect to your house WiFi SSID after the Echo SSID disapears. On my RPi this does NOT happen and I have to manually change the SSID connected to, back and forth while setting these up. I connected my units and ISY Portal to my Canadian Account. What a mess! Turns out amazon.ca and amazon.com accounts are the same accounts and share your shipping addresses. If you have a "default" American shipping address this will never work from a Canadian IP address. I found that selecting English (Canadian) will not allow it to work either and had to return to English (American). Since spokens are used their should not be any real difference. ecobee4 amazon account change is done in the ecobee web app, not on the stat. I spent a lot of time trying to find this. I had to star over with every Amazon device and re-programme them setting up WiFi, geographic addresses individually, and metric selections. All working fine now. I will likely experiment more with switching over to English (Canadian) later. So far V3 seems a lot faster to switch devices on/off even though a delay of up to about 1 seconds is often found before I get the Amazon "OK". Priority of process seems to be given to getting the job done now. Better!

MY IP address was in NY when that happened. The only thing that ever identified me as a Canadian was my google account, when installed on a virgin computer. Once I removed my google account. the Alexa app was accessible again. New: I just attempted to access the V3 skill in the amazon alexa app. Not happening! I get a warning that my language does not match my account. Click continue to correct it to English (Canada). When Continue is clicked, it jumps to the Smart Home page and there is no way to access ANY skills now. Amazon just locked me out of my amazon account access and all further skills I guess Gary's clue will need to be followed (thanks). I will have to open a Canadian amazon.ca account and try it. After all, these cloud services are only about selling people something anyway.

When I first bought my Dots and picked them up in NY I registered and account with amazon.com at the address I was staying at. Despite all this I was not allowed to download the app period as a Canadian. How did they know? I went out and bought a brand new tablet for $200 with absolutely no google accounts on it yet and it allowed me to access the app download. Once I installed my google email account into the new tablet email program I was barred access to the Alexa app again with a warning for Canadians. Amazon was able to access information in my google.com email account and determine I was a Canadian. I originally thought they were accessing my google cookies but I can't see how a cookie could contain my home address location, and give it out just for asking. Conclusion: Google and Amazon were in bed for the initial Alexa programming. The whole voice thing wreaks of google design, being so far ahead in AI anyway. Amazon was lucky to produce a store website.

Many, many of us are Canadians here. Many of us use Alexa with the ISY portal.

Maybe I am a causality of the cloud style service through too many bottlenecks from Ca to Ca.

Benoit hasn't released it yet . oooops.. Sorry. He announced (up higher) it was out this morning.

Definitly. Alexa has been increasing in problems lately with long delay (10-30 seconds) very frequently as well as just ignoring requests, and multiple units duplicating commands. I changed all of my units to "Echo" (from "Alexa") for a wake word as a workaround for the Ecobee4 stat clash, and now all the units are babbling away in a quiet room sometimes. It seems "Echo" is even worse than "Alexa" as a wake word. Seems even a click sound can wake my Echo / Dots. I constantly have flashing lights on the top of these as they are becoming more of a nuisance than a help. I hope V3 can help some of this. Not the Wake word but the delays.

Fill the heat shrink with silicone caulking and then shrink them.

Sunrise will also cancel the Then / Off portion. If From Sunset To Sunrise (next day) And ( Control 'Garage / Double Door' is switched On Or Control 'Garage / Single Door' is switched On ) And Status 'Garage / Garage Side Door Switch' is Off Then Set Scene 'Garage / Garage Lights' On Wait 10 minutes and 10 seconds Set Scene 'Garage / Garage Lights' Off Else Wait 10 minutes and 10 seconds Set Scene 'Garage / Garage Lights' Off

Fred. I like to use a less definitive logic. In this case it (99) would not likely ever happen but... If ....stat.temp <= 99 Then .....whatever The other thing that can combine a bit of a check filter into it If ....stat.temp > 60 AND ...stat.temp < 85 Then .....do what I want Else ....notify me something is wrong with stat.

Saskatchewan! Yeah, I have often though there must be a cheap plug-in device that can remotely be turned off and then it self times back on without any power. They could be used in many places. I have an Insteon OnOff module on my router with an ISY algorithm to cycle it, but what could do that for an ISY and PLM? ISY could turn itself off but not back on again.

Factory reset each device and use the admin console "restore, if they were already linked in. Takes a few seconds each device.

I tried this but with so many gadgets using the same device it ties up Insteon traffic. I had nothing but trouble doing this and worked out a different solution. Flashing about every 5 seconds was the limit to not tie up the rest of my Insteon actions. The MS action, directly linked scene with the light (same KPL) could take up to 45 seconds to respond at times, while the flashing was happenning. Even just operating the LEDs without a Wait comes with a severe warning you may cause All-On comm clashes. Not sure why this is predicted to be such a problem but I don't understand the multi-mode technology jump problems going on with v5 either.

Yes. Powerline has reports of working 500' away for many. Sent from my SGH-I257M using Tapatalk

Sometimes dissimilar metals can bond to each other. A smear of silcone grease on the prongs works wonders for some receptacles that are too tight, can do it. Nasty situation.

I have a shop outbuilding located about 20 feet off my garage far end. Then the garage is about 28 feet across until the closest Insteon dual band device is pluggedin beside my dual Outback Inverter system. The outbuilding is coated in metal foil insulation and it has a metal roof. Even the joints in the insulation are covered in oil tape. Unless you locate an FM radio un front of a window the whole dial goes blank and receives nothing. Despite the RF blocking inside this outbuilding the Insteon device comm's work perfectly. I have the occasional miss inside my house but never to my shop.

That would work. We always have to watch which order we set variables to actually do things in so with power failure the importaant one doesn;t get done while the less important one doesn't. In this case the Init $s.siren variable is the most important, not the program enabling.

Welcome to the dark side! Seach your feelings. You know v5.0.10 to be true.

That slways brings us back to one logical error...a power failure during a wait period. Once the option to run at startup 'if', 'then', or 'else' is implemented, it might actually work most of the time. Sent from my SGH-I257M using Tapatalk

Guessing you mean PST?

I believe that is usually a WiFi connection problem when you get that message back. Upgrades may have been in progress.

I have found variables to be very reliable and simple to use. Most of my multiple scene rooms are controlled by variables. A Switchlinc stuffs values into a variable depending on the sequence and a bank of programs in a folder react like magic. They never fail and can be operated from anywhere in any program without understanding what the lighting is currently doing, Scenes used, programs used, or Network resources. As an example when my garage door is open, I flash a corner lamp red, about 1 pulse per 5 seconds. When the garage door closes, what was the lamp doing? It's easy as I don't need to care. Just refresh the variable value the variable contains and the whole room restores to whatever it was doing, Even if Off. If I change the initiator switch to a KPL or something else. I just use the same values and the bank of programs I haven't seen for years does all the work.