sorka

One more thing. I'm assuming I can't get push notifications from myQ to the ISY that are timely to the second so I'm going to route my magnetic contact switches to digital inputs on my CAI8 after all so my ISY knows exactly when my door opens or closes. I need this to trigger various external lighting scenes at home when the garage door opens at night.

So I rolled the dice yesterday and drove a 90 mile round trip to the nearest Liftmaster dealer and purchased two 8550WLB openers with 7 foot solid rail kits. Installed the first one last night. Night and difference in quality of everything compared to the Mattel look and feel of the Genie and the soft start/stop is real and progressive unlike the lurchy two speed affair of the cheap Genie. One thing I will give the Genie is that the Aladdin app shows you the wifi connection status and the signal strength which the myQ app doesn't. Anyways, I did the same test this morning that failed on the Genie. I setup a rule to close at a specific time and unplugged the cable modem 3 minutes before the rule was to execute. Time came and as expected the rule failed and the door did not close. I waited a few more minutes and then plugged the cable modem back in. Waited for it to come up so everything had a connection. Now already there's a difference. myQ still shows the door status as open while the Genie is in a state that says door status unknown and that door must be operated locally to re-establish state. So I tried to close the door with myQ and it failed. So far same as the Genie which never recovered even an hour later. But 10 minutes after plugging the cable modem in, I tried a second time to close and this time it worked fine. The system was able to recover and I think I know why. The Liftmaster knows it's open/close state which is required for the TTC feature to work from the control panel which the Genie doesn't have. What's also interesting is that the Homelink communication is two way with the security 2.0 feature. On our Prius, when the door is opening or closing, the homelink display shows and up arrow or down arrow in the direction of the door motion for exactly as long as the door is moving which is pretty cool. So I ordered my Autolocks after this since I'm happy with the openers. I know many folks have complained about the wifi reliability. I'm hoping mapping a VLAN to the garage ceiling access point that is dedicated to the opener and less than 10 feet away that it will be reliable. Some wifi devices, like my ring doorbells don't work well on mesh with multiple APs broadcasting the same SSIDs.

Is this the standalone myQ or the myQ built into the opener?

No kidding. After the failed, I put the 3 inputs from my photobeams on my CAI8 (which I'm powering via POE from my Unifi switch) and the house water control (1 in and 1 out) also on the CAI8. For the garage doors, I figured I'd just replace them after 22 years with modern units that have control built in. It's unfortunate non of them work locally/offline and get tripped up when the internet or power goes out. Half tempted to just keep the old Liftmasters after all and just hook the CAI8 up to them as well.

I actually like the i/o lincs except for two things. A month or two back, all six of my i/o lincs failed simultaneously. Non of the other hundreds of insteon devices failed so it's really strange that it was just i/o lincs. They never recovered. Secondly they randomly opened my garage doors responding as if to an all on. This is a well known issue with the i/o lincs and why many have had to dump them.

Can you comfirm this? Do you mean through the app or through the API? Maybe the thing that is broken is intentional for some obscure safety reason and if you actually use the close command through the API it works? But unless you've done what I said above and this program a rule through the myQ app and then have it fail because you've blocked the service from reaching the door and then unblock it after the rule fails to execute and THEN issue a command through the API to see that it still works, I'm not sure I'd consider this debunked yet.

Having a hard time attempting to ditch the i/o lincs which I really dislike. So I just installed a Genie which going back because it has a massive security flaw that can leave me unable to close the door with the app when I'm away from home. Now I get that neither the Genie nor Liftmaster doors operate their rules in offline mode when the internet is down. It would be awesome if auto door closing rules still executed locally but I know they won't. But what actually happens is beyond belief and makes Aladdin completely useless to me. Say you have a rule to close the door at 10:00 pm. At 9:55 PM, the internet goes down. I live out in the country with decent gigabit Comcast but it goes down 5 or 6 times a week for 10 to 20 minutes on average. Now 10 pm rolls around and the server can't send the command to the door to close it at 10 because the internet is down. Internet comes back up at 10:15 and rules that failed to execute when the internet was down don't. What's worse is the app won't let you operate the door until you first operate the door locally to re-establish state. So if you leave your house and forget to close the door and the door rule fails to close it because the internet happens to be down at that time, you are royally screwed with no way to remotely close the door even after the internet comes back up. So in an attempt to find out if myQ has the same limitations, I contacted Liftmaster supprt and told them what happens with the Genie I just installed and they informed me, at lest they were honest, that myQ has the exact same limitation. Just coming here to confirm. Sometimes support folk aren't as educated as you might think. Also, maybe it was an issue that was eventually fixed and maybe it's still an issue leaving both myQ and Aladdin as non starters for me.

My liftmasters are 22 years old. They're very loud and they consume 10 watts each of electricity sitting there doing nothing. I controlled them with my i/o lincs until all six of my i/o lincs died at the same time around my house. I'm now using the i/o on my CAI8 for my photobeams and water valve control from my ISY. I either need to buy replacement i/o lincs or find a new solution that works without REQUIRING the cloud for local control. Hence the Chamberlain myQ solution is a non starter since it not only requires going through their off site servers via the polyglot/myq solution, but they've now started charging a monthly fee for new accounts. So unless the Genie openers have some sort of direct access rest API, I'm going to need to go with an add on product like my current Insteon solution.

Thanks. That worked seamlessly! I moved it off my NAS because I'm scheduling it to turn on for only an hour a day so my Blue Iris can do it's long term storage backups. It takes 50 watts just sitting there doing almost nothing 365. Just did solar and 3 powerwalls and cutting out unnecessary usage.

I have NodeLink running in a docker container on my Synology. It want to move it to my RPI. I'm using both DSC and CAI. Do I need to turn NodeLink off first on the synology? Will it mess things up if I try to configure it on the RPI first? Do I need to delete the nodes on the ISY from the old copy running first? Will I nee to edit all my programs that use the DSC and CAI nodes?

Just did a shotgun permission add "sudo chmod ugo+rw /home/pi" and "sudo chmod ugo+rw /home/pi/node" and it succeed without error.

Trying to install for the first time on a RPI 3 B+. The only other thing I've ever installed is polyglot. sorka@raspberrypi:~ $ sudo curl -sSL http://automationshack.com/Files/install.sh | bash ### Updating System - this may take several minutes All packages are up to date. The following packages were automatically installed and are no longer required: coinor-libipopt1v5 libmumps-seq-4.10.0 libraw15 lxkeymap python-cairo python-gobject python-gobject-2 python-gtk2 python-xklavier realpath Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ### Cleaning/Creating directories mkdir: cannot create directory ‘/home/pi/dotnet’: Permission denied bash: line 25: cd: /home/pi/dotnet: No such file or directory ### Installing .NET Core 3.1.7 ### Downloading NodeLink /home/pi/node/NodeLink.dll: Permission denied /home/pi/node/NodeLink.runtimeconfig.json: Permission denied ### Modifying startup script ### Starting NodeLink bash: line 45: dotnet: command not found ### Install complete. Login to NodeLink at http://192.168.1.98:8090 No if I do a "sudo mkdir /home/pi/dotnet" it creates the directory but after running the script and getting this error, that directory is done.

Just had an 8.16KW and 3 Powerwall installation and did a nice long system test yesterday. Since I don't have PTO, I disconnected the main service breaker first which kicked me into back up mode. I then engaged the inverter and the panels. Most of the power generated went to charge the batteries which started out about 18%. Worried about how the system might mess with Insteon communications, I did a query on everything (about 200 devices). This normally takes about 2 minutes. But off the grid, it zipped by in 20 seconds or so. This is repeatable. Turning solar off (but still with powerwalls connected) and the main service breaker back on, times go back to the typical 2 minutes. I'm assuming that this means there are lots of retries. My Insteon network is mostly reliable(99.9%) but I assume it's just that the retries hide failures. Likely that powerline is very unreliable and that wireless it what's mostly succeeding with the non dual mode devices receiving their signals from closer dual mode devices that acted as wireless relays. So what could be going on here? Unclean power from PG&E? Interference from a neighbor?

I tried two of the i/o lincs plugged in all over the place. When trying to do a restore, there's a 100% failure rate on lincs getting written. Also the status light doesn't light back after a factory reset.

No bridging other than through wireless devices on opposite legs. I used to have wired in phase coupler on the 240 volt line going to my Jacuzzi (shortest average run) but once I bought the insteon access point and put them on separate legs, I removed the wired in one with no drop in reliability. Then once over half my insteon devices were dual band, I tossed the access points. Remember that I said the i/o lincs won't even respond when the PLM is pugged directly into an i/o linc.

About 3 or 4 times a month, all Insteon devices in my house come on. I have no ISY programs that send the ALL ON command yet it still happens.

Already happens from time to time which is why I get notified whenever my garage door is open for more than 5 minutes when alarm armed in away.

My best guess is that there was some sort of electrical event that killed the i/o lincs and that they must be susceptible to some sort of device damaging event that the other devices were able to deal with.

But the other powerline only devices work fine. Even if the PLM powerline interface died, the fact that other devices work implies at the very least that dual band devices are relaying the wireless only signal from the PLM. Plus if the powerline interface died on the PLM, the reliability in general of the Insteon network would not be very good. So when factory resetting (holding button in for 3 seconds or more while plugging back in) results in the normal beep, then led turning on for a moment and then going out. But it never comes back on. According to the instructions, after it turns off after the beep, the status LED should come back on. It never does.

KPL? The i/o lincs don't respond even with the PLM plugged directly into one of the i/o lincs. This has nothing to do with interference. These were spread through the house in different locations from one end to the other. All the other powreline only insteon devices are still working fine.

And before someone suggests powerline interference leaving wireless in tact, I still have quite a few powerline only insteon devices and they all still work.

I have 2 for my garage, 1 for my house water valve, and 3 for photobeam sensors. Yesterday every one of them stopped responding. I tried factory resetting one of them and doing a restore. Nothing. Finally removed one and, factory reset it, and then did a "new insteon" device. Still no luck. Did they all really fail at the same time??????? I've ordered two replacements for the garage doors but am going to use the CAI8 for digital I/O I need for the other applications.

It's not another program. Sorting the run time shows that's the ONLY program that ran recently when it happened and there is no other program that calls that program.

It runs every day if the garage door is already open. So maybe that's a bug since it shouldn't unless the status actually changes which it isn't. This didn't used to happen. The program has been unchanged for 10 years and this issue only started happening after updating to v5.

The below program triggers every day at 10 minutes after sunset if I have a garage door open. How can I make it so the time range is not a triggering even but simply a condition check when either door status is switched off? Do I create a parent folder that just has the time range only and put the program in that? Garage Door Night Opens - [ID 0015][Parent 0010] If From Sunset + 10 minutes To Sunrise - 10 minutes (next day) And ( 'Garage Door 2-Status' is switched Off Or 'Garage Door 1-Status' is switched Off ) Then Run Program 'Front Flood Timer Override' (If) Set 'Breezeway' On Set 'Garage Main' On Else - No Actions - (To add one, press 'Action')