All Activity
- Past hour
-
OK @paulbates, got my new PLM and installed it, following @Techman's instructions. Went smoothly. And so far, all my insteon devices are working. Which means that outlet I replaced and chewed up in the process was probably still good after all. Is there any reason to keep my defective serial 2413S PLM, or toss it out with the outdated 2412S?
- Today
-
I'm glad there are smart people like you! Tried another browser, and it worked like a charm! Thanks so much for your quick help and support!
-
srjacob started following migrating from the ISY994 with Elk module to Einsy
-
I have a Insteon network, an ISY994, and an Elk M1 System. I would be interested in getting an Eisy and replacing the ISY, but I am really concerned about the ISY-Elk interface. I use this heavily, and have dozens of programs written in the Elk (rules) and in the ISY to both control lighting, garage doors, and an electronic gate. I would hate to rewrite and convert all of these programs just to migrate from the ISY to an Eisy. Is there an easy to do this migration, or should I leave well enough alone (there is no pressing need to convert)? Everything seems to be working fine, and I have spares for the ISY and serial modem. Thanks in advance. Steve
-
I would suggest to try a different browser, or perhaps try incognito mode (If using Chrome). I believe a browser extension is probably interfering somehow. You could also try to press F12 and look at the browser console, then navigate to my.isy.io. You may see in the console an error message that could give you a clue.
-
cksedg started following Can't log in to my account on the portal
-
I'm trying to add some new scenes to allow Alexa to control them from spoken commands. I've done this many times, but now nothing works. I haven't been on the isy portal for some time, and now I can't log in at all. https://my.isy.io goes to a blank white page and just sits there. I tried the UD home page, which says to log in from the console. When doing that, it just goes to a blue authentication page with no place to enter anything. Have I lapsed in my membership? Have things changed so much that I'm not up-to-date? Any help anyone can give me will be greatly appreciate!
-
Should I remove the rear middle seat heating - It does not seem to be reported. Does it make sense in automations - would you turn on the seat heat remotely?
-
It looks like someone worked their magic somewhere. I was finally able to get it authorized. I didn't do anything special or different. Looking forward to the next version for enhancements.
- Yesterday
-
I see that Jim is actively working on updating the library to work with newer firmware and whatnot. Probably just wait for that to be released.
-
No. All Plugin (formerly Node servers) configuration is done on the web for Polyglot. Don't mess with anything in admin console for plugins (node servers). Sounds like you might be in the wait a while phase. I think it could take as long as 48 hours based on reading another post.
-
In the Universal Devices Administrative Console, the node server configuration has a line for inputting a password. Is a password needed here? would this be causing the Onecall Data Query Failed error?
-
Here is an IFTTT webhook I use for reference. This is not to send a text, but how it is configured would be the same, you would just call a different webhook.
-
-
ok. i'll give it a try later today
-
@scott basilius I believe there have been some issues of the API taking a little while to be available. I believe @bpwwer has said to allow several hours to as much as a day and it should work. If you just generated the key or since you said you generated a new one give it some time to activate on their (OpenWeather) system. It should work soon.
-
To double check that, I deleted the node and installed it into a different slot. Same issue. Some examples of the messages that are being spewed in the debug log: 2024-11-20 03:00:51.254 Thread-11 (run_forever) kasa.discover ERROR discover:error_received: Got error: [Errno 64] Host is down ... 2024-11-20 03:00:51.727 Thread-4638 (handler_poll) udi_interface WARNING SmartDeviceNode:shortPoll: I: Already running ... These messages are appearing every 20ms or so. I was wondering if my poll values are incorrect? Any ideas on what they should (typically) be? Also,my versions: PG3x Version 3.2.27 Plugin 3.1.4
-
scott basilius joined the community
-
i'm getting an error "query:query_onecall: Onecall data query failed" when i start openweathermap. I tried generating a new API key and still get the error. Anyone familiar this error?
-
There's nothing to do with the file. This was just a way to test that there's no networking issue preventing access to the certificate. If that was the case, that could have been a reason for the error message you are getting. At this point, I'm not sure why you are getting this error.
-
Hello Richtimpa, I do not have a power wall but will try to offer some insights and/or questions you can ask the Tesla rep. 1) What type of lights are blinking more often? LED or Incandescent or both? Are the lights on Dimmers? From your description it sounds like it may be a combination of things. It is likely the Power Wall (PW.) has internal filtering (across the line capacitors) to reduce the noise level it puts onto the power line. We refer to those as signal suckers. A signal sucker can make the communications less reliable and result in the sluggish query you see. It would be somewhat difficult to find an Insteon filter large enough to "isolate" the PW signal sucker from your power line. A large "Line Reactor" or inductor-only filter could possibly help but identifying that would be difficult without Tesla's help. You may have had some other signal sucker issues in your home prior to the PW install so the PW may not even be at fault for that one. It also sounds like the Solar Install may be communicating with the PW over the power lines and sending signals near zero cross that cause the lights to Flicker. LED would tend to be the most sensitive to this. If the biggest issue were with LED then a different brand might be less sensitive. If on Dimmers then adding a device such as a "Jasco lighting bypass" might help. If at all possible to get input from a Tesla expert that would be best as these types of issues can be difficult to resolve without knowing more about the Solar-PW interconnections. Having an Oscilloscope to observe the power line requires a device to filter out the large 60hz waveform in order to observe low level power line noise interference. Best of luck to you.
-
You need to contact UDI direct for something like this by submitting a ticket.
-
Can you post 10 - 20 log entries, especially ones that repeat?
-
Likely a tight loop somewhere in your ISY program code. Do a search for that device in the admin console and examine each program that contains that device. These can be tough to find if you are using complex logic that may involve more than one program that interact.
-
When I enable the kasa plugin, it appears to absolutely flood the system with log messages, lagging the entire system and preventing me from logging into the pg3 interface. Any ideas?
- Last week
-
Before Soft Start. On 100% and dim down. After Softstart. Both On 100% and dim down and X10 Extended Dim commands. That was also when the new surface mounted components and different processor where introduced. Smarthome used the On 100% dim down and Preset Dim. Smarthome modules don't respond to X10 Extended dim and X10 don't respond to Smarthome Preset dim. I think Leviton used the Preset dim also. Not sure about the ACT A10 protocol as it is built on X10 commands with added features. Found a file with a small part of one of the PLM developers sheets. DimDif.txt
-
Quietminded started following Trouble with PLM replacement
-
There are those here a lot more knowledgeable about electrical theory and problems than me, but they haven't chimed in, so here goes: There are similar stories here on the forum. Here's one, a long read but worth it Temporarily disconnect the powerwall from the house power long enough to confirm that the problem goes away when you do. If it does, see 3. below. If it doesn't, you'll need to go breaker by break to establish where it's coming from, then go to 3. below when you find it. It seems likely it's the powerwall given the timing, but powerline actual problems vs perceived problems have been a slippery, unpredictable slope in my experience. Consider filtering options, which will be a guessing game. Insteon makes a plug in filter but I'm guessing that's not how your powerwall is wired to your house Insteon makes these. They are designed to go near the flicker light, but I would suggest trying it near the powerwall. There are 2 types and Insteon mentions that they can't say what will work in what situation, just try, This is the link to the install page. Not that expensive to try out. Good luck!
-
Hard to say for sure, but relatively easy to eliminate as the culprit.