smileyw

specifically this " I updated "/usr/local/etc/pkg/repos/FreeBSD.conf" to the following (change "latest" to "quarterly") Then ran: "sudo pkg upgrade -f mongo-c-driver"

shbatm's change to the conf file fixed it! It actually came back online virtually instantly, but I went ahead and rebooted the Polisy anyway once it compelted. I assume I should just change it back now and not run the update again until this all gets sorted out?

I am suspecting there is a bad package or something out there... Its kinda bummer since everything in my house is somewhat down at this point and has been for a day. I have to remember where the light switches are again Hopefully it is an easy fix.

I have the exact same problem. Did you fix it, and if so how?

I can safely say that some of those tickets were because at the beginning the Polisy would let you set the ports to 80/443, and then the whole system would need to be factory reset. However, now the PG2 is on in the Eisy, there isn't a port conflict anymore. I will say that a lot of ISY integrations (like the one for Stream Deck, and the one for Hoobs/Homeseer do not allow you to pick ports (even if you put it in the URL itself). They simply do not work, which kinda sucks. I have considered doing some work with my firewall and a hairpin firewall rule to work around this, but I never got around to it...

Can I actually add a matter device now (I have a Polisy and the new zmatter board installed)? I got a new tp-link Matter module (Tapo P125M) and would like to replace a failing Insteon wall wart. Is that even possible at this point? Its kinda confusing if I can or cannot do that yet?

I have the same problem as a few others (specifically mbking) . I attempt an upgrade, UI closes, and it seems to start the upgrade, but never does anything. Do you want us to manually update at that point, wait for the next build, or open a ticket? UPDATE: I used the sudo pkg install -r udi pkg cmd, then restarted everything then did the update via update button. Now everything is on 5.5.

I suspect the issue here is probably the port. I am running into a lot of this a lot. Lots of these systems will not take the hard coded 8080 port for IoP. They only like port 80.

Did I miss this somehow? Is there an iOS widget now that can do individual actions? I just have the one that goes to favorites, but I wish I had a couple of individual ones instead.

I ordered one, but will the "beta" part be software or hardware? In other words, am I going to have to buy a replacement when the final version comes out, or just update software in the Polisy?

I just want to say that I think this is the first time ever in my ISY lifetime that I just simply told the UI to do an automatic upgrade. It has always been manual updates to various beta versions. It worked, and updated the BIOS too as it was supposed to.

One is called the "Polisy administrative console" while the other one is called "ISY Launcher". I am not sure where I even got the Polisy one in the first place. Either way, I will just stick with the ISY finder. I was just assuming that if there was one that was called Polisy, it made sense to use it for the ISY on the Polisy.

I looked around and couldn't find an answer to this, so I figured I would ask here in case others have this question in the future. I see there are two different java finder/admin apps. One for ISY and one for Polisy. As far as I can tell both of them work with ISY on Polisy. I assume we should use the Polisy version? I am asking because the ISY version works slightly better on my mac since it created a desktop shortcut while the Polisy one did not, so I am using the ISY version for now. Is that a problem?

Did you try it? I assume it would be the same, but I did some research tonight, and I cannot find any standard cable that is the same config as the PLM. Before I spend a bunch of money I want to be sure.

I am fairly sure it is not a Cisco cable (from what I have read in the instructions and on here. I bought this, but I have not put it together yet. https://www.amazon.com/gp/product/B00006IRQA/ref=ppx_yo_dt_b_asin_title_o05_s00?ie=UTF8&psc=1 I will update when I do. I did manage to find the pinouts and color coding for everything, I just need to sit down and try everything I think is right, and get it all done. I will update everyone when I do, and give instructions once I (hopefully) have it all working.

So is it just RX, TX and Ground? If that's correct, RX is 1 on the RJ45, TX is 8, and Ground is 7. On DB9, that would be 2 RX,3 TX,5 Ground. Did anyone build one of these? I lmisplaced my adapter years ago, so I am going to have to make this from scratch.

I saw that one, but I don't get that far. I just get a 404 at the root. That seems really odd to me. I'll open a ticket.

I couldn't. The uninstall/reinstall seemed to have helped a bit. Now I can see the ISY from the finder again, but the website still doesn't work. It answers, but just gives a blank page. It seems like the ISY WebUI is missing some files? I get a 404 at the root, but if I go directly to web/index.htm I can login, but the home dashboard files are not there either. It has been so long since I setup an ISY, is there something specific I need to do to get the website working properly?

I am dipping my toes in running ISY on Polisy. I had the ISY running in the console once. Now I can't get it running again. It stopped when I changed the http port from 8080 to 81. I could never get to it from the a browser, but I could get to it from the java console. Now neither work. I have rebooted, restarted the ISY service, etc. Is there an easy way to remove the ISY package, and re-add it, or delete the config file to effectively reset the ISY to default. (I have nothing setup, so no loss.)

Nothing in my house is working. Both Google and Echo are down. I very much suspect that the expired cert is the problem across the board here.

At one point I thought it had a turn-up or down X degrees, but I can't remember the command (and have been trying to figure it out again...) Does anyone remember the verbal command for that (or if I am crazy).

That fixed it. I was spacing out and using the wrong variable type. Thank you!

I know this is a somewhat old thread, but I am scratching my head on this... I setup a leak sensor and built the programs. When I test the sensor, I can see the status go from 1 to 9 (which is correct), but the notification does not fire automatically. If I manually tell the ISY to run the IF statement it works, but shouldn't that be automatic? Literally, IF the variable is 9, THEN send the notification. What am I missing? It has got to be something simple. Attached is a screenshot of the very simple program. P.S. The program is enabled so that isn't it.

Michel, I wasn't sure if you wanted feedback here or someplace else, but I was guessing here? First off, it works! I can finally control my Tstats! I removed the programs that I had from the portal (in the Echo config), and added the two tstats in the portal. The Echo discovered them and works. The only thing that doesn't work is "[increase / decrease] the [device] temperature." When I try that it tells me that I can only set the temp from 32 to 104. I don't think this is a big deal for me, but since I believe it is supposed to work, I thought I would mention it.