apostolakisl

It i just one command, "set armed status night".

This is the same issue I see, this is arming my Elk panel. It succeeded in arming, but I got the message. It is a command type of favorite that sets the alarm system to armed night in this instance. Arming the system also triggers some programs in IoX to run.

You could try a different computer and see if it has the same behavior. Keep in mind you had more issues than just the Java console. I would look into what @Javi said.

I randomly get those errors on ud Mobile as well. The command succeeds, yet I get an error. Unlike the op, I am not consistently seeing it.

This is where eisy ui says I am after the ssh upgrade. It appears I am in the staging repo. I don't know that I need cutting edge features on this polisy, but I would like to be certain it keeps working smoothly, especially with UD mobile.

For what it's worth, I just updated a Polisy as per the above instructions and it seems to have gone off without a hitch. It took just minutes, maybe 10 at the most, probably less. The java admin console and eisy ui both open and everything looks normal. Going forward, I assume i can update using eisy ui update page? Or will polisy continue to require ssh?

Nothing is wrong with your router if you can ping the device using the lan address. I was under the impression that your ISY wasn't showing up on the IoX finder, not that it showed up and you couldn't click on it and get a menu. If you put in the LAN address, IoX finder finds it and correctly shows the firmware version and all, but when you click on the line it doesn't pull up a menu, well that isn't your router blocking it. It sounds more like a Java issue. Completely remove Java from your computer and reinstall it and then download the "start.jnlp" file from the forum. https://forum.universal-devices.com/topic/24381-iox-launcher/ None of this explains why you said your programs weren't running.

By WAN side of your router, you mean your public Ip address and then you have port forwarding setup? If that works, but being a computer on the same LAN can't see the ISY, then something is wrong with your router. You could also just ping your ISY from inside the LAN. Are you sure the computer you are using is on the same LAN? You don't have it on a guest network or some isolated network? And if your computer is on the same WAN as ISY, and you use WAN:port and have your router set with port forwarding, well that usually doesn't work. You usually can't bounce out of and then back into the same WAN like that. Typically you can only do that from a different WAN. Which would also explain why you aren't seeing ISY on your local connection. Another test, from your computer that is accessing isy, open a command prompt or powershell prompt and type ping xxx.xxx.xxx.xxx again where xxx.xxx.xxx..xxx is you LAN ip address of ISY. You should see 4 successful pings. If not, then you are either not on the same LAN (or VLAN) as ISY, or your router is doing something to block you.

By WAN address, do you mean using the portal address? Anyway, that would explain why UD mobile worked, probably you had it configured using the portal rather than a local connection. But if you are logged into the admin console, you can find your LAN ip listed in the settings section and try manually setting those into iox finder as I listed above. Did you set up your isy to have a static address in your router? Iox finder should find your ISY on its own, but if something is going on in your router, your router can block network discovery if configured to do so. I don't know how that would change all by itself, but maybe your router is getting flaky?

Are you able to log into your router and check to see an active connection and get the ip address? With the ip address, try putting http://xxx.xxx.xxx.xxx:8080 (substituting your ip address for xxx.xxx.xxx.xxx) into the java iox finder manually and see if it pops up with the unit being present. If so, obviously open it. Also, try using ssh to log into it. In windows, type "powershell" into the search box to open powershell. from the prompt, type ssh admin@xxx.xxx.xxx.xxx (again, subsitute your ip address) and then the password is also admin which it will prompt you for if is alive and responding at that ip. If you have apple, I don't know how to open an ssh session, but I'm sure you can google it. But again, I would take the earlier advice of a new power supply. I'm sure you have a suitable one somewhere in your house, just be sure it has sufficient amps. I forget what that number is, but look at your current ones amp rating and find one with at least that many amps. This is where power supplies fail, they peter out on the supply amps, so they may register 12v when under no load, but as soon as you start pulling a load, the volts drop. ISY can sort of work under these circumstances, which is seemingly your issue. Also, replacing the plm is likely to cause more issues than it solves. To properly replace a plm, you need to be able to log into ISY and tell it "restore plm" or all of the links will be wrong and that just confuses the issue more. A bad PLM would not prevent your from opening the admin console, so don't blame that on the plm. It would probably be better to boot ISY without any plm rather than the wrong one at this point. Again, my first thought would be a flaky power supply.

Might just ask the forum or chat gpt how to write the program.

I have IoX setup at my church controlling all the HVAC and lights. There are a bunch of people who I want to give access to the system, but setting them up is a bit of a hassle. No way in the world they are going to do a reasonably good job at setting up their own favorites. So, would it be a good idea to backup my own personal UD mobile, then create a UD mobile profile that is good for the church, then backup that profile and restore it to each person's phone? Then restore my own profile back to my phone. Also, do backed up profiles on an Android recover to an Apple?

good to see they are available again. The beauty of PLC is that it just never goes sideways on you, never in my life have I ever had to reboot a WC8. I thought they were done since several times I have looked for them and nothing for sale anywhere. And I bet AI can write PLC code like it wasn't nobodies business.

Further configuration to make most useful in UD mobile. I wanted to have 4 "radio" buttons in ud mobile that worked like the kpl buttons on my wall. I wanted to tap which ever speed and have that speed turn on and have the icon turn red. Press a different speed, and the previous icon goes back to blue and that one turns red. 1) Created 4 virtual nodes using the virtual node plugin. Set them as "switch". Named one each for off/low/med/high. ie, key 78 value switch, key 79 value switch, etc. Restarted the plugin. If the nodes don't show up in admin con, then restart it. Renamed the 4 nodes in the admin con to Fan off virtual, Fan low virtual, etc. 2) Added all 4 of those nodes to each of the 4 scenes as responders (you could set the one that is for that node as controller, ie high virtual switch as controller in high scene, if you wanted to control that switch and have it control the scene. 3) For each controller of the scene (ie, the primary scene, and the kpl button(s) controlling the scene), set the "on level" for each of the nodes to "off" except the virtual node matching the scene (ie, virtual node high is set to be "on" when the scene is on, all others are set to be "off"). Don't forget to do it for each controller. 4) In UD mobile, create 4 favorites, using the scenes as the display node, one each for each scene, set them as "command" type. 5) Add a command, which is to turn on the scene. 6) Change your display node to the virtual node corresponding to that scene. 7) In advanced configuration, set it to turn the node red if value equal to "on" (ff0000). I also had it set formatted value to "-". I added a second advanced configuration that sets the formatted value to "-" when "off". Now it just always has a dash, it doesn't show on/off which is confusing and unnecessary when the icon turns red when on and blue when off. 8) Finally I set the icon to be a fan. I would expect that if you set the virtual node as a controller for the corresponding scene, you could use that virtual node as the primary node in your ud favorite, but otherwise set things up the same. I didn't try that since I already had created the 4 favorites using the scene before realizing I couldn't get the 4 buttons to turn red when its speed was on.

Just doing some programming using the java console. I know you are moving away from it, but something seems to have happened to scene management. If I open a scene on the admin console page, the control buttons (on/off/query) are gone. In addition, if I try to write a program to turn on/off/query a scene, those options do not exist. In programs already written that turn a scene on, it shows "DON", but you can't edit it or write a new program. In Eisy UI, I have those controls. In the screenshot, you can see that bottom section where those buttons would normally be, it is empty. Only option in programs is to write changes. This is on two different computers and having restarted Java console.