apostolakisl

Yes, transatlantic fiber is how Germany is connected to the US. I agree, the bulk of the latency is almost certainly rooted in server response not distance. An interesting related fact is that the speed of light in fiber is slower than through a vacuum (or air). This can add a few milliseconds of latency for long haul transmissions when comparing terrestrial fiber to laser or rf. SpaceX is marketing using their satellites to laser relay satellite to satellite across the globe for extremely time sensitive transmissions. Most notably traders doing arbitrage between. say, New York and Hong Kong. Apparently they are willing to pay $millions per month for the service. Even though it has to go through maybe 10 or 15 hops and doesn't take a straight line, it still beats the terrestrial fiber.

Funny that I push an Insteon button on a wall 10 feet from a ceiling fan and the fan turns on, but the signal first goes to Germany, then to an Amazon server (wherever that is), then to the fan company server (wherever that is), and then back to my house. And it works every time. How many thousands of miles do you suppose? Edit. And if I used UD mobile logged in via portal, you would add a new first step where it goes to UD server and then back to my house ISY.

I have had perfect success using a webhook setup and an Alexa plugin. I don't recall that it has ever failed. There is a skill for Alexa and then you create webhooks on here: https://trigger.esp8266-server.de/ You use a network resource to send the webhook. EDIT: I just went to that website and, if I don't log in, the creator says it is broken, but it isn't, at least for me. I use it everyday and I even added more webhooks to it just a month or two ago. Not sure if it is possible to currently add it to your Alexa or not, but for me with it already there it works great and I am able to keep adding more. I have about 20 as is. EDIT 2: It looks like Alexa still has the skill for you to add. You do have to use the primary amazon account and once you add your webhooks, you tell Alexa to discover devices and then the webhook shows up as a device that you can use to trigger whatever you want on an Alexa routine. At that point, you basically just send the url to the internet from a network resource or just put it into a web browser and usually in less than 1 second it is doing its thing.

To further this, it is not just Elk. It is seemingly random nodes across the entire system. Insteon nodes, PG3x nodes, Nodes from IoGuy Nodelink. I see no pattern to it. @Javi Example: Admin console on local connection: Admin console as viewed via portal login at the exact same time from different PC:

Exactly. @Javi This has been going on for at least a couple weeks. It is consistently the same nodes that don't work while other nodes that seemingly should be identical work fine. The first place I noticed it is a perfect example. I have shortcuts setup for my garage door and my wife's garage door. Both are Elk zones (zone 22 and 34). On different expansion boards, but I don't think that is a reason. When the doors are closed or open I have to change the color of the icon from red to green. So I quickly noticed that the icon was neither, but rather the default blue. Every now and then, it would populate, say "closed or open" and set the color, but typically, just blue. My wife's door, always populates. It will populate on occasion. It seems like the way to have that happen is to have the admin console open or have UD mobile open, and then change the status of the node. It will populate, but it doesn't stay populated for long. Certainly won't stay populated if you close your session and open again. Here it is: And then there is also the 0 and 1 for Elk status instead of armed/disarmed/etc which, as far as I an tell, is a different issue with the newer firmwares.

I can confirm same on ud mobile. I switched to local settings and now it populates everything.

So I have isolated the problem to logging in via the portal user/password. Anything that uses the portal (UD Mobile and admin console not using port 8080). For example. This screenshot is from logging in using port 8080 admin/password @bmercier And simultaneously on another computer using the portal login.

Recently, perhaps with a recent update, elk module no longer reports any of my keypads, except maybe a parameter shows up and then goes away, and a handful of zones show no status. I see no pattern to the zones not showing. If I open elk rp2 all status is there. If I query, it might temporarily report voltage. I restarted the node which didn't help. I really don't want to delete and re add the node because of all the reorganizing I did with folders and names for the various things that would all need to be redone.

If the power flickering/going out/coming on, may have resulted in the switches shutting down and then booting up without the proper power environment leading to incorrectly set RAM(I assume Insteon switches have RAM). As we all know, power supplies have capacitors that keep our electronics running for a few seconds even when power is removed. But as the capacitors charge decays, the voltage and current supplied is sub-optimal. So power coming on for a second after shutting down and then going out for a second would allow the boot to continue but with incorrect power during that sensitive time of booting. That would be my guess as to why the flickering power resulted in misbehaving switches and a proper boot fixed it.

@Ross Yeah, those temp intervals are way too big to be of any use tracking a refrigeration system. Basically, it would only be helpful to tell me if the unit failed completely. Thanks for taking the time to look that up.

I just tried edge and it is the same. was using chrome.

I tried collapsing the folder tree down and after closing the first few, as soon as I clicked on about the fifth one down, they all popped back open again. Happens every time. Not seeing the same thing with nodes, but nodes aren't in folders. EDIT: seems to be a time thing. About 5 seconds after collapsing a folder, it pops back open.

Can you tell me if the Caseta control is cloud based or local?

Can you set the temp interval or is it predefined? I could make this work just fine if I could set it to something like .5 degrees F. Anything that takes a replaceable battery can be "hot wired" to an external power supply, I have done this many times, sometimes more invasively with soldering and whatnot, but usually I just cut a piece of dowl wood ~1/8 inch shorter than the length of a AA or AAA battery and drive screws into the ends that I use as screw down terminals for wires. I run the wire out a small notch I make in the battery door and connect to an external power supply.. For example, is something uses 2 AA batteries in series, I just put one screw in the end of each of 2 dowls and arrange the dowels such that it provides the 3v across the two correct end points. Then I plug into a 3v power source. 3v power supplies aren't so common, but they exist. If it is a 3 battery setup I will usually use a 5v power supply.

. I have 10 wireless tags and have never had to physically reboot any of them. I must be on at least 10 years on the oldest ones. I have had to do a "reset states" a few times. Though it has been a long time since that has been needed. Not sure if wireless tag changed something or just random timing. 4 of these are inside walkin coolers which are substantial 6 walled metal boxes and the signal gets through. I have all of them set to 30 second updates which gives me the resolution needed to track compressor and evaporator behavior precisely. Dealing with the refrigerator repair guy trying to tell you he fixed something and being able to prove he didn't has been very valuable.