bcdavis75

I am also finding my Sonos NS in a failed state about once a day now. Log attached. ST-Sonos_1-3-2023_114314-PM.zip

Bumping this. There was already an "Issue" listed on github. But as far as I can tell, this isn't being addressed. What's the the proper channell to get support for a Node server that's broken? It would be nice to get up and running again.

Hey all. This NS has become totally non functional for me. As with some others, I was finding it in a failed state several times a week and having to manually restart. However, now it's just not working at all. It says 'connected' after restart but it is clear not connected in the admin console.

That would be great. Thanks!

Is it theoretically possible to add that functionality to the Node server?

Hi all. Couple quick questions... I have a polisy and have migrated my ISY over. Currently I only use insteon devices and have held off investing in zwave etc as Matter appears to be the future. So, this upgrade looked exciting but what are the differences between the forthcoming eisy v. a polisy with this new upgrade installed? Are there good reasons to consider consider just upgrading to eisy when available (price difference notwithstanding). Also, is true there are no actual matter devices on the market yet?

Happened a day ago I think. The Log says "report this!". I was able to restart it successfully. Log attached. ST-Sonos_9-7-2022_94019_PM.zip

Hey All. I try to keep all my IoT devices on a IoT Vlan (using Unifi Dream Machine). My Isy (on Polisy) is on a different Vlan. Despite my experiments with firewall rules and Mdns settings, the Node server can seem to see the kasa devices. Has anyone else had success in a similar setup?

Hi all. I just ordered this replacement cable on amazon before reading this thread: https://www.amazon.com/gp/product/B08V539JMQ/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 Is this essentially the same cable that Smartenit sells? Or do I need to buy their cable to avoid frying my PLM?

And I may have answered my own question. I found in the noderserver configuration window that the old IP address of the Polisy is hardcoded there. After updating to it's VLAN 2 IP, things are working! I'd still love any advice on network segmenting with Polisy and ISY though.

So I definitely should have asked for advice BEFORE just plowing ahead but... I'm wondering if anyone out there has some advice on setting up ISY (still running on it's own box) and Polisy when running a segmented network. Here's my setup: VLAN 1: Admin. Has the ISY, all out devices (iphones laptops etc), and generally trusted devices. It also has my Sonos devices. VLAN 2: IOT. This contains things like my MyQ garage doors, Kasa devices, etc. My Polisy originally lived on VLAN 1. Recently, I was working with @Jimbo on getting my Kasa node server up and running--it was not able to discover devices on VLAN 2. We confirmed this was due to the network segmenting issue by moving one of the KASA devices over to VLAN 1 and seeing get discovered. Oddly, I have not had any issues using noderservers like MYQ where the MYQ openners sit on VLAN 2. So, I decided to try moving the Polisy to VLAN2 and then adding a firewall rule allowing NEW / ESTABLISHED / RELATED connections specifically between the Polisy's IP and the ISYs IP. The seemed to work--the devices can talk to each other. Moreover, the KASA, node was able to add all the devices. The nodes also appear in the ISY admin console. The only problem is, nothing works lol. When ever I attempt to execute a command on any noderserver in the ISY, I the below error. A few quick other notes: PGC nodes still work fine. Also, My Sonos devices are on VLAN 1 because I read they are fickle and trying to put them on an IOT network is more trouble then it's worth. Lastly, I did not move the ISY to VLAN 2 because I figured I stop and ask questions before potentially breaking more stuff... so maybe that's an answer.

Good news. That all seemed to have worked. My PG2 nodes are working again. Thanks everyone!

sudo shutdown -r now after what Michel wrote?

Yeah. Sorry about that. I should have trimmed the txt file. The ping failures were me testing something unrelated. I'll run "sudo service polyglot status" when I get home this evening.

Corrected. Thanks!

Not that I can tell. Also, it's not impacting PG 3 nodes. They seem to work fine. No other signs of network issues.

Log attached. I don't know what I'm looking for exactly. Log.rtf

Hey Goose. I followed the steps to install PG3. Specifically: curl -s https://pkg.isy.io/script/update121.sh | sudo bash sudo shutdown -r now cat /usr/local/etc/udx.d/static/update13.sh | sudo bash sudo shutdown -r now sudo pkg install pg3 sudo service pg3 enable sudo service pg3 start Also I tried restarting polygot on polisy in PG2. No go

Hey all thanks for the suggestions. Here's what solved it. I had to go to the apple keychain and search for polisy under certificates. Then I clicked on the polisy cert to open it. The I clicked on TRUST. The I changes all available options to "Always trust". And now I have my proceed link back in the Chrome. Incidentally, typing thisisunsafe also did work. but that was the only other solution.

I'm using https. If I use http, my screen looks just like yours.Here's what it looks like:

I'm sure there must be a topic on this somewhere but I can't find it. I've been lazy up until now but it's time to figure this out... I cannot access Polisy from chrome on my Mac. Works fine from Safari--but I don't really use safari. Typically in chrome, when I get that "this site is not private", I can click on advanced and go there anyway. For some reason, that option doesn't exist for Polisy. Thanks!

First of all, fantastic guide, Thank you! I'm not certain I should have jumped in with both feet but what can I say, I'm weak. Anyway, I got as far as getting PG 3 loaded and successfully bought and installed a PG3 node--that was cool. But problem now is that the process did something to my PG2 nodes. They all show disconnected and I cannot get them to reconnect. I'm attaching the logs from my MYQ PG2 node (I don't think a PG3 version exists yet?). If anyone has a suggestion on how to troubleshoot, that would be much appreciated. MyQ_logs_1-17-2022_110832_AM.zip

I see. Thanks. So just clear the last bit of cloudyness... With ISY running a on a Polisy, what are we planning to connect to that will also plug into the wall and replace the Serial PLMs that have been discontinued?

Sorry, I'm sure I'm being sense here; and I don't know what DB9 means. But if a PLM is still required when running ISY on the Polisy and the only PLM I know of that works with ISY is discontinued, what has changed?

Well, that's exciting. Couple follow up questions; 1) Will the restore from ISY to Polisy ever be possible? Or should we plan to rebuild from scratch on Polisy? 2) The sudo commands you list--how do you run them? 3) Lastly, I'm still confused as to what actually replaces the Insteon Serial Modem on the policy.