MrBill

@Andre DouyonAre you running the official release of Oracle Java 8 from https://www.java.com or some other distribution? UD only supports Oracle's Java 8, you may have success with a different Java distribution, or you may not. Clear your java cache, you must check the box for "Installed Applications and Applets" Also delete any files you see named start.jnlp or admin.jnlp then download a fresh copy of start.jnlp from this link: https://isy.universal-devices.com/start.jnlp The first time it is run it will re-install the ISY Launcher icon on your desktop.

Clear your java cache, you must check the box for "Installed Applications and Applets" Also delete any files you see named start.jnlp or admin.jnlp then download a fresh copy of start.jnlp from this link: https://isy.universal-devices.com/start.jnlp The first time it is run it will re-install the ISY Launcher icon on your desktop.

Interesting. I have no explanation. Check Program > Summary tab and see if all 3 of the Variable Control 2 programs like this one: HVAC- Variable Control 2 - [ID 003C][Parent 0038] If 'HVAC-Dry / HVAC-Heartbeat' is switched On Or 'HVAC-Dry / HVAC-Heartbeat' is switched Off Show as Running Then in the Activity column .

Since there is another thread on the same topic down in the Mobilinc subforum I'm going to ask the moderator to lock this thread. The original poster here has resolved his problem, the Moblinc connect issue should continue at the thread linked above.

Also be aware that if you're using Mobilinc connect you will need convert to the ISY portal to use UD Mobile. It should also be noted that with the original Mobilinc apps (pro, HD, and Orchestrated) can be configured with the ISY portal. (I think for Mobilinc X the user has to pay a one time fee to use X with the ISY portal....not an expert in that area tho.)

For the record, when I made my second post in this thread I had a sneaking suspicion that there were two different problems: the OPs where he needed to reboot, and a second problem perhaps with mobilinc connect. What I couldn’t tell yet was wether or not OP also suffered from the second problem.

That's correct. The devil in the details is the definition of "close". 18" might be too close... i.e. over modulation... the human analogy is that when a sound is over amplified we can't hear it correctly because it's too loud. On the other hand it's a known fact the 500 series has a weak transmitter.

Is the problem with MobilincConnect? Mobilinc pro is working fine for me thru the ISY portal. However I don't have MobilincConnect or Mobilinc X.

I had exactly the same question when I saw that. You beat me to posting. let's tag @bpwwer.

@paulw Have you rebooted the ISY yet? If not, do that and try again.

Pretty sure it's just looking for an Http 200 OK response. The "Net Module Rule: 68" portion of the error message just indicates that it was Network Resource number 68 that caused the error.

Make sure that you have the Oracle official Java 8 from www.java.com there are a bunch of other distributions floating around with other numbers, those aren't Oracle Java releases. Also make certain you are using The Isy Launcher which is linked above it ends in start.jnlp. The first time you run that program it will install an icon on your windows desktop called ISY Launcher to open the admin console. The method you are using in the Screenshot above has been deprecated due to browser security. Opening the admin console now does not involve any browser.

Just out of curiosity, if you disable the query all program for testing, does the lock work the next morning? (to disable the program right click the program name and pick disable) Also are you using the most current firmware release for the 994 or Polisy? If not, upgrade the firmware and retest. if it still persists, it sounds like you found a bug to report, open a ticket support@universal-devices.com

+1 for that. I try to minimize what needs cloud access. I also don't particularly care for required services. It hadn't completely gelled with me until this discussion that PG3 required so much phoning home.

Even if it wasn't hysteresis @apostolakisl program examples should solve your problem. Once the notification is sent the sensing program is disabled until the temp falls. You can arrow that gap hysteresis if you want, just follow the example so that program 1 gets disabled.

It's too bad that portal login didn't become the front end login for PG3, that is to login to PG3 the user logs into portal. (then the fact there is no method to reset a PG3 password wouldn't exist!)

2 programs 1st program: If 'SensorPushNodeServer / Media Closet' Temperature >= 87°F then (blank) else (blank) ------------------------ 2nd program If 1st program is true then notify else (blank)

I think the problem is the from address line, which we can't see from your screenshots. Double click the Customized Content in the admin console. take a look at the from line of the Window that pops up. the format in that box is supposed to be Name:email@example.com with the : being an important separator between two fields. Also Please note: After you click OK to close that dialog box, YOU MUST ALSO press the save button at the bottom of the window that opened it. Personally when i was using email for notifications I always left the FROM line on the individualized content blank to accept the server default. You need to be careful with the Second part (after the colon) of that field. Many spammers use that to alter the displayed from address... likewise in 2022 if the from specified there and the actual account don't match your email can get flagged as spam.

no need to restore PLM after a power outage. also as mentioned... link counts are difficult if you have a large number of devices and a large number of wireless devices. Programs can be disabled. Link count can be done while no ones home to flip a switch.... BUT heartbeats from wireless sensors will also throw off the link count. It should be understood that the link count is thrown off by large margin's... not 1 or 2 or 3. When a signal interrupts, the link count continues from the address of the device that interrupted... meaning huge blocks of links can be skipped over or counted twice.

to echo this it's literally ANY Insteon communications. I have over a dozen battery powered devices that send heartbeats, and a single heartbeat will screw up the link count. Disable programs, cover motion sensors and do many links counts in a row until you get the same number more than once, that's probably your link count. why are you needing to rebuild after a power outage? I literally do nothing after a power outage. And what specifically do you mean by "rebuild"?

There were several versions of that item, as far as the ISY is concerned they all work the same, thus the inclusion under the part number they were known by. I believe one model specifically meant "retail packaging". I'm not sure immediate/delayed applies to ISY. I have alot of open/close sensors, they can be included in a scene to turn the light on when the door is open, or they can be used in programs with either control or status. I have many that control lights via a scene, some that control lights via a program. All door sensors are included in away mode programs to let me know something has been opened while away, etc. retires is simply communication retries. You shouldn't need retries > 1, if you do then you have a different communication problem that you should attack instead of increasing retries.

I don't restart them often either, but there always needs to be a plan. (I did need to login to PG2 from Mexico once earlier this year, but it turned out the node server was working, I just didn't think it was.)

I would hope that there are plans to expose PG3 through the portal. Currently if I need to log into PG I need to connect to my home network via VPN. Those who don't have a VPN server would probably just open ports and expose it. It's not possible to assume that node servers will stay running and not need to be restarted. If someone is on vacation they may need a method to reach their PG instance.

did you restart the admin console? the node servers profile is only read when opening the admin console.

only sales@universal-devices.com could tell you whether the 500 series 994 board will ever be in stock again. (I don't know how many they have to order at a time, but if they have to buy a larger rather than smaller qty I doubt they will). other than that, yes 994 development has ceased. there will be no new anything hardware or software. They will as they have done with version 4 issue maintenance releases to the firmware as demands require (things like DST changes, expired certificates, default mail server changes, etc)... but the 994 is at End of Life and won't get anything new...