Jump to content

bleepblorp

Members
  • Posts

    109
  • Joined

  • Last visited

Everything posted by bleepblorp

  1. Hi gmanor77, I had been using Houselinc and an Insteon Hub prior to moving to an ISY994i. You are correct. You can make scenes and events with conditions and triggers that function similar to Houselinc as well as a lot of functionality that Houselinc does not do. I've been extremely happy with it. As to question #1, I am successfully using all of the modules you mentioned so yes. #2, yes. The software interface lets you change these settings without having to have physically touch the module. This is what the 'options' pop up looks like in the admin console for a micro on off module:
  2. I can't say I've used the dusk.dawn event to turn on a light before, but I have used it to email me when states changed when I was trying to get a sense of its behavior. What I noticed was that my various motion sensors would change dusk.dawn state multiple times a day ... maybe 5 to 8 times randomly. I also noticed that it would sometimes trigger the same state multiple times. For instance, it would trigger on and then 30 minutes later trigger on again. In the end, I can't say whether or not this explains your situation, but I do think this may be another variable to consider. As to what you are trying to accomplish is it possible to use programs in combination here? If so, you could have one program turn on the light from dusk and off at dawn. A second program could look for motion events during dawn til dusk. Of course this would mean the ISY is triggering the scene and not the sensor. Not sure if that delay is okay for your use case. Also, from other threads I have come to understand that 'As Motion Occurs' will send continuous on messages as it sees motion which doesn't seem useful for this case. The 'After timeout only' setting should work and will generate less traffic and battery drain.
  3. I agree! Thanks for sharing. I just set this up with my leak sensors. I've not implemented a watchdog in any of my previous ISY projects. Very cool!
  4. This totally worked for me as well. Awesome! Thanks so much for finding the root of the issue and a solution, Michael. Much appreciation! Best regards, Bertram
  5. I appreciate you having taken a look at this, MWaverman. I'll take a look at setting up a proxy as well.
  6. I do have an ISY Pro. It is running the latest firmware release, 4.0.5.
  7. Hello, I recently discovered Notify My Android and have been reading posts on the forum that suggests people have successfully been using this with ISY and presumably with HTTPS. If I configure the resource for HTTP and port 80 I can the test notification is received, but not HTTPS. The resource is configured as follows: Specifically, after I press the Test button an Error pops up saying Request Failed and the Resource Response says N/A. Looking in the Event Viewer I find an entry that says the following: Net-Resource: Failed connecting to http://www.notifymyandroid.com From another thread related to Prowl there was a suggestion to uncheck Verify HTTPS Server in the Network settings of the Dashboard. I have looked into this and it is not checked. Does anyone have a suggestion?
×
×
  • Create New...