Guy Lavoie

Also, in case it does go up, take logs of the connections, so you can compare and see what the difference is. Redirect the output to a file that you name with the date every time, such as: netstat -a >march24 Then you'll have files to compare.

One diagnostic thing you could try, if you're ok with using ssh, is to monitor socket usage, to see if it creeps up over time. Log into the eisy with ssh and do this: netstat -a | wc -l This gives you a list of active sockets, the output is piped into the wc command, which means "word count", the -l option counts lines. You'll get a number. My eisy is showing me 187 right now. Note the number, and redo this every few days to see if it stays stable or creeps up. Doing just "netstat -a" will show you a list of active connections. the "foreign address" will show who the connection is with.

Leaving the admin console open for extended periods (like overnight) can cause similar issues. Make sure that's not the case.

That's interesting. I have a test Polisy running 6.0.5 with a Zigbee smart plug and it's working fine. Maybe it's device specific.

Well I added a Weiser lock using it's PIN code (printed next to the QR code). The node title shows "Door Lock [S2 Access] [S0]"

I would try ignoring it for a day or two. Let the mesh network figure itself out.

Well, plugin development is a whole other subject, and I've only experimented with it a few months ago. I'd like to learn how to create and share useful ones. This involves learning to program in python, which in itself is a challenge. I'll get to it in due time. Documentation is very sparse. I mostly figured out the little I know through reverse engineering. I started off with a timer plugin because my previous home automation controller (the ADI Ocelot) had them and are an integral part of programming. The speed of detection of IR sensors will always be variable, because of the way they figure out the change in IR energy being reflected. There is a certain "ignore" time built into them after detection or else you would get too much traffic and false triggers. I'm glad the Insteon ones have that On-only mode, allowing your own program to decide what to do with continued detection.

I'm doing something similar for a motion sensor located in a small storage room in the basement with a fridge, and that also has a sink that I'll use for cleaning paintbrushes, etc. The idea is that I'll usually just go in to get or put something in the fridge, and I turn on a Hue bulb for a default of 30 seconds, but I want that 30 seconds to be extended if I'm still there and moving around. That's retriggering the timer. There are also fluorescent ceiling lights that I can turn on with an Insteon wall switch if I want more light, such as when using the sink. 75% of the time, the Hue bulb is enough for just going in for a moment. The motion sensor is placed behind the door, such that if I walk in and turn on the wall switch, the status of the wall switch will be known to be On before the motion sensor sees me. My Insteon motion sensor is set up in the On-only mode, sending a On command every time it detects motion, and it's internal timer is disabled. This mode exists for the purpose of letting you create retriggerable routines in software. I have two programs for doing what I want. One program Looks for the On control events from the motion sensor and keeps retriggering the timer. Note that since I'm using two different lights, the status of the fluorescent light switch (B7...) is used as a flag to AND with the motion sensing, so that that switch needs to be Off for the motion sensor routine to turn on the Hue light. MS motion sensor Hue light - [ID 0012][Parent 006A] If 'MS Storage Sensor' is switched On And 'B7 Storage' Status is Off Then Set 'Hue / Hue-Storage' On Set 'Timers / t3_storage' Raw value 1 The second program looks for my 60 second time period to expire, turning off the Hue light: MS storage turn off Hue light - [ID 00C2][Parent 006A] If 'Timers / t3_storage' raw data 0 > 60 Then Set 'Hue / Hue-Storage' Off Set 'Timers / t3_storage' Raw value 0 Now a few things here: The "Timers" you're seeing here is a plugin I created, that increments once per second if it is set to any value other than zero. You could do an equivalent thing with a program like you did with your Timer Decrement program, except that it increments the variable instead of decrementing it: If $sTest_Motion_1_timer > 0 Then Wait 1 second $sTest_Motion_1_timer += 1 The other thing is that you're using the same light for both motion sensor activated or manually switched on. That makes it a bit harder to disable the timer mode when manually switched on. You would need to modify my "And 'B7 Storage' Status is Off" with a status variable instead, and have two separate programs that sets the variable (such as to 0 or 1) whenever the condition of the light switch changes due to control events from that switch. It would be sleeker to follow the status of the switch with a single program, but the status of the switch would be changed by either manual switch activation or by motion sensing...you couldn't distinguish which the case it is. The bottom line is: if the way you did it works for you and you understand it, stick with it. "Efficiency" becomes quite secondary.

Well, nothing quite like getting it from the official source. It's disappointing, but I'm not surprised. Thankfully I only had about a dozen Zwave devices.

You could either get a Zooz usb stick, or the UDI ZMatter dongle (it does Zwave and Zigbee) to add Zwave functionality to your eisy. It's not built-in. The ZMatter dongle might not currently in stock.

Good, we need more pests! Seriously, I'm just one more enthusiast who's enjoying the trip to an unfinished destination. Forums are great for us, to share our findings, and questions. To answer your first question: yes, that something is a Google Home mini (Google's own idea of a smart speaker like Alexa). When I was trying out smart speakers, I snapped up a Google Home mini for $15 on marketplace. After initial testing I ended up adopting Alexa. It stayed there, unused for over a year. Then Matter came along and I discovered that it supported Matter. So my first test was with that, talking to a GE Cync bulb (wifi). Then I got it shared to the eisy with the first IoX release that introduced Matter support (5.9.1), roughly a year ago. Yes, the eisy can directly talk to a Matter device, but cannot yet set it up without a 3rd party platform to initially configure a device and then share it. They're getting the plumbing working first, and getting to the finishing touches in due time. For your second question: I'm not a HomeKit user so I can't answer that. There has been some HomeKit integration development too, and I believe there is a eisy plugin for it. It depends on what you're trying to do: getting HomeKit to control devices connected to the eisy? Or the other way around? There are also Home Assistant users here too (I'm not). They would know more about how to get the two talking to each other.

So on the Polisy, did you go into Configure and click on "Migrate to Zmatter" and follow the procedure to create the migration backup? I did all that, multiple times, and never got it to work. You should open a ticket, and tell us how it goes.

Do both controllers have the same Zwave device (Zooz stick or ZMatter)? I tried a migration from Zooz to ZMatter and never got it to work. I also had placeholder nodes like you're seeing. I ended up manually redefining the Zwave devices. Looks like a general migration issue. You should open a ticket.

Energy monitoring plugs are making these plugs more worthwhile. Glad they're being introduced.

Try powering off your eisy and rebooting. I've had to do that after configuring the dongle.