larryllix

...I have two ISYs and now two policies now and they are all going obsolete due to loss of hardware availability. The polisy boxes still have software bugs yet also. * sigh* Now a new hardware box is being released shortly again. Who ya' gonna call? Sent from my SM-G781W using Tapatalk

I had at least one sun dependent program fail to run and when I examined my a/c I found my clock out four hours and my sunset/rise times out about 1-2 hours. I power cycled my polisy, reloaded my a/c and the errors would not change. Ran the firmware update and still had a clock that would correct itself for a while and then jump back four hours again later. Clock would correct itself each time the co-ordinates were edited slightly and saved. The next day everything was back to normal. Began to think I imagined the whole thing but my sunset based deck lighting failed for sure. All works like normal again????

It isn't the communications between ISY and the Amazon app. It is the internal software inside the amazon software that wouldn't trigger the routines. As in the past, several of us demonstrated that the pseudo MS point was being fully activated inside the Alexa software. Sent from my SM-G781W using Tapatalk

Google? You mean every user of Matter will paying a subscription fee within 5 years after we are all hooked? I wonder how they can make my RGBW lighting advertise? They can't talk or display text.

...or Insteon could create a PLM that could only talk Matter to our ISY boxes. UDI takes another step in isolation from Insteon prevention? Sent from my SM-G781W using Tapatalk

V5.4.4 Daylight savings. My IoP has reverted to standard time with errors that will not go away. The displayed time in the admin console jumps backward 4 hours but corrects itself after the location is jogged by updating to the same location. Now my sunrise is too early by one hour and my sunset is too early by two hours. Thus happened on Sunday after the time change. Sun based time triggers have failed. These times have been working correctly since the DST time change in spring 2022. I have rebooted and power cycled polisy several times without any success in clearing this. UPDATE: This cleared up the next day when I opened the admin console again. I could not get the times to correct themselves no matter what i tried the first day.

The sensor and your time frame condition both attempt to do the same things. Also both conditions act as triggers at the nodes of the conditions. These can cause unexpected results until you understand how that works. Time frame conditions have a status that is true between the two times but also cause triggers of Then at the first line and cause triggers of the Else at the second line. Sent from my SM-G781W using Tapatalk

...but I was hoping my camera would talk to my light bulbs. Nicely posted. Sent from my SM-G781W using Tapatalk

@DaveStLou @macjeff @garybixler YAY! My Alexa routines just talked to me when I got home about 3:30 PM EST today!

Weird! That has never been the case for my 5-6 tickets so far.

5.4.4 is the latest version. @MrBillpossible typo?

My forecast is after all the dust settles, most of the excitement will have been for nothing and we will have another count in the already 1234 protocols. Hopefully, this is not what happens but we have been here so many times before. You will never get three companies to agree on a protocol or protocol implementation and the home automation field is getting so broad there will always have to be "special cases" built into the protocol. That will end up making 200 implementations of the same protocol that only talk to each other on Feb 29th each year. Gawd, I hope I am wrong on this one.

Saturday is a day off for UDI support.

Me thinks you should open a ticket with UDI. That UUID:0 bothers me as deeper trouble than we bargained on. Check your ISY About to see it's UUID and versions.

Definitely. I agree. This happened before and IIRC alexa routines wouldn't trigger for about a year. Amazon always told me it was working fine. Their support group doesn't have a good reputation. This typical of front line support to filter out everything they can, blame it on the user, and look good to their employers on the other side of the world. All my other calendar additions, voice commands over ISY Portal, and timers, reminders, and alarms work just fine. Only the routines quit working yesterday. I sent amazon my own note but I didn't use the help/support chat bot but rather the improvement suggestion messaging. I don't want to hear all the help feedback offers to show me how to click a mouse.

Usually when Alexa reports she is having trouble, it means she can't contact the mother ship due to WiFi down or somewhere in the chain is broken.

Some people just prefer to clean finger prints off light switches. Now you have to install a dimmer and who is going preset it it every morning and night to the correct levels? "Honest Daddy! I will feed the puppy every day...I promise!"

Good advice. However I found for many by logic, I want the bulbs to go dim by time clock, rather than the sun times (I don't go to bed at 5 PM in the winter) so I make sure not too many are being hit on at the same time.

MY routines quite working yesterday also! This happened a few years ago and amazon was always tight lipped about it, and never got back to me. The problem just went away after about a month last time. I have checked all the data spots all the way through and the problem, again, lies with the routines just not triggering, despite every other data point working from variable to pseudo device in the alexa app. You are not alone.

The MS needs to be in Linking mode or ISY will try and retry many times to write to a device that cannot accept any data....thus...BUSY (That would be the Insteon comm channel via PLM)

I have always used adjust scene for bedroom lamps and others that are not wanted at 100% in the middle of the night. It works well and only hits on the LampLincs twice per day. For other multi-bulb scenes, I use command levels % option for each light, especially where it may be a dynamic constantly changing level. eg. I developed a constant compensation for outdoor sunlight levels, where lights inside changed not only brightness levels, but colour temperature (warm to cool white) of the bulbs, based on time of day. The snag there was using lumen detectors (CAO Tags) that updated frequently and yet ran on batteries that would last for more than a few months. It is nice to turn over in bed some nights, triggering the MS and the lamps only illuminate to about 12%, as low as they will go reliably with a LampLinc and LED bulbs. I can still manually command either lamp to go on 90% vocally and it also disables the MS from setting that lamp back for two hours. ISY rocks.

Although I use preset scenes for some lighting, for variable lighting I do not use Insteon scenes. I just use ISY commands with the level % option, specified by a variable. To change the setting in an Insteon scene requires about 10-15 seconds and can get you caught in the middle of the process, under certain situations. IMHO that is asking for devices needing factory reset frequently after they get messed up. .

Yeah. I don't know why amazon hides those commands at the bottom of the list where nobody can find them. I keep the Windows webpage alexa app around just for that mostly. I don't find it on the mobile android app though. My alexa keeps finding other devices, like my laser printer and trying to flood me with advertising to buy their overpriced ink. Every time I delete the printer from the device list it finds it again and start the advertising cycle again. Not impressed with that one but it makes me replace tone cartridges early, wasting more supplies.

I use a program shift register to record the last three events into a variable. Now when a certain pattern is found and triggers various programs I know which way things went. Each room and device has a designated two digit number based on variable constants dedicated to this, and a few other jobs. Text messages and emails are sent using these variables along with a chart of room/device numbers so the reader can interpret where the action is happening, all from one notification message. IOW: no need for a message from each room or device. One message does it all for each function. I have used the same setup for motion sequence (break-ins), leak detection and other functions where the location in the house is important. The common variable used for each function and multiple rooms also allows one program responses that can handle every room, instead of a separate program for each room x (times) a separate bank of programs for each function. Anybody interested in this I can post my programs that handle this. However using three devices in a series is not without it's occasional failures. I do think using only two devices in a sequence would be much more accurate and successful.

Nice catch! Yeah I forgot about the Else section running when status logic is Anded with a switched control event. A switched control event is always False if it wasn't the trigger for the program's own If secton. Marking my post as such.