apostolakisl

Running 5.4.3 and I don't see this. Looking under I have a "networking" tab which is the same as it has always been with the web server, network resources, and wake on LAN sub tabs. Using them as pass through switches could be useful if you want to put polisy in a location that has only a single ethernet connection and already has a use for it.

Networking bridging, but I wouldn't think you would want to have polisy be in charge of that. But in my world I do all of that using vlan's and poking holes in the firewalls where something needs access to multiple vlan's. And yes! Why not label the stinkin ports. I had unplugged my polisy for some reason a while back and was like, damn, which one was it again.

It appears they are network ethernet ports. On PG2 you can go into configuration and turn those ports on. At least it looks like you can, I haven't actually done it. But just playing with the settings and not saving them, each of the 3 ports has its own MAC address and can be configured with their own IP addresses. But I can't imagine a use case for multiple networks.

It is actually in the wiki. But seriously, how frustrating to right off the bat not even know where to plug in your ethernet! Back to my question, what is the ultimate purpose of having 3 network adapters (plus wifi)? Connect one end of the included Cat5e cable to Polisy’s Network Port and the other to your network. You must use the port that’s closest to the right most edge of Polisy when the front of Polisy is facing you (closest to the db-9 serial port). Note: the network must initially be DHCP auto enabled

Questions, Why 3 ethernet ports? It is a bit confusing right off since you don't know which one to use without trial and error or reading the instructions. I have not tried changing these settings, but it appears you can turn on multiple ethernet ports at the same time and get different IP addresses. And I guess you can turn on wifi at the same time as well for 4 simultaneous networks?

So what is the behavior you are looking for? Currently the program triggers 3 times. At 6pm, at 30 minutes before sunset (both true) and 11pm (false). Are you trying to only have one true trigger? If so, why? What is the behavior as written that you don't want? Having the program run true the second time each day simply sends a command to turn lights on that are already on . . . effectively doing nothing. The only thing that I can imagine is that you are sometimes manually turning the lights off in between the two on times and don't want it coming back on. And as Larry noted above, the from/to isn't needed for both times. You only need the 11pm off trigger in there once. You can just do if time is 6pm or time is from 30 minutes before sunset to 11pm. This no longer holds true if you have additional triggers, like an outside program that does a "run if" on this one.

found this on reddit. It is a v1 hub, so not that much help. Took a picture of my V2 hub. Lots of header pin locations to choose from.

Do you suppose you could just get one of these: https://www.ebay.com/itm/181006995656?hash=item2a24db90c8:g:4hEAAOSwcgNZD8mI And connect to the rx/tx pads on the hub? The hub actually has a really nice and powerful radio in it so it makes a nice access point.

Use repeat every 1 minute. If the pump changes status it will imediately switch from true to false or vice versa. It will start to run on its own first time pump chages status. Or click run at start up to trigger it at startup.

So, should I scalp all my spare plm's on ebay now?

I saw that, but I can't understand how that applies to that sentence. It sounded like he was saying the parts are no longer manufactured. Where ETL refers to data, not parts.

? sorry not hip to that abbreviation. EOL?

Regarding UD hardware, It doesn't fail. It just doesn't. I understand that memory cards on some units fail, but, that is just in the nature of memory cards and UD of course doesn't make those. I would be surprised if the OP actually had a hardware failure. As far as UD software. Official releases are excellent. For those of who like to play with beta and alpha stuff, oh yeah, there are issues. Polisy and PG I would still call a work in progress. More so migrating from other systems into it. I think if you did a virgin install, you probably would not have issues. As far as support. Crazy good support.

sounded like you still had the unmanaged node servers in the first 3 slots when you called them "phantom".

I think you needed to have the PG3 slots in question empty prior to restoring pg2 backup into pg3.

above is what I found to work. @GTench

Roomba triggered today from a program in ISY. It also triggered last night from a native Roomba schedule. I haven't manually triggered it, though I have opened the app and connected.

You can spend $500 to $1000 for a serial PLM on ebay, or buy a $379 polisy and use your current usb plm, and sell your 994 on ebay for maybe $200. Of course by buying the polisy, you will also be future proofed for at least a decade.

I agree. I would recommend doing what I did above because it carries over all your configurations for the nodes you do want to move over and it leaves any non-qualified nodes (ones you didn't pay for) as unmanaged. But it is quite a goofy process.

So this appears to be the story. 1) backup PG2 2) delete the PG2 nodes you plan on moving to PG3 3) restore the PG3 node server using the PG2 backup 4) restart the NS's you're migrating, perhaps twice before they show up in ISY. Definitely not an elegant process.

What if I is already on PG3? Will I need to delete it from there and add it again?

So if I delete the node from PG2, it will not delete the configuration from ISY? Right now, both PG2 and PG3 claim to be managing the same node. Before manually "stopping" the PG2 version, both said "connected". PG2 below PG3 below

This may be answered elsewhere, but I can't find it. I am trying to migrate nodes over from PG2 to PG3. I have loaded lots of nodes on pg2 with many of them there as curiosities that I really don't care to pay to move to pg3. I am starting by moving over what is free and then will buy what I actually want. Anyway, I restored a pg2 backup in pg3 using the button that says it does that. Example, Blue Iris now shows on pg3, but it still is on pg2. Do I at this point delete it from pg2? Or will that delete the node from ISY even though it is still on PG3? The NS configuration page on ISY AC shows that the node is configured for PG3 with port 3000 as the port and other stuff that is c/w it talking to PG3. I stopped the Blue Iris NS on PG2 and restarted it in PG3 and PG3 shows connected. So now what? Delete from PG2? After restarting PG2, it still shows connected to Blue Iris, I would expect it to say unmanaged.

Of course I set it up. PG3 node lost connection to ISY, not to Roomba. The log still showed data flowing in from Roomba. The AC was getting no updates, so the values stayed as they were. After an AC restart, the fields were left unpopulated. Other PG3 nodes were still connected to ISY.

Its own built in schedule. As I mentioned, I don;t know how they work that, it could be on the cloud or it could saved directly to the unit. I suppose I could shut my internet off at 1am when it is scheduled to run and see if it runs.