MrBill

You must not be old enough to remember the 2 years during the Arab Oil Embargo (circa 1973) when Nixon suspended the switch for 2 years. In my location in the world it didn't get light outside until after 9am in the winter months. I'd go for standard time year round, or the shift that we follow now. I hope we never have year round Daylight Saving time again, it was awful. (caveat: Realize that Sunrise does vary across the time zone, the further north the worse winter Daylight Saving gets.)

FIRST, Have you installed Java? Hint, a higher number following the word Java doesn't mean better, it means different version, different purpose, different features. Specifically, you want to install Java 8 from https://www.java.com (you might get other versions to work, but you're on your own for java platform adjustments to make it work, Java 8 is the intended supported version of Java. Second, Install The IoX Launcher. The first time IoX Launcher is run it will both install an IoX Launcher icon on your desktop AND start your first admin console instance. In the future use that Icon to launch the admin console. (the IoX Launcher icon is different that just re-running the start.jnlp file that is downloaded to install.)

I hope you meant to type that you did not anticipate the reset to default. After all there is an entire section in the upgrade instructions on the topic: Security was upgraded, there was no way to decrypt your old credentials then re-encrypt.

Some MAC users can never get Launcher to work correctly, others use it everyday without issue. If Launcher doesn't work for you the alternative method is to download the admin console from the ISY itself... http://IP.OF.THE.ISY/admin.jnlp (replacing IP.OF.THE.ISY with the actually IP address such as 192.168.1.222 etc) Save the admin.jnlp file to your desktop and use that to open the admin connsole. the downside to this is that some people run into browser security issues and the admin.jnlp file must be deleted, java cache cleared, and re-downloaded anytime the ISY's firmware changes. the admin.jnlp file used here must match the firmware of the ISY, when using Launcher the correct version should always be used automatically.

You must mean you have the button set for "non-toggle Off". In that case pressing the button sends "off" (or "fast off" if double clicked). If the button is a scene controller all members of the scene will get an "Off" (or "Fast off") when the button is pressed (or double pressed. You said you created a scene and a program? Please tell us more about what each does, do you need both? If you want to set a Scene ON from an "Non-toggle off" button you can do that.... If Button.B is switched off or Button.B is switched Fast Off then Set Scene1 'On' else (nothing) Another way to turn off a buttons light after a program has run is the make a new scene, with just that button as the only member... Button.B.Scene... Then do something like: If Button.B is switched on or Button.B is switched FastOn then ....do something... ....do something else... Set Button.B.Scene "off"

True. I use THIS group of programs to identify that a DST time adjustment occurred, then restart the looping programs. Note there are programs that are set both "disabled" and "Run at Startup" in that group. Those are important settings.

...and "Sunset" as the only condition is only true for 1 second, at sunset.

I have a program for each transmitter, that is manually run from a Home Assistant dashboard: FrontDoor.reset - [ID 01A4][Parent 01B5] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Resource 'NotificationNS.DoorTrouble._resetCountersBegin' Wait 1 second Resource 'NotificationNS.DoorTrouble.FrontDoor' Wait 2 seconds $iDoor.FrontDoor.HBmissed = 0 $iDoor.FrontDoor.HBmissed Init To $iDoor.FrontDoor.HBmissed $iDoor.FrontDoor.BatteryDays = 1 $iDoor.FrontDoor.BatteryDays Init To $iDoor.FrontDoor.BatteryDays $iDoor.FrontDoor.TransCount = 1 $iDoor.FrontDoor.TransCount Init To $iDoor.FrontDoor.TransCount Wait 2 seconds Resource 'NotificationNS.DoorTrouble.FrontDoor' Wait 1 second Resource 'NotificationNS.DoorTrouble._resetCountersComplete' Run Program 'hb.FrontDoor' (Then Path) Else Resource 'NotificationNS.DoorTrouble.FrontDoor' It spits out a message that the counter will be reset, then gives the old totals before resetting then resets and outputs the rest counters and another message. Seems like overkill on messages but it is nice to have the final counts before reset.

First get rid of any files named admin.jnlp or start.jnlp that you have laying around. next clear the Java cache including Installed Applications and Applets (which is a box you need to locate and check, it is not selected by default) are you using a Mac or Windows? Windows it's best to use The Launcher. The first time Launcher is run it should also install an icon on the desktop called IoX Launcher, use that to start the admin console in the future. The first run does two things 1)install desktop icon, 2)start admin console. Mac it might be the same launcher (use link above), (some users have no issue, other users can never make Launcher work on Mac)... if launcher doesn't work for you... download admin.jnlp from the ISY... https://IP.Addr.of.isy/admin.jnlp and move it to your desktop. (Anytime ISY is upgraded that file must be replaced after firmware upgrade.) Launcher should get the correct admin console each time it's opened from a cloud source.

I use the Kasa KP115 a couple of places where I want to make certain the device is actually consuming energy. (ex: pipe heat), otherwise I use the less expensive version, 4 for the same price as 1 KP115 but without energy monitoring and just rely on status to decided if it's been left on. Note: Your post didn't say anything about outdoor requirement, but your example is an outdoor device.

I don't think there is a substitution for the strings your looking for. You can crudely get what you want by using 2 integer variables (in addition the one your already using). Integer variables in an ISY can have a decimal value these days (when they were originally named they couldn't), and the decimal should be set to 2 for these. One for date and one for time. These don't need to be state variables. In your program that increments the activity counter add lines to set those variables such as: $iDoorLastOpen.date = [Current Day of Month] $iDoorLastOpen.date /= 100 $iDoorLastOpen.date += [Current Month (Jan=1, Feb=2, etc.)] $iDoorLastOpen.date Init To $iDoorLastOpen.date which will yield and integer variable value such as 2.16 (today). likewise build similar for time using [Current Minute] + [Current Hour] $iDoorLastOpen.time = [Current Minute] $iDoorLastOpen.time /= 100 $iDoorLastOpen.time += [Current Hour] $iDoorLastOpen.time Init To $iDoorLastOpen.time this will yield a time in the same format 16.38 (I assume the hours will be 24-hour format, but I've never used [Current Hour] for anything before. Unfortunately the separator is . instead of / or : however this is one method to achieve being able to read the date/time in the notification.

You're correct. I have many (20+) Insteon battery devices and have a heartbeat program for each. I also have a dedicated Network Resource to send the notification via pushover. I haven't kept up with the @Jimbo.Automates Notification Node Server. The PG3 version may have some help for the need to create multiple notifications. (I'm still using my 994 and PG2 for on my live system.. whenever eisy becomes stable I'll move on). I made an Excel tool for creating repetitive Network Resources for my heartbeat and wireless tag notifications where I need multiple Network resources that are almost alike, if anyone wants it send me a PM. Here is an example: Each battery device has 3 integer variables, all 3 are reset when the battery is changed. "missed" seems to be most relevant for surface mounted insteon open/close sensors, they tend to miss random heartbeats, but that doesn't mean they are dead. The example here is that type sensor, and it missed today, but the last time it missed was 12 days ago. The Heartbeat program I use is: hb.FrontDoor - [ID 0066][Parent 0072] If 'Door Switches / Front Door / Front Door- Heartbeat' is switched On Or 'Door Switches / Front Door / Front Door- Heartbeat' is switched Off Then Wait 24 hours $iDoor.FrontDoor.HBmissed += 1 $iDoor.FrontDoor.HBmissed Init To $iDoor.FrontDoor.HBmissed Wait 2 seconds Resource 'NotificationNS.DoorTrouble.FrontDoor' Run Program 'hb.FrontDoor' (Then Path) Else - No Actions - (To add one, press 'Action') For Insteon hidden open/close sensors I use 24 hours since the heart beat "wait", which is every 21 hours (or something like that), surface open/close and leak sensors I use 25 hours for the "wait". The 2 second wait is because there needs to be a brief wait after the counter is updated before the notification is sent or the old value will be sent. It loops by running itself as the last line.

you might be missing a . Humidity: ${sys.node.node003_wh31_3.CLIHUM}

What happens if you go to https://192.168.12.31:8443/rest/subscriptions (you should get prompted for credentials, it's your admin console credentials it's asking for) (note, on purpose that's not the same url as the ws:// url above, its only simmiliar) That might tell us if you have the IP address correct, but I might not tell us much if you use subnets for IoT etc... then you're probably into your networking rules, especially of the IP of the ISY and eisy are different.

I do see the notation "not saved" in your current screenshots, not sure if that's the result of a current change or because it needs re-saved. Other things to verify: 1) Help > About... are the firmware and UI versions exactly the same? 2) the Programs > Summary tab... look for Yellow...

I find they are both very powerful, perhaps equally, but they are very different.

Don't get blinders on that the only source of noise might be the hot water heater and blower-- that was just a good place to start since motors are always likely candidates. I haven't had to do this for ages, but years ago I had to identify the network/router/ISY/PLM breaker, then turn off half the breakers at a time, then test, then the other half and test... then half of those... etc until i had the source of noise narrowed down to one circuit. Turned out it was a kitchen countertop appliance, just keeping it unplugged most of the time was the initial solution, it's since been replaced. This can be caused by a lot of things. Programming that's in error, inclusion in scene, or bad links stored in the device. That's likely device links that have become messed up. I would start by selecting each device in the device tree one at a time, right click and pick "restore device".. Be patient this will take awhile to get thru. This re-writes the devices links to what the ISY expects to be there. I don't expect that problem 1 (hot water) and problem 2 (balcony lights) are the same issue. My guess from what you've said here is that problem 1 is a noise/signal issue and problem 2 is a bad link issue... but 2 may have originally been caused by noise or poor communication.

@K-bert The Z-wave backup is saved on the 994's MicroSD card. Subsequently when you back up the 944 that file is picked up and included in the backup.

Yes I would definitely try anything to see if you can change the behavior. Either unplugged, plugged in somewhere else, or even just experimentation. make the hot water heater run and see if it fails consistently when it is. Filterlinc is Insteon's plug-in filter. I think it was supposed to return to the shelves in January (from a November slide I have saved from an Insteon event), checking the stock on insteon.com now tho, I'm not spotting the item. A number of people have suggested other filter options over the years but I'll let them chime in when they see this post.

@JMcKain try deleting your .state files https://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored

The first thing I would question is if the problem occurs when the gas water heater that's plugged in is running. Normally I'd guess that it's not... that 90% of the time it works... it's running for some other reason and a signal is sent to the plug to turn the other outlet on and it never arrives due to noise. If that's the case a noise filter may be needed for the gas hot water heater/blower.

Sean I have no additional solutions for you. I know nothing about running java under linux. As @Geddy mentions, i'm not sure any of the forum regulars do.

There is an AMAZING Home Assistant integration that works with all versions of the ISY (ISY994, Polisy, eisy).

You say this is a long standing issue, did it ever work correctly? If you're seeing the ON value in the admin console, but the outlet has not turned on, that sounds more like a communication issue. There are many possibilities from bad device to noise makers and signal suckers. I just checked and 2663-222 does appear to be a dual band device, so that's good. Being intermittent makes it even harder to track down. If it consistently fails, you could open the Event Viewer and set level 3 in the dropdown, then try to capture failed communication traffic. Post the failed output in this thread and someone that amazing at reading the Event Viewer will likely come along and interpret it. Keep in mind, posting event viewer traffic where the outlet did turn on won't tell anyone anything, only when the admin console changed to ON but the outlet didn't turn on. How far away is the nearest dual band device? Perhaps try adding something closer. If it fails frequently enough that you can test, I'd turn off and unplug things on the same circuit as the pump and see if it works more consistently. If its a noise maker cause the problem, sometimes its possible to track those down turning off whole circuits.

I hadn't noticed that slot until this series of posts... and you're right it's probably an unsupported port, but OMG wouldn't it have been nice if UD had used it for migration. Pop your MicroSD out of the 994 pop it into the slot on eisy and watch the migration move forth.