dwengrovitz

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 have monitoring with Envisalarm, but without Sidekick. As @hart2hart mentioned, cutover was easy and they do the job like any other monitoring service. I haven't had any real emergencies to test them, but I did have a motion sensor with a low battery that needed to be replaced, and I started the replacement not realizing tampering with the sensors was something that was monitored. Sure enough, they called when I took the battery out of the sensor and asked the usual questions. So I've been pleased, and the price is considerably less than what I was paying with my prior monitoring service.

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 absolutely agree. It's been a lot of fun working with the ISY devices, and the support provided by @Michel Kohanim, UDI, and the community of users in these forums has been extraordinary. Looking forward to all that 2020 brings. Cheers.

Just curious ... are you running the same environment I am (Mac/Catalina)? On my machine, there's no simple way to ignore or get past the warnings. If I use Chrome, I cannot get to Polisy without typing "thisisunsafe" to dismiss and bypass the warning (and that's not exactly an obvious solution). And if I use Safari, there's an option on the privacy message that says "visit this website" but it doesn't work. Selecting that option just redisplays the "this connection is not private" message. I'm not worried about attacker stuff on my internal LAN ... I'm just pointing out some access issues that, if resolved, might make it a bit better experience for other Mac users running Catalina when they try to get their Polisy running.

Sorry ... I was just hunting for solutions or workarounds. Perhaps the issue I'm seeing is related to changes Apple recently implemented with TLS server certificates? I don't know how directly relevant this is to what's going on with the Polyglot/Polisy system, but at least one other person has run into the problem I'm seeing with not being able to access the app via Chrome. A bit more research on my end located the following: Apple has introduced a series of new requirements for SSL certificates to be accepted by Catalina, documented at https://support.apple.com/en-us/HT210176. To summarize: - Key size must be at least 2048 bits. - Hash algorithm must be SHA-2 or newer. - DNS names must be in a SubjectAltName, not in the CN field only. For certificates issued after 2019-07-01: - The ExtendedKeyUsage extension must be present, with the id-kp-ServerAuth OID. - The validity period may not be longer than 825 days. Interestingly ... there's a workaround on Chrome if one runs into this problem when accessing Polyglot or Polisy. When the error message is displayed about the connection not being private, you can click somewhere on the page and then blindly type "thisisunsafe". This will instantly bypass the warning. Not sure this is a great solution for the long term, but it did allow me to get to the app directly via chrome.

You're luckier than I am with Safari. I wonder if something needs to be updated on the certs being used by Polyglot and Polisy to fix this.

Is anyone else using a Mac with the Catalina OS on it to access Polisy? Ever since upgrading to this OS, I've been seeing issues with accessing Polyglot using different browsers on this platform. Unfortunately, the issues seem to also apply when accessing Polisy. I can access Polyglot/Polisy using Firefox, but if I use Chrome I get an error (see attached "Privacy Error 1.png") and am unable to proceed. I see a similar issue when using Safari (see attached "Privacy Error 2.png"), but while it looks like you can get to the site by clicking on "visit the website" ... that doesn't actually work. I've tried this using two different Macs running Catalina and the results are the same. I've also tried accessing Polyglot/Polisy using Mojave and, while a privacy error is displayed, there's an option that still allows me to get to the app. Just wondering if this is something unique with my systems, or if there's an underlying compatibility issue with MacOS, various browsers, and Polyglot/Polisy. I think Catalina tightened down a few things from a security perspective, but it would be a shame for MacOS users running the latest OS to run into this when broader distribution occurs.

I'm seeing similar issues to others. My Polisy had a noticeable rattle so I opened it up and the wifi card wasn't attached to the main board. Reseated it, and went through some of the update steps described in prior postings. I can still SSH into the box, but the web UI isn't accessible. Glad to see Nodelink running on this. I hope that's a supported option going forward as i could then totally repurpose the Pi I've been using to previously run Nodelink and Polyglot.

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.

Thanks for the response. I have three of these motion sensor II devices, and they all seem to be registering about the same value (-24.5 F). So they appear to be working consistently, I just need to add about 100 degrees to get the actual temperatures.