keepersg

That did it! Thank you very much for your efforts to solve this. Much appreciated. Among, other things, I use the solar radiation value to determine whether the green house lights stay on during the day. Particularly important in the early part of the growing season here in the Northwest.

I haven't ever had to reboot the isy994. eisy has been running for months without needing a reboot. Java and windows access is still the same old pain....

Here's the java log during admin console start up. Looks like the admin console is regarding that node entry as invalid: Java Web Start 11.431.2.10 Using JRE version 1.8.0_431-b10 Java HotSpot(TM) 64-Bit Server VM JRE expiration date: 2/15/25 12:00 AM console.user.home = C:\Users\keepe ---------------------------------------------------- 😄 clear console window f: finalize objects on finalization queue g: garbage collect h: display this help message m: print memory usage o: trigger logging p: reload proxy configuration q: hide console r: reload policy configuration s: dump system and deployment properties t: dump thread list v: dump thread stack 0-5: set trace level to <n> ---------------------------------------------------- http://192.168.1.117:8080/WEB/iox.jar http://192.168.1.117:8080/WEB/ce.jar http://192.168.1.117:8080/WEB/bc.jar http://192.168.1.117:8080/WEB/chart.jar U7[10].[18]addNodeDefs invalid entry ----<nodeDef NODETYPE="139" ID="e8db849ae9_1" NLS="sensor"> <sts> <st ID="TEMPOUT" EDITOR="I_TEMP"/> <st ID="BATLVL" EDITOR="I_BATTERY"/> <st ID="CLIHUM" EDITOR="I_HUMIDITY"/> <st ID="WINDDIR" EDITOR="I_DEGREES"/> <st ID="GV6" EDITOR="I_DEGREES"/> <st ID="SPEED" EDITOR="I_SPEED"/> <st ID="GV7" EDITOR="I_SPEED"/> <st ID="GUST" EDITOR="I_SPEED"/> <st ID="GV5" EDITOR="I_SPEED"/> <st ID="RAINRT" EDITOR="I_RATE"/> <st ID="GV16" EDITOR="I_RAIN"/> <st ID="GV1" EDITOR="I_RAIN"/> <st ID="GV2" EDITOR="I_RAIN"/> <st ID="GV3" EDITOR="I_RAIN"/> <st ID="GV4" EDITOR="I_RAIN"/> <st ID="GV14" EDITOR="I_COUNT"/> <st ID="GV11" EDITOR="I_BATTERY"/> <st ID="SOLRAD" EDITOR="I_RADIATION"/> <st ID="UV" EDITOR="I_UV"/> <st ID="PM25" EDITOR="I_PM25"/> <st ID="GV10" EDITOR="I_PM25"/> <st ID="PM25" EDITOR="I_PM25"/> <st ID="GV10" EDITOR="I_PM25"/> <st ID="GV8" EDITOR="I_BATTERY"/> <st ID="GV9" EDITOR="I_BATTERY"/> <st ID="CLITEMP" EDITOR="I_TEMP"/> <st ID="DEWPT" EDITOR="I_TEMP"/> <st ID="GV15" EDITOR="I_COUNT"/> </sts> <cmds> <sends/> <accepts/> </cmds> </nodeDef> ---- java.lang.IllegalArgumentException: U7DriverControl dup param [PM25] at com.universaldevices.u7.U7DriverControl.fail(Unknown Source) at com.universaldevices.u7.U7DriverControl.<init>(Unknown Source) at com.universaldevices.u7.U7DriverControl.newStatus(Unknown Source) at com.universaldevices.u7.U7NodeDef.<init>(Unknown Source) at com.universaldevices.u7.U7NodeDefs.addNodeDefs(Unknown Source) at com.universaldevices.u7.U7NodeDefs.addNodeDefs(Unknown Source) at com.universaldevices.u7.U7NodeDefs.addNodeDefs(Unknown Source) at com.universaldevices.uxt.UXTProfileDownloader.registerProfile(Unknown Source) at com.universaldevices.uxt.UXTProfileDownloader.loadAllProfiles(Unknown Source) at com.universaldevices.uxt.UXTNodeServerMgr.loadProfiles(Unknown Source) at com.universaldevices.ui.UPnPClientApplet.prepareAuthenticatedSession(Unknown Source) at com.universaldevices.ui.UPnPClientApplet.prepareAuthenticatedSession(Unknown Source) at com.universaldevices.ui.UPnPClientApplet.authenticate(Unknown Source) at com.universaldevices.ui.UPnPClientApplet.onDeviceOnLine(Unknown Source) at com.universaldevices.upnp.UDControlPoint.onLine(Unknown Source) at com.universaldevices.upnp.UDControlPoint.updateDeviceInfo(Unknown Source) at com.universaldevices.upnp.UDControlPoint.addDevices(Unknown Source) at com.universaldevices.ui.UPnPClientApplet.start(Unknown Source) at com.universaldevices.ui.UDIDefaultLauncher$2.run(Unknown Source) Z-Wave event: control=[_25] action=[1.3] -- Extended Info -- <eventInfo> <zwave CBP="false" CONNECTED="true" RELAXDELAY="0" INTERVIEWTIMEOUT="0" SECUREINC="2" HOMEID="3883420666" NODEID="1" RELAXDELAYDEFAULT="15"/> </eventInfo> -- Z-Wave event: control=[_25] action=[7.1] -- Extended Info -- <eventInfo> <options> <files ZMATTER="true"/> <dongle ZMATTER="true" ZWAVEOTHER="false"/> </options> </eventInfo> -- Z-Wave Backup Options: - zmatterFile= true - 500SeriesFile=false - zmatter connected=true - other connected=false Zigbee event: control=[_27] action=[1.3] -- Extended Info -- <eventInfo> <zigbee CHANNEL="26" CONNECTED="true" RELAXDELAY="0" INTERVIEWTIMEOUT="0" RELAXDELAYDEFAULT="1" CHANNELDEFAULT="26"/> </eventInfo> --

Tried this, including a reboot iteration. Unfortunately, I had the same result.

The plugin reads many values from Ambient and correctly lists them in PG3. The plugin log shows no errors in doing this. UDI mobile shows all of these values correctly but the admin console doesn't. The indoor node has correct values but the main node shows the values from the last node accessed. It will show the values from the indoor node or from any node. Below is a screen shot of the main node right after I accessed the Flume sensor node. The eisy log shows no errors and periodic reporting of the different values from the plugin. I agree this is some issue with the admin console and will open a ticket on this.

That was the problem and removing the & enabled the plugin to get the data from Ambient Weather. However, I have a new issue. The plugins data shows up correctly in UDI mobile but not in the administrative console. I'm seeing only a few values in these three nodes: And the data displayed are not current or matching what is shown in Polyglot or UDI mobile. I have deleted and reinstalled the nodeserver, restarted the admin console, cleared the java cache with no change in the results. Appreciate any help.

Very helpful. Thank you, I'll fix that tonight.

I've installed the plugin, retrieved an API from ambientweather.net and only one node is created with my weather station's name. I've done this multiple times without success. The Ambient Weather plugin on Homeseer works flawlessly. Simply can't get it to work. Log on startup is attached. Any help appreciated AmbientWeather_1-8-2025_81244_PM.zip

@Geddy....Just a restore from the data in IoX to the device. I think it was likely just the connection to the PLM.

After much delay, I have finally migrated my system to my eisy. It went reasonably well, the only hiccup being that I had to restore the settings on many of my devices after the migration to access them I'm not sure why that was...my Insteon devices cover the entire product generation line (still a couple of originals in service) to i3. No rhyme or reason I could discern on which required a restore. It's now up and running perfectly except waiting for the Ambient Weather plug in to populate. I have to say, pulling the ISY994 out of my automation cabinet was surprisingly difficult emotionally...long a faithful service by that little machine. I'll keep it as a backup in case things go south. Many thanks to UDI (Michael especially) for all the initial help with getting the eisy going and for so many years of such excellent support.

Thank you for the point about 'aggressive water' Didn't know about the water in SW Ontario or for that matter here in Portland. Portland's water comes off of Mt. Hood and is chlorinated and then pH adjusted with ammonia (forming chloramine) to a pH of about 8.5-8.8. Then it's treated with sodium carbonate and carbon dioxide which reduces/eliminates corrosion of vulnerable plumbing components. This is an important point. Untreated chlorinated water with a pH above 8.3 (alkaline) will dissolve the zinc out of brass fittings (and dissolve lead). So will significantly acidic water that is not chlorinated. I've thought about getting a tankless water heater but did not know about this potential complication.

Interesting. I have multiple devices that have had successful simultaneous (shared) connections on port 2101 to the Elk from the ISY994, HS3, HS4, and the Automation Bridge. It is true that running Elk RP will block those connections. It connects securely on port 2610 and apparently requires dedicated access. So, I disconnected all of the devices that have had access through port 2101 to the Elk M1G. The Elk NS then connected and correctly created the nodes for my system. I then reconnected the ISY994, HS3, and HS4 successfully and all the devices and the Elk NS are able to share port 2101 successfully. M1 Firmware 5.3.10 MXEP firmware 2.0.44. non-secure access is enabled. It would be a serious limitation if the Elk M1G couldn't connect to multiple devices since that would prohibit the utilizing it for home automation if you had it connected to an external service for monitoring.

The Elk NS is essential to my ability to migrate to eisy and my efforts to get it to connect with my Elk have not been successful. Perhaps something I'm just missing. I've tried to follow the directions carefully. My settings are copied below. These settings work for my HS3 and HS4 Elk M1G plugins with no problem. Those two plugins and my ISY-994 Elk module are all connected and receiving data but I cannot get the Elk NS to connect. I have tried to get a NS log while starting the NS. Nothing shows up. I have stopped other NS, stopped the Elk NS and restarted it to try to get a log specific to the Elk NS. I have attached the PG3 log from that event as a text file. I have deleted and reinstalled the NS without any changes. Any help appreciated and let me know what additional information I can provide. Elk NS start.txt

Upgrade from 5.6.4 on eisy went without a hitch. Didn't require a reboot. Definitely improved i3 integration with the paddle switch and the keypad but there are still a few problems. I have no idea what the new screen for both of them labeled keypad flags is supposed to do. The settings on it don't seem to do anything and aren't reflected in the status boxes. Some of the settings like dim level for the LEDs appear to work now and the status of the switches are accurately reflected in the AC. The AC controls the switches correctly including dimming now. There are LED settings on the paddle switch for red, green, and blue colors that don't do anything. Progress for sure but still some things that need to be fixed. I probably could install thes switches now with adequate control to make them part of my home system.

Yes, I see the same behavior. I don't think it is fully supported yet. I also have an i3 4 button keypad that is not yet fully supported.