dwengrovitz

A short press on each of the buttons did indeed update the status from Unknown to ON (DON). I'll experiment a bit more with that function, but it looks like the issues I was seeing are now resolved, thanks again! Still happy to send you a Flex Switch if you want one. :-)

Thanks for the update. At first glance, my temp sensors now all seem to work correctly. The Flex Switches also appear to work, but the status of the additional two button controllers appears as unknown in the Admin Console. I can live with that, as I don't really use that function, but if you'd like to fully support that just let me know and I'm happy to assist with logs, testing, and whatever else might be needed. Heck - message me your shipping address and I'll have Amazon send one to you to test with just to say thanks for the great community support!

@Panda88 - I tried sending you a debug log with some screenshots, but the UD message system just said "Panda88 cannot receive messages."

I am seeing some unexpected things since updating to the latest release. My Local hub now says "Alert" under "Supply Status" in the devices View, and in the Current State when listing devices via the Admin Console. I don't recall seeing that before (but perhaps just missed it) and am not quite sure how to address that if it's a real issue. The Current State and multiple other values appearing in the Admin Console device view show as "Unknown" for several devices and device types, including my Flexswitch devices (YS5709-UC) and some but not all of my temp/humidity sensors (YS8006-UC). If I manually update the device status for those devices via the Admin Console, the values seem to get updated but many return to show "Unknown" statuses again shortly after update. When updating status manually via Admin Console, I occasionally get "TCP client read response failed" messages (NS-70-YolinkLocal).

I definitely agree with that statement. I had integrated MyQ with my ISY environment way back when and it really pissed me off when they shutdown access through their API, so much so that I eventually got rid of anything MyQ-related. I've had good success with YoLink as an add-on replacement, though I used their Garage Door Controller rather than their Finger Controller.

I consistently have issues with status deltas across the various UIs, to the point where the only one I can really use is the Admin Console when logging in with my ISY credentials. Does your question apply to just the device status or also flag status? For example, in the Admin Console (login via ISY credentials), all of my devices and device flags have current states. In the Admin console (login via portal credentials), most devices are missing flag status. In eisy-ui, most devices are also missing flag status.

I reached out to Insteon about six weeks ago to ask about the status of their rumored new PLM. The comment I received back from their support folks was: "There are plans to release a new PLM with increased memory and enhanced capability. The module has already undergone testing, though a few items are still being refined before production. While we don’t yet have a confirmed release or availability date, it remains an active item on our development roadmap." So no date set, but it was still on the roadmap as of early November.

I have a couple of these I3 keypads and am using them as 2-way switches to control the same four devices. I'd really like the 4 buttons to mirror each other in terms of which button controls which devices, but it's not possible to do that with just an eisy as reassigning the load hasn't been implemented there yet. I think it's been around two years since this requirement originally surfaced in the UDI forms, so I submitted a ticket to get an update. Sadly, the response was "Updating the code to support moving the load to a different button is on the list but I'm not sure when or if it will be prioritized", so that doesn't sound too promising.

My experience with the Eve Home Energy (Matter) modules was also very useful. I have a ton of relatively new Insteon switch devices and an eisy hub for lighting control in my house. I also have Home Assistant set up to integrate a lot of non-Insteon devices in my environment, such as a dozen Smartwings Shades (with Matter over Thread motors). For the longest time, I could not get them to reliably stay online, even with their latest firmware update (1.3) which supposedly implemented improvements in that area. As you mention, the Eve On/Off modules include a Thread Border Router. After I installed a couple of those around the house, my Matter/Thread network and the Smartwings shades have been rock solid. I've also converted a bunch of YoLink sensors to use the local Matter network via their YoLink Local hub, and they have also been rock solid, and maybe even slightly better performing with signaling being local versus using the cloud. I even have a Shelly 1 Mini device integrated through the Matter interface in eisy that I use to control on/off (via an Insteon switch) and scheduling (via an eisy automation) of an old towel warmer device near a shower. I'm not a Matter/Thread expert, and Matter/Thread is clearly early in its evolution, but I credit the improved coverage and reliability in my environment to those Eve devices.

It's been a while since I've done that, but I believe you can setup a state variable within your ISY or eisy device and expose that to the Amazon Echo ecosystem via the ISY portal as a device/contact sensor. Then setup a routine with the Alexa app to monitor the state of that device/contact sensor as the trigger, then perform whatever you want on the Amazon side via the Alexa routine.

The issue seems to be resolved in the Yolink Local plugin for my motion, vibration, and contact sensors. Thanks!

FYI. I submitted a ticket to UDI on this issue, and Michel replied he was "... escalating the ticket. Please stay tuned."

It happens for me regardless of if I'm creating new programs or editing programs I've had for long time.

Interesting ... I also ran into this problem. I installed a new Local Hub and went to update my programs so they used the status from that plugin, but in the process, I had to change all of the logic from options like "is Open" and "is Motion" to "is not Closed" and "is not No Motion". The "is not" option is a workaround, but not being able to specify status options like "is Open" and "is Motion" is kind of problematic. Would it help if we opened a ticket with UDI and asked that they take a look at what's happening on their end? I'm not in any rush, and can certainly wait for them to address things in the new UI, but it would be nice to have that function/capability back at some point.

Yolink support states: The Local Hub units currently available are already the latest hardware revision. There are no additional hardware updates planned at this time.