larryllix

Do you have delayed writing to battery devices option turned on? Have you put your MSes in Linking mode and wrote the updates to them. Mine took almost ten minutes each to dump the ISY cache into them. Every MS motion sensed would cause a massive Insteon data storm for several minutes. After dumping the cache out, and disabling the delayed write option all is running fast again. I had lights responding 20-40 seconds later with direct scene control to the MSes..

Paddles or Keys do not have a status. As posted elsewhere Not Off will never be true. 'Off' will be when the event happens. Not cause the Else to run because it is now False while being evaluated from the event. In your case posted If control switched Not Off Then do A Else do B 'do A' can never happen. 'do B' can.

I had an OnOff Module (plug-in for humidifier) randomly send out a Scene On code when operated, instead of an 'On' ACKnowledgement. A simple power cycle cured that one, after months of sleuthing a phantom "All On" with some recognisable pattern intelligence.

OK, wrong person to ask, The "delete All" was in the original Alexa App in both the Android and the Webpage version. Now, with the newer Alexa app, the app doesn't give full functionality on my mobile Android 4.4, or in any browser I have been using since, Amazon decided to obsolete users not supporting recent google advances. I would have to borrow my wife's phone to see if that feature still exists. UPDATE: The "Delete All" option is still there in the RPi Chomium rendition of the Amazon webpage app. https://alexa.amazon.com/spa/index.html#appliances

Good catch! This may be a desirable feature for the OP. Each time the gate is changed open or closed, Else will run resetting the Else timer, effectively making the algorithm 5 minutes after the last gate change the next open will notify. Gate traffic will extend the time.

In the past every so often, after playing with the setup, you would have to go to the bottom of the device list (In alexa app) and "delete all", then rediscover or you got duplicate names and trouble. The trend today is to grab onto everything you can in a database. As a piece of software, they think it makes it look smarter.

iR control? My grandfather used to talk about that technology. Just kidding. I was going to go that route with the iR Insteon plug-in, but I could never get it to work with ISY. After finding the two LED transmitters wired into opposite polarity and fixing that, I gave up a few ISY versions ago.Of course, when you buy things from SH into Canada, you are at your own risk and defects just become garbage. Spent some bigger bucks and bought a Network capable A/V receiver. That was fairly easy except for telling Google Home it was in the Gathering Room. Never tell google anything. It loves to turn off my receiver with the lights now. Soon to be booted to the curb as SkyNet continues to grow constantly Now I have to figure out the encrypted jargon for a Samsung TV

No network connectivity? Will you use iR to control them? Sent from my SGH-I257M using Tapatalk

Why do you want to talk too a RPi for this? You can control most A/V receivers directly from NRs. I wrote python3 code to receive GET requests on my RPi from NRs that I have posted in another thread somewhere.

I find a similar situation as Paul with the humidty figures. I constantly hear people say their humidity is about 50-60%. I think in a calibrated world this is way-off-centre. I try to keep my humidity between 36% and 44%, set on my ecobee3 and ecobee4. My humidifier could run 100% of the time and I would never be able to keep it over 40% using about 10-15 gallons of water per day. If my humidity approaches 40% my windows would be raining and running water onto the floors in the winter. Double pane with low-E coatings and argon gas filled. I have no wired humidifier but use ISY to interrogate my ecobee4 for it's setpoints, and current humidity. Then I run my floor humidifier co-ordinated with air-handler fan cycles. This is also co-ordinated with my HRV ventilations system. They all get pulses of long or short run time based on the requirements of the setpoints. The HRV ventilator cycle length is based on whether the humidity or dryness outside will benefit the house interior and also if the temperature outside will benefit the inside air temperature. This means that when the stat does a setback and the air outside will give free cooling, it get it. If the stat brings the setpoint up in the morning and the air temperature will benefit the inside temperature it will get it from outside via the HRV. All these cycles are based on ISY's knowledge of the house temperature and humidity from my ecobee4. This worked just as well with my Venstar T7800 stat previously, also.

I don't see the homework issue as a problem. For math they gave to formulate their problem into a prper sentence and usually understand what tgey are asking first. It becomes easier to just get the answer out of their head. Great for advanced things like squares and cubes. Night Time stories and music are great The intercom and emergency phone dialing features can be nice too. I already bought my 5 year old granddaughter a Dot and my 4 year old grandson is getting a Dot in March. Only because GH was too expensive at the time. GH is better for the non-techie AFAIC. Just don't allow vocal purchasing. I think it is stupid to order something blind anyway.

Here is the program where I use the two decimal places just for looks. MM.DD The three time triggers are just insurance against a power loss or me playing with the program during the time. Note that the scratchpad variable can be Integer but the resultant variable MM.DD must be State in order to trigger the programs that depend on it. Also you need to set two decimal places for them. Set MM.DD - [ID 00B8][Parent 0006] If Time is 12:00:01AM Or Time is 3:00:01AM Or Time is 6:00:01AM Then $sISY.DayOfWeek = [Current Day of Week] $sISY.DayOfMonth = [Current Day of Month] $ISY_Date.scratchpad = [Current Day of Month] $ISY_Date.scratchpad /= 100 $ISY_Date.scratchpad += [Current Month (Jan=1, Feb=2, etc.)] $sISY.MM.DD = $ISY_Date.scratchpad Else - No Actions - (To add one, press 'Action') And this is how the usage looks. The programs do not care what day of the week or year it is. I have many programs for other devices that use the same variable for dates ranges independent of the year. Until V5 I was changing my program times every year but usually when the time comes it was forgotten about and had to be reset after the cycle should have started. Xmas Lights.9' tree - [ID 00BA][Parent 00C0] If ( Time is Sunset + 15 minutes And ( $sISY.MM.DD >= 11.15 Or $sISY.MM.DD <= 1.06 ) ) Or ( Time is 5:00:00AM And $sISY.MM.DD >= 12.24 And $sISY.MM.DD <= 12.26 ) Then Wait 1 second Set 'RecRm Christmas Tree' On Wait 6 hours Run Program 'Xmas Lights.9' tree' (Else Path) Else Wait 1 second Set 'RecRm Christmas Tree' Off

I have 3 Dots, an ecobee4, an Echo and three Google Home minis. The GH minis are a lot smoother for looks and AI but so far, the minis are trouble due to the AI making assumptions.. If they don't understand the device you stated, they make something up, even if it is every device in the house. Alexa makes up some excuse about multiple units and asks for a repeat and never guesses. At this point I have almost give up on the minis for HA. "Turn on Red bed", "Turn on Red bedroom", "Turn on Red Lights", and "Turn On Red bedroom lights", can all get various devices that contain Red in the name and usually all 9 of them will get triggered. "Turn off bedroom lights" gets every colour program and white lights in that room as it assumes I mean everything with bedroom in the name. You can see ISY run through flashing most of the rainbow and white before turning the string off. duh! With Alexa. "Turn On the Red lights" gets one room and "Turn On red bedroom lights" gets another room as they are two different programs. For looks, smoothness of operation, sound, function and online AI, the Google minis are far ahead but that AI gap is closing.

The best is still as I posted and I still use it with a slight modification. I use two decimal places now so that the value becomes MM.DD, or 12.25 for Christmas. I can post that later if needed. Just follow the same link. https://forum.universal-devices.com/topic/17157-more-flexibility-in-schedule-setup/?p=152606

Only when I am alone. Sometimes I use blue, purple, mauve, or indigo, but never green. I have a program turn them off in 2 hours. Just-in-case.

I have discovered that Google Home can only understand two words and does not understand three word in a phrase. "Hey google! Turn on red lights"...Turns on red lights in Gathering room....as per vocal in ISY Portal "Hey google! Turn on red bedroom lights"...turns on red bedroom lights and then turns on 8 more red LED systems in gathering room. Google Home makes assumptions that other devices matching two words of the three word phrase vocals are the same grouping "Hey google! Turn on bedroom red" ...turns on just the red bedroom lights and it echoes the correct phrase from the ISY portal translation database ..."Turning on red bedroom lights" Google Home finds the most closely named device and operates the correct device despite the vocal not matching it. Google Home is using only the first two words of my vocal and making assumptions on the third key word.. 1. Is this a deficiency in the ISY portal software or something that Google is causing? 2. Is there a way to turn off this Google Home grouping assumption stupidity in the app somewhere?

This problem has been getting worse as time goes on. I have just added a third Home Mini along with my 3 x Dots, 1 Echo and an ecobee4 (Alexa). The problem seems to be Google Home only listens to the first and last vocal words of the device. Alexa has and always works fine using the same vocal syntax. In the past, I discovered I had to change my vocal "All Lights" because GH determines this is every device in my home (despite my definitions), including the rear doorbell, workshop dust collector, water well pump and a few other gooodies. Not a good scenario and almost useless, if not dangerous. Then I discovered that any rooms I had assigned to devices in the Google app may be assuming the word "lights" (plural), means every light in that room grouping. (that I think Google mistakenly called a Room instead of a group?). I had to create a ridiculous room name "Unassigned", because like most Google AI, it will never "let go" of an idea leaving the user frustrated with assumptions, they don't want. After 2-3 hour of searching, I couldn't find a way to actually remove an item from a room once assigned. It knows more about what I want, than I do, I suppose Anyway, here is the latest google Assumptive Intelligence. with about 20 different devices involved that it thinks I want operated together. All devices are only operated by ISY programs. Alexa. Turn on red lights..Turns on red coloured LEDs in Gathering room...works perfectly Alexa. Turn on red bedroom lights. Turns on red coloured LEDs in bedroom...works perfectly Hey google! Turn on red lights...Turns on red lights in Gathering room....works perfectly Hey google! Turn on red bedroom lights...turns on red bedroom lights and then turns on 8 more LED systems in Gathering room to red. Interestingly enough. There are no cross programs or confusion in ISY or the portal. It's just Google making ridiculous AI assumptions again. As a test I tried this, reformatting ISY portal vocals. Hey google! Turn on red lights...Turns on red lights in Gathering room....works perfectly Hey google! Turn on red bed lights...turns on red bedroom lights and then turns on 8 more LED systems in gathering room to red. Hey google! Turn on bedroom red lights...turns on red bedroom lights and then turns on 8 more LED systems in gathering room to red. This is being repeated for every colour, red, orange, yellow, green, blue, purple, mauve as well as white sequences every light in both rooms through every program controlling the whole colour spectrum. So with Hey google! Turn on white bedroom lights....9 LED string take turn flashing through 7-8 colours and then end up with a random colour or white. Note: These are direct devices but rather all programs, one for each colour in each room. As much as I think the google home minis have a much smoother feel, look, sound, and operation than amazon Dots, google's AI drives me crazy trying to tell me what I want. grrrrrrrr... Short of throwing a brick through google factory's front door here, anybody have any suggestions? Even how to delete all these things and start over. Somehow I doubt the app will ever forget anything no matter how hard I try to delete it and/or reformat my mobile devices, or even smack the pres in the head as he comes out the door of the google factory.

This problem has been getting worse as time goes on. I have just added a third Home Mini along with my 3 x Dots, 1 Echo and an ecobee4 (Alexa). The problem seems to be Google Home only listens to the first and last vocal words of the device. Alexa has and always works fine using the same vocal syntax. In the past, I discovered I had to change my vocal "All Lights" because GH determines this is every device in my home (despite my definitions), including the rear doorbell, workshop dust collector, water well pump and a few other gooodies. Not a good scenario and almost useless, if not dangerous. Then I discovered that any rooms I had assigned to devices in the Google app may be assuming the word "lights" (plural), means every light in that room grouping. (that I think Google mistakenly called a Room instead of a group?). I had to create a ridiculous room name "Unassigned", because like most Google AI, it will never "let go" of an idea leaving the user frustrated with assumptions, they don't want. After 2-3 hour of searching, I couldn't find a way to actually remove an item from a room once assigned. It knows more about what I want, than I do, I suppose Anyway, here is the latest google Assumptive Intelligence. with about 20 different devices involved that it thinks I want operated together. All devices are only operated by ISY programs. Alexa. Turn on red lights..Turns on red coloured LEDs in Gathering room...works perfectly Alexa. Turn on red bedroom lights. Turns on red coloured LEDs in bedroom...works perfectly Hey google! Turn on red lights...Turns on red lights in Gathering room....works perfectly Hey google! Turn on red bedroom lights...turns on red bedroom lights and then turns on 8 more LED systems in Gathering room to red. Interestingly enough. There are no cross programs or confusion in ISY or the portal. It's just Google making ridiculous AI assumptions again. As a test I tried this, reformatting ISY portal vocals. Hey google! Turn on red lights...Turns on red lights in Gathering room....works perfectly Hey google! Turn on red bed lights...turns on red bedroom lights and then turns on 8 more LED systems in gathering room to red. Hey google! Turn on bedroom red lights...turns on red bedroom lights and then turns on 8 more LED systems in gathering room to red. This is being repeated for every colour, red, orange, yellow, green, blue, purple, mauve as well as white sequences every light in both rooms through every program controlling the whole colour spectrum. So with Hey google! Turn on white bedroom lights....9 LED string take turn flashing through 7-8 colours and then end up with a random colour or white. Note: These are direct devices but rather all programs, one for each colour in each room. As much as I think the google home minis have a much smoother feel, look, sound, and operation than amazon Dots, google's AI drives me crazy trying to tell me what I want. grrrrrrrr... Short of throwing a brick through google factory's front door here, anybody have any suggestions? Even how to delete all these things and start over. Somehow I doubt the app will ever forget anything no matter how hard I try to delete it and/or reformat my mobile devices, or even smack the pres in the head as he comes out the door of the google factory.

Except about 20% of the price of Amazon.

Stusviews has had some luck with this. Look for another thread in the search engine.

This is one feature I always like to install. The just-in-case safety lines. Spot on!

I don't know why any designer would use these old Molex style pins for a PCB edge connector, anymore. People using the old SS-50 bus (SouthWest Technical Products) based computer motherboards, know what I am talking about. After about a year of use it was very common to have to unplug and replug these connectors every few weeks to wipe the contact metals clean again. This was with 1-2 MHz CPU signals. I hate to think about GHz speeds using this junk. Then came the contact cleaner spray and silicone, anti-oxide spray coatings and then eventually polishing the oxide away, and garbage. Gold plating was tried with much better luck but became too expensive. I see the ISY Zwave assesory PCB uses these connectors as well as the GPIO bus on RPIs.

Welcome to the UDI forums!!! I would get a proper direct wired thermostat system for this application. The difference between 102F and 105F is from luke-warm to scalding feeling, where you will not be able to get in the tub. The Insteon stat will never handle this accurately enough. If you want to monitor and use ISY based setbacks etc.. I would recommend using a CAO Wireless Tag that comes with the remote probe. There is currently another thread regarding this matter in the forum. Once you purchase a Tag manager, other Tags can be added for so many applications with ISY. The kumoapp code for this is posted in another thread on the forums.

Find the thread with the CAO Tags information. I posted a kumoapp program that you can drop into the kumoapp. This will take some talking you through it but you can do it.

You need to write your program in the Else section then you can use. Hey Google! Turn Fan Off.