larryllix

I think @Brian H was keeping score years back. I would be sure a raspy sinewave voltage would make the caps work harder to smooth off those sharp edges. Some have had many PLMs burn out, while others have never had a problem with their first one. I still have my original PLM from 2016? but it was retired for a USB unit on my polisy. I suspected it at one point in time, and replaced it for a few months, but returned it to service after I tested the "spare".

Possibly it could but I have avoided NSs mostly as they were residing in another box at the end of a cable and via switches and routers. I prefer sources of data as reliable as possible. On power up how long would it take for a NS to have accurate data available? My guess would be about 30-60 seconds after other programs have already done things based on time 00:00.

Thanks. OP corrected to include "Not triggered" The truncating of superfluous decimal is a problem for appearances for sure. We want floating point...usually. $sSys.MM.DD init to $Clock.scratch? IIRC there were cases where the variables were not initialised before programs attempted to use them. It may have been a quirk in the system time parameters. Only more recently, did I discover you can [Run at startup] and redirect the action back into the Then section after the [Run at startup] typically evaluates to False and runs Else. Also, IIRC there may have been an intermediary version where the startup process did not evaluate in proper order? It may have become redundant now. Very observant!

This may be of interest to some involved with seasonal lighting, using programs that are year independent. In the past we had to change our date triggers due to the year portion being static. Here is how I accomplish this task using my favourite little engine that could....ISY The Date Variables First we use the system variables to create a variable indicating the month and date of the month. I shift the resultant two decimal points so it looks nice to the user and can be used to create filters that will respond for 1, 2,3, 10 days or the whole month by eliminating the comparison decimals and only using a whole number representing the month. This requires creation of several state variables containing two decimals of precision as well as several Integer variables for calculation usage. These are necessary so that programs triggered by state variables are not triggered erroneously every time an intermediary calculation result is obtained. Only the resultant is actually transferred into the State variable. State variables are prefixed with '$s' in my system $sSys.MM.DD contains the month and day, both using two decimal numbers 01.01 to 12.31 $sSys.hh.mm contains the hour and minute, both using two decimal numbers 00.00 to 23.59 $sSys.hh.5mm contains the hour and minute, both using two decimal numbers, except it only updates every 5 minutes 00.05 to 23.55 This variable can be used to trigger cyclic programs that you only want updated on a 5 minute basis in order to not flood ISY with unnecessary processing or excess traffic on your device protocol Eg: excess Insteon traffic when you slowly dim lighting in the evening. clock.sync - [ID 0003][Parent 0002][Run At Startup] If // Run at Startup enabled Time is 12:00:10AM Or Time is 6:00:10AM Or Time is 12:00:10PM Or Time is 6:00:10PM Then // update $sSys.MM.DD $Clock.scratch = [Current Day of Month] $Clock.scratch /= 100 $Clock.scratch += [Current Month (Jan=1, Feb=2, etc.)] $sSys.MM.DD = $Clock.scratch $sSys.MM.DD Init To $Clock.scratch // update $sSys.hh.mm Repeat Every 20 seconds $Clock.scratch = [Current Minute] $Clock.scratch /= 100 $Clock.scratch += [Current Hour] $sSys.hh.mm = $Clock.scratch // update $sSys.hh.5mm $Clock.scratch.noFrac = [Current Minute] $Clock.scratch.noFrac /= 5 $Clock.scratch.noFrac *= 5 $Clock.scratch = $Clock.scratch.noFrac $Clock.scratch /= 100 $Clock.scratch += [Current Hour] $sSys.hh.5mm = $Clock.scratch Repeat 1 times Else // Run at startup will evaluate False Run Program 'clock.sync' (Then Path) Program Usage Now we use these variables in programs like this Christmas lighting one. Note the multiple times and multiple date combinations in use. Also my lighting scenes are driven off State variables that trigger banks of lighting scenes. I find not directly operating lighting scenes offers much more control and simplicity of programming the end user logic. Making later changes becomes a snap. A special note should be given to date ranges that include the end of the year. The range dates need to use "OR" logic, not "AND". IOW: we are saying after Nov.15 or before Jan. 07 since contiguous numeric dates stop at 12.31 and start again at 01.01 without any break in the calendar dates. XmasTree.onOff.inititiate - [ID 00D8][Parent 00D7] If // Vocal input also ( Time is Sunset - 15 minutes And ( $sSys.MM.DD >= 11.15 Or $sSys.MM.DD <= 1.07 ) ) Or ( Time is 5:00:00AM And $sSys.MM.DD >= 12.24 And $sSys.MM.DD <= 12.26 ) Then Set 'Dining Room / Christmas Tree' On Wait 7 hours Run Program 'XmasTree.onOff.inititiate' (Else Path) Else Set 'Dining Room / Christmas Tree' Off Simpler Usage Eaxmple Here is another example of using this system. This is a theme setter for Independence day. Note the usage of the ISY native time trigger ANDed with the $sSys.MM.DD variable to achieve this. Festive.set.USA - [ID 0083][Parent 007D] If Time is 12:10:00AM And $sSys.MM.DD is 7.04 Then $Festive.theme = $cMODE.USA $Festive.theme Init To $Festive.theme Else - No Actions - (To add one, press 'Action') Canada Day Date Range Program Example Festive.set.CanadaDay - [ID 007B][Parent 007D] If Time is 12:10:00AM And ( $sSys.MM.DD >= 6.25 And $sSys.MM.DD <= 7.02 ) Then $Festive.theme = $cMODE.CANADA $Festive.theme Init To $Festive.theme Else - No Actions - (To add one, press 'Action') Christmas Date Range Except New Years Day Example Note the combination of IS native time trigger ANDed with a date range and the New Years Day exclusion logic. Festive.set.Xmas - [ID 0081][Parent 007D] If Time is 12:10:00AM And ( $sSys.MM.DD >= 12.01 Or $sSys.MM.DD <= 1.15 ) And $sSys.MM.DD is not 1.01 Then $Festive.theme = $cMODE.XMAS $Festive.theme Init To $Festive.theme Else - No Actions - (To add one, press 'Action') Hope this inspires other programmers to be more creative with their ISYs. They are as powerful as your imagination. The cloud is the limit!!

The system has several system date and time variables that can be used but only on the right side of condition equations. I have created a few cyclic programs that update state variables so that I can create year independent programs that will operate seasonal lighting events. Time only triggers can be created in the "If" section native conditional logic.

@Michel Kohanim@bpwwer Has anymore thought been given to upgrading the modulus function to floating point? I didn't see it in IoP v5.4.5 upgrade

aartech.ca has this alternative on sale right now for only $1149 CAD. Sale ends tomorrow and it goes back up to $1378.62 CAD. It should perform as well as a polisy pro. You may need to add some I/O to it to make it work with your HA system. HomeSeer Pro

Yup. My routines started working again overnight now.

Same problem with routines again. Triggers from ISY go all the way through to display the change of state in the alexa app but the routines are not triggering like they did a week ago. Something set the alexa routines into misbehaving again. Last time amazon had to correct something but it seems the disconnection broke the Routine triggering again. Routines have been checked as still all enabled, tested for voice output from the manual trigger, and trigger point tested from ISY. Must be something that breaks the Routine internal logic. UPDATE: Routines began working many hours later. Rebuilding them, and dis/enabling them, did nothing but sometime in the middle of the night they repaired themselves.

Mine came back by itself except that I disabled the skill and it had to be re-enabled again. Routines will likely have to be re-enabled after pseudo devices went MIA. Thanks @bmercier

Mine came back up and reconnected by itself. However I had to reconnect my ISY Portal and amazon account skill again after the bad advice amazon app gave. hmmmm...routines likely need rebuilding and enabling again.

@bmercier Same here. ISY Portal server must have crashed.

@Michel Kohanim Nothing. ISY Portal has crashed.

No. The box contained about 40 Insteon devices. When I first grabbed the device to unplug it from the chain of OnOff modules it seemed totally intact. When I attempted to pull it out of the receptacle less than about 1/8" it shattered between every plug pin. As I began to wiggle it, in order to reduce further damage the device let go inside on all mounts and the electronics began to expose themselves as the device split apart. At that point I realised it was going to be garbage and pulled harder. I have been storing spare devices like this for years. Never happened before but maybe I need to examine the rest (and maybe lube the pins before putting any back into storage). I need to reduce my spare parts storage and this seems like it would serve that need well. *SIGH* If this was due to shock of some kind, then somebody hit it directly with a hammer. It shattered like glass when I pulled on it.

It was existing from Win 10. Still sounds like his problem though. Sent from my SM-G781W using Tapatalk

@RGKS

Yeah but...new company and I wouldn;t hold old devices against them. I want them to succeed, either way. I have never had one do this before. This one just disintegrated in my hand as I pulled it out of the other Insteon device. First it fractured between all the plug pins and then as I tried to not fracture any more it pulled apart as all the mounting pins broke apart. I remember Teken posted about this a few years ago and found it hard to believe. Hopefully it was just one production run of some cheap plastic.

I hope they improve the designs, all the way around. I just this got unit out of a storage box, never been used, but was plugged into another device in the storage box. It has never seen UV or heat. I am just glad it was not alive while I tried to wiggle it out of the other device's receptacle. Plastic broke in about 8 places, between AC plug pins and mounts of the electronics inside. Never seen service and now garbage. @Tekenwas right on the money. Insteon found another way to make them cheaper. Glad that guy is gone.

Java is likely one of the most popular programming languages in the world still. I doubt you will see UDI move away from java. There would be no advantage. The admin console runs in java and is not related to, or use, any browser. Your java firewall is likely blocking it from running freely and will need to have permissions installed to allow the admin console to run. There is a security tab in the java setup app, found in your Windows Control Panel Browsers use javascript language. The two are not similar or related.

Why do you want a Pro version?

Not on your Desktop. It would be found in your "Downloaded Documents" folder and I doubt it is java. The admin console will be java after the downloaded app loads it.

This process becomes more crytic and hidden every improvement of Windows and ISY. Gives users something to do. For windows 11 here is what I had to do. Run the URL from your posted step 4 above. Select "Save File" from the options. This will create a file called "start.jnlp" in you downloaded files folder in Windows 11. I have my "Downloaded Documents" moved to my Desktop. I hate Windows always attempting to hide everything. The icon will be some unfamiliar avatar you may have never seen before. Click your "Start" button on your task bar. Select "All apps" on top right corner. Now search down through your app list for "IoX". Right click on it, select "More", and "pin to taskbar" Now you should have the familiar icon/avatar show up on your taskbar for easy launch of the new renamed "IoX" = ISY launcher.

I don't think polisy and the z-matter board go together???? Sent from my SM-G781W using Tapatalk

...I have two ISYs and now two policies now and they are all going obsolete due to loss of hardware availability. The polisy boxes still have software bugs yet also. * sigh* Now a new hardware box is being released shortly again. Who ya' gonna call? Sent from my SM-G781W using Tapatalk

I had at least one sun dependent program fail to run and when I examined my a/c I found my clock out four hours and my sunset/rise times out about 1-2 hours. I power cycled my polisy, reloaded my a/c and the errors would not change. Ran the firmware update and still had a clock that would correct itself for a while and then jump back four hours again later. Clock would correct itself each time the co-ordinates were edited slightly and saved. The next day everything was back to normal. Began to think I imagined the whole thing but my sunset based deck lighting failed for sure. All works like normal again????