MrBill

Do you leave your admin console open 24/7? If so have you restarted it lately? It's better to only open the admin console when you're actively using it, but if you choose to leave it open a lot, restart it everyday.

Quoting notifies..... Occupancy only works with the app Locative and Locative is only available on the iOS platform (they dropped the android version). Occupancy V2 only works with UD mobile and not locative. I also think UD mobile and Occupancy V2 is only supported on the Andriod version and not iOS, but personally I'm confused looking at the Occupancy V2 wiki page because it's last edit was in August 2018 and I wasn't aware UDI mobile was around in August of 2018. Paging @Javi because he knows this answer.

I agree on mobilinc, I wouldn't send anyone that direction anymore. as far as UD mobile, it's great, and I do use it for one off issues that I haven't built controls for in my HA dashboard. I think for the most part HA will remain my mobile interface, but its absolutely awesome to have UD mobile and be able to reach devices, programs, NR's etc that I don't have controls built for. On thing I love about HA is that I can use my laptop to "develop" the dashboard and then it can be used from mobile, wheras with UD mobile I have to hold my phone to "develop" or 'create all the favorites' and scaled down controls... I probably will just never get around to that, especially if I have to do it on the phone and not build it for use via the laptop. I don't know what the case would be tho had UD mobile existed first.....

This is a hard question to answer. All I can really say is "it depends", but I guess that requires some explanation.... so here goes some rambling discussion....... First and foremost... one of the reasons I choose to the ISY platform to start with "all local, no subscriptions required, no add-on fee's" I didn't mind paying $20 on-top for Mobilinc Pro, However I was instantly turned off by Mobilinc X when it was released because it required an annual subscription, and for that reason I never bought it. Finally frustrated with Mobilinc Pro tho due to the "Already subscribed" bug I next invested in eKeypad, and later I bought Agave too. (turns out the "Already Subscribed" bug is caused by something unknown other than Mobilinc, but the problem really seems to be a Mobilinc bug and I lived with it a long time trying to resolve it). So, over time I spent considerably on "add-ons", but as noted dislike annual fees.... But the fear of recurring fee's does have a pricepoint... For example: I have no problem subscribing the Portal at it's low rate of just ~$1.00 per month, I also like the two year subscription duration. So I favor a flat fee, with no recurring subscriptions, but in certain cases will buy a subscription. Another disclosure I'll make is that I've actually made a few private payments to node server developers to get my "suggestions" moved higher on their priority lists. I'm not bashful about offering incentives, that's happened multiple times in amounts like $30, $60 and $100 depending how badly I felt I needed the change/modification. All that said tho... there's another economic factor in the mix. I was originally attracted to Home Assistant because both @asbril and @carealtor were using it. What I found when I got there tho, is that the UDI integration is amazing. I was finally able to set up a mobile experience that has wife approval.. and she actually will use it.... while I try to make ISY the "center of the universe" in a couple of places I have delegated "control" to HA over the ISY.. in two cases what I need isn't available thru ISY/nodeserver, and in other the HA integration is just better than the ISY nodeserver. All that said the core integration count for HA is sitting at 1860... that equates to 1860 nodeservers that are built in and free to use.. there's also 1000's more that are free but have to be added through the community store. So all things considered this is a driving force in whether I'll buy a nodeserver or use the HA integration. After all HA and ISY operate so well together they seem to be like Siamese twins.... TL;DR Yes I'll pay... prefer 1 time charges over subscriptions, but will also evaluate all options before paying.

You're probably correct, I have one scenario involving a nodeserver that I never worked out which causes issues during the Query All My solution was a minute before the query disable the program and re enable it 16 minutes later.... in your case something like... If From 2:59:00 AM to 3:15:00 AM then Disable Dim Master LEDs else Enable Dim Master LEDs ... would disable the program screenshot above from running during the query. Edit to add: in my case that was originally a trouble shooting step, but I never figured out a better fix so I just left it...

It's really a mindset and it really boils down to which device is considered the "scene controller" or even more broadly which device the "controller". My mindset is that the ISY is always the center of automation, Alexa is only a voice assistant that lets me operate the automations stored in the "Controller". In your first scenario you were attempting to make Alexa the controller and let the ISY be the assistant the knows how to turn on and off certain lights.

X-10 House code J is 1 1 1 1 Status Request is also 1 1 1 1 So it makes some sense that noise could produce house code J status requests. However if X-10 is properly implemented it would be hard to get the start code repetitively in noise, and the fact that each X10 transmission must be received twice to be considered valid. more information on the Physical Layer of the protocol can be found in the wikipedia article.

Are you using Locative app on iOS with Occupancy? or Occupancy 2 with UDI Mobile? I can answer the iOS with Occupancy... To update your location manually open the locative app and long press the "Location" in the "locations" screen in the app. (if "Edit GeoFence" pops up you tapped, you need to long press.) On long press you'll see a context menu popup with the items Trigger "Enter" Event and Trigger "Exit" Event. Use those to manually get your phone back on the correct side of the fence. Also there seems to be a problem with Locative and being upgraded to iOS 15. The developer still hasn't answered my email, but the solution seems to be "After upgrading to IOS 15, uninstall Locative, restart the phone, reinstall Locative." Other variations of those steps might work, I haven't tested. Those worked on mine and my wifes phones. The symptom that caused me to uninstall, restart reinstall was that "Exit" events were mostly not working. It's worked correctly since uninstall/reinstall tho. To save time and frustration be sure to tap the "location" then copy and paste your 2 webhook URLS to a NOTE on your iPhone, so that you can reverse that and paste them back into the app on reinstall.

A couple posts up he said: but we don't know how much time that equates to...

Correct, you don't want "adjust scene" for just turning the button on or off.

As I pointed out in your other post... unless you already have it you won't find a 2413s PLM to buy at this point. You can however install the non-plm firmware on the second ISY.

To add another troubleshooting step to @larryllix What happens if you try to turn the Basement /Wet Vac on and off from the admin console? Nothing wrong with the program, except that it doesn't last long, are you assuming that within an hour that you'll take over? You could use the newer "repeat while" program architecture, or you could simply add a Run Program 'Wet Vac' (then path) to the end to make it loop forever or more specifically until you stop it.

How are you trying to "Write" the changes? The GUI is NOT intuitive... CHange the on-level dropdown then press On-Level to the LEFT of the dropdown to "Set" the value.

THIS IS AWESOME!! Thank you... I have bookmarked this post.

Someone recently reported successfully swapping parts between 2413u and 2413s to bring the 2413s back to life. I don't think there are alot of test cases tho... but it did work for someone. Hopefully smarthome will get more 2413s stock... but there is good news on the horizon, ISY to moving over to the Polisy hardware... it's being Alpha tested now... ISY running on polisy hardware supports either the 2413s or 2413u.

try plugging the outdoor module in on the same circuit as the ISY/PLM Also Note that device codes on the stickers can be hard to read... 22.80.75 the 80 could be 8D, B0, BD

@Geddy is absolutely correct! It can't be in a folder. Another issue is that it can't be dimmer vs on/off, they both must be the type. here's the wiki page

It exists for me. If you only have one 8Button keypad that may be why it doesn't show up, add the replacement device to the ISY and check again.

I would try turning off huge chunks of breakers in your panel and then rechecking. I tend to start with half, then the other half. then half of whichever group got rid of the noise... then half of that group..and so on... until I get down to a single breaker causing the issue. I know which breaker I have to leave on to keep the ISY and the network up, that's the only one I don't flip off during the process.

Factory reset the switch clears the switches memory, the switch remains in the ISY... "Restore Device" then causes the ISY to reload the switches memory as the ISY wants it programed. You could try just doing a "Restore Device" without clearing the memory first. If your attic gets hot, most do, it's likely not a good place for the switch. I'd try to move it anywhere into the conditioned space. In one house where I helped straighten out some problems we cut in some switches near the ceiling in a bedroom closet to move switches out of the attic. I have one near the ceiling in my laundry room just because I didn't want it in the attic for something we added. It can certainly be frustrating when you know you're doing it correctly but it doesn't work. Insteon also can drive me crazy at times because it takes so long to reprogram complex scenes and/or multi-button controllers.

That actually looks correct. Sorry for being persistent but you wouldn't believe the number of users that can't grasp that concept. What I would do next, is one at a time, factory reset each device, then select the device in the tree, right click it, and select "Restore Device" 2477D's and 6 or 8 button KPL's the reset proceedure is pull out the air-gap for 10-seconds, push it all the way back in and HOLD IT until the long beep Stops. then after a pause it should beep 2 more times. I've forgotten how to factory reset the wireless remotes, google "Insteon <Model Number> manual" and look for a pdf from cache.insteon.com near the top of the search results. I actually have to to this about once every year or so for our masterbed room overhead light, I think the memory in the switch is flakey, but it's out of warranty and only happens every year or so and I only have to actually facto.ry reset the 2477D itself. The other causes that can randomly trash can be communication errors, and the fact that the switches are often shipped out with junk links.. .as a result I try to remember to factory reset new out of the box switches as as they are installed before being added to the ISY.

Highlight the red node of the scene one at a time and show us that. An Insteon feature is that the same scene can behave differently based on which controller controls it. in your scene: You have the root of the scene selected, the information that you are looking at on the right side of the screen is what happens when the ISY itself is the scene controller. Move the Blue selector down one line at a time and watch the right side of the screen. What is shown as you do that is what happens when each of those controllers are used. In other words your scene must be programmed 5 times.... that can be the same 5 times or 5 different configurations.

In your example you need to configure the scene 5 times. You have the root of the scene clicked in the tree in the left side of the screen for each screenshot. You also need to click each RED controller link and configure the scene attributes for what happens when that controller is used. (this works differently that it did in V4 firmware where there was a copy button)

Wait for the chief to get his endians in order! Must be FedEx.

You don't control scenes with a scene, you control devices with a scene. In these two scene's as virtual 3-ways, both devices should be controllers. If they aren't the lights on the switch will not stay in sync, and the ISY will not correctly identify the state of both switches. Everything scene 1 Switchlink is a ? (switch1) 1 switch link is a ? (switch2) 1 Switchlink is a ? (switch1) 1 switch link is a ? (switch2) keypad link button is a ? (ButtonA) There's a couple of approaches here. One is to add button A to the Kitchen Scene and dinning room scene as a responder. that will make that button light up if anything gets turned on, and one press should be off. In that case Button A would be the only controller in this scene. and pressing it would be All On and All Off. In my house I have little use for "all on" but I do like all off. If it's a 6-button keypad I always use button d for that, if it's 8-button I use button H. I set it to "non-toggle OFF" and add everything I want to turn off, that includes switches and other buttons on keypads that might be on. As you exit any area or room the bottom right button is always All OFF for what is behind you. Examples exit the Master Bath, button D is the bottom right it's all off for the Master Bath, Exit the Master Bed Room itself button H is everything behind you, which includes everything in the bedroom, AND everything in the master Bath (it as its own sub-All Off but Master Bed Room All OFF includes everything in the Master bath all off and everything in the bedroom). At the bottom of the stairs the All off there will turn off everything downstairs (or behind you). Head out to the garage to leave... the button H by that door is All off for the whole house.