MrBill

My understanding is that the portal had to be modified to make way for portal access for PG3. The problem however is that an unexpected reboot was forced on all PG3X (limited to eisy at this point). The circumstances were unusual, and I'm not certain how the issue could have been mitigated, but an unexpected reboot when the customer may not be available to fix any issues that come up is not excusable. I've generally worked out all the issues that I once had on reboot, but I'd still be uneasy about an unattended reboot.

And I'll add that UD never discusses release time frames. The organization is small, priorities can change rapidly to promise a release is virtually impossible. We actually don't know that 5.6.0 will be the number of the next release. While the version numbering system of UD Mobile seems to be incrementing the middle digit after the minor release reaches .9 that's not the way firmware versions have followed in the past... i.e. the next release may be 5.5.10

is it an eisy? if so, is it connected to portal? If so, the cause of the reboot this morning is known and unrelated to this thread.

There are many bad UX's issues with the admin console. Unfortunately fixing those is virtually never a priority to UD.... One that I complain about frequently is: How does this screen work? If I change any of these 5 values, do they change instantly after the dropdown is adjusted, or do I need to press "write changes" perhaps? or something else? The correct answer is "Or something else" that is not remotely intuitive to the user... Change a drop down, then you must press the corresponding button that looks more like just a label to the LEFT of the drop-down. That answer is virtually impossible to guess. Another good question.... why are Integer variables [still] called Integer variables? After all they can have a decimal [now].

Fri 2023/03/24 07:21:49 AM 0 -5 Start IoX started at 07:21:49 AM.... sure seems like it rebooted to me...

Perhaps your eisy went through a random reboot, someone I was chatting with indicated they had one this morning with eisy... unclear what's causing those. Unfortunately the platform is still going thru some growing pains.

Every Insteon device in your system contains links which contain the PLMs hardware address. (just like switches etc, the PLM has an Insteon address in the form 12.34.0B) When the PLM is changed, ALL of your insteon devices must be updated with the new address. Yes, for large systems it's large project that can result in hours of "system busy" and there will probably be errors along the way that require some devices to be "restore device" again after all is done. Changing the PLM is not something to be done on a whim.

For eisy/Polisy 2413U is the best choice. 2413S can be used but you then also need a serial to USB converter cable.

I don't think that portal functionality has been yet enabled. I can't seem to find the reference this morning but somewhere in the past few months I've seen seen discussion that work is being done to make node server accessible through the portal, but that hasn't actually happened yet. Lack of the ability to access node servers through portal, even just to restart them, has been a missing feature since Polisy was invented. I think we are close to resolution on the that issue, but we aren't there yet.

@KConover If you haven't yet discovered it.... Scene's appear AFTER devices in the "Your Devices" list. Scenes are preceded by the icon instead of the device icon

keep an eye out... i bet they return under some condition. I doubted it was the GFCI from the start which is why I suggested something downstream of it.

I'm curious if it's the actual GFCI causing the interference, or a device wired downstream of the GFCI off the line side terminals. As far as leaving it off or on, I'd choose off if you can do without it until you pick up a replacement. Less interference of signals/noise is always better. I get where you're coming from with the power interruptions, it's a pain to reset clocks and whatever else is different because the power was off. That is about the fastest method to track down the offender tho.

Something is generating stray noise that looks like X10 traffic to the PLM. Interesting that its Status request, house code J because status request in binary is 1 1 1 1 and house code J is binary 1 1 1 1 the start frame however is 1 1 1 0 and the final bit is 0 when the frame is a unit code and 1 when it's a command code... so if I remember the whole frame is start code, house code, function code, final bit or in this case 1 1 1 0 - 1 1 1 1 - 1 1 1 1 - 1 (dashes added for clarity) And it appears to be repeating this "frame" with great regularity. It might be an older insteon device (early insteon was capable of having an X10 address) that has gone rogue, Or it might be something else. To find it use process of elimination. I tend to do this quickly by turning off half the breakers, then if not found the other half, once we know which half has it (without turning off the PLM/ISY circuit) then i turn off half of that half and keep working with halves until i have it down to 1 breaker.... once you know which breaker it's on then search that circuit.

As @DennisC mentions upgrade to the latest version, but since this is posted in the ISY994 section of the forum there are a few things to bring to @kurelgyer's attention. If upgrading from V4 to V5, you should read the directions and then we should discuss that further before you actually do it, there's a few points that are important and a caveat or two.... If you're already on v5 there are two possible endpoints for you. If you don't have Z-wave, or have a 500 series z-wave board, then upgrade to v5.3.4. If you have a 300 series z-wave board, you can't go past v5.0.16C. It should also be noted that ISY994 is at end-of-life and no longer receiving non-critical updates. To upgrade to eisy you need to be on the latest v5 firmware before migration.

Before you can install the launcher tho, let's make sure you have to correct version of Java installed. Many people think they need to search google or oracle.com for the "latest version of java" which is wrong because like tomatoes in ketchup there are at least 57 varieties of java. Download and install Java 8 from https://www.java.com (if you've already installed a different Java go uninstall it first). Java 8 is the supported Java for UD's admin console. Other varieties of Java may work but probably not "out of the box", meaning you have to know how to configure it to work the way Java 8 works as soon as it's installed. With Java a bigger number is not better, its a different variety... you need Java 8.

Correct that's all you should need to migrate. I have an eisy but haven't yet migrated. I was going to in early January but ended up waiting for various reasons, now I just need to find the time.

No, as mentioned above download Java 8 from https://www.java.com , Also be sure to uninstall the SE SDK first...

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.