Michel Kohanim

Hi larryllix, Neither. And this is what makes NMM challenging to describe. ISY understands commands, properties, and events. What the contents of commands, properties, events "mean" are completely immaterial to ISY as long as it knows how to represent/present them to ISY User (Human Being or AI). So, there are really no drivers in ISY except for "communications, commissioning, and security". Let's try an example: 1. ISY currently does not know how to do anything with NEST 2. Someone creates a NEST Node Server (on Polyglot or in the cloud) and the only thing this node server is telling ISY is: - You can change cool and heat set points with a range of a valid values - You can dim/brighten the backlight - You can change the mode with an enumeration of valid values 3. You integrate this to ISY. ISY does not know NEST is a thermostat. So, purely based on #2: - It creates a GUI that shows you commands for changing set points, dim/brighten/mode - It creates hooks for scene management (say you want NEST to be in the same scene as your INSTOEN thermostat so that pressing button on thermostat does something to INSTEON or vice versa) - It creates hooks for programs using valid enumeration for everything defined in #2 + a lot of other things which are left out for the sake of simplicity Now, what you do with #3 is completely up to you: You can control NEST through UI, you can put it in a scene with anything else, or you can have programs for it just like any other device in ISY. There's absolutely NO code change on ISY. None. In short, NMM moves the intelligence out of the model and moves it up one level to the actual user (or AI) because, at the end of the day, we are not talking about some organic society of things that figure out how to make a civilization (but NMM does allow for this). We are talking about some higher level intelligent being knowing what to do with a thing (through ISY for our purposes). I hope it makes sense. With kind regards, Michel

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

Hi larryllix, Very very close with one exception in the following: It's NOT mandatory for the device to say "I am a thing-a-ma-jig" and the properties you listed do not have to be anything ISY has ever seen before. For instance, a property could be "thing-a-ma-jig" To make it even simpler, all the device needs to let ISY know are: 1. You can do this to me (send me these commands and parameters) 2. I can do these to you (send you commands and parameters such as number of physical button presses) 3. These are my properties All the above are completely FREE FORM and developer defined. No dictionaries, etc. So, in effect, you can define an autonomous car if you wished. Or, a robot. It's up to you. Now, the challenge is to make this simplified to the point that everyone understands the concepts. And, as you know, marketing is not one of our expertise (yet)! With kind regards, Michel

Thank you all for all the feedback. I think we should start with putting a video together. Does anyone know a good videographer/video editor? With kind regards, Michel

Hi Neal, Most likely ISY cannot query the thermostat or it's in Off mode. With kind regards, Michel

Hi tibbar, It should work in 5.0.10. With kind regards, Michel

Teken, There are no consortiums, bodies, or otherwise certification authorities. The point is that you don't need them UNLESS you want all things of type-x to have the same attributes/methods. And, even then, you will only need a compliance layer. I think we are getting too deep into theory. What we really need to talk about should be related to ISY/UDI. Such as: 1. Are there any demand for a marketplace of things for ISY? And, by things, I mean anything. They don't have to be devices, lights, thermostats, etc. It could be what Mwester invented or an expiration RFID on milk cartons. Again, they could be anything 2. If so, how can we reach developers and get them excited? 3. What other things should be included? Such as those you have on your list (which are already supported by Polyglot) With kind regards, Michel

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

Mwester, Didn't really get what you mean. No one is suggesting another scripting language. And, we are not at all suggesting that NMM is just a generic fill-in-the-blanks framework for the masses (not yet at least). It's a developer tool so that developers can define whatever they want and that thing will immediately be able to participate in ISY's framework without ISY having to know what type of thing it is. Precisely what you did with ESP8266. So, I guess I do not understand. larryllix, NMM is definitely not DNP3. It's 100% opposite of DNP3 since it does not define things. It just defines how things should be defined so there are no super/subsets of anything. With kind regards, Michel

Hi Teken, My pleasure. Polyglot is refined enough to the point that we are currently using it for our CEC project which is mission critical. Also, Polyglot is just a Python binding for NMM. What we miss is marketing/videos and, in short, something to get developers/hackers excited. I think a Kickstarter project is a good idea but haven't thought it through yet. With kind regards, Michel

Thank you all. Yes, it should be Meta Model! Teken, Node Meta Model describes HOW things should be described rather than describing/defining things. NMM does not enforce any dictionary or predefinition of things in the world. You can define anything you want and you are not bound by what some standards body decides you should fit into. For instance, how does one define Harmony Hub? What's the dictionary for it? What is it? And, yet, Jimbo defined one based on whatever he thought the Hub should be/behave/do. The same goes for Outback inverter that einstein.42 defined (except for Sunspec, you won't find any standards that define inverters. And, sunspect does not define anything else BUT inverters --> silos of things). So, NMM is basically liberty for things: They can be whatever they want to be (or their creator decides for them). With kind regards, Michel

Hello everyone, I think everyone of us, especially those using Polyglot, would enjoy this article: http://www.eetimes.com/author.asp?section_id=36&doc_id=1332193 With kind regards, Michel

Hi dbuss, I do not think Alexa is tied to the same account as you linked to your ISY Portal. What I suggest is this: 1. Unlink the Amazon Echo account from ISY Portal (under My Profile) 2. In the Echo app, Disable ISY V2 3. Close all your browsers. Also, please make sure you use a computer. Some mobile apps keep cookies around 4. Log back into ISY Portal and redo: http://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration#Instructions_for_Smart_Home_API With kind regards, Michel

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.. It was not one of the steps in the original post. The only other issue could be that they are not linked with the same accounts. With kind regards, Michel

Hi dress, Did you map devices to names? With kind regards, Michel

Hi Dean, Thank you. Please keep us posted. With kind regards, Michel

Hi Dean, This seems to be a defective thermostat or it could be related to the dead-band. It's best to contact RCS. With kind regards, Michel

Hi Noremac, My pleasure. To answer your questions: 1. Backup should be fine 2. Yes, restore devices also restores the PLM With kind regards, Michel

Hi Xathros, Thanks so very much for the details. I'll talk to the team and see what we can do. With kind regards, Michel

Hi savimgc, http://wiki.universal-devices.com/index.php?title=ISY_Developers With kind regards, Michel

Hi Guys, For those with ISY Portal and 5.0.10 firmware: http://wiki.universal-devices.com/index.php?title=ISY_Portal_Node_Server_Occupancy_%26_Locative_app_Instructions With kind regards, Michel

Hi Noremac, Please reboot your ISY, go back to PLM Info/Status. If you still see "connected", then the PLM/ISY is probably OK. What you need to do then is: 1. Restore a good backup FROM BEFORE you did ANYTHING to ISY (especially before any PLM restores/etc.) 2. Move the PLM to a different outlet and one which is not shared with other transformers and power supplies 3. If you have any INSTEON thermostats, unplug them Retry: http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Restore_Devices With kind regards, Michel

Hi Nancy, Can you please send your UUID to support@universal-devices.com? With kind regards, Michel

Hi leonpc, Added as a bug #469. With kind regards, Michel