MrBill

the really nice thing about the replacement is that they CLONE your old hub's address. You don't have to re-link your entire system.

they will replace it for you free. The new one is cloned with the old ones address. my son's failed and he went thru the process it was basically easy. https://www.insteon.com/support-knowledgebase/2015/10/20/migrating-to-a-new-insteon-hub

What happens when it fails? is there an error message? For clarification, your issue is connecting the admin console to your ISY though the portal? do you have the same issue when connecting via the local network or are you at a remote location and can't try local vs portal?

Happy you got it worked out from that. For future info: the search function in this forum tends to leave a lot out. Instead of using the built in search I used google typing this into the search box: site:universal-devices.com /CONF/ENABLED.D2D As an added advantage the google method also searches the wiki and forum at the same time. Google site search is also a handy feature to use on many other sites. Just use site: in your google search specification.

here is a similar thread:

I got excited.... briefly. Unless I'm missing something tho, I believe they are out of stock. I did finally find an item with an 'add to cart' button, but many items on that site are missing the crucial 'add to cart' button, without calling I'm assuming that means out of stock, although they don't actually display those words either.

From the release announcement (first post of this thread):

I use Comcast for ISY. Originally it was just sending to the AT&T MMS gateway, but there were too many late or disappearing messages. First I added a time stamp as an attempt to track that. Eventually I downloaded Xfinity Connect app on my phone, and configured it to the same email address the ISY sends 'from'. Then I added that address to the 'to' of the emails being sent. Xfinity Connect is really just a simple email client that I wasn't actually using with my human based comcast email. Later I tried to eliminate using email and move notifications over to Pushover, which is more reliable but still not perfect. Also the * wildcard for node name doesn't work with network resources. In the end, I use all. Most messages go ISY to my phone via 2 routes and I get 3 notifications total. It's not all bad because usually there are only a few a day, and there is redundancy so none get completely missed. to recap: the ISY smtp is configured to send FROM example@comcast.net. notifications are sent TO "10digitNum@mms.att.net, example@comcast.net" and then sent again via Pushover. On a good day I see 3 notifications at about the same moment on my phone. Sometimes the AT&T version gets delayed or lost, can't do anything about that. Sometimes I notice the notification from the Xfinity Connect app is missing, that means that for whatever reason that app got logged out, so I log it back in. Finally the Pushover version of the message is rarely missing but sometimes it is.... never figured out what to do about that, but in the case of for example "low battery" messages the Pushover version will be missing the node name, but that will arrive in the other forms of the message.

I'm not certain you're correct, but I haven't loaded v5.1.0 to test because I don't think it's included for this reason: and that list appears to include: Since I have no Z-wave and that bug doesn't appear to be addressed I haven't loaded the update.

Correct. It doesn't work. UDI never comments if that is a bug, or they exist for a future use reason we haven't been told. You can only set the admin user name and password, the rest don't work.

I agree with lilyoyo1.... it sounds like a bad device. delete it from the ISY, factory reset it again, Don't add it back to the ISY yet, but wait it see if it turns on on its own. If it's bad don't forget it has a 2 year warranty.

@danbutter, the topic was insteon, not z-wave, but here is a past thread with the exact same issue:

I think i got the concept of the new item after re-reading the first post. For clarity tho, The DirecTv power supply is just a new item in the home, not something controlled by the 2634? The next troubleshooting steps I'd take if this were my problem: First I would use the 'find' feature on the programs tab to double check this isn't for some reason included in a program. Right click the folder "my programs" at the top of the program tree on the program tab and use the 'find' feature to look for errant program entries. Assuming it's still unsolved, I would then use Tools > Diagnostics > Show device links table, after then links table is done generating then I would press the 'compare' button. If difference are found you might screen shot and post. Lastly I would reset factory default on the device. Next to last page of this PDF. After factory restore you will want to select the device in the ISY device tree, right click it and pick 'Restore Device'.

Are you speaking of an Insteon 2634 or some other device? and as @Teken mentions are these ON events showing up in the ISY Level 3 event log?

The only thing that could be a serious issue is if your programs make extensive use of adjust scene where the scene controller is a wireless device such as a motion detector, Open/Close Sensor, Hidden door sensor, or wireless Insteon remote. Specifically: Where the Action in a program is Adjust Scene and the Controller is a battery device. This isn't always used by everyone, but it might be used to provide, for example, a different level of dimming at night. The function does work correctly when the controller is NOT a battery device, however the action will not convert when upgrading 4x -> 5x, and the program will need to be manually adjusted and then re-saved. Other than this issue, I agree 5.0.16C is rock solid.

I use that value from the wireless tags nodeserver like this: (run at startup) If '#1704 / Freezer' Last Update Time > '$freezer.tag.hb Raw' Then $freezer.tag.hb = '#1704 / Freezer' Last Update Time Wait 11 minutes Send Notification to 'Bill' content 'Freezer HB' Else - No Actions - (To add one, press 'Action') Normally the wait is interrupted because of an update, so the then body only finishes when an update is missed. I've considered adding one more statement to the end of IF: Run Program 'Freezer HB' (else body) and then making Else Wait 24 hours Run Program 'Freezer HB' (if) to make sure it gets restarted... and to nag with another notification in case I forgot to deal with it... but I haven't tested that but I don't see a problem where it wouldn't work... except if maybe the nodeserver wasn't running with the ISY restarted.

Ideally you would use seconds from the epoch which is easy to obtain in python, thus it stops when the node server stops, but never resets. the Wireless (CAO) tags node server is a shining example:

the always increasing time in seconds value is a simple method that never fails.

it was.... when you right click an Insteon device in the tree the "replace with" context menu does not appear if the device located in a folder. It must be moved to the root level to use the function.

if you're having this kind of trouble you should open a ticket. support@universal-devices.com include the new and old email address as well as your UUID to expedite.

I just created this program: AAA TEST - [ID 00E8][Parent 0001] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then $temp_test = 1 Else $temp_test = 0 Added it to the portal as: "Alexa, Turn on the toaster" sets the variable to 1 "Alexa, Turn off the toaster" sets the variable to 0.

do you have an else body in the program? in my experience on is then, off is else. or paste the program and show us how you have this set in the portal, maybe I'm not understanding what you've set up.

The magic happens in the portal. Instead of mapping Alexa to a device she's instead mapped to update the state variable.

it can be done... here's almost what you asked for: the change you'll need is in the alexa.on program you'll need to repeat each of the devices dim levels. The problem is scene's can't be dimmed, they can contain members preset to a certain level for that scene but they weren't designed for setting the scene itself to a certain level. I actually have a group for 3 lamps that I did with individual controls like in the linked post (1 variable and 3 programs for each lamp). And then made a "group" program to control the individual lamps: Alexa.on - [ID 00A1][Parent 00A4] If $Dim.Lamp1_2_3.group > 0 And $Dim.Lamp1_2_3.group <= 100 Then $Dim.Lamp1 = $Dim.Lamp1_2_3.group Wait 1 second $Dim.Lamp2 = $Dim.Lamp1_2_3.group Wait 1 second $Dim.Lamp3 = $Dim.Lamp1_2_3.group $Dim.Lamp1_2_3.group = -1 Else - No Actions - (To add one, press 'Action') Alexa.off - [ID 00A3][Parent 00A4] If $Dim.Lamp1_2_3.group is 0 Then $Dim.Lamp3 = $Dim.Lamp1_2_3.group Wait 1 second $Dim.Lamp2 = $Dim.Lamp1_2_3.group Wait 1 second $Dim.Lamp1 = $Dim.Lamp1_2_3.group $Dim.Lamp1_2_3.group = -1 Else - No Actions - (To add one, press 'Action') Basically if you use the group spoken to set a level for the group, these two programs set the variable for each lamp with a wait between each. The group variable always gets returned to -1 as soon as it's used so that anything you tell alexa registers as a change. You could also just do one scene for the group and in the alexa.on program, set each fixture to the level.

@bmercier probably needs to assist you.