simplextech

@bmercier, it's been a while but I ran into this issue with Agave a couple months ago and I just now tried testing this again. No rush on this as it's almost summer, but I'd like to plan for fall/winter to determine if this will be fixed/resolved especially with mobile/tablet app usage as I have plans for installing some tablets around the house this summer. UDAjax - control works fine with the drop down and the heating setpoint is set correctly. HAD - you can click and set the temp but afterwards it automatically jumps the temp to the max setpoint 86F. The issue with HAD I think is also affecting Agave and probably other interfaces as they exhibit the same issue. [EDIT] Just tested with eKeyPad ISY and same issue of any setPoint change jumps the thermostat to 86F

I'm also curious if/when the Insteon Siren will be supported or not. I was thinking of buying a couple while on sale.

You can run the ISY with Insteon and Z-Wave OR ZigBee at the same time. However the ISY ZigBee is really only useful for connecting to power meters (utility power meters) which "standard" ZigBee does not do. ST does Z-Wave and ZigBee ZHA. The only gain you get from ST is the ZigBee. However because ST is mostly cloud based all communications must go out to the cloud to ST then back to your ISY all through the cloud requiring a good internet connection ALL the time. Hubitat is essentially a ST "clone" that provides good Z-Wave and ZigBee capability and a ton of the device handlers from ST have been ported to Hubitat already. I wrote a nodeserver specifically for Hubitat to utilize the ZigBee capabilities from Hubitat from the ISY. You can use the Z-Wave also but why when the ISY can already handle the Z-Wave on it's own. The flip side is you could have an ISY with ZigBee for power meter use AND connect Hubitat to then also have Z-Wave and Zigbee ZHA..... That combination gives you everything from the ISY. Downside is that nodeservers are not well supported by the mobile apps (Agave/MobiLinc) at the moment. This will probably change as I post this out of curiousity... why are you writing it ZeeWave?

ISY does not support ZigBee ZHA profile devices. There currently is no NodeServer to integrate ST directly. I have produced a Hubitat NodeServer which does integrate the Hubitat hub with ISY for devices. The current devices supported are limited because I do not posses every possible device. If you chose to get a Hubitat hub and use that nodeserver then I can work with you to include device support.

The Z-Wave connection will not allow the depth of interaction you are looking for and it's ONLY for Z-Wave devices. The typical usage of the master/slave controller is to allow the master controller visibility/control of the slave controllers Z-Wave devices. This is generally used in a migration scenario of being able to bulk add the devices from a previous controller to a new controller and then shifting the Master role to the new controller making it the Z-Wave network ID Owner.

I don't think Insteon is going anywhere anytime soon. As for the hardware failures I see that with z-wave devices as well. So I don't think it's a Insteon only thing about quality control or anything. I had a HomeSeer switch just fail intermittently and it was only a couple months old. Depending on devices, QA, build issues at the time of production run etc etc there are many things and as these are electrical devices + moving parts + exposed to surges, brown outs, etc (excluding those with whole house system protections) I think it's quite amazing that the devices last for years in general terms. If anything I think Insteon needs to do a better QA to prevent DOA devices as I've received a DOA fanlinc out of an order of 3 which isn't a great ratio. But again I've also received DOA components out of z-wave orders.....

If it's still getting updates that's great. It's not available for Android in the Play Store.

Only for neither really. Locative is no longer developed or supported. I don't think it's actually available in either app store anymore (if it is then it shouldn't be) and the different locations to download it from are "questionable" unless you have an older "known good" version or you compile it from source yourselfe as the github repo is still available. Great app.... just no longer supported. Same thing happened with the Android app I used to use egiGeoFence the author got tired of trying to fix things that Google was breaking with Android Location services....

Unfortunately the NodeServer will not interface with SmartThings. SmartThings is a cloud based system and any access must route through their cloud service. This is possible but far outside the scope of the Hubitat NodeServer that I developed and makes your entire environment still dependent on the cloud for functionality. If you have a lot of ST devices and you would still like to use them I would recommend buying a Hubitat hub! And tell them you're buying it because of this NodeServer ?

Which NodeServer? The Hubitat NodeServer?

I thought the point WAS to get yelled at? Put some LIFX bulbs (Or other smart color bulbs) in there and change their hue to make everything appear like soft white but with a nice orange tinge in the light and her makeup will come out looking like a spray tan!

Opposite lighting rule? Motion turns off the lights instead of on? So enter the room and lights go off... leave and lights turn on.... ?

The sensors update the Ambient Weather system every 60 seconds and the data feed to the nodeserver is real-time as changes happen. Wireless Tags are also great and I've been thinking about buying some too

I use Temp/Humidity sensors that connect to my Ambient Weather station. I have one of the sensors in the bathroom and a very simple program: Bathroom.Humidity - [ID 0020][Parent 0001] If 'Ambient Weather / WS-1401-Addon' Sensor 1 Humidity >= 75% Then Set 'Bathroom / sw.Bathroom.Fan' On Else - No Actions - (To add one, press 'Action') I have other programs that check if the fan is on and for how long and then turn it off. But just a very simple humidity check mainly used if someone is in the shower without the fan on...

Use of the "is not off" comes into play with Dimmers. On = 100% Off = 0% What's 42%? Not On but Not Off...

Welcome. Like I said it's a good system and the developers put a lot of focus on ST device compatibility. I think most ST devices work so do most Iris devices (not v1 though). So it's a good "joining" of systems and after almost of year of me fighting them they gave in with a integration option

Hubitat Elevation is a new kid on the block which is built around being a local processing. We all call it a local SmartThings as it's very much a clone of the ST system. I'm working on an integration currently. The initial prototyping has been released and I posted about it here: As an integrator as well but more on the software side of things I try to keep things local if possible and if it makes sense. Hubitat is a good system with some minor growing pains but it's worth looking at. Almost all of the current users are former SmartThings users! I have a first public release version of the hub and it's been improving greatly in the last year.

Updates from overnight showing the temp/humidity updates for the NYCE Motion Sensor:

Here's some eye candy and some preliminary logs. This is going faster than I anticipated. 2019-03-13 00:25:57,696 [NodeServer] [DEBUG] ----Device Info---- 2019-03-13 00:25:57,697 [NodeServer] [DEBUG] {'installedAppId': None, 'name': 'motion', 'value': 'active', 'hubId': None, 'descriptionText': 'Zooz 4-in-1 Sensor: motion is active', 'deviceId': 465, 'unit': None, 'displayName': 'Zooz 4-in-1 Sensor', 'locationId': None, 'source': 'DEVICE'} 2019-03-13 00:25:57,699 [NodeServer] [DEBUG] ----Device Info---- 2019-03-13 00:25:57,721 [NodeServer] [DEBUG] ----Device Info---- 2019-03-13 00:25:57,722 [NodeServer] [DEBUG] {'installedAppId': None, 'name': 'motion', 'value': 'active', 'hubId': None, 'descriptionText': 'Zooz 4-in-1 Sensor: motion is active', 'deviceId': 465, 'unit': None, 'displayName': 'Zooz 4-in-1 Sensor', 'locationId': None, 'source': 'DEVICE'} 2019-03-13 00:25:57,723 [NodeServer] [DEBUG] ----Device Info---- 2019-03-13 00:26:03,193 [NodeServer] [DEBUG] ----Device Info---- 2019-03-13 00:26:03,195 [NodeServer] [DEBUG] {'installedAppId': None, 'name': 'motion', 'value': 'active', 'hubId': None, 'descriptionText': 'Dome Motion Sensor motion is active', 'deviceId': 468, 'unit': None, 'displayName': 'Dome Motion Sensor', 'locationId': None, 'source': 'DEVICE'} 2019-03-13 00:26:03,196 [NodeServer] [DEBUG] ----Device Info---- 2019-03-13 00:26:11,512 [NodeServer] [DEBUG] ----Device Info---- 2019-03-13 00:26:11,513 [NodeServer] [DEBUG] {'installedAppId': None, 'name': 'motion', 'value': 'inactive', 'hubId': None, 'descriptionText': 'Zooz 4-in-1 Sensor: motion is inactive', 'deviceId': 465, 'unit': None, 'displayName': 'Zooz 4-in-1 Sensor', 'locationId': None, 'source': 'DEVICE'} 2019-03-13 00:26:11,515 [NodeServer] [DEBUG] ----Device Info---- 2019-03-13 00:26:11,538 [NodeServer] [DEBUG] ----Device Info---- 2019-03-13 00:26:11,539 [NodeServer] [DEBUG] {'installedAppId': None, 'name': 'motion', 'value': 'inactive', 'hubId': None, 'descriptionText': 'Zooz 4-in-1 Sensor: motion is inactive', 'deviceId': 465, 'unit': None, 'displayName': 'Zooz 4-in-1 Sensor', 'locationId': None, 'source': 'DEVICE'} I have a ZigBee NYCE Ceiling motion sensor added and working. Motion is REAL TIME and the other values update based on standard interval of the sensor. Also to note Z-Wave devices are also being supported in this integration and I'm going to see if I can include the built-in native apps from Hubitat which will also include full Lutron Caseta Pro / RadioRA integration capability. The integration is with the Hubitat Elevation hub. I'll post full details and information once I get this further along. So... probably tomorrow sometime.

Then give me a little time. Prototyping has started for a polyglot to interface the system.

So it's not specifically about SmartThings? More about the Zigbee devices? So.... Zigbee integration is of interest? If so the up-side is I've been considering developing this for iSY as I'm also working on an integration for HomeSeer as well. It will not be using SmartThings as that is primary cloud based which I do no like. In summary... IF the hub/interface etc was in the $100-$150 range total and integrated with ISY that is of interest?

Can I ask why specifically SmartThings? If the goal is for temperature readings there are other z-wave sensors that report temperature and other means of getting temperature. I will agree the Multipurpose sensor from ST is a good sensor but it is Zigbee.

This is what I've been doing... my event viewer is scrolling too much to be able to watch there

It's not. That was a dummy program that I used to copy/paste from and things I'm toying with so ignore the Then statement it's not relevant. I'm just trying to make sure I understand the use structure of time within ISY versus what the editor allows

I think I found a new tagline