gzahar

Needs to be: Then Repeat 1000 times Set 'Flooding light group' Fast On Set 'Flooding light group' Fast Off Wait 1 second Repeat 1 times Wait 1 second Also, last 2 lines are not doing anything in this setup.

Of course you'll need to put it on a loop in case you not home when the announcement goes off. But also make sure it doesn't go off every hour overnight or it will be your fault again.

I guess I should have looked closer at mine. Wiring in progress...

How did you do that? I've used one of these for many years, but needed a 'parallel' sensor system to integrate ISY. Mine is pretty old, maybe the newer models have a contact closer output (or did you hack into the circuit board/wiring).

Per the post you replied to above: - get a USB PLM and swap the boards

Do you have the same number of bulbs/switch on the good vs bad locations?

Click settings, choose Account, edit the email address in the first text box that has your email, click Save.

The 2414U is actually a PLC vs PLM. Not the same. You could make a cable.

If you are trying to to delete links that the ISY knows about, you should adjust the scene(s) w/in the ISY, including deleting any devices that are no longer installed. This should update the link tables in the devices. If you are trying to delete links the ISY doesn't know about, just doing a restore device should get rid of these.

For startup resync, enable 'run at startup': If status AC = off, wait 5 minutes, set Delay=0.

When you turn root "LR Lighting" scene on/off from Admin Console, do all the lights work or just the 2? What command are you giving Alexa? Do you have any other scenes or devices with similar names? Select one of the 2 lights that do go on/off and look to see if they are a member of another scene that Alexa could be operating.

They are available, you just have to pay $5 more for the garage kit! Edit: Never mind, those are out of stock also now.

It is probably set in one of the momentary modes (click the options button on the device page). When it turns off (in this mode), the I/O Linc does not send back status that it has turned off, but a query will show it as off. Either take it out of momentary setting if that is not the way you want it to operate, or create a program that queries the device 5 or 10 seconds after detecting it turn on (the timing of the query needs to account for the amount of momentary delay). That will keep the console in sync.

I am getting the same empty screen when trying to add a nodeserver from PGC (I'm assuming PGC is supported). In my case a number of errors are reported when the nodeserver is first started up (or stopped and restarted). These are 503 errors stating 'Couldn't update driver to ISY', and 'Failed to load xyz... to ISY...Try again using the portal "Profile Upload" button.'. Also: "Requested ISY not online". Both PGC and ISY portal show my Polisy ISY online, and I am able to control devices through the portal.

I think I may better understand your confusion about FOR. In a simple program If FROM 8am FOR 2 hrs THEN turn lights on ELSE turn lights off The FOR would control when the lights were turned off (ELSE statement). If the ELSE statement is blank, the FOR becomes meaningless. You have not given the ISY anything to do at the end of the FOR time. It will not assume you want to "undo" the turn lights on (THEN statement).

Good to know! Thanks.

I was aware of that (that it could be changed) and it was my first thought, but it seemed more trouble to reconfigure the components using the HE nodeserver than to just change ISY port.

Think about it as two horizontal bars representing a start time and end time. One is fixed and starts at 5:30 and lasts for 6 hours (ends at 11:30) The second starts at a changing time (sunrise -30 minutes) and also has a length of 6 hours. The program will trigger at the beginning and end of each bar, but will only be true (execute THEN) when the start of one overlaps the other. This will be at the start of the last occurring bar. As mentioned by @MrBill all 3 other cases will be false and execute ELSE. If you make the 6 too small (bar length), you run the risk of one bar ending before the other starts (no overlap) so the program will never be true. Not knowing how far your sunrise (-30 min) drifts from 5:30, I can't say what a safe minimum value is. Also if you are using any WAIT logic in THEN; you need to make sure that after the latest bar starts, the earlier bar doesn't end less than any wait time you may have in the THEN or it will get interrupted and never finish the rest of the program.

I ended up, changing the ISY to use port 8081 and then re-enabled Hue Emulator.

From what I have read, uninstalling the app should remove the prompt. I would try installing and removing again.

Never mind, Restore Modem is what I needed. ------------------------------------------------------- Does anyone know how to factory reset the 2448A7? Or at least delete all of the links in it through the ISY interface (I have 2 links from some previous usage I don't remember). File - Delete Modem says it removes the PLM (in addition to the links) from the ISY which is not what I want to do (unless adding it back is not an issue).

Found the problem. (I think) If anyone is using the Hue emulator nodeserver and left the default configuration at port 8080, you will need to change it to something else. Not sure why https port 8443 wasn't connecting reliably, but may be due to traffic from hue emulator on port 8080 locking up isy service? But able to connect on both ports now, after stopping hue emulator nodeserver.

Seeing the following (after above steps & reboot): [admin@polisy ~]$ uname -a FreeBSD polisy 13.0-RELEASE-p3 FreeBSD 13.0-RELEASE-p3 #11 releng/13.0-n244752-b368bb75bad: Tue Jul 13 23:39:11 UTC 2021 ec2-user@bsdev.isy.io:/usr/obj/usr/src/amd64.amd64/sys/POLISY amd64 [admin@polisy ~]$ sudo pkg update Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. [admin@polisy ~]$ sudo pkg upgrade Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Checking for upgrades (0 candidates): 100% Processing candidates (0 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. [admin@polisy ~]$ sudo service isy status isy is not running. [admin@polisy ~]$ sudo service isy start loading uftdi.ko kldload: can't load uftdi.ko: No such file or directory /usr/local/etc/rc.d/isy: WARNING: failed precmd routine for isy

SHELLY 1

It won't work directly because the RJ45 pinout on the 'USB to RJ45 serial adapter' isn't the same as the ISY RJ45 pinout. You will need something to adjust the pinout at the very least.