drich

As far as I know the ELK M1 should be able to talk to any alarm monitoring company, but it is up to that company whether or not they want to support it. Most companies seem to have one or more systems that they prefer to deal with. That said, I've been using Alarm Relay (https://alarmrelay.com) since I installed my ELK several years ago and love them. They are very affordable at $8.95/month, will happily support a long list of homeowner installed systems, and in general provide great service. On the few alarms I have had, I typically get the call from them before I even get the text page from my alarm company. And when we did have a break-in, they stayed on the phone with me while I confirmed the break-in with our cameras and they got the police to respond faster than I ever could.

I got a ticket on resending the e-mail: #11411

No, oddly I didn't get anything back from support. Let me attach it here and try resending the e-mail. ISY Error Log.zip

@Michel KohanimI sent in the logs last week (I realize it was a holiday weekend and likely no one has even looked at them yet). FWIW, the problem seems to be getting worse. I rebooted yesterday evening as the ISY couldn't connect to the ELK again, and the problem has already reoccured this morning. I am not seeing anything obvious in the error or event logs that could be triggering this, and I have disabled most of the programs calling network resources at this point. I also just noticed that several of my Z-Wave devices are sitting with the "writing changes" icon showing in the UI. I wonder if that could be related?

I will send in a set of logs the next time this happens.

The thing is, it works fine after a reboot. Then within a couple of days it'll start throwing that SOCK-READ-16 error and fail. I have been having problems with my polyglot server, is it possible there is a resource leak somewhere and that is causing the ISY to run out of socket connections? I fixed the polyglot issue last night, so if that is the case this should stop happening.

I have an Elk M1 Gold that has been working great with my ISY994i for years. Recently however I have noticed that the response to requests for the Elk has been slow and after my ISY is up and running for a few days it seems to lose the connection to it entirely. The only thing I see in the event logs are messages like the following . I don't know if the socket errors are related, but they seem to start showing up in the logs around the time that the connections start failing. I don't think it's a problem with the Elk network interface, as that seems to work fine with Home Assistant and with anything else that queries it directly. Any ideas? I'm currently running 5.3.0, I'm not sure if this started occurring with the 5.3 upgrade or it was happening before and I just didn't notice it. Sun 12/27/2020 20:28:47 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:28:47 : Elk Query All Failed, requesting retry Sun 12/27/2020 20:28:48 : [ELK-TX ] Get Topology Sun 12/27/2020 20:28:59 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:02 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:02 : [ELK ] Disconnect Sun 12/27/2020 20:29:02 : [ELK ] Connect Sun 12/27/2020 20:29:02 : [ELK ] Connect Successful Sun 12/27/2020 20:29:02 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:13 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:13 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:15 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:16 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:20 : Elk Query All Sun 12/27/2020 20:29:20 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:24 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:24 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:28 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:28 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:28 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:29 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:31 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:31 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:31 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:31 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:37 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:40 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:40 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:43 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:29:43 : SOCK-READ-16 - Buffer Overflow Sun 12/27/2020 20:30:10 : Elk Query All Failed, requesting retry

I'm finding more and more products that expect including a new device to be "magic" and have virtually no way to configure it on the device itself. Both these light bulbs and a set of z-wave outlets I have automatically include/exclude when you first turn them on (or plug them in in the case of the outlets). I have yet to see any Z-Wave lightbulb that does more than respond to an existing inclusion when first turned on, or with three (or some other number) of power cycles of the bulb. However, using the Silicon Labs Z-Wave PC Controller as an example, you can include a device in non-secure mode simply by cancelling the window that asks for which security keys to use. I would expect the ISY to do something similar. For example, if I disable secure inclusion, I would expect the ISY to include the device as an insecure device -- even if it reports that it supports security. Or at the very least to prompt me and let me make the decision at the time of inclusion.

With all of the Z-Wave changes in this release, is there a way to include a secure device w/o security? I have a couple of Z-Wave light bulbs that have issues when included securely. The vendor tells me they will work better (and generate about 1/3 as much Z-Wave traffic) if I include them as non-secure devices. However, if I disable "Allow secure devices" in the ISY admin UI, it refuses to include the device at all.

Just in case anyone else runs into this, I can confirm that downgrading to Java 8.251 fixes the problem. You have to manually remove 8.261 first: sudo rm -fr /Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin Password: sudo rm -fr /Library/PreferencePanes/JavaControlPanel.prefPane sudo rm -fr ~/Library/Application\ Support/Oracle/Java And at least in my case, I had to log into the admin interface twice - it appears it had to install itself before working properly.

Nice find, thanks! This is yet one more thing for me to hate in Catalina. I've lost track of the number of apps I have had to re-download and install because they can't read or write my Documents or Downloads directory.

Is anyone else having issues with the admin console after upgrading to Java 1.8.0_261? I am getting prompted for the login every 30 seconds or so, which makes it impossible to do anything. I ended up installing Java on my Windows 10 server that runs BlueIris just so I could access the admin console. I have tried all of the usual Java tricks -- I've cleared the cache, re-downloaded the start.jnlp file, increased the allocated memory as suggested in the 5.0.1 release notes, and even rebooted the ISY. I'm seeing this in both 5.0.16C and the new 5.1.0 that I upgraded to this morning (from Windows since I couldn't get a backup on my Mac).

Same problem here. Both of my Aeotec sensors had to be synchronized in order to get them talking to the ISY again. This also deleted them and recreated them, which meant I had to rename them all over again. It took me three tries to get one of them to resync, I almost had to climb a ladder to pull it down and move it closer to the ISY (IMHO, the antenna on the 500 series dongle is almost useless).

To followup to my earlier post in this thread, I was able to successfully include both of my Inovelli switches after doing two things: Upgrade to the Series 500 dongle Use a test rig with a neutral wire on the switch. I'm not sure if it really required both, but that worked for me. I tried to pair it without a neutral, but my test box doesn't put enough load on the switch for it to power up (it's just a small neon lamp). When I get time I'm going to try and experiment a bit more with a larger load and no neutral on my spare switch..

That's what I said I was doing above. I'm looking to see if there is a better or other way. That requires four separate programs for every fan and runs the risk of a race condition that causes the fan motor to cycle on and off if I have the else condition set on anything other than the "Off" rule.

The closest thing I have found is four separate programs that turn on/off the four scenes instead of the buttons. If I avoid doing anything in the else clause, it looks like I can avoid the race condition. If there isn't a way to deal with the individual buttons on the keypads, I may be stuck with this. Sync KPL - Fan Off Piano Room - [ID 00A0][Parent 0001] If 'Fans / Piano Room Fan' Status is Off Then Set 'Fans / Piano Room Fan Low' Off Set 'Fans / Piano Room Fan Med' Off Set 'Fans / Piano Room Fan High' Off Else - No Actions - (To add one, press 'Action') Sync KPL - Fan Low Piano Room - [ID 009D][Parent 0001] If 'Fans / Piano Room Fan' Status is Low Then Set 'Fans / Piano Room Fan Low' On Else - No Actions - (To add one, press 'Action') and so on - for all four states on each fan and all six fans in the house.

Actually I mentioned that in the first paragraph. If I want to use the fan with proper fan control from Home Assistant, I have to use the FanLinc device directly, not the scene. Therefore I need to control the KPL buttons manually. If I try and update date the scene from the program I can end up in a race condition where the fan is toggled on and off if someone turns the fan on and then off again from HA. For a status command you don't need the "is not off" check you use above. The state check will trigger when the FanLinc becomes low or when it goes to some other state. That part is working fine. It's the setting of the KPL status that doesn't work. I have a feeling this is a limitation in Insteon and the only option is to trigger the scene -- which runs the risk I mentioned already.

I have started doing some of my automation via. Home Assistant (mostly to integrate with HomeKit), and have run into an issue with KPL buttons being out of sync. The problem is primarily with ceiling fans, as in order to get proper support in HA I need to talk directly to the FanLinc, not the scene that contains the KPL buttons and the four FanLinc states. I was hoping I could just create a program that syncs the button states when the state changes, but I haven't been able to figure out the magic incantation to get that working. Is it not possible to update button states on a KPL (set as the scene controller)? Here's an example of what I am trying. "Fans / Piano Room Fan" is the FanLinc, "KPL / Piano Room Switch" is the KPL. I have buttons for low, med, and high configured in scenes. Sync KPL - Fan Low Piano Room - [ID 009D][Parent 0001] If 'Fans / Piano Room Fan' Status is Low Then In 'KPL / Piano Room Switch / Piano Room Switch Low' Set 'KPL / Piano Room Switch / Piano Room Switch Low' To On Else In 'KPL / Piano Room Switch / Piano Room Switch Low' Set 'KPL / Piano Room Switch / Piano Room Switch Low' To Off Anyone have any tips for this other than "don't use KPLs and FanLincs"? (which honestly, is starting to seem like the best choice given the lighting issues I'm having with LED flickering and the FanLinc - I'm waiting to see if the Inovelli fan controller will pair with the ISY and/or work reliably).

I built myself a test rig a few years ago, it's really handy for pairing devices and testing out new configurations. It's made up of a double J-box, terminal strip, 120V neon lamps, and an appliance cord.

I'm looking forward to giving one of these a try as well. I'm surprised to see someone say "pricey" though, since they are less than half the cost of using a combination of a FanLinc and KeypadLinc like I do now ($160 for the pair). And given the problems I've had with the latest generation of the FanLinc, and the lack of support from what is left of Smarthome, I really need a replacement. That is, if we can get the inclusion issue with Inovelli and ISY resolved... (I think I'm going to break down and order the Series 500 board, if I can find instructions on upgrading)

Looks like it is already there: https://github.com/UniversalDevicesInc/ZWave-Devices/issues/18

One more data point (which makes me think this is an ISY issue, not Inovelli) - it turns out that it *does* pair, just that the ISY can't see it. I also have Home Assistant running with a Z-Stick, and that can both see and control the switch after pairing with no problems. I'm going to go ahead and open up a support issue on this, as it is hopefully something than can be fixed easily in firmware.

FWIW, here is the device communications even log from an attempt to exclude the device followed by another attempt to pair it. Wed 05/20/2020 17:03:55 : [ZWAVE-TX-NR ] [0105004B01ED5D] REQ ZW_REMOVE_NODE_FROM_NETWORK FUNCID=1 STATUS=237 UID=93 Wed 05/20/2020 17:03:55 : [UZW-CMD 2 ] Start Exclude Wed 05/20/2020 17:03:55 : Listening for Z-Wave devices to remove from the network Wed 05/20/2020 17:05:42 : [ZWAVE-TX-NR ] [0105004B05EE5A] REQ ZW_REMOVE_NODE_FROM_NETWORK FUNCID=5 STATUS=238 UID=90 Wed 05/20/2020 17:05:42 : [UZW-CMD 8 ] Cancel Include/Exclude/Learn Wed 05/20/2020 17:05:42 : Removing Z-Wave devices stopped Wed 05/20/2020 17:05:43 : [ZWAVE-TX ] [01030020DC] REQ MEMORY_GET_ID Wed 05/20/2020 17:05:43 : [ZWAVE-TX ] [01030002FE] REQ SERIAL_API_GET_INIT_DATA Wed 05/20/2020 17:05:43 : [ZWAVE-TX ] [01030005F9] REQ ZW_GET_CONTROLLER_CAPABILITIES Wed 05/20/2020 17:05:43 : [ZWAVE-TX ] [01030002FE] REQ SERIAL_API_GET_INIT_DATA Wed 05/20/2020 17:05:43 : Device 51 excluded from Z-Wave network Wed 05/20/2020 17:05:51 : [ZWAVE-TX-NR ] [0105004AC1EF9E] REQ ZW_ADD_NODE_TO_NETWORK Wed 05/20/2020 17:05:51 : [UZW-CMD 1 ] Start Include Wed 05/20/2020 17:05:51 : Listening for Z-Wave devices to add to the network Wed 05/20/2020 17:06:13 : Z-Wave device detected, retrieving info 2 Wed 05/20/2020 17:06:13 : Z-Wave device detected, retrieving info 3 Wed 05/20/2020 17:06:18 : Z-Wave device detected, retrieving info 5 Wed 05/20/2020 17:06:18 : [ZWAVE-TX ] [0105004A85F0C5] REQ ZW_ADD_NODE_TO_NETWORK Wed 05/20/2020 17:06:18 : Adding Z-Wave devices stopped Wed 05/20/2020 17:06:18 : [ZWAVE-TX ] [01030020DC] REQ MEMORY_GET_ID Wed 05/20/2020 17:06:18 : [ZWAVE-TX ] [01030002FE] REQ SERIAL_API_GET_INIT_DATA Wed 05/20/2020 17:06:19 : [ZWAVE-TX ] [01030005F9] REQ ZW_GET_CONTROLLER_CAPABILITIES Wed 05/20/2020 17:06:19 : Exchanging data with secure Z-Wave device 52 of type 4.17.1 Wed 05/20/2020 17:06:19 : Adding secure Z-Wave device Wed 05/20/2020 17:06:19 : [ZWAVE-TX 52.0] [98/04] Security Scheme Get - supported=........ ACK,AUTO To=0x34 Wed 05/20/2020 17:06:29 : [ZWAVE-ADDSECURE] Error 3 Wed 05/20/2020 17:06:29 : Failed to include secure Z-Wave device 52 of type 4.17.1 Wed 05/20/2020 17:06:29 : [All ] Writing 0 bytes to devices Wed 05/20/2020 17:06:29 : [All ] Writing 0 bytes to devices

Has anyone gotten one of these to work correctly? I haven't even gotten a response from Inovelli support from a couple of weeks ago.

Between the almost-daily sales from Smarthome, the fact that they have outsourced support (at least judging by my experiences of the past year with their support dept), and the lack of any response from their engineering dept on defects in some of their devices (see my thread elsewhere on my FanLinc issues); I think it's just a matter of time until they cease to exist. My biggest problem is that I haven't found anything that can replace some of their devices -- and believe me I have looked. As far as I can tell there is no equivalent to the KeypadLinc or FanLinc from any vendor using any protocol. The few things I have seen that are equivalent to an InlineLinc or MicroDimmer just don't work all that well when I have tried them. As other have said, if Insteon goes away I will probably go with a mix of technologies. I will likely end up with quite a bit more z-wave (I have some today and it drives me crazy with how often I have to rebuild the mesh) and a variety of other application-specific devices. As I have learned the hard way with my Ring Doorbell, I am not buying anything that only works over wifi or depends on the cloud or the existence of some other vendor's servers to operate. Sooner or later, if it doesn't run in my house, it is going to go away (case in point -- my Roost smoke detector batteries that no longer work because the vendor decided to stop supporting the older devices and the solution is to replace them at $35 each). Personally I think it is more likely that Smarthome will disappear and they will sell the technology to some other vendor who will continue to support it and potentially enhance it if they think there is a market for it.