bipto

Welp, never mind - I was able to borrow a 12V/3A supply from an external hard drive and ISY came to life! Looks like I'll just be ordering a replacement power supply rather than an ISY - cheap and easy! Thanks mwester! ?

Great suggestion, thanks! Any idea what the ISY's current draw is..? I notice the ISY power supply is rated for 1A, but unfortunately the only junk drawer wall wart I have available to test is only rated for half that. I'm guessing that's not enough..?

Woke up this morning to a cold house. Tried to log on to ISY to find out why she hadn't adjusted to the daytime temp (as she has done reliably every day now for years) but she didn't respond. When I went downstairs to check on her she didn't greet me with her usual flurry of activity lights, I saw only her power LED, very dimly-lit. Alas, I think ISY has died... So what happens now..? I will be purchasing a replacement this afternoon - do I need to purchase the EXACT model..? I DO have a recent backup and I was on v5 so I don't imagine there would be major migration issues... What about things like licensing, portal integration, etc.? How do I go about getting things "switched over"..? Any other potential pitfalls I should be aware of..? Thanks for helping me out during this difficult time...

Will the aot option cause any issues when used with mono 5.18? As usual my timing sucks and I think my Christmas eve Pi rebuild may have put me in that situation. Seems fine - any harm leaving it?

We too are back on the air without any intervention from me, probably a glitch in the Matrix... Thanks for checking Benoit!

Though I can't be 100% certain from my office, my wife is complaining of symptoms that sound similar... PM sent. Thanks Benoit.

Yeah, I'm pretty much lost too. It may take screenshots and a couple of drinks for me to figure this out...

What's new / different in V3..?

I see the same behavior with my Generac XP8000E. The lights on dimmers will flash with Insteon traffic until the generator approaches about 50% load and then they quiet down. It's irritating, but better than living in the dark. Insteon behaves far better on this model than my previous Generac GP series, and neither the devices nor the bulbs seem any worse for it given the limited number of hours they've seen on gen power. Probably amuses the neighbors...

I'm thinking this wiki excerpt doesn't hold true in cases where the IF clause contains a device / program status or state variables. In such cases the IF is immediately re-evaluated if any of those elements change. Much of my programming relies on this feature. Correct me if I'm wrong...

Thanks for verifying that this is not what you're seeing, Stu. I did attempt to selectively forget the duplicates, but they all reappear on the next discovery. Not sure exactly where to go from here... The bottom line is despite the dupes the integration is there and everything seems to work. My gut feel says this issue lies with Alexa, but I may submit ticket to see if someone here can glance at the logs to verify... Thanks again! --Bill

But I'm not so sure... It is interesting that the duplication is off the spokens rather than the devices/scenes, but the fact remains that there is still duplication. As an example, an ISY Portal Scene in the following format: Name: Lighting Scene A Spoken 1: "these lights" Spoken 2: "those lights" Spoken 3: "them there lights" Will appear listed in the Alexa Device page as: "these lights" Lighting Scene A --- "those lights" Lighting Scene A --- "them there lights" Lighting Scene A --- "these lights" Lighting Scene A (scene) --- "those lights" Lighting Scene A (scene) --- "them there lights" Lighting Scene A (scene) --- So 1 scene / 3 spokens = 6 Alexa devices discovered... I could be mistaken, but based on other folks' descriptions here I don't believe this behavior is typical / correct...

Thanks for replying, Stu. I've added both scenes and devices (though no programs as of yet) to the portal app, both result in a pair of entries with the only difference being a suffix of "(scene)" vs. "(device)" on one of the two... I'm trying to keep the spokens to a minimum - most have just one. I hadn't noticed before but now that you ask I see that the duplicates seem to be based not on the number of scenes/devices, but on the number of spokens i.e. a scene/device in the ISY portal with two spokens will result in 4 discovered devices on the alexa device page...

Resurrecting an old thread here, but this seems to describe my situation pretty well. Please bear with me, I'm an ISY veteran, but I've only just embarked on this whole Portal / Skill / Alexa adventure within the past week - all this stuff is pretty new to me... I am seeing similar behavior, where every scene added in the ISY portal results in two discovered devices on the alexa page, one bearing the name of the scene, and the other the name of the scene appended with "(scene)". As others in this thread have described, the Echo - ISY integration works well and these scenes are being triggered as expected - it just seems that there are twice as many on the alexa page than there ought to be. Unlike the originator of this thread, I am attempting a new setup of the V2 skill - there is no upgrade involved. I too have executed "Forget All" and re-discovered - the duplicate entries reappear. I have attempted to unlink the Amazon account, remove my ISY from the portal and rebuild from scratch. I have applied all the suggestions in this thread to the extent I understand them, but the result is the same. Any help / further suggestions you folks could lend would be much appreciated! -- Bill

Really... I wonder what Smarthome's Black Friday / Cyber Monday sales were compared to past years. Down I'll bet. Sounds like cutting off the nose to spite ones face... Well this could be a *good* thing I guess - it might be just the motivator I need to kick this habit. My Insteon build-out is getting down to the "nice to haves" anyway, and I'm pretty sure I can find better things to do with my money than financing Joe Dada's bad business decisions...

Yeah, looks history may not repeat this year... That's ok, my order will keep until Christmas, and I'll hope for a better sale then... Sent from my HTC6500LVW using Tapatalk

The ELK output will not respond to a random All-On event...

3 emails and two postcards so far, no movement on the discount as of yet. But I'm a patient man...

Best approach would be to read available info, understand the scenarios where others have seen this happen, and determine whether your particular setup could present / support these conditions. No "fix" per se, but there are programming techniques to minimize / eliminate risk. Keep in mind that many, if not most, have never seen one of these events. Forum thread... http://forum.universal-devices.com/topic/10516-random-all-on-event/page-1 Wiki info... http://wiki.universal-devices.com/index.php?title=INSTEON_Random_All_On_Events

Yup.

Yup. And the shipping deal will likely be better too. If there's one thing I've learned over the years of my HA build-out, it's that you ALWAYS wait until the last day of the Smarthome sale before making your purchase...

That's great news Paul, anxious to hear how you make out...

In shopping for our new system last summer, I found that while the majority of manufacturers' high-efficiency (~92%+ AFUE) models were likely to offer ECM technology, it seemed to me that most models in the 80% class (value / contractor lines) are still equipped with PSC motors, no doubt to hold cost down...

Like your Carrier units, Rheem also has their own line of "smart" thermostats that allow control of total control of fan speeds, burner levels, etc., but they run a proprietary network and would have been damn near impossible to automate, so I chose to go with what Rheem calls their "legacy thermostat support." For people who run in their legacy mode there is a series of dip switches on the control board that allow for some fine tuning of the fan speeds for the various modes and stages in this setup. If I remember correctly, the default "Fan On" speed is about half of the stage one speed, but this was adjustable +/- 300 cfm or so via dip switch settings. In my case, all this information was listed in the Rheem homeowner's guide. Hopefully you'll find the same...

Interesting question / topic, Paul - so here's my 2 cents... Ever since we had our new furnace / heat pump system installed last summer, I run the blower fan FULL-TIME during waking hours when the house is occupied. I was first presented with this suggestion by the system installer, and have done significant research through the manufacturer and other sources to validate the idea. I was skeptical at first with concerns of noise, drafts / constant air movement, and power consumption, but none of those turned out to be an issue. At the low speed that the new ECM motors offer in Fan On mode, the noise and air movement are barely perceptible, and power consumption is rated at a very reasonable 75W continuous. I'm assuming your modern equipment has the same variable-speed capabilities. I do not run the fan 24/7 as I do make adjustments based on time of day and occupancy. During sleeping hours the fan is programmed to run 12 minutes per hour (apart from heating, cooling and humidity demands of course), and when the house is unoccupied the fan is simply set to auto, effectively off as heating and cooling set points are significantly set back in this situation as well. After running with this policy for nearly the entire year+ that we've had the new equipment, I could not be more pleased. The obvious upsides were 1) that with the constant circulation we have a more consistent temp across the entire house with little to no perception of the temperature change across the two degree deadband, and 2) with basement ductwork not allowed to cool below room temp between heat cycles, we no longer get that annoying "cold blow" for thirty seconds when the furnace first starts as it is bringing the ductwork to temp. Another potential benefit worth noting is that the allergy sufferers in our household seem to have had a much better year. Obviously one year is not enough time to attribute this improvement solely to increased air circulation / filtration, but I'm betting it played a part. The only downside that I have noted is that I now have to change my filter more aggressively than I was used to with our old system, which, with the increased air circulation was certainly to be expected. These are my observations based on our particular circumstances; your mileage may vary. Questions, comments and criticisms are welcome and encouraged... --Bill