MikeD

Was the port to Pushover from Prowl difficult?

FWIW, I tried 10000 and still no go with Prowl. Will pursue change to Pushover.

I just updated to v4.9.0 and still have this error when attempting to send a push notification to Prowl.

I only received the above error once. The second time I tried to test a Prowl network resource I received a different error message, something like DNS server not found I think. Every subsequent test resulted in an “n/a” error response. I rebooted my ISY just to eliminate the possibility of something hung. My ISY rebooted normally without errors, so I doubt it is a corrupted memory card. I would think we would see a different symptom if Prowl terminated their service. Don’t know what the issue could be. Maybe someone here has an idea.

I seem to have the same problem with PROWL. My last Prowl notification was on 1/14/2022. ISY-994 running v4.7.3. *NOTE: Network Resources sent within my LAN function normally. Only the PROWL notifications produce an error.

I have both my ISY and PLM on a UPS. Been configured this way for years without issue. There is a dual-band SwitchLinc a few feet away and other dual-band Insteon devices nearby. I would say just try it as long as there are dual-band devices within earshot of your PLM.

Is '$GarageOpen' an Integer or State variable? It needs to be a State variable to trigger program2.

Although I started with Insteon, I now primarily look at z-wave solutions. Just be aware that multichannel devices will not work if you are running 'official' v4.5.x software. Multichannel is supported in v5(in alpha), and UDI is commited to z-wave, however the implementation is ongoing. I have several z-wave devices, including a Schlage lock, Aeotec doorbell, some plug-in switches, and the older MultiSensor 6. All work in v4.5.4 that I am currently running. Do a search on this forum before you purchase a z-wave device you are interested in. Someone may have posted compatibility information.

Sorry, I forgot to count my Insteon remotes plus my leak and hidden door sensors that were in separate folders. I actually have 34 Insteon devices! I use Prowl to inform me via a network resource whenever any of the following is triggered: - Any exterior door is opened/closed. - My shed door is opened/closed or motion is detected in the shed. - My garage door is opened/closed. - Garage or shed doors left open for 10 minutes, repeated every 10 minutes until closed. - All actions of the Schlage lock on my front door. (17 separate network resources. (I have not tried variable substitution for user actions) - Low battery in any door sensor. - High or low temperature alerts for my two Z-Wave thermostats. - To play several announcements in my Aeotec doorbell. (Like a rooster call when my garage door is opened. ) - When my automated blinds open at sunrise and close at sunset. - To activate / deactivate text alerts from Blue Iris when my interior cameras sense motion when I am not home. And maybe a few other things I forgot to mention.

109 active programs 24 Scenes 42 Integer, 24 State variables 95 Network resources 14 Notifications All this for 21 Insteon and 14 Z-Wave devices. Nice to be retired.

As I understand it, once you do a Z-Wave backup it becomes part of your next ISY backup. If you add another Z-Wave device you need to perform another backup before it becomes part of your next ISY backup.

Hi Tim, Thank you for putting together this detailed roadmap on how you set up the services for logging. I use Prowl for notifications that works similar to Pushover. In the past I was doing rudimentary logging locally but have no need for it presently since there is only a few family members accessing my BE469 and Prowl notifies me when they do. Your tutorials are very informative to those who have yet to go down this road! ~Mike

I like the Aeon doorbell since you can load it with mp3 files and selectively play them. I have several programs that are triggered by door sensors and play different mp3s. A rooster crows when my garage door opens. Don't know if it serves as well as the siren but it sure is a lot more versatile and fun.

Make sure $sLeakWashingMachine is a State variable, it appears to be by looking at the name. If you manually change the value to 9 (from some other value) your program should run if it is a State variable.

Hi oberkc, Always thought ZWave devices do not work with scenes in v4 but would work in v5. Thanks for the info.