larryllix
-
Joined
-
Last visited
Posts posted by larryllix
-
-
Sandry, no, that is the the evidence that was needed. It proves that when Insteon powers the fan, the fan (most likely motor) is injecting line noise back down the circuity and overwhelming the fanlinc. Some type of filter is needed.
I've used this with insteon devices that were overwhelmed by ECM furnance motors and transformers. Its very easy to wire to 110vac if you can fit it in the fan body.
Paul
I have to wonder how they can call this "in-line"?
-
Wink made those implications too. It most likely just connects to your other hubs, increasing your hub count by one.
Sent from my SGH-I257M using Tapatalk
-
1
-
-
Hi larryllix,
Thank you! Actually Chris is the brain behind NMM so one of the Ms is not for Michel!
Ah, I forgot to tell you the best part! There's absolutely NO NEED to write anything inside ISY including device blocks. Polyglot (or something like it) shall remain and perhaps one day both ISY and Polyglot can be combined into one (I think that's what you are referring to). The last part depends on our resources.
With kind regards,
Michel
Finding this fascinating...doesn't that mean passing a specific node driver code to the other end, making the other end CPU code dependant and the code hardware dependant?
OTOH, Perhaps a scripting language that already understands individual box hardware (sound output, video, Insteon PLM, wired siren) is the underlying secret then? That would mean ISY would not really be needing much OS change, just the ISY994X box would get smarter and understand where to send what node signal. ISY would become a smart peripheral to it, somewhat.
-
Teken,
NMM is very much the opposite of Vera, Smartthings, HomeSeer, etc. If a developer uses NMM (and understands the concepts), then the nodes themselves will understand each other even without an ISY, or a dictionary, or an app, or anything else. ISY is just a tool that has implemented NMM client in such a way that these nodes can immediately participate in ISY's framework, programs, and extensions (such as Alexa, Google Home, CEC, Energy Management, etc.).
One thing that I have to stress is that node servers do not have to be physical things. They can be services in the cloud (just like our geo fencing node server).
What we are thinking about, what we can do, and what we will ultimately do are very different topics. And, of course, they depend on demand.
With kind regards,
Michel
Trying to understand your concept, please verify my paraphrasing/analogy.
NMM sounds like a definition for a protocol that will allow a device to send a complete device descriptor block to ISY (or other smart device) and ISY can instantly self install node pieces that understand all the given aspect/parameters to be expected from the device.
In effect, ISY could start out knowing nothing about any device. When a device first connects to ISY (or other smart device), it sends it's personality and/or configuration. ISY would then configure itself, installing all the styles of node drivers it was told about and now understands the remote device with all it's nuances.
On a simpler scale, it would be Plug'n Play, but on a smaller chunk scale (not on a whole device driver scale), to be able to represent any possible new device with many less drivers than one large one for every device produced.
Simplified protocol talk
DEVICE. "I am a thing-a-ma-jig . I contain an MS=On/Off, Brightness Level=0-100%, Battery Voltage=0-3.5 volts, Angle Detector=0-360 degrees" -----> ISY "OK.... Installed Thing-a-ma-jig.....Ready for values"
Thanks Michel
-
1
-
-
Edited by larryllix
Michel
One other item that will help get developers excited is an existing Consumer base
That means making sure all existing users have an easy path to adoption...selling a rPi preinstalled plus a couple of node servers should generate revenue and accelerate adoption
Excellent! A multilevel hardware/software offering may also be a winner.
Offer the hardware, hardware with basic polyglot, just polyglot, hardware polyglot and one installed node server, complete with paper instructions enough to reveal the whole soft manual stored in the ISY994x box.
Sent from my SGH-I257M using Tapatalk
-
-
-
Edited by larryllix
I was speaking on how other companies do their 3way switches. For example, the GE jasco uses the traveler so it will not talk to another switch (may have changed since I tested capabilities but it was that way at one time). In the end, it's irrelevant as this is all hypothetical. They made their choice and from a personal standpoint, I agree with it
X10 did the same thing. In fact even the load bearing switch was special with an extra wire to receive the 120vac pulse the 3-way special X10 wall button created on the traveller wire. The house wring required a hardware 3-way circuit to begin with.
Insteon does it so much better, and the way most circuitry is going...keep the hardware generic and universal, and let the end user decide how s)he wants to design the logic with as many options as possible available.
-
1
-
-
To clarify most of the repurpose comment, I moved and I didn't want my price further reduced due to weird switches that people would want money discounted from the asking price due to needing electrical work done to remove the weird devices.
After the deal was made, I removed the X10 wall switches to take with me, because I wanted them. On the day of closing the new owner walked in and asked, "what happened to those switches?". I answered some made up story about only operating with my computers, when she said, "Good, My father is an electrician and he said he could replace them all with normal switches. That will save us some time and money".
Now they sit in a box as I went to ISY and Insteon for a better system.
-
Michel.
Nicely written and expressed!
This sounds like you are redesigning DNP3 protocol. It's a very popular SCADA protocol used the world over,
Been there, done that. It gets out of hand with brands completely incapable of talking to other brands due to the immenseness of the protocol. I wrote an DNP3 analyser once. Just enough to fix the incompatibilities between two brands of equipment. WOW! I spent six months and maybe covered less than 10% of the known protocol, without any custom internal protocols.
For HA automation a subset of DNP3 could be defined in addition to the many other subsets already registered. Video widens the protocol somewhat but well defined already.
-
Edited by larryllix
Looks like the Internet is fighting IPv6 extended IP addressing.
Interesting that this can penetrate through routers into the LAN, that reconfigure addressing to LAN addresses. Ports seem to be used for similar purposes but routers like to play and convert them, as well. ISPs can block and tweak port numbers.
SNI creates an addressing scheme that can now penetrate the router madness (being part of a lower level of the protocol) and can cause distribution inside a remote LAN, behind a firewall.
-
Edited by larryllix
Interesting. What benefits will that provide users?
Not sure. The box has been added into the ISY Network resources for certain services that require it.
A better analogy might be when the packet arrives at your router via IP address ww.xx.yy.zz from the Internet, the port number allows it through the correct router firewall, and the SNI could direct the correct computer to use the packet.
Thanks to mwareman in another recent thread...
https://en.wikipedia.org/wiki/Server_Name_Indication
Probably cheaper than purchasing a bunch of IP addresses.
-
-
I believe in home automation as a goal, The remote control is fun but not really any point if the HA is done properly. I probably touch a wall or lamp switch only about 2 times per day in normal daily activities. ooops. I lied. I touch my ensuite SwitchLinc many times per day, but right now, having it change laser intensity to not wake up the spouse intensity twice per day is good enough automation. That may change later when I get ambitious.
My goal is not to require any switches at all, so a special 3-way switch that cannot control a load and only performs half the usual tasks usually available with devices in a switch box, is not much use. Out of my 10 Switchlincs in use, I have none without a connected load. I always back up vocals with a hardware switch somewhere. If my ISY failed i have manual remote controls for all lights in a cupboard somewhere.. If those batteries were found dead and needed, then there is the plug in the receptacle to be pulled..
I do have a hardware four way system in my front foyer and a three-way system in my stairwell. apostolakisl's easy switch to reach applies in those cases and also I was warned in many places over the years, not to automate staircase lighting. Ever had a power failure while walking down a staircase? You quickly grab for a railing, while your feet freeze and your weight keeps going forward. Creates a moment of complete panic.
-
Edited by larryllix
www.blinds.com or www.blinds.ca in Tx. has the best prices I have seen. I have dealt with them twice now from Canada.
-
-
Edited by larryllix
Mini-Remotes are switching devices without a load connection. Get the one button rocker ones. There is your 3-way switch unit without load connections. Get some wire nuts and get over it. The X10 3-way switches required house wiring between the dummy and the load connected switch so they weren't usable for upgrading like Insteon SwitchLincs are.
I have a junk box full of three way X10 remote switches and after decades of using them I wouldn't buy a 3-way Insteon Switchlincs, even if they were available. For a few bucks more the full SwitchLinc gives me the capability of repurposing it later, when my brainstorms change. I prefer one standard style of SwitchLinc I can use anywhere I want, not have to have a stockpile of different switch styles to use for different applications.
Similar to Stu, once you activate some real HA and vocal controls, and not just install remote control systems, the need for 3-way starts to disappear.
Perhaps SmartieHouse knows more about the future than we think.
@Teken. Thanks for that
-
1
-
-
Hmmm. Don't know either. I re-followed my own directions and got the same value that's the second entry in my finder that I added.
I'm not sure how pasting a link in the thick java client finder would cause a download. That sounds more like what happens when you run the ISY's web page from the portal and ask it to install the admin console.
Paul
Used the bottom method with the URL cut'n paste.
Being very confused why the admin console link mysteriously appears on my Win 7 desktop....
-
Hi larryllix,
Thanks so very much for letting us know. ISY Portal does not know anything about 5.x branch. We definitely have to make this more clear. I do apologize.
With kind regards,
Michel
Thanks Michel.
Furthering this. Was there something I did to mess up the access using a v5. UI?
Mostly when I do these things I end up with an Admin Console link on my desktop. I suspect that was a v4.6.2 and I forced it to replace my v5.0.10 UI in my folder (Win 7).
Should I have just deleted the new a/c link and used the existing one and would that be the proper method?
-
That link documents how to add the portal link to your ISY finder to your existing copy of the admin console... for just that reason.. whatever copy you have on existing your PC is the one you'll use.
Paul
The link provided in the Portal "ISY Information" was added to my existing "ISY Finder".
I am not sure why it loaded v4.6.2 or how it would even know which version to load.
-
Following the Wiki instructions to use the admin console from the ISY Portal, it loaded v4.6.2 UI instead of matching my v5.0.10 f/w.
Luckily I caught the error without any ISY program damage when it loaded my programs in less than 15 seconds instead of the usual 2-3 minutes. Then I noticed that programs were not complete with errors marked.
This needs some attention and I believe somebody reported a bad version load in another thread somewhere else.
Thanks!
-
This is dangerous!
It installed UI v4.6.2 over top of my v5.0.10 UI.
I caught it when I noticed that the programs loaded in less than about 20% of the usual time and then found mnay of my programs incomplete with <unspecified devices> lines. Luckily I didn't save anything and did some digging o I would have destroyed my ISY program image.
In the back of my mind somebody had previously reported this and UDI noted it. This needs to be fixed ASAP and make the Admin Console from the Portal useless.
-
I also prefer one less device to understand and keeping the style list down to one device. I use three way systems in my house but all Switchlincs have their own loads. I use programs that can selectively act as three-way switches or not.
Typically it works like this. Tap on only gets it own load. Double tap On, gets both loads on. Same with Off logic. This allows me to remotely turn a light on at the other end of the house (wrap around deck and porch lighting) and then turn the local one off. Useful occasionally.
Alexa has made much of this program logic redundant now. In the end the total and independent control of as many finer lighting components works better. Dimming can be done by ISY and is never wanted during 3-way operations.
eg.
Alexa, Turn On outside lights
Alexa. Turn On side deck lights
Alexa. Turn On porch lights
Alexa. Turn on runway lights (under side deck)
...and the Off reciprocals
-
@Teken. Thanks! I wanted access though. This has never worked for me before. When accessing this style I only get a page full of XML code.
@Paul. Thanks. Looks like the first few lines don't match the newer style...maybe? I followed Michel's list and got there. Just editing some programs for a new MS and I get occasional socket and other errors (UB?) via the Portal. It ssems to act as if it is reconnecting every few minutes too with the "can't connect to Christmas Tree (disabled) device".
Good enough/workable for doing some necessary maintenance while away if the need ever arises though. V5.0.10.
Disable Device
in ISY994
Use an overriding long term timer so if the Off signal is not received, the light turns off anyway.
Many users disable the Off inside the MS options.