larryllix

I thought the wallwart was not available any more. Either way, it is fairly cheap and easy to cut the plug off an old 5v cell phone charger (microUSB?) and strip the wires. Leave the batteries in for backup but use good quality cells that don't leak.

Welcome to the forum! You haven't stated what firmware version you are running. V5 made a big jump in possibilities as far as making these things easier. In v5.0.9 alpha, I have periodically running time of day, and day of month, system parameter grabber programs that put DD.MM and hh.mm into decimal state variables. Triggers to look for random dates and random times could be created, easily, from the random arithmetic function built into ISY.

I use seasonal time filters in Folder conditions. The group of programs can then only run during that season and only one time based filter is required. OTOH: because folder conditions are odd / rare and not easily spotted when browsing programs I use very explanatory folder names eg: "Heating on schedule at home" This saves me a lot of digging to find why it works a year from now.

It's Electrical Safety Code.

hmmmmm.. doesn't sound very good, so far. I was going to suggest a factory reset of your ISY but being a more complex procedure you may want to initiate a support ticket request with UDI. People report them to be very responsive. There is a link with every Michel Konahim's post. IIRC you have already power cycled the PLM and ISY properly. Assuming your programs and device profiles are all still intact, have you tried to do a restore PLM again?

I would try to enable one battery device at a time, put the device into linking mode and then try to force each device query. The 1011's are normal as the general query failed on those devices, as they should have. I had trouble trying to wait for the device I put into linking mode, to get auto-queried by ISY each as the device linking mode times out and it would miss it again. I was persistent and as I got more devices stable it sped up. Now I didn't block or disable anything, so I got into a query storm with battery devices that couldn't respond and it really ground things to a halt. I would do things a little differently next time but it sounds like you did some of that, already. You'll get there. It was frustrating for me too.

I found a new PLM took hours and hours choking on every battery devie I have. I have ten MSes so it choked a lot. Once it stopped I put each battery device into linking mode and queried it only, until it behaved like I thought it should. My guess is your ISY is still choking on the massive query. You should be seeing a lot of busy bxes in the admin console. IIRC I went to bed and did my battery devices in the morning. While this was happenning I could get almost nothing to respond on my ISY. Every action took minutes.

I use Insteon SwitchLincs with many Luminus BR-40 LED bulbs and they work fine down to about 8-10% dimming. I don't see why your bulbs wouldn't work but I have no experience with this brand. Usually, problems can be cured by adding on small incandescent bulb to the circuit somewhere. I don't think you will know for sure until you actually try it. With multiple bulbs on one dimmer, your chances of working well are very high. Off glow and flicker don't usualy happen with more than one bulb on a SwitchLinc. You may exeperience some slight flickering at certain levels which you could avoid in your ISY scenes.

"Thermostat" is a reserved word for Echo/Dot and IIRC you can't name a device that without creating confusion.

Everybody knows its a thingamajig with eight whatchamacallits where the whodickies light up like whatzits. Not the thingamabob ones that look like gizmos or widgets with whatnots on them. Sent from a tiny keyboard. Response may be brief.

The Venstar was the only stat that gives out it's API for local (no cloud required) access. I like the Venstar T7800 for access via NodeLink but it seems to have a much more amateurish style than the Nest and Ecobee3. Greener grass? It's good that you chose a unit wth WiFi as then you are independent no matter what happens to your HA choices, down the road. You are dependent on a cloud interface but reading io_guy's comments, the ecobee3 is cleaner and more desirable that the Venstar. Not sure what aspects are making this opinion but he is the one that interfaced to them for us ISY users. Reading and watching reports about stats, they all have one problem or the other. Two of my son's have Nests and based on their praises of them I am glad I didn't go near them. Ecobee has contact burn out problems with A/C that has too heavy of a contactor. Venstar has a wandering sensor that I have to recalibrate about twice per year. I am very sensitive to 0.5C changes, though. I will be interested in hearing how you like the stat and may quiz you donw the road. I found the information on stats very bad and boxes contain nothing but "dreamware", where you imagine all the cools things but will never know until using one for three seasons. Even when contacting tech support I found the tech didn't know the difference between calibration stability and deadband hysteresis. Tech toy company gone HVAC?

Corner placement may make Alexa more sensitive to bass sounds also and contribute to the problem. I know speakers produce bass sounds at a much higher volume when placed into corners so maybe the same thing applies. Teken did some hinting on things he did with Alexa boxes, using some sound masking set ups. I need to do some experimenting with that. In a one large room Gathering room you don't get a lot of places to install an Alexa appliance, not only due to lack of walls, but lack of receptacles. Strangely enough, on one experiment, knowing my speakers saturate the microphones, I tried a Dot on top of the speaker columns. That worked slightly better. I tried to acoustically isolate it from the speaker cabinet with materials but that didn't help any, probably as it got higher off the cabinet and could hear the speaker front better. Thanks for the Home observation. Eliminates any jump over urge for now.

My wife usually pauses the TV when we try to talk to Alexa.I find the large speakers make Alexa almost completely deaf, no matter how low the sound is or where she is in the room. I have given up attempting to have Alexa control my AV system. She can turn it on OK but then becomes deaf. Sometime my Dot in another room will answer with two in the room I am standing in. Watch the dark blue LED pointing where she thinks the source of the sound is. When you see it spinning in every direction while you talk, it's almost useless. Other times she just "disconnects" so I am not the only one that has given up. I don't try to demostrate Alexa to guests anymore. She just embarrasses me, almost every time. If somebody else talks during the demo...she just gets confused.

I had this happen many times. From the admin console query each device and see - if the level changes - what the level is - if the combination of device levels matches any of your scenes. - if the status changes of the devices are recorded in the ISY log. I haven't had problems with this for a while but to my best guess I had a OnOff appliance module spitting out bad code that matched a scene I have. Most of the time the ISY log had an error from the device each time this happened. The cure - I unplugged it a and plugged it back in. I haven't seen the problem since, This is not conclusive but a good indication and only time will tell...never know for sure though. Just power cycling every device may fix it for you but I would want to, at least, get a suspect device first.

I prefer a combination of techniques. The best I have seen, is intiated at the remote by only sending exception reports (violates change % rules etc.) with a periodic heartbeat, usually containing a different parameter each time so that all points are absolutely updated once per every N data points x heartbeat period. Next in line, is a system that uses receiver end querying, but the remote does the same thing, sends the exception reports (data changes that violate rule limits) with one additional parameter (in a round robin fashion) each answer. In a more primitive system the additional parameter didn't happen, and the query end had to issue an all data points poll every X time. Then a flood would happen whereas every data absolute in the system was sent. With today's modern networking techniques, collisions are not usually a problem with lower protocol level, check techniques. Our LAN Ethernets live on that technique. Insteon does that fairly well. Insteon has poor checks at the higher levels. eg. ISY send a lamp On, and receives a status confirmation of On. Then what? Maybe the lamp isn't even plughed in or the triac blew last week. This could not be tolerated in an industrial control system.

In my setup I have to have both WiFis turned on because that is how they talk to each other.

I tried everything I could think of and found in manuals and instructional forum with no luck. In the end, in two attempts over months, now, the only way I can make my Cisco (DD-WRT) co-exist with my ASUS (native) is to share the same SSID and password. They must have some distance between them so they don't clash too hard. Port forwarding from outside via the two routers always works with the device's correct IP addresses though. IP reservation table work in the master ASUS for the remote devices also. This is despite the master ASUS router only showing 1 IP address for all the units hard connected to the Cisco but always shows an extra digit beside the ID showing how many units are connected through it. I tried all the bridge modes and access points and none of them ever worked for me after a few weeks of studying the things.

$60? Heck my last RPi 3 came at about $120 canuck buck. My first RPi came a few hundred dollars as it only supports HDMI and I didn't have a monitor that was less than a few years old with HDMI, a keyboard and mouse, since RPi would take those mini round connectors that all my dozen keyboar and mice have. OTOH the Tags that started out as $15 now run $30-50 and Tag manager is another...what? $50 ...but then us Canucks have to pay our part for the Obama wall to protect against our slingshots that sting so badly on our "bare arms". Things has changed man.

Wouldnt using a Synchrolink be the monitoring tool to notify the user of a pump failure even if it is the Syncrolink that fails? It seems to me, knowing this is a possibility, an ISY, a monitoring Synchrolinc, and some logic, would be enough to be a top quality alert system. Sent from a tiny keyboard. Response may be brief.

trackR has some "coins" that transmit Bluetooth and are absolutely useless for the purpose sold. Their range is the typical range of Bluetooth, about 10 feet. Using an RPi that can detect BT may work if how to interface with the signal can be discovered, sending a signal to the ISY REST interface (that part is easy) The other thing that comes to mind is a thick rope tied on the outside of a pneumatic self closing door. Train a few dogs to push the door open to go outside, and pull the rope, from outside, to go in, making use of the slow close. Another would be a couple of well placed, and shrouded, Insteon MS units and an IOLink, using it's output contacts to activate an input to the door circuit.

You have a repeat statement line with no code to repeat underneath it. You've been out to C too long The construct works like this. Repeat every 45 minutes ...do this ...do that Repeat 1 time ....do something ....do something else

I have the same thing with, especially one Dot, about 10 feet from my router. Perhaps the WiFi is too sensitive and loses connection due to over driving the receiver, being so close?

When the compressor us shut off the refrigerant pressure equalising can turn tge compressor motor backward. If yoy turn on the compressor while the motor is turning backward, most motors will start in reverse. Now you can destroy your whole system. The time delay is needed to protect your system. I did this once, due my stat and compressor on different curcuits, and hopefully my compressor wasnt damaged. Luckily I was outside, heard the awful noise of a compressor running backwards, and responded quickly to the breaker panel, just dropping the compressor circuit. http://hvac-talk.com/vbb/showthread.php?919272-single-phase-copeland-scroll-running-backwards Sent from a tiny keyboard. Response may be brief.

The REST interface is passive and programs, and even a browser, can operate programs, scenes, devices and variables directly by ISY's 'catchers mitt' Sent from a tiny keyboard. Response may be brief.

CAO TAGs have introduced a new unit that sends luminance. People are really impressed with their operation, so far. I have four but no luminence ones yet. They are easy to interface with ISY via it's REST interface. The basic features are temperature, humidity, motion, battery voltage, and no luminance, al in the same tag. Range is good, usually up to a few 1000 feet. Charting is native on their website for all parameters.