
GHenry
Members-
Posts
79 -
Joined
-
Last visited
Everything posted by GHenry
-
eisy v5.7.1, Aeotec TriSensor v2.21 How do I access Z-Wave parameters? I know how to access node parameters (e.g. ${sys.node.n001_…}), but… I have an Aeotec TriSensor whose battery level I’d like to use in programming/reporting, but I can’t figure out from Z-Wave X-Ray what the syntax might be. Thanks in advance for any insight.
-
Responsible people and companies usually want to limit expectations and avoid over-promising. That’s a good thing! My guess is that you won’t see it coming, but you’ll hear about it after the fact. Patience!
-
“AutoUpdate Status: Authorization Failed!” & “Java Internal Error” on launch
GHenry replied to GHenry's topic in IoX Support
Thanks for the insight! AFAIK there's only the security problem that MacOS won't launch an unsigned app (Java or otherwise) when double-clicked; instead one must right-click and choose Open (there's also an unnecessarily arcane way to do it via System Settings). Thereafter it launches via usual double-click. Otherwise, Java is supposed to be platform independent (but things are occasionally not what they are supposed to be!). -
You can also right-click on the icon and choose Open from the contextual menu.
-
“AutoUpdate Status: Authorization Failed!” & “Java Internal Error” on launch
GHenry replied to GHenry's topic in IoX Support
MacOS 14.2.1, Java 8 update 391 build 1.8.0_391-b13 (current). My laptop, running the same system and Java versions, produced only the “authorization failed” error and not the Java internal error, so I cleared caches yet again, and now neither computer gets the Java internal error. Sigh. I really hate reinstalling Java, but I guess I’ll have to bite the bullet. Per the (out-of-date) Home Automation Cookbook, I also tried https://my-eisy-ip-addr:8443/admin.jnlp, which I prefer because it goes directly to the admin console (since I only have one eisy). That produces only the “authorization failed” dialog on both machines, so maybe the desktop’s Java installation isn’t the culprit. Could the “authorization failed” be due to the eisy's self-signed certificate? Who knows?! Thanks again for your on-going interest! -
“AutoUpdate Status: Authorization Failed!” & “Java Internal Error” on launch
GHenry replied to GHenry's topic in IoX Support
Drat! Did all that, but still getting both errors. Insight/suggestions? -
“AutoUpdate Status: Authorization Failed!” & “Java Internal Error” on launch
GHenry replied to GHenry's topic in IoX Support
I'll try that on Tuesday when no lighting changes are scheduled. I presume that's as opposed to just rebooting from Configuration. Thanks again! -
“AutoUpdate Status: Authorization Failed!” & “Java Internal Error” on launch
GHenry replied to GHenry's topic in IoX Support
Thanks for the Christmas Eve response! Ugh, I did all that, but still get the same results. Guess I'll have to tackle Java next week. 😱 -
“AutoUpdate Status: Authorization Failed!” & “Java Internal Error” on launch
GHenry replied to GHenry's topic in IoX Support
Not to answer my own question, but I also am getting this Java internal error dialog now on login. I can't tell whether they're both referring to the same condition, but again, everything appears to proceed normally. Mystery! Insight? -
Wow, thanks, that’s what I was looking for! I discovered the Z-Wave/Xray menu item, but that didn’t have “Node Info”…the contextual menu did, thanks again!
-
How do I grab a value from a Z-Wave device? I have an Aeotec TriSensor and would like to include the lux reading in notifications. How do I grab it? I’m guessing something similar to “${sys.xxx…}” but where do I find that info?
-
eisy v5.7.1, Z-Matter dongle (11/23) After logging into my eisy, increasingly I get a dialog box which says “AutoUpdate Status, Authorization Failed!” That's not very enlightening! Nothing seems amiss, and after dismissing the dialog everything seems to work fine. Where is this coming from, and do I need to worry about it?
-
Maybe an update to the requirements for the node server?
-
Yeah, that did it for mee too, thank you! Who'da thunk it? Thanks again!
-
Wish there had been a trial version…
-
Thank you both! As I suspected, at 2.16, it's not current. I have the .otz file (ZWA005_TriSensor_US_V2.21.otz) and will try again to upload it via the contextual menu item Z-Wave/OTA Upgrade (despite the dire warnings; it didn't work the last time but didn't seem to do any damage either).
-
Will there be an update?
-
How do I read the firmware version of a Z-Wave device using eisy 5.7.1 and Z-Wave USB dongle? I just purchased an Aeotec TriSensor and want to ensure it’s up-to-date.
-
Thanks for the response. I’ve been waiting a lot longer than 10 minutes! I’ve attached the downloaded OWM debug-level log (it doesn’t show up on the PG3x page), which suggests that the API key is the problem. However, I’ve reconfirmed that it is correct. I also corrected the elevation to 220 meters, FWIW. Does any of that suggest a solution? debug 12.log
-
PG3x v3.2.16, eisy v5.7.1 Yesterday I purchased and installed the OpenWeatherMap eisy node plugin, then rebooted. I got the 401 error, although my API key shows as correct and my email address is confirmed with OpenWeatherMap. Today starting at 14:46:53 I uninstalled and reinstalled the plugin with the same results, except that in the mobile app, the status of devices no longer shows up; ironically however OpenWeatherMap shows as “connected” in notifications, although I’m not sure where the mobile “bad gateway” is coming from. Screenshots and PG3x log attached. Obviously I’m missing something! Any insight? pg3-current 2.log
-
If On Sat, Sun Time is 8:00:00AM on And 'Automation / Outdoor Temp' Temperature < 40.5°F From a pure logic standpoint, shouldn’t this program execute only once, at 8 a.m., and even then if and only if the temperature is below 40.5°F? Doesn't the proposed change make it execute at all times between 8 a.m. and almost midnight (again, if and only if the temperature is below 40.5°F)? If ( From 8:00:00AM To 11:58:30PM (same day) ) And 'Automation / Outdoor Temp' Temperature < 40.5°F
-
eisy 5.7.1, ZMatter dongle, Aeotec TriSensor ZWA005 (f/w unknown) I installed my TriSensor only for the light (lux) reading, and now see seven devices. I wanted to update firmware and had the .otz file handy, but only the device named “Home Security Alarm” had the update option. I tried it (despite the dire warnings). It never succeeded (see attached log), but the TriSensor is still connected and reports lux level every 3 minutes. So: How do I read the f/w version number, and how do I update the firmware?! Thanks in advance for any insight. ISY-Event-Log.v5.7.1-Install TriSensor.txt
-
I read somewhere that eisy didn’t support S2 authentication. Anyway, when presented with the security dialog, I had to “select none,” and that caused SEVEN devices to appear: Home Security Alarm, Motion Sensor, Motion Sensor (again!), Multilevel Sensor, Wake Up, SC Basic Assoc 2, and SC Basic Assoc 3. All I wanted was the lux reading, and that’s only in “Multilevel Sensor.” Good grief! What are all those things? Can I just delete SIX of them?!
-
eisy f/w 5.7.1, Z-Wave module 21075, Z-Wave “beta version” (?) I’m trying to install an Aeotec TriSensor which supports Z-Wave Plus. Installation is straightforward except for security, but I do not see any values for light, temperature, or motion…I do have two new items, ZY 001 V1 Alarm and ZY 001 Wake Up, but no readings. I know the devices work with ISY. Any insight?
-
Support thread for: PG3x v3.2.2 (August 18th, 2023)
GHenry replied to bmercier's topic in Polyglot v3 (PG3x)
Upgraded PG3x successfully from 3.2.1 to 3.2.2; after reboot of eisy, my disabled programs were still disabled.