jwagner010

Anyone out there use the Neato Botvac even if you don't have the experience to write a Node Server, just curious if I am the only person who uses a Neato Botvac versus a Roomba?

Not sure what that has to do with my suggestion and use case?

In some instances I use Programs to turn on devices as I require the program to do a number of 'checks' before turning on the device. When adding a Program to the favorites dashboard it would be nice if we could show the status of the device that the program is turning on or off next to the Program itself. For example, if I have a program called 'Ceiling Fan' and add that program to the favorites dashboard, when setting up the Program called 'Ceiling Fan' as a favorite it would be nice to be able to select the device to show as status on or off against that program on the favorites screen. I know I could just put the Device itself under the program as a favorite, but given I don't want to turn the device on unless the program does the checks I would prefer not to have the device itself on the favorites screen. Not sure if others have a need for something like this, and I am sure it would be low on the priority list but wanted to put it out there for consideration. That and geo fence would be awesome !!!! @Javi Appreciate the time on this app, finally something that works with node servers, awesome job.

Really liking UD Mobile on iOS. Great job. On iOS will UD Mobile support GEO fences? It is the only thing keeping me running mobilinc which I would like to do away with completely if I could. Thank you keep up the awesome work.

Thanks for the suggestions. I have a Aeotec Multi Sensor 6 kicking around, while I hate to use it for this purpose, appears there are not similar z-wave devices per OP, so will look to try the Aeotec this weekend if time permits

I have a scene that includes a homeseer dimmer switch (HS-WD200+) and a homeseer switch (HS-WS200+). The HS-WD200+ is the controller and the HS-WS200+ is a responder. If both devices are on / scene on, when I press the paddle to turn the HS-WD200+ off, the HS-WS200+ turns off - expected behavior If both devices are off / scene off, when I press the paddle to turn the HS-WD200+ on, the HS-WS200+ doesn't respond / stays off - Any thoughts what's going on? Cannot figure it out. The ISY 'sees' both the On and Off paddle presses of the HS-WD200+ but the HS-WS200+ just doesnt respond to it. Is my HS-WS200+ and I should just replace it? I can control the scene on/off and devices directly from the ISY Console with no issue, but local on taps don't trigger the scene / HS-WS200+ on. Do I just need to replace the HS-WS200+?

I am looking for a z-wave vibration sensor, one which is battery powered and 'relatively' small. I know there are multi-sensors out there but really prefer a single purpose vibration sensor device. Similar to this one, which would be perfect for my needs but unfortunately its zigbee: https://www.aqara.com/us/vibration_sensor.html Interested if folks have seen something like this on the market for z-wave? Just FYI before someone asks, I have a range hood that I would like to detect when it is operating. Long story but I cannot get to the wiring (would evolve busting out drywall which I just don't want to deal with). A vibration sensor like this should work well.

Personally, if the current Insteon support can be built as a Node Server and that node server is done in a way where the community can add to the node server for new devices, taking the load off UDI, I think that is a good compromise. Just my personal opinion. But there would have to be a governance process in place where UDI could take input from the community for new devices and review them before updating the node server. I know it is not a simple thing, there are likely to be conversion issues, but thats home automation, its never seamless as we all know, but thats the price you pay for progress. re: The PLM going out of production, yes that does worry me, so I for one will be making sure I have a replacement or two in the cupboard next time Smarthome have a sale. Should it go out of production I am sure someone way way smarter than I will find a way to take the Smarthome hub and turn it into a PLM should this occur. My biggest concern is Smarthome going under or just killing off Insteon. Again my personal view, is while I don't expect it to happen anytime soon, it will happen, that is a given, technology always becomes obsolescent at some point, whether in a year or 20 years, it will happen, by that time there will be other options out there for us that meet all our needs and an upgrade path so as devices die we can introduce other options. Short story for me: 1) Insteon as Node Server (with process for community input for new devices) 2) Port over Network Resources, not everyone has the ability to write Node Servers and Network Resources are an easy way to set up simple calls to third party devices

+1 Network Module +1 Insteon support. Open source NS if Smarthome doesn’t support third party integration

Appreciate the counsel. Figured I would need to look for a cheap laptop, kind of sucks but I cannot complain I guess, the ISY has been great value for money over a decade. The good news for everyone else is, knowing my luck, as soon as I buy the laptop the non Java version will be released the next day !!!!!!!

I shudder to ask the question and I pretty much know what the answer will be 'it will be available when its released', but I will ask anyway !! I access the Admin Console through my employer laptop (windows 10) and have done so successfully for over 10 years. Unfortunately, my employer has decided that it will no longer support Java and is actively removing it from all machines across the company. They have their reasons with the changes to the way Oracle now licenses Java to large enterprises. I cannot fight city hall on that one, is what it is. My predicament is I don't have a personal laptop. So to my question. I hear that UDI is working on a non Java based Admin Console interface. I will not ask exactly when it is likely to launch, but would ask if it is highly likely to launch in 2021 even if in December? I can probably limp along to the end of the year, and hope no changes to programs or adding / removing devices is needed. Just trying to gauge the general timing here as buying a laptop/desktop is an expensive proposition for me to access a user interface as the ISY Admin Console is the only thing I cannot do from my employer provided laptop so I would really just be buying a laptop to access the ISY (ps I also have a POLISY) Long question but wanted to add some color as I know UDI is a small shop and I am sure going as quickly as possible.

I was hoping someone out there may have developed or would be willing to develop a Node Server for the Neato line of robot vacuums. They have an API and JS SDK (https://developers.neatorobotics.com). The API requires interaction to the Neato cloud service with an OAuth authorization process which is well and truly beyond my knowledge/ capabilities hence the question. Have looked for a local API but cannot find one. Hoping the community has a common need and one could be developed for Polisy / polyglot.

Not a solution today but perhaps a node server could be written to connect multiple ISYs together. Polling interval could be set to appropriate level or program(s) written to query the NS on certain control triggers if real time status is important. Beyond my capabilities but maybe something UDI or someone with knowledge and time wants to consider.

Anyone have any ideas or a guess when we might see this new 4 button key pad?

I see how to get to the feature, that’s very clear, but that wasn’t the question. The question is what does it do?

@Chris JahnI too would be interested to understand exactly what this is. Is there documentation describing what this actual is / does? Much thanks. “Optional Basic and Button Press/Sensor Detection nodes for Z-Wave devices (See Z-Wave node level menu in the Admin Console)”

Looking for some opinions and recommendations. I currently have an all Insteon installation, switchlines, outletlincs, motion detectors, thermostats, leak sensors, etc, with close to 50 devices in total. Have been happy with my installation overall and in particular extremely happy with my ISY, the brains of the system which I have been able to integrate with pretty much anything using the network module. I am about to go through a major renovation and will be looking to move to zWave, although I have been happy with Insteon, the All On and All Off is a deal breaker for me, plus the limited evolution/choices of the Insteon devices. I do plan to stay with the ISY and will upgrade to version 5 of the software. To my question, one of the things I really like about my Insteon thermostats (Venstars with the plugin Insteon dongle) is that they push any temperate and humidity changes back to the ISY real-time, in addition to any manual status/mode changes. I use changes in temperate to trigger other events, fans, etc and so having the ISY see temperate and mode changes real time with the thermostat pushing the information is important to my set up (I do not want to be constantly polling the thermostats). I am not familiar with the various zWAve based thermostats so looking for recommendations of zWave thermostats that do push this information automatically back to the ISY controller. PS. I live in an apartment with Water Source Heat Pumps.

Went and purchased an Insteon Hub. My only option for managing these device options. It is a shame that I need to buy another controller to manage these settings but I have no choice unfortunately.

Does anyone know what the device options defaults are for the 2844-222? Pretty disappointed that UDI isn't fully supporting this device in the 4.x code base given it is a key device in any system. I understand the frustrations that UDI has with getting the API and like usual would probably need to reverse engineer it, but given it is such an important device in any home automation set up I would have thought UDI would have looked to solve this WITH FULL SUPPORT versus making folks wait for 5.x and we cannot even get a straight answer on when that will be officially released. Love the guys at UDI and always sing their praises but must admit this is the first time I am really disappointed in UDI.

Works perfectly for me. http://forum.universal-devices.com/topic/18951-ir-companion-for-amazon-echo/?hl=%2Bglobal+%2Bcache+%2Beddy&do=findComment&comment=176935

Confirmed it is fixed for me. Thanks for the quick (weekend) turn around. Truly amazing.

Go to your ISY portal, click on Tools->>Connectivity->>Amazon Echo. Then from the list that comes up, click on one of the Scenes you have mapped, and add an alternative spoken to that scene, save it and look at the new scene name in the portal list of all scenes, devices, programs, etc you have mapped and you will see the first column called Name, for Scenes it is naming them by the spoken words and for Devices it is naming them based on the device name in the ISY. It used to be this name column would use the ISY scene or device name from the ISY. Also the Amazon Echo list in the portal doesn't download correctly from the portal for scenes when you add a alternate spoken to them now

Mine work it is just the naming convention of the scene in the portal list that gets screwy when you add an alternate spoken to a scene (nb this behavior is just for scenes not for devices)

No in ISY portal. Go to your ISY portal, click on Tools->>Connectivity->>Amazon Echo. Then from the list that comes up, click on one of the Scenes you have mapped, and add an alternative spoken to that scene, save it and look at the new scene name in the list of scenes and devices and you will see the problem.

When I first set up my echo in the ISY portal and added devices and scenes the name for each device and scene I added defaulted to the name of the device or scene as it was named in the ISY (all good). Today I went to edit some of these Amazon Echo mappings in the ISY portal by adding alternative spokens and when it saved the name in the ISY portal changed to the spokens for scenes and for devices it remained as the device name in the ISY. This makes it terrible confusing to maintain the list of devices/scenes in the portal. I liked it when the ISY portal named each mapping consistent with the device or scene name in the ISY itself, not the spokens. When was this bug introduced? Also when you download your ISY Portal mapping to the csv file, the scenes now don't populate their name in the csv file.