oberkc

Well, if sunrise in your case (or at least if ISY thinks it so) were bfore 4am, you might get this combination of values. Have yo checked to see that your sunrise and sunset times are accurte in the ISY?

My approach would be to create a variable, to have states either equal to zero or one. Once created, you could add the variable to alexa, as a “sensor” device. In alexa, use the newly-added sensor as a trigger for a routine. Create or modify your ISY programs to change the value of the variable at the desired times. I believe alexa interprets a sensor as ON when the variable equals one, and OFF when zero. (This is all from memory. Details may be off, but I believe the concept is accurate.)

I have sometimes thought about the opposite approach: using the ISY schedules and programs to kick off alexa routines (for those actions not available directly via ISY). Unfortunately, my desire to have an automation system independent fromthe cloud is dying.

Have you looked through the program summary to see which programs, if any, ran when the lights came on or other unexpected times?

FWIW, I have a couple of the Govee flood lights. They continue to work fine at my house. (Though certain control options were limited.)

Just tried and the authorization app on the azure server and it continues to not work as I expected from the instructions (no response, no userid).

I had the same experience when I migrated. Unfortunately, I could never figure out how to solve that problem and ended up removing the non-responsive devices and re-adding them as new.

That makes sense, however, if they do not work at the intended location, but DO work if moved closer to the PLM or another location, that can be a clue about the underlying cause (it tends to suggest that the device works, but that there is something causing communication problems).

In my mind, this is either a PLM failure, a device failure, or a communication failure. Based upon everything you have tried so far it sounds as if we can discount the the probability that it is the first two. Considering the possibility that it is a communication problem, have you tried temporarily moving the Appliance link to a different location, closer to the PLM, to see if communication improves. Additionally, do you recall of any recent changes to your household electric appliances any new devices Recently Added?

Yes, I can view the cameras via VLC, but this is a local IP address. The problem that I experience seems to be when I tried such an address in ud mobile I had less success and could not get this to work from outside my network using the external ports I have reserved and forwarded for each of the cameras. It has been a while since I have last tried, and I was not extremely motivated to get this working, since I already had a viable option for viewing via IPCamViewer app. Maybe I will give it another try.

I have several reolinc cameras. I have them working with alexa, google, and the ipcamviewer app on both android and alexa, with direct connections (not cloud-based) through static ip addresses and port forwarding. This makes me think that it should work with ud mobile. Unfortunately, I have never figured out how to make it work with ud mobile. Still, it may be my minimal skills in this area that comes into play. Maybe I just donkt have the necessary stream address for these cameras .

As I understand, keypad backlights have two settings. One setting is for how bright the backlight is for ON condition, and the other is for how bright the backlight is for OFF condition. Perhaps your could check these settings and adjust as necessary. I believe this can still be done through the admin console.

There is also the log that can be downloaded and viewed as a spreadsheet. It would show ALL activity and you would have to filter the results after downloading, but this might work for you.

A single garage door? Without seeing your programs, I can only speak conceptually. I assume, also, that if one of your phones enters the geofence area and the other is already home, the same thing happens and your garage door triggers, even if the door is already open? It could be in one of a couple of places. First, how do you define, logically and programmatically, when you house is occupied? It sounds as if you trigger the garage door when each phone enters the geofence region and I assume you do the same when each phone exits. You may want to consider creating a condition for occupancy (I use a variable for this) where you house is occupied when EITHER of the phones is in the geofence and unoccupied when BOTH phones are outside the geofence. Set the variable to some number (I use 0) when occupied and another number (I use 1) when unoccupied. I then use the variable to trigger the garage door. Doing this only triggers once, regardless of whether one phone is already at the house when another phone enters the geofence area. Alternatively, and possibly in addition, one could create a set of programs that would first check to see if the garage door is already closed before trying to open it rather than simply triggering the opener each time a phone enters a geofence.

ISY Scenes are an integral part of the linking process. Now is the time to play around with scenes, otherwise you are severely handicapping yourself. Play around with controllers, responders, response (brightness, ramp rate, etc...) levels to different controllers within a scene. You will get it quickly.

Yes Yes, as a scene. One thing that is often not apparent is that devices added to a scene as controllers are, by default, also responders. Add your two switches to the ISY, then create a scene in which both switches are controllers: instant three-way.

Do you have any idea what software version is on you ISY? While I am not certain, I wonder if the current ISY finder works with some of the older software versions. I recall that in the past, we had to install new launchers for each ISY software version. I also thought that we could access through a web browser at one point.

To be clear, wait statements do not force an evaluation. Programs will not automatically "keep evaluating" during wait statements. Wait statements are not program triggers. There would still need to be an external trigger to occur to force an evaluation during a wait statement.

I stand corrected. I thought the were both STATUS conditions. I need to get better glasses.

While this does not answer the question directly, there might be another option... First, disable the notifications via the Ring app. Second, create a notification in IoX, triggered by the Ring motion sensor. (This notification could certainly be paused by whatever method you have in mind.) Third, send this notification to your phone via UD Mobile. (May require the notification plug-in in Polyglot.) I do not recall a means to pause Ring notifications via ISY. I believe the Ring app allows notifications to be set only to occur within a defined timeframe, but that is the extent of my recollection.

I believe Techman was trying to make this point. There are program triggers, and there are program conditions. To use your example: IF Door light status is ON and Hall Light is switched ON Such a program has two conditions. Either condition may be a trigger for the program to evaluate. Once either condition is triggered (by a change of state), however, the entire IF statement is evaluated. So...if door light status changes to ON and hall light was already ON, the program would trigger and evaluate TRUE (both conditions are true).

I am not sure I understand what you’re asking. Are you asking whether it is possible to add a condition in one program based upon whether another program is enabled or not enabled?

I don’t use that sprinkler system and can only guess. I do wonder if using the sprinkler system schedule along with insteon is incompatible. Have you considered the possibility of disabling your program based upon time. The time that you would disable the program would be the time that it is natively running.

In fact, scenes ARE "Insteon's method". And scenes, unlike programs, do not rely on ISY involvement. You are doing yourself a disservice by not using scenes. This is a capability that makes Insteon better than any other protocol that I have tried.

How many z-wave devices do you have? If not too many, it might be easier to simply add them as new to the EISY. Be sure to make a note beforehand which scenes and programs contained the zwave devices. If my experience is any indication, even with a series 500 ZWave board in the ISY with backup, the transition to the EISY did not go smoothly. It was a bit of work restoring all the zwave devices and they often ended up with different names (ZY vs ZW) which required fixing of scenes and programs regardless. If your zwave devices are limited in quantity, I would remove them from the ISY (taking notes where they were and creating a backup of ISY without any zwave devices) and starting from scratch with the EISY and zwave.