MWareman

I use dusk/dawn triggers from the motion sensor and have each dusk or dawn trigger start/reset a 24 hour timer. If the sensor battery dies I get an alert once the 24 hours expires.

I think that’s a mischaracterization. ISY never sends an All-On message. Otherwise, ISY would know all devices are on - and it doesn’t. What is happening is a message collision on the power line, and it looks confusingly similar to the All-On message - and older devices are acting on that apparent message. Newer devices now ignore the All-On to avoid the problem. It’s possible that spamming the ISY API with messages could have caused such a collision between the ISY sending scene on messages rapidly and devices confirming the new status back to ISY - which would be retried if the insteon network is congested.

I posted somewhere how to setup Apache to reverse proxy ISY retaining support for the websocket subscription used by Agave. Unfortunately, I’ve not found a way to reverse proxy the SOAP subscription needed by Mobilinc or the Admin portal.

Two things. First, confirm you are using the second portal accounts username and password. Perhaps obvious, but worth checking. Second, if the second portal account, do you have the ‘Preferred ISY’ correctly selected? This is the ISY that Mobilinc will connect to.

In the second Portal accounts profile, did you set the preferred ISY?

I don’t believe so. You can set the notes field using the SOAP interface though.

The Polyglot web interface has an option to reboot the ISY as well... in case it’s needed...

Yesterday - I got notified that my CISSP has been issued.... https://www.youracclaim.com/badges/0b05f642-70af-43b6-b320-2042229ac49c ....and today I passed the 'AWS Certified Solutions Architect - Associate' exam. That completes the certification portfolio I was aiming for. Now - I've just got to maintain the necessary CPEs...

Ahhh, yes. M5.large. Affecting enterprises everywhere.... Good luck with the changes! We’ve also hit issues with this issue stance type over the last few weeks and got advised to move away from them...

Do you have 2fa on your Gmail account? If so, you’ll need to use an app-specific password instead of your regular gmail password. You will also need to allow ‘less secure’ access to your gmail account. Otherwise, basic auth over TLS will not work.

4.6.2 is the latest stable release. The 5.x versions are Alpha (not even Beta yet), and so are not considered stable yet.

One does not simply add only the zwave add on though - especially for locks. As many of us found out - zwave requires at least 3 powered (non battery) devices to form an initial mesh. Locks don’t count, but the ISY does. Most locks need a security enabled beam forming repeater device - like the Aeon Siren (although other devices are now reported to be as good). Avoid the original Aeon ‘repeater’ - it does not work with locks.

When establishing an SSL connection, it’s the server (ISY) that has the computationally intensive task of calculating the session setup crypto. In commercial sites, many system use hardware assisted process for speed (at work, I use F5s...). The ISY, on the other hand, has a CPU less powerful than an Arduino (ish - it does not take much to keep up with Insteon and Zwave serial communication speed) - and no crypto processor. That calculation is going to take quite a while. Re-do your certificate at 1024 bits and you will see a 4 time improvement in speed (assuming your current cert is 2048bits).

I see the Else in the code example...

I wrote a PHP script on a Linux system that triggers on an API call from my ISY, obtains an image from the camera (a Foscam in my case), and then sends the image to Pushover (where it’s displayed on my phone, and can be saved to the local phone).

I have 4 minis and 1 regular Home. The most popular function is ‘Hey Google, broadcast.....’ and all Home devices wake up and broadcast the comment following. It’s become a whole house dinner bell... I also have my Minis ‘paired’ to either a Visio Smart TV or a non-smart TV with a Chromecast. My Vizios are connected to Sonos Playbars. This allows me to ask for any given piece of music and my Google Music Subscription springs to life playing thru the Sonos. It’s a very slick integration.

I don’t think Insteon devices support adjusting the ‘Button Hold’ ramp rate. I think it’s fixed in firmware.

Yesterday, I finally took the day off to take the CISSP exam, and passed... So now I have CISSP, CCSP and CCSK. A full complement of IT security certifications...

Add a small wait (couple of seconds) before the notification is sent. And retriggering will cancel the wait and start the program again. Only the last trigger will get to the notification. A side item. Using an iolinc to control the door is not secure. Insteon has not security, and it can be spoofed.

Before implementing remote closing, consider the safety implications. Plenty of kids have got seriously hurt by closing garage doors even when the IR LOS safety devices are working fine. Doors usually have a power based auto-reverse as well - but it’s when this fails that the chance of injury rises significantly. My choice is not to do this without a camera to visually verify that the door closing area is clear - and add a closing siren (such as the MyQ system does).

Every time this thread gains a post, I am reminded of why I won’t get a roomba.... https://www.usatoday.com/story/news/nation-now/2016/08/15/pooptastrophe-man-details-night-his-roomba-ran-over-dog-poop/88667704/

What about the ‘Verify’ checkbox? That likely needs to be unchecked....

The substitution happens in the sending process, not the receiving process. Chrome has no way of knowing your device states, so cannot substitute your variable. To do this, you will have to set this up as a network resource.

Post a screenshot of your network rule (black out the Authorization header!). There are a couple of gotchas to check for. To test substitutions, try it in an email notification and make sure it’s working there to substitute the correct value without anything non-numeric.

Awesome! The other day I pinged their support asking for a way to control my Ring Floodlight (and 2 spotlights) by API. You cannot even do this via IFTTT - there are only triggers for Ring, no actions. Glad to hear it will be coming to the Portal!