paulbates

You'll need to download the log, open it in Excel and see what happened at that exact time. Eg, if a program ran

It was more text based, but I used to use the Home Automation Dashboard (HAD). I used it more for reporting status but it also did control. I hosted the pages on my ISY 994i at the time. I just took a look and the pinned posts that explained its used are not there, suggesting maybe it was depreciated. It had a rich set of capability with the ISY while being 100% html driven My guess is that while it may not be supported, the capability is probably not taken away. You may want to scroll through that sub forum and see what you find.

The combination of older PLM and flaky behavior says it's time to get a new PLM and handle the swap on your terms, not when things get a lot worse and it stops working.

,The first thing to do is look at the UD Mobile app. Yes, some things are in beta.. but I've recently returned as ISY user in a new-to-me house and was pleasantly surprised how much its capable of and where its headed. I can now do some of my tasks including programs on it. Yes, to do everything I still need the admin console, but I'm having a good experience on both my ipad and android phone using UD Mobile There is a potential door number 2: A small headless PC appliance on your home network. They do cost <= $200, but you've already spent a lot on your system, and will easily spend more than that migrating to something else not to mention the time to recreate what your programs do. I haven't tried it, but my understanding is that Remote Desktop, RDP, can be enable on the w11 home that would come on the headless pc appliance. Then it would be a matter of finding out if your company restricted RDP on the laptop.. you could see now if its possible to open RDP and define a new host.

The first thing I would do is a backup, if you don't have a current one. It doesn't hurt to replace the SD card, especially if the ISY is older... I'm going to say 5 years but others may have a better range. That way you replace it on your terms. I know there is a procedure for replacing the SD card on the wiki somewhere. My recollection for the procedure is to pick one of these: Copy the image of the current card to a new card using a computer that has an appropriate slot. Insert it in the ISY and restart. Backup iSY. Replace the card with a new one. Restore ISY

It's possible that the SD card became loose in the physical move from place to place. Unplug the 994, unseat and reseat the SD card, plug it back in

Perfect, thank you Jimbo.

I know what I want.. I used pushover in my last house. One of the things I liked and used was pushover's "apps", which sorted notifications into folders. It was pretty cumbersome to set up all the Network Resources to get to that end. Fast forward; I have read the notification server and UDM docs.I have eisy, UDM and the notification server. When I look at the notification service in UD mobile, one of the options is "Add Pushover Service nodes", and when I click it, there's a user and app fields. Before I try it out and stumble through it, I'm wondering what the intentions are or if someone has tried it and knows: Questions This is intended one way: eisy programs/scenes->Notification sever->devices->pushover? I can use "Add Pushver service nodes" multiple times to connect with multiple pushover apps I've created? It shows up as a device I can use in a "Then" statement from my programs to create notifications more simply? Do the notifications sent this way not show up on UDM?

I set up a new ecobee smart thermostat and bought the ecobee NS. Though there was a little bit of a wiring adventure, the thermostat install went fine and started the heater up, mobile app works. I followed the directions for the NS and got the PIN code when firing up the NS entered it in my online account within a few minutes. That was the end of it. I got the basic device (pink in the picture) but none of the info from the stat. I went to the node menu, picked the ecobee and install all devices... after a few minutes i got these devices. I think I'm missing the main control pane, and the names on most of the individual items is wrong... See pics I'm guessing an uninstall and reinstall is in order? But want to make sure I don't goof up the pin part.... will that be needed again??

I haven't personally tried it, but "Send X10" remains in the admin console under Devices when creating a program. There's no reason for UDI to remove code to support X10 when moving to iox. The thing to think about: Physically connecting from the eisy to the powerline for X10. You'll either need: The right cables & adapters to get a PCS05 x10 powerline adapter connected to the EISY... USB serial adapter+ the right serial cable ... or... Possibly an Insteon USB PLM. The question is does it support X10? It likely does, but a number of Insteon devices dropped x10 support. If no one here knows, you can ask on forum.insteon.com If it does still work, a serial PLM does work but needs the optional UDI cable/adapter. If there's a chance you'll build your father's powerline network with new devices, and the if PLM still supports X10, I'd add new Insteon devices and would get the USB PLM so both can be installed

Thanks @Jimbo.Automates .. Does your NS communicate with the ecobee door/window sensors?

I'm on-the-line. The stories I've read here say that the ecobee can do a lot of functionality on its own with no programming. There's some appeal to that. RIght now if I buy a refurb Ecobee, they offer 2 of their door sensors at a decent discount. That's the next-to-top smart thermostat, a remote sensor and 2 entry sensors for south of $200... hard to say no. At the same time, I am really comfortable with the insteons.

@Hoosier Daddy One more question. The comment that occupancy reporting takes a while, that suggests that the sensor network is managed by polling vs interrupt/signaling from the sensor?

@Hoosier Daddy This helps a lot. In my previous home I had the Venstar colortouches and venlink/nodelink... the reporting and control for the ecobee look very similar. Now there are more questions 🤪, but they are ecobee specific and I need to look/read a little more. Thank you.

I'm looking at an ecobee stat. I want to monitor one door and window with a sensor to shut the AC down when either is left open, and also be aware of them being opened when traveling. I know how to do this with Insteon wireless open/close sensors, my question is can I access the same information from ecobee smartsensor for doors and windows with this node server? It would help to have screenshots of the AC for this plugin

I have an eisy. the upgrade itself went fine. Two things to note: Notifications stopped coming to my android phone and ipad via UDM.. Haven't had a chance to diagnose it yet. I happened to run the upgrade about 1.5 hours before my yard lights off program ran. They ran on the reboot of the iSY and the "catch up window" is the default and much shorter than that. I don't think this is specifically related to this upgrade

Sorry about the frustration. More physical investigation is in order Was the house originally designed for smart switches, or the owner that installed the switches wasn't the orginal builder? In addition to the switches you can see, there may be Insteon inline or micro modules behind fixtures Have you looked near the electrical panel for the hub/isy/controller? The switches are older, possibly powerline only - and the electrical panel is the center of the Insteon powerline network To the comment(s) already made above, you should see if you can work around the problem to use the house Buy a few regular switches from the hardware store Pick a few switches in key areas causing the most pain. Factory reset the switch - here the manual, look at the bottom of page 14 (printed page #) Did that work so the light switches on Yes - move along to the next No - replace with a regular switch Repeat on another key switch

I just got an eisy and added dusk/dawn programs and had programs not function 100% using the "Time" command. The way to check out what's happening is to go to the program tab, and then click the Summary sub-tab to the left. That provides a list of programs and run dates/times... including the Next run. See what next run says for these programs. I had problems there that vanished, but arguably I was making changes at the same time. One of the things I saw was that the Next run for some of my programs using the time command was that the scheduled day was the next day... this was in the am, 8 hours or more before dusk

The motion sensor can be set to send an "on" to a device or scene when it detects motion, and then sends an "off" after a specified amount of time. You'll need to look at the manual for 2842-222 as well as options in the admin console to change the settings. Some things can be set in ISY options and some things are jumper pins on the back..but its not hard to figure out What type of light is it.. regular, LED, fluorescent, low voltage? An unreliable "off" command could be because the light you are turning on is injecting line noise and possibly cause the "off" message to not reach the switch once its turned on...unlikely but possible and easy to eliminate: To test if the load is the problem, remove the light bulbs if possible and retest. If that doesn't solve it, add to your program's then clause, put a 3 second wait at the end, and another turn light off. The motion sensor does this, it sends 2 "Off" commands a few seconds apart

Do you have an eisy and a functioning python dev environment set up to work in? Here are some things to review to get started, assuming you answered "yes", twice, above: There's an python API that defines communication with the eisy resources and formatting of data appropriately: https://wiki.universal-devices.com/index.php?title=ISY_Developers:API:Python

@IndyMike and @Geddy Thanks for responding The same happened to me Mike... a while after discussing it here, I made some mods, another program I left alone, and they all went to where they should be for Next Scheduled Run!(?). Included in this was no longer having it wait a day to start a new program with a schedule. Calling this one closed, thanks again

Thanks @IndyMike. Could be something that's been there all along and didn't notice or forgot. I'll update it and let it run and see what happens.

Thanks @Techman. I created a new program with only the schedule condition to trigger at dusk minus 30 minutes and no other conditions. Its first "next scheduled runtime" is tomorrow, thursday at 5:53pm, and dusk today day is 5:17, so it will be a few minutes before that. Wondering if you or someone could create a test program like above with the only condition being if time = sunset - 30 minutes, save it and then look at next scheduled runtime. If it doesn't happen on other systems then I'll know it's something specific to me and I'll submit a ticket. Thanks in advance if a couple of people are willing to try that

I'm guessing its dst related, but I'm writing new programs on a new eisy so can't be 100% sure I'm writing programs that look at time. At this point I'm not worried about the one running the next day vs today. The problem is the "next runs" are all times that look correct for before DST took effect.. an hour after the sun has set. The eisy reports the correct DST at the top, but next run is ~1 1/4 hour behind. Am I doing something wrong? The "Lights on at Dusk" program was working as written before the time change Take a look: (Sorry about the eye strain on the last one, it can be "zoomed in on"

I have an eisy with the latest iox. While my system did successfully change time related to DST, I have a problem with this program: Lights on Dusk - [ID 0003][Parent 0002] If Time is Sunset - 30 minutes Or ( 'Premise Lighting / Back Patio Lights - Kitchen' is switched Fast On Or 'Premise Lighting / Back Patio - Living Room' is switched Fast On ) Then Set 'Premise Lighting / Premise Lights' On 75% Else - No Actions - (To add one, press 'Action') When I look at the program summary tab, it's next scheduled for tomorrow @ sunset - 30, not today. I had this same problem initially when I first set up my eisy.. I wrote this program, earlier in the day, and the "next scheduled run" was the following day... not the day of as it should have been. The problem cleared up after letting it run the following day and its been fine... until DST change. I have 2 time of day programs that shut these lights off at specific times and they are both scheduled appropriately. I just rebooted the eisy, no change.