Phil G

I need to get a life. I read through this like it was a murder mystery. Saw the green 'Solution' box at the top so I knew the killer was going to be revealed by the end. I couldn't figure it out. Good eye, @Geddy.

Thanks @IndyMike for all the information. I'm holding out hope that Eisy will eventually work with some reliable presence sensors. I purchased an rPi kit from HA a few years ago back when Insteon was on the ropes but never took the plunge and set it up. Tried using Zwave switches with Polisy, but it was not a good experience and when Insteon came back online I stocked up on replacements and tossed the zwave stuff except for some sensors which work fine. Even though Eisy supports zigbee, it won't talk to this sensor?

@IndyMike, the Zigbee occupancy sensors sound interesting. Would you mind sharing what device(s) you are testing and how they are working out for you?

These look great, but they're sold out. I'd buy a handful if they're not too painful to add in and manage. My experience with zwave and anything non-insteon, so far, is not encouraging.

Thank you Techman. I resolved this problem by disconnecting the lock from the Ultraloq wifi bridge and then including it again even though the IoX node was still listed. I included as a new node and I was then able to 'Remove Fail Node' on the old node. I think that using the Ultraloq wifi bridge as well as Zwave was creating problems. Not too many posts on this forum regarding Ultraloq U-bolt locks, so I'll add some info here in case someone else comes up with issues. I like these locks quite a bit although I don't have anything to compare them with. They seem to be solidly built. I wouldn't spend money on the fingerprint feature because it just doesn't work reliably. I was having some quirky behaviors with my 2 locks, so I disconnected both of them from their wifi bridge (each bridge only accommodates a single lock) and only use the UD Mobile app for remote status and activation and zwave inclusion/exclusion. I still can get full lock status with the Ultraloq app using bluetooth; gives me all the other features like access logs, firmware version, etc. Battery life may be an issue; some users report only 4-8 weeks of life using rechargeable NiMH.

I'm having trouble getting a reliable zwave connection to an Ultraloq U-Bolt Wave lock. It was included on the zwave network and then quit responding the next day. I'm now trying to exclude it but it is returning a communication error in the Ultraloq app. In IoX, the lock node is not responding at all, but I use "ZWave > Remove Failed Node" , I get this error: Any thoughts on how to deal with this?

Thank you for the explanation. I didn’t understand this aspect of using scenes vs program statements to control devices. This may explain my occasional device communication problems where I’m switching 5-10 lights with program statements and one of them doesn’t respond.

@paulbates, could you expound on this comment please? Are you suggesting to create another scene with all of the devices added, or something more elegant? Why would a program not be needed to set the devices to 'off'? Thanks in advance.

So you saw the message “start.jnlp was blocked” and clicked on the Run Anyway button?

I didn't explicitly import the certificate, so I think it happens when you first run the start.jnlp and get a Mac OS warning that the app developer is unknown. Here is how to override the warning and complete the install: I'm on Mac OS Sonoma 14.5. The 'Privacy & Security' setting to allow identified developers looks like this (it may look a little different if you're on a different OS version, but the selection is in there somewhere). Since UDI is not identified, maybe this doesn't matter so much, but I select it anyway: Now, when you double-click the start.jnlp file, you should get this popup: Select OK, then open Privacy & Security settings again and notice that "start.jnlp" was blocked. Select 'Open Anyway' to install Launcher: I think this process installs their app signing certificate. Since you said earlier that you don't see this certificate as being installed, then I'm assuming that you've never successfully installed that Launcher.

Do you see the Universal Devices trusted certificate? (click on Manage Certificates...)

I'd bet you're going to like the Ecobees. The only active control I do with IoX is adjusting the humidity set point for my upstairs Ecobee when the dehumidifier kicks on. I want it to run for at least 30 minutes. Otherwise, I can only say that I'm very impressed with their cloud service reliability as well as the hardware. I added 3 new thermostats recently to 3 remote shops that I monitor around town and they all showed up on my Admin Console w/o any action on my part. Kudos to the node server developer, @Jimbo.Automates, too! Well worth the cost. My only worry is that the Ecobee server might go away some day.

@paulbates, out of curiosity, why not use the Insteon sensors?

That would be my assumption. A good question for the developer @Jimbo.Automates. The NS configuration shows parameters shortPoll set at 60 and longPoll at 180 (seconds?).

I don't use the Ecobee window/door sensors so I'm not sure how they would show up in the AC, but their temperature/occupancy Smartsensors do show up and can be accessed by IoX. The occupancy reporting takes a while and isn't suitable for lighting control, but adequate for a security related program. Here's an Ecobee thermostat: