Nestor

One handy feature of UD Mobile is “Advanced Status Configuration”, allowing change of icon and colours based on states of other programs and nodes. Will this be an upcoming feature of EISY-UI?

Ran the commands. Looks like it's running in both now. Thanks!

As requested...

response: uid=349(polyglot) gid=349(polyglot) groups=349(polyglot)

Issues with my YoLink plugin sent me back to the admin console where I soon discovered the IoX was no longer connected. After reconnecting my IoX from the admin console and successfully restoring the YoLink, I discovered PG3 no longer works in EISY-UI. Everything seems to be working at present so I'm reluctant to mess around with PG3 in the UI further until I understand what's going on. Is this what's supposed to happen? Screenshot below from EISY-UI (left) and from the connection opened via the admin console (right).

UPDATE: Deleted Plugin entirely and reinstalled. Re-added UAID and secret key. Restarted Plugin and now everything is back.

At first, I thought I had no issues with the upgrade/update but it appears my YoLink nodes are no longer responsive. Here's what I can find: YoLink Setup: Node Server - Offline; Status: Initializing. Remaining Nodes (3). Two door sensors and One Speaker Hub. All are empty. PG3: Yolink Current Status: Connected. No apparent issues. All other plugins are operating as expected. I tried the following: Deleted all nodes from IOx but have been unable to re-add them. Rebuilt Nodeservers but no change. Not sure where to go from here.

Theme toggle works although some text stays white when going to light mode. ETA: I see you mentioned there are still issues.

Successful upgrade here. Followed the instructions including running an ethernet cable from my PC to my router. (It's usually on wifi). Everything was back online 22mins after clicking on the upgrade button. So far so good.

Update: Seems my solution resembles this earlier thread . Thanks to Michel and his prompt response to my ticket, I successfully installed and started eisy-ui by accessing eisy.local via command prompt and following the ssh commands. Thanks

Okay, thanks.

IP address doesn’t work, either. Do I need to enter a port as well?

Successfully upgraded my EISY to 6.04 and everything seems to be working, however when I try to use http://eisy.local or https://eisy.local, I get "connection refused". IOX Finder only displays the usual port 8443 url for the admin console and nothing more. How can I confirm I have eisy-ui installed, and if needed, install it? Thanks

Trying to integrate a new Yamaha Receiver and I keep getting this error when I try to send a network resource command. The accompanying Net Module Rule changes: 12, 58, 59. Tried to locate a definition for the error in the wiki but couldn't find anything. Any idea what they are referring to?

How best to do this? Some background: I have a program that sets an INT variable based on whether certain combinations of doors / gates are open. (0 = secure ; 1 = not secure. ) The monitoring program is used with a door chime so that I receive an alarm if a gate is not secure when I let my dog out into the back yard. It's a straightforward program with lots of ORs so I won't bore anyone with it unless someone feels it's relevant. Along with this program, I created a folder in UD Mobile with mapped values based on the status of said variable. Inside the folder are mapped-value icons of the various doors and gates being monitored. If the folder icon/colour indicates "not secure", I can tap on the folder to reveal which gate / door is open. Everything has been working well until one day when I just happened to open the folder (which was "secure" status) only to find one door was indicating the blue "default" icon prior to mapping. Further investigation revealed to be a dead battery, which after replacing, restored communication however this has revealed two issues: The default icon/colour of the sensor with the dead battery indicates an indeterminate third value which I haven't mapped, but I can't figure out what that value is and I don't know how the EISY got to that state. The indeterminate state described in (1.) will not cause my program to indicate "not secure." I tried simulating the node loss by removing the battery while the sensor was indicating the door was "closed" however the variable doesn't change. EISY still thinks the door is closed even after forcing a run-if. Forcing a query in either UD Mobile or the admin console while the door sensor battery is removed gives an error message, but it doesn't change the output of my program. Any ideas how I can integrate this node comm loss into my monitoring program? Thanks