Guy Lavoie

That's good to know. I would have thought that the PLM would have done that, not the ISY. That way, a failed scene command could have been reported back to the ISY as a communication error with a device.

Interesting. I did think about motor noise interference, but hadn't looked up the fact that the i/o linc is powerline only, which would certainly make the problem more likely. I also have a separate closed door sensor and Insteon thermostat in the garage (which is detached from the house but close by). Maybe adding an unused lamplinc might be an idea for signal strength.

I thought I'd start this thread after another user (oberkc) mentioned a problem similar to one I've been having, where the status of the door closure detector doesn't seem to be updating. In my case, it seems that the status of the door detection remains On (ie: the door is closed) even after opening the door. The result is that a command to then close the door doesn't do anything. In testing it, I would issue a Query from the admin console and that seems to update the status. In response, I've added a few Query commands, spaced with Wait statements after opening the door. This hasn't been implemented for long enough to know if it's a viable workaround, but I'd like to know if others have experienced the same thing with this module?

Interesting, a few days ago I also created a test program (but simpler than yours) to test that a series of waits would always complete, as part of trying to understand this problem. I created 9 integer variables, and a program like yours that incremented one variable, sent a few Insteon commands (turning off basement lights), wait a few seconds, then increment the next variable, etc, all the way to the end. Then I had a second program trigger it every few minutes. My thinking was that if the program ended before all the waits had executed, then some of the later integer increments would be missing. I let it run overnight. The next day, all the integers had incremented to the same value, about 550. None were missing. Both our tests seem to indicate that the problem is elsewhere. Having motion sensors in the mix can certainly be a factor. I suggest that CoolToys try to simplify it down to something more linear (without anything that might cause random triggers, like motion sensors) and/or break it up into several programs that would make it easier to troubleshoot.

Yes, I hope they give out a few more details of how it works, what's needed, etc. A teaser screen shot of the new admin console wouldn't hurt

Not to hijack the thread, but are you talking about the Insteon garage door kit that has an i/o linc? Just reply yes or no. If yes, it might be worth starting a separate thread on it. Thanks.

I'd do it like this: If 'Motion Detector' is switched On (Control) And $Test1 is 0 Then Set 'Test Switch' On Wait 1 minute Set 'Test Switch' Off ------------------------------------------------- Override motion sensing If 'Test Switch' is switched On (Control) >>> paddle the switch ON Then Stop program 'Motion turns on Switch' Set $Test1 = 1 ------------------------------------------------- Wait 15 seconds after turning off the switch before resetting the variable (to prevent motion restarting timer) If 'Test Switch' is switched Off (Control) Then Wait 15 seconds $Test1 = 0 The idea is that $Test1 is a flag that enables the motion sensor (when = 0) or disables it (when = 1). The override program sets it to 1 to disable the motion sensor from generating a switch On command. The last program looks for the switch getting turned off manually, and waits 15 seconds before re-enabling the motion sensor to turn the light on again.

Well the text says: Link WiFi-based Matter switches/plugins directly. Link Thread-based Matter switches/plugins through the Nest Hub (2nd Gen) or Apple HomePod. All through UD Mobile! I'm guessing that for the wifi based devices, the Zmatter dongle shouldn't be needed. For the thread based devices, it's not as clear. Thread is a wireless communications standard that requires a controller that acts as a router. It's like an extension to wifi, allowing a mesh network between devices, and using low power, which is important for battery powered devices. I'm guessing that the dongle will play a role here, though the mention of the Nest Hub or HomePod seems to imply that either one of those devices is also needed, or that it might be an alternative to the dongle. That should certainly all be cleared up soon enough for us. But your question is a good one: is the dongle necessary for Matter to work?

That's not an easy question to answer. It varies with how many walls you have what they're made of, etc. Ideally, any given devices would be able to "see" at least two other repeating devices, allowing the alternate paths to set up based on signal strength. That's what mesh is all about: getting redundancy through multiple alternate paths, instead of manually determining and configuring a signal path.

Well the version itself could always be fully capable, but could offer wizard style utilities for people who want to do simpler stuff like scheduled tasks or macros. A bit like the Alexa app from Amazon, which steps you through programming a routine. That could help someone get started. Then if they want to get in deeper, access the full programming screens. The mention of ipads in the case of Chris's friend Warren is another thing. I actually commented on this elsewhere, when it was mentioned that Apple Homekit support would be added. Apple users are more often than not non-geeks. They just want things to work without needing to go into technical stuff. This is where wizard like features might help with that.

Well, the more features and device support that gets added, the harder it is to create a dumbed down version. What do you leave out? I suppose you could have it just do macros and scheduled tasks...like a hub.

Any difference in range would probably be very minor. Zwave really depends on it's mesh network topology to get signals to devices that often aren't even in the same room.

It's probably just to widen the market for the eisy. The world of home automation has evolved from the early geeks who probably started with X10 (...I plead guilty) and has slowly "cunsumerized" itself with shrink wrapped products like Alexa, smart thermostats, and Homekit. Apple users aren't usually techno geeks: they're more often drawn to the slick look of the products and just want it to work. But once we get into home automation, some of us will want more than just a fancy remote control with pre-programmed routines. More often than not, those users will likely also not want to lose their initial investment, but rather add to it. Insteon was successful because it also worked with X10. Now someone who got into automation with Apple products can go the next step and expand into full programmability with the eisy.

Hopefully, they meant to say browser based...

Hah, naming devices for voice control has it's quirks. When you start to have many devices, finding good, unique names becomes a challenge.

My question is: how different will the look and feel of the new admin console be? For all it's quirks, we get used to them, so needing to relearn stuff is always a bit annoying. Will there be new console user features too? For example, it would be handy to be able to comment out program lines instead of always needing to delete them. New monitoring tools? Another thing that would be useful is a user log file that you can write to by program action. It would be handy to be able to do things like log the locking/ unlocking of doors, alarm activation, or for troubleshooting. It would be easier than needing to try to filter through hundreds of lines of the activity log. Just a few ideas.

That would be a unix version that eisy is running on. It's currently been 13.1 for most people.

If you've read up on the way Hue works, or even signed up for their developer program, you'll know that you can have local control by sending REST style commands as in your example. The "special key" to access the hub is unique, and is generated by the hub when you request one, and the link button on the hub has been pressed. I learned all about the Hue protocol by messing around with HA-Bridge, which is a java program that emulates a Hue hub, and allows you to trigger command line programs, http requests, etc from Alexa. I originally used it to control X10, directly and also through my Ocelot controller. I'm still using it with the eisy. Your comment about looking at the admin screen and causing you to hesitate is common. The learning curve looks steep. The trick is to conquer little bits at a time. I'm still new to the eisy (I first got it in August this year, have been an Ocelot and X10 user for 25 years). Then there is the forum that you can search through and ask questions. That's how we all learn!

That's one of the big selling points of a controller like the ISY: local control. A lot of vendor specific hub products go through the internet as a cloud service. UDI only sells controllers, so they're not tied to a particular device communication technology. Now the two products mentioned so far (Hue and Venstar) both feature local APIs, which is why they can keep working without the internet. Some of the vendor features like skyport for the Venstar might not work, but the ones using the local APIs will. Same with Hue. I'm not sure if the Hue app requires the internet or not (I'm seeing messages that a user account will soon be required) but the ISY or eisy can certainly keep talking to the Hue hub, unless they end up changing that someday.

That brings up a question I've had in the back of my mind: where did the names ISY99, ISY994i come from? Doesn't exactly roll off the tongue. It sounds more like a part number than an actual name. I'm sure there's a story...

I agree, and furthermore, the people developing the software shouldn't be the document writers! The usual problem is that they're too familiar with how it works, so they'll overlook stuff and can't always anticipate some of the questions that some of the users will ask themselves. I say that from experience. The Applied Digital Ocelot controller was a great little controller, but with gaping holes in it's documentation. The way the logic operates, order of precedence, etc wasn't properly explained. When they brought out the next major revision of C-Max (the equivalent of the admin console), they actually hired me, a user living in another country who had never set foot in their offices, to rewrite the manual for it. 150 pages later, it really made a difference, and they were very happy with it. It didn't happen by magic. I sent countless emails back and forth with the software developer, and we really figured out how everything worked, down to the size of the internal command output buffers, etc. and put words to it. That's the kind of thing that would need to happen with the eisy.

It often happens that you need to exit and log back into the admin console to see plugin related things, especially if you made a configuration change to the plugin.

Normally yes. https://wiki.universal-devices.com/Eisy:User_Guide Scroll down to zwave

One thing I did for pool solar pool heating automation is to make a waterproof temperature probe to use with a supported thermostat (used for temperature sensing only). My first version was with a spare Venstar T7900 , connecting a 10k thermistor, configured as an external temperature sensor. I used a stainless steel drinking straw, pinching one end closed and sealing it with JB weld. I soldered a two conductor wire to the thermistor leads, put it in the steel tube, and then sealed the wires coming out with JB weld. I put the end of this "probe" in the pool skimmer, where it's shielded from sunlight, and it's provided very reliable temperature reading. Next summer, I want to make a new version using two Insteon 2441TH thermostats (that I got as part of used lots of Insteon devices, they literally cost me nothing). One will measure the water temperature, and the second one the air temperature in my rooftop solar heating boxes. I was using a on/off fixed setting baseboard thermostat for that. Now I'll be able to use program logic to decide to switch on the solar heat based on temperature differential. An added bonus will be the ability to ask Alexa the water temperature.

The two connectors are for the zwave and zigbee antennas.