xlurkr

Updated to 5.0.16C, and the pending updates are gone. I hope they'll still be gone in the morning. The Dimmer node still must be queried, and there are still no options for setting the variables. After I do the physical installation, I'll do a network heal and see if anything changes. If not, that's OK. I only need to be able to set the dimmer on/off. The relay MUST be sensed when manually switched. Someday I'll upgrade to the 500 series dongle and >5.0.16, but the war stories of that dongle with the Schlage locks are holding me back. -Tom

I'm halfway through installing one of these and it's not going great. First, let me state that I'm on FW 5.0.16B, and have the 300 series dongle. After several false starts, I have the set of nodes displayed in the attached image. I can control the Dimmer Switch node, but I need to query it to get it to show the correct status. It also doesn't have an Options button, and looks exactly like an Insteon dimmer, so I'm wondering if the ISY got confused when adding it. The 26.1 On-Off Power Switch can be controlled, and also automatically updates the status. Cool. The Binary Switch and Scene Buttons are blank, but that's consistent with what everyone else is reporting. I could probably live with it as it is now, except that, as the image shows, it claims that updates are pending to everything except the On-Off. It's been that way for 8 hours now. I have clicked "Write Changes" on the dimmer, right clicked and selected "Write Updates to Device", rebooted the ISY, and nothing changes. I can certainly exclude it and include it again (will be the 6th time), and might just try that after posting. I could do a network heal, too, but I'm reluctant to, because I spent 4 hours yesterday adding a Schlage lock, and I'm afraid to do anything with network-wide consequences unless absolutely necessary. Also, the Zen30 is in a temporary box close to the ISY to do the inclusion and setup, and I'd rather not heal until it is installed in its permanent location. Recommendations, anyone? -Tom

And I can verify that if you try to log in to your account on the website, the only option is a button that redirects you to the portal. -Tom

@Michel Kohanim Is there anything you can do to get the AC (and REST calls, etc.) to reflect that the STATUS of a dimmer is 100% if it has an on level of less than 100% (or is currently at <100%), and is turned on a second time to go to 100%? If not, OK, I'll use lilyoyo1's workarounds. But I thought you might want to think about eliminating one possible source of STATUS being inaccurate, if it's not too difficult or problematic to implement. -Tom

I have been making some changes lately to my ISY, and just noticed something. I have several dimmers and KPLs that will turn on to the on level (let's say 75%) when first manually switched on, then go to 100% when switched on again. Not sure if all Insteon dimmers do this, but probably. Anyway, in the AC and UD Mobile and maybe all other interfaces (tbd) the status of the node remains at the initial on level after I do the second manual on actuation. Is this by design? Even weirder, if I dim it manually (up to 85% let's say), the status reflects that. Then if I manually press on again, the light goes to 100%, but the status drops to 75%. Sorry if this is well known or a defect that has been fixed. I'm on 5.0.16B. I was trying to create some scenes with levels of less than 100%, with lights I couldn't see from my location, and the difference between the status as reported by the AC and the actual light levels was messing me up. -Tom

@simplextech: Do you know if ZLink has their own switches that are the same as the 200 series of HomeSeer? The naming and feature set of the ZLinks look more like the HomeSeer 100 series. -Tom

FWIW, it is stories like this that are keeping me from upgrading to the 500 series board and > 5.0.16. I have no need to upgrade, but I'd like to stay current if possible. I only have a few Z-Wave devices, but I don't want them to stop working. -Tom

When I was having my problem, I copied Michel's command and pasted it into a ssh terminal session on the Policy. I got the HTML response, and bash choked on it. Two days later I did exactly the same thing, and it updated correctly. I would say that the server destination has occasionally been borked. Not sure how or why, but this isn't just about browsers or incorrect paths. -Tom

This morning, the curl | bash command worked, and I successfully upgraded to 12.2. The NS installed correctly. After initial configuration, it's working fine. Thanks to all for your help, especially Rob. The most logical conclusion is that the current version of this NS requires version 12.2 of the OS. I hope 12.2 doesn't break any of the other NSs, but I suppose if it does, the authors will fix them over time. -Tom

Michel: It is working this morning. It was not yesterday. Curl was returning HTML, not a bash script, and bash was choking on it. See my first post in this thread. I don't know what changed, but it was broken, and now it's not. Thank you. -Tom

Ticketed. -Tom

Ticketed. -Tom

That's what I'm saying. Thanks for the the technical version. What I've been trying to do all day is run my first NS on my new Policy. The Policy is up-to-date, as far as it knows. The NS won't install correctly. Everyone trying to help me has already upgraded the OS to 12.2, so they told me to do so. I tried to and can't, apparently. I'm out of next moves. -Tom

Can you try this yourself? The curl command on its own, I mean. I get back some html, not an install script. -Tom

Couldn't you run the curl command and pipe it to more, like I did, just to see what you get? I wonder if that command returns something different now, compared to when you early upgraders did it. Michel said this was temporary, as he was moving to a new upgrade process, or something. I will open a ticket, once it looks like my situation is unique. -Tom

OK, I will, but isn't curl returning the wrong thing? What I got back doesn't look like a shell script to me. -Tom

Yes.

Yes, ssh in Terminal on a Mac. I am using the correct pipe character. I got the curl output I posted above by piping that to more. What do you get, right now, if you execute the curl command? -Tom

OK, the update fails. Details are in the "100 Packages..." thread in Geek Batch. -Tom

Here's what the curl returns: <html> <head><title>302 Found</title></head> <body> <center><h1>302 Found</h1></center> <hr><center>nginx/1.18.0</center> </body> </html> -Tom

Trying to do this right now. I get bash: line 1: html: No such file or directory bash: line 2: syntax error near unexpected token `<' 'ash: line 2: `<head><title>302 Found</title></head> -Tom

The logs/ directory doesn't appear to exist. I will try Rob's suggestion next, since I tried running install.sh before he posted and got this: ld-elf.so.1: /usr/local/lib/libpython3.7m.so.1.0: Undefined symbol "close_range@FBSD_1.6" Collecting polyinterface Using cached polyinterface-2.1.0-py3-none-any.whl (13 kB) Requirement already satisfied: requests in /usr/local/lib/python3.7/site-packages (from -r requirements.txt (line 2)) (2.22.0) Collecting python-dotenv Using cached python_dotenv-0.15.0-py2.py3-none-any.whl (18 kB) Requirement already satisfied: netifaces in /usr/local/lib/python3.7/site-packages (from polyinterface->-r requirements.txt (line 1)) (0.10.9) Collecting markdown2 Using cached markdown2-2.3.10-py2.py3-none-any.whl (34 kB) Collecting paho-mqtt Using cached paho-mqtt-1.5.1.tar.gz (101 kB) ERROR: Command errored out with exit status 1: command: /usr/local/bin/python3.7 -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-zygobz9e/paho-mqtt/setup.py'"'"'; __file__='"'"'/tmp/pip-install-zygobz9e/paho-mqtt/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-pip-egg-info-yzk5qby4 cwd: /tmp/pip-install-zygobz9e/paho-mqtt/ Complete output (1 lines): ld-elf.so.1: /usr/local/lib/libpython3.7m.so.1.0: Undefined symbol "close_range@FBSD_1.6" ---------------------------------------- ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

I just uninstalled it while logged in, and I can now see that the node servers directory is empty, unless something is hidden. Just in case, I ran the rm command you suggested. Reinstalled; same errors in the log. Now that I'm logged in, are there any particular files you want me to look for? -Tom

Sorry, thought I was clear. I hadn't logged in at all, just uninstalled the NS from the GUI, which I hadn't tried before. It warns you that it's going to delete the files and directory, and I said OK. Rebooted, attempted to reinstall the NS, and got the errors in the log that I posted above. Next step is to log in and delete the directory myself, after uninstalling again. I'm taking it slowly, b/c it's obviously possible to do damage this way. I'm trying as much as I can to use the Policy like the appliance it's supposed to be before manually intervening. I hope you understand. Back soon. -Tom

I just deleted the NS, then uninstalled it from the Polisy. I had not done that before. When I reinstalled it, I got this in the log: 2020-12-23 11:02:45 [polyglot] info: NSChild cloneRepo: Successfully cloned ISY-Inventory into NodeServer directory. 2020-12-23 11:02:53 [polyglot] error: NSChild: Install failed - Non-zero exit code: 1 2020-12-23 11:02:53 [polyglot] error: NSChild: ISY-Inventory cloneRepo: Error: runInstallProcess: undefined 2020-12-23 11:02:53 [polyglot] error: Error: runInstallProcess: undefined at runInstallProcess (/snapshot/polyglot-v2/lib/modules/children.js:45:11) at <anonymous> at process._tickCallback (internal/process/next_tick.js:188:7) 2020-12-23 11:02:53 [polyglot] error: NSResponse: Success: false - cloneRepo: Error: runInstallProcess: undefined I looked back at the log, and it also reported these errors the original time I installed it from the store. Later I will login and delete the directories as you suggested, but I thought I'd show you this first in case it sets off any bells. -Tom