dwengrovitz

Thanks for releasing this on PG3. I'm just starting to migrate a few of my nodeservers from PG2 to PG3 and this was one of the first I tested. Took a couple of restarts but eventually all my tags migrated smoothly. One thing I did notice is the same typo I posted about for the PG2 server -- "commumicating" vs "communicating". Pretty minor, but probably something to update at some point.

Try typing "thisisunsafe" ... without the quotes, not in the address bar, just type it on the keyboard when you hit that page.

Does Nodelink support working with ISY on Polisy? If so, are any special configuration settings required?

I never could figure out why the devices (mainly my switches) would not update unless manually queried after migrating over to ISY on Polisy, but I ended up deleting and re-adding each switch individually, and refreshing/saving any programs that used them, and they are now updating automatically as expected.

I'm seeing a similar issue with switches. I moved to a new USB PLM, and did a restore. The ISY sees my devices and can control them manually and via programs. The status of motion and leak sensors seems to update okay, as does the status of devices connected via node servers. But the status doesn't seem to be updating properly for any of my Insteon switches unless I query them.

I have a number of legacy devices from the old X10 days that I used to control via my ISY994i. Mainly things like a chime that would go off if one of my Insteon leak sensors detected a leak. I did a quick search through the forums, so my apologies if I missed this in prior posts, but will ISY on Polisy support X10 devices via an add-on module like the ISY994i did? I did not see that module as one of the ones that was migrated when I did the backup/restore from my ISY994i to ISY on Polisy.

Thanks - reseating the USB cable did the trick.

I tried doing a backup and restore from my ISY994i to my Polisy. It appears that the configurations have moved over as all of the devices and programs seem to be listed, but I am not able to restore the configuration to a different PLM and can not communicate with any of the devices. The PLM restore gets to the same point every time and fails. The error I see is: Any suggestions on how to proceed? Best I can tell, the restore routine dies when looking for a file that doesn't exist in the backup from my ISY. I could not find FF0108.REC in the zip file from my backup.

Tried that multiple times, but it didn't work for me.

I got the same mismatch between admin console version and firmware as @tazman when using: https://<your polisy ip>:8443/admin.jnlp But things matched up and worked for me when using: https://isy.universal-devices.com/polisy/5.3.0/admin.jnlp (though I had to remove the "d" from "universald").

I used Nodelink originally for years and switched over to the Envisalink node server shortly after it became available to interface with my DSC system. The integrations were rock solid, and I have nothing but praise for the developers of those platforms.

Thanks @MrBill. Much appreciated.

@carealtor - can you elaborate a bit on this? I had kind of given up seeing if I could fine tune the LED brightness since this issue has been there for so long and I was never very successful in trying to accomplish this via the admin console. I guess I never thought of using a program to do it. Would you just run a program that sets backlight levels to a set percentage?

I re-ran the install script on my Pi. Is the latest version V0.10.1 or V0.10.0? My system shows the latter, but the release notes only show V0.10.1 with no mention of V0.10.0. In addition, the auto-update doesn't seem to see the proper files and I'm getting a 404 error. Here's the startup (w/o IP addresses) on my system: 2019-10-26 23:47:43 - ISY NodeLink Server v0.10.0 started 2019-10-26 23:47:43 - OS: Linux raspberrypi 4.19.75-v7+ #1270 SMP Tue Sep 24 18:45:11 BST 2019 armv7l GNU/Linux 2019-10-26 23:47:44 - Web config server started (http://192.x.x.x:8090) 2019-10-26 23:47:44 - ISY resolved to 192.x.x.x (5.0.16) 2019-10-26 23:47:44 - ISY Node Server config detected (profile 1) 2019-10-26 23:47:45 - Auto-Update: Error updating file: The remote server returned an error: (404) Not Found.

Wow ... your timing could not have been better. I was literally in the process of re-building the NodeLink setup on my Pi 3 b+ late last night when I saw your notice so I switched plans. Installation on Debian 10.1 went fine, and the interface to my DSC panel and Honeywell thermostats seem to be working. The NodeLink web interface on the mono version would frequently show periodic errors for me, like timeouts or problems with the stats responding, but so far this morning the panel is error free. I am also running Polyglot on the same Pi. Will let you know if anything crops up but so far all is well.

Has anything changed with respect to reading or setting backlight levels in the latest code versions? I'm running V5.0.15A, and am seeing some really odd things with the backlight setting. If I set the backlight level on one device (for example, a 2466D), I see the settings for a number of other devices updated to reflect whatever I set the value for on that one device. I'm not sure the actual devices get updated (they definitely don't all seem to reflect the setting if I look at the LEDs) but the value showing up in the admin console does. For example, I have around 35 Insteon switches, with a mix of types (2477D, 2466D, etc.). To start, I set every switch backlight individually to 100. Then, I set one switch to 50, and I now see the backlight levels for 26 other switches now showing as 50.

I ordered one ... will let you know what I learn when trying to integrate it with my ISY.

Not sure if you ever heard from anyone on this question ... but I would also be interested in hearing about experiences with this device. I see that there is a Nodeserver for SenseMonitoring in the Polyglot NodeServer store. Might be kind of interesting to be able to have some integration with ISY when various devices are on or off in the house.

If you mean upgrade to Raspbian 9 ... unfortunately that's not an option for me just yet, as the other apps I'd like to run won't work in that environment.

Got a new toy over the holidays (a Raspberry Pi), so I thought I'd try installing Nodelink on it. I have some other apps I need to run that require Raspbian 8. Does the install script for Nodelink care which version of Raspbian I'm running?

Seems like there are more than a few parties interested in this, and it's been a while since anyone asked ... so I'll take a turn. Any new news on when the gates might open? Dave

Yes ... not joking. That's pretty much the entirety of the feedback I received. Although I think the person who was handling the support line sounded like they were fairly new, so it's possible this topic was more advanced than they were prepared to address. Either way, I'm not planning to use the Motion Sensor II devices as temperature sensors anywhere any time soon. Would have been pretty cool if they could do that reliably, but the ones I have continue to indicate the temperature is between -19.5 and -24 degrees Fahrenheit. And it definitely isn't that cold outside in Virginia this time of year. Or any time of year for that matter.

FYI ... I did contact Smarthome on the issue with temperature values being way out of whack, and they basically said the Motion Sensor II is not designed to provide any temperature readings. Oh ... and if I was having any issues to do a factory reset.

I'll try contacting Smarthome and if I receive any kind of productive outcome I'll post an update. Thanks for letting me know. Dave

I had one of the sensors inside, and I was able to put it into setup mode and slowly recalibrate it. The highest value I could get it to take was 71.9 (and the inside temp where it was located was around 74). However, once it sat on the desk for a while, and the setup timed out and went back into normal operating mode, the temperature reset to -24.5 F the first time the sensor detected motion. I have the sensor set to do a query on the device when it detects motion, as that seems to be the only way I could actually get any readings from the sensor other than motion sensing. The other two sensors are outside, and they require a bit of work to get to, so I'm testing with just one of the sensors for now. But the temperature of all three devices reads a steady -24.5 F.