smokegrub

I just thought of something, the sensor may need a shim to improve the reliability of the button press. Thoughts?

I have six of these devices with three each located in two homes, each with an ISY. One has malfunctioned and it is more than 300 miles from where I will spend the winter. Today, that device sent 75 emails falsely indicating it was open. I had to disable the device in the ISY to stop it. If I were there, I would put the device into linking mode and try to resolve the issue. Is there anything I can do to remotely get it into linking mode? I feel confident there, isn't but I have to ask.

I manage the remote reset of a Insteon wireless stat by powering it through a dual band device. I cut the power, wait a couple of minutes and repower. I use that stat solely for the purpose of monitoring temperature. If other Insteon stats are as unreliable as mine I would have to recommend against it.

For what its worth, I just completed setting up a tabletop enclosure with a KPL. Works beautifully!

: )

Please accept my apology, I incorrectly entered the device ID. I mistook a "B" for an "8"! This is the second time over several years that i have done that!

Trying to link a Dimmer Keypad (6-button) to my ISY. I have tried linking using New Insteon Device by typing in the device’s address. Didn’t work. I assume that is because the device is not in linking mode. I tried holding down button “a” (I saw a vague reference to that elsewhere). That didn’t work. Any help will be appreciated.

Although I have never used variables I believe you could use them to compare the temp in the early morning with that of mid day and, if no change is reported, change the battery.

No nodeservers, no Zwave just Smarthome devices and Alexa. I tried to upload the error log but it is 2.6 mb and didn't load. Shall I copy a portion of it and attach?

Candidly, Michel, I would not know what I was looking at even if I knew where to find that log. I cannot imagine what might be happening that would make my ISY so busy. As you know, I have two portals which deal with separate Google accounts on separate ISYs. Of course, any help will be appreciated because use of Alexa has become so undependable as to be almost useless.What are the types of things that can affect the ISY's queue?

I have a few of these every day. It is getting to the point that Alexa is simply not dependable. Even though I often get feedback that a spoken was executed, in point of fact, it wasn't.

I have been getting far too many Alexa responses of "OK" when, in fact, the spoken was not executed. I have reached the point where I check behind Alexa's response of "OK" to see if, in fact, the desired action occurred. That defeats the purpose of using spokens. Are others having the same problem?

How old is the PLM at that location? What color is the light on the side of the PLM? Try unplugging the PLM for a minute or so and plugging it back in. If your wife can't access via the LAN the portal will be no help. If none of these offer a lead, submit a ticket to UDI asking for help.

First thing I would do is reboot the remote ISY.

This has now occurred at a second residence with a different ISY! That makes it almost a certainty that it on Amazon's end.

This has now occurred at a second residence with a different ISY!

On three separate occasions this past month I have encountered situations where my devices display a red light when I issue a spoken. Alexa says something to the effect that I am having trouble accessing the internet. I can fix the problem by rebooting all six Echo's. I can still set timers,

You are correct. I just could not determine how to fix that. Michel was gracious enough to help and all is working. That only cost me about two days work!

I have posted here previously but feel compelled to note the support UDI customers receive at this forum and from the company. The products are of exceptional quality but some of the work they can do is complex. That is where the forum and company truly shine.

I appreciate your "jumping in". I did, to the best of my ability, what Benoit outlined above. Both portals show the devices for my Chesapeake Portal. When I try to log into the Amazon account for Wolf Creek using those credentials it opens the account for Wolf Creek! I see no way for a relative novice such as me to resolve this. I hope Benoit agrees to remote into my Mac and sorts this out. I was able to use one account at a time previously. Now, I have lost that ability. As bizarre as it may sound, the last time I talked to my wife (Chesapeake) she said she can control devices upstairs but not downstairs. Go figure.

Now when I attempt to log into the Amazon account for Wolf Creek it logs into Chesapeake! This is becoming a maddening waste of time!

I would love for you to remote into my Mac. I will provide the credentials you will need to access both Amazon accounts. I have spent days on this and now I have lost practically all utility. I suspect you will be able to do in a few minutes that which we will continue to chase. If you are willing to do so, let me know hat you will need.

I tried logging out of the Mac app and Alexa on the iPhone. At Wolf Creek Alexa would say a spoken was being executed but it wasn't. I called Chesapeake and found upstairs devices responded to spokens; downstairs did not! I then opened the Mac app and logged into the Chesapeake account. All devices displayed properly by only the upstairs devices responded to spokens! At Wolf Creek Alexa said she was doing something but the device did not respond. I am going to check the portals and see what devices are in each portal. I completed that task and each account displays the proper devices under Connectivity.

I did this and it appears I am getting close. However, a problem has arisen. When I tried to access the Amazon account for Wolf Creek in my Mac app it opened the account for Chesapeake! How do I fix that? Thanks for your continuing help.