walkman9999

Edit: The motors on the blinds are "native" z-wave. I don't know if they have a built-in gateway between RTS and Z-wave or are actually z-wave, but there are no external gateways and they pair using Z-wave protocol. I'm not sure. I tried to look up in the spec sheet, but blinds were purchased thru Costco so not sure model of Somfy motors. Is there a way to tell? Not sure if relevant, but the blinds are paired with Z-Wave include command to both the supplied remote and the EISY, and the remote was paired the same way with EISY.

Hello - New to Z-wave, but I see in the event viewer and the log that EISY is (attempting to?) waking-up the Z-Wave remote I use for Somfy blinds every three minutes. This seems excessive, but I'm not really sure if the remote responds to these requests. I'm concerned that it will lead to short battery life for the remote. I see that I can make changes to this interval on EISY by selecting the remote and setting the interval but I don't know what the comm are for and if changing the interval is a good idea. Anyone shed any light? TY Log: Main House / Shades / ZY 003 Shade_Remote / ZY 003 Wake Up Status 0% Mon 2025/03/03 00:24:21 System Unknown Main House / Shades / ZY 003 Shade_Remote / ZY 003 Wake Up Status 100% Mon 2025/03/03 00:27:22 System Unknown Main House / Shades / ZY 003 Shade_Remote / ZY 003 Wake Up Status 0% Mon 2025/03/03 00:27:22 System Unknown Main House / Shades / ZY 003 Shade_Remote / ZY 003 Wake Up Status 100% Mon 2025/03/03 00:30:23 System Unknown Main House / Shades / ZY 003 Shade_Remote / ZY 003 Wake Up Status 0% Mon 2025/03/03 00:30:23 System Unknown Main House / Shades / ZY 003 Shade_Remote / ZY 003 Wake Up Status 100% Mon 2025/03/03 00:33:25 System Unknown Main House / Shades / ZY 003 Shade_Remote / ZY 003 Wake Up Status 0% Mon 2025/03/03 00:33:25 System Unknown Main House / Shades / ZY 003 Shade_Remote / ZY 003 Wake Up Status 100% Mon 2025/03/03 00:36:26 System Unknown Main House / Shades / ZY 003 Shade_Remote / ZY 003 Wake Up Status 0% Mon 2025/03/03 00:36:26 System Unknown Main House / Shades / ZY 003 Shade_Remote / ZY 003 Wake Up Status 100% Mon 2025/03/03 00:39:27 System Unknown Main House / Shades / ZY 003 Shade_Remote / ZY 003 Wake Up Status 0% Mon 2025/03/03 00:39:27 System Unknown Main House / Shades / ZY 003 Shade_Remote / ZY 003 Wake Up Status 100% Mon 2025/03/03 00:42:29 System Unknown Main House / Shades / ZY 003 Shade_Remote / ZY 003 Wake Up Status 0% Mon 2025/03/03 00:42:29 System Unknown Main House / Shades / ZY 003 Shade_Remote / ZY 003 Wake Up Status 100% Mon 2025/03/03 00:45:30 System Unknown Main House / Shades / ZY 003 Shade_Remote / ZY 003 Wake Up Status 0% Mon 2025/03/03 00:45:30 System Unknown Main House / Shades / ZY 003 Shade_Remote / ZY 003 Wake Up Status 100% Mon 2025/03/03 00:48:32 System Unknown Main House / Shades / ZY 003 Shade_Remote / ZY 003 Wake Up Status 0% Mon 2025/03/03 00:48:32 System Unknown

Excellent info with a compact delivery! Thank you!

That explains that. I will look for instructions from the Aeotec side. You don’t happen to know how those parameters are set from within the device, do you? They mention. The “configuration command class” but I’m not sure how that is implemented.

I'm taking this approach and testing. I set a $Temp_HIGH variable to 1 when the initial event is triggered and do not trigger again if the variable value is already 1. I have a second program that sets $Temp_HIGH to 0 when the temp is below 80 and the value is already 1. Any feedback on how to handle this in a different way is welcomed: Program #1 Temp_HIGH - [ID 0018][Parent 0001] If 'ZY 011 Home Security Alarm / ZY 011 Multilevel Sensor' Temperature > 80.0°F And $Temp_HIGH is 0 Then $Temp_HIGH = 1 Set 'Main House / Fans / Server Fan' On Send Notification to 'Prowl-Normal' content '!Temp_HIGH' Else - No Actions - (To add one, press 'Action') Program #2 Temp_LOW - [ID 0047][Parent 0001] If 'ZY 011 Home Security Alarm / ZY 011 Multilevel Sensor' Temperature < 80.0°F And $Temp_HIGH is 1 Then $Temp_HIGH = 0 Set 'Main House / Fans / Server Fan' Off Send Notification to 'Prowl-Normal' content '!Temp_HIGH' Else - No Actions - (To add one, press 'Action') EDIT:: This works fine for my purposes. Marked as solved in case it helps others.

I have a simple program to trigger an Insteon switchlink and send notification when Aeotec sensor temperature goes above 80 degrees. The problem is, when the temp stays above 80, the program will continue to run, triggering the switchlink and sending notifications unnecessarily. The program uses the Status of the device (image3.jpg), when I do similar programs for Insteon devices I use "control" instead of status, but I don't see the temperature sensor listed under control (image4.jpg). Any tips?

Hi - I have the Aeotec sensor working as expected on my EISY to trigger events based on temperature. I would like to make changes to the parameters of the device and found this manual that describes parameters and values. For example, I have no need for LUX or Motion sensors and I'd like to shut them off to save battery life. One the EISY, I see a place to change these parameters but having two problems using it (see image1.jpg). I am having trouble locating a manual with all the parameters. I found the parameter for a similar device from Aeotec (https://www.benext.eu/static/manual/aeotec/multisensor-6-ZW100-C.pdf), but my device is a 3-way sensor (TriSensor (ZWA005). Not sure how to push to device. I figured this out, use HW button on device to wake and then set Wake-Up to Keep Awake on console. When I set the device to Wake and choose "Set Parameters", I see the comms in the event window, but status of Motion Detector doesn't change. Suspect I'm using wrong parameter or value. P.S., I'm creating two separate posts for two issues to keep things organized. Second problem (program logic issue) solved. P.S.2, I added screenshot of the manual I found and linked above.

Just getting started with this, and following instructions found in the link below. The goal is to have both the EISY and the included z-wave remote control the blinds. I added the blinds to EISY and can control them as expected. I then followed the instructions to pair the Bali premium remote control to the EISY and this succeeded as well. Following the instructions, I then paired the remote control to the blinds which is successful. The remote works as expected until I use EISY to control the shade, at that point the remote stops being able to control the blinds while the EISY still can. [minor edit to describe things better] It is as if the blinds can only be paired to a single controller, although the link (and Bali's support folks) say otherwise. I'm looking for any insight into what I should be looking for, any tests that may show what is happening, or really a better understanding of the process (e.g., why does remote have to be paired to EISY?) Haven't found much in the forum, hoping someone has worked through this and can help. Attached is a screenshot of the EISY console. TY

Older, single-band devices and some noise on the wire contributed to this. The devices have been replaced and comms are as expected. TY @IndyMike for the decoding help, I've found the explanations useful in other troubleshooting of I1 vs I2 devices. Marking solved.

As suggested by replies, combination of bad programming, older devices, and a questionable PLM contributed to this problem. I can't say specifically which of the changes solved the problem, but it no longer exists. A smoking gun would have been nice, but marking solved as the troubleshooting was helpful. Thanks all.

Not sure if it is implemented, but it would be possible to use the MAC/Insteon ID to get a FW update to the devices. Wouldn't work over a WAN, but within the local network the capability is there. (I rarely get to offer any expertise, but network guy by trade.)

That is a great answer, thank you. I think what you've said, along with @lilyoyo1's point about the upgradability of the new platform makes the decision for me. Appreciate the feedback. And, removing ALL ON from the command suite is ultimately a good marketing move. That uncommanded command was responsible for giving home automation a bad rep in my fam.

Thanks, all for the opinions and info. Does anyone know if the powerline protocol has been updated, similar to the way it was updated between I1 and I2? I'm not an expert on this category, but I2 devices perform noticeably better in my somewhat noisy environment and any additional improvement would be a consideration for me. Thanks again for the input so far.

@IndyMike, all good info. Making suggested changes to simplify programs. I was wondering about the "Link for responder XX.XX.XX not found" as well. I tracked down the MAC/Insteon ID and restored both the device and the PLM, but still they persist. I believe all of the devices listed are KPLs if that sheds any light. Looking at any logs of what happens "on the wire" always yields a few mysteries (I'm a network guy). Found that all mysteries do not need to be solved so taking that approach. Appreciate the insight as always, will post back if anything interesting happens. Otherwise, I'll close the thread in a week or so.

Should have specified, I have EISY.

Hello - I'm replacing some non-dual-link switchlinks in my network and ran across two choices, wondering if anyone has any insight on differences? Possible shortcutting the assignment, I'm interested in the best comms for the devices (I2 was a huge improvement over I1 in my environment), but I'd like to match the style of the 2477D if comms are not significantly improved in the PS01. I read reviews on Insteon website, but I didn't find mention of any new protocols. Maybe I missed something. Is there a compelling reason to go with PS01 over 2477D? All opinions welcomed. TY!@

Keeping the thread updated. I have existing Insteon filters on both of the UPSs (+ the refrigerator), but it is clear that there is still a wireline problem. As @Techman and @IndyMike pointed out, the devices that are problematic to write to are older, single band devices. I can eventually get them restored, but it takes multiple tries to do so. Because I have so much invested in the system, I'm going to replace those devices. I will also follow the steps I've found listed in this forum to try to isolate the offending device(s). Unfortunately, I have a number of 12v/24v LED drivers that I suspect, but have no remediation for. Hopefully, the dual-band addition will be enough to restore reliable comms. Will report back. Thanks for help so far.

At this point, when I attempt to restore *any* device on my network, I eventually get a "Failed writing to Devices" error. I am not proficient at decoding the messages I see on the attached log, but it seems that things work until we get to the SET-MSB(OF) packets. I get same behavior when reading the device links table. I'm saying "things work" because the exchange of TX and RX messages seems quick, and generally at least one and usually two hops left. Attached is the restore of a switchlink that seemed to cruise along for two minutes until the "Failed to write" message appeared. I'm concerned that there may be a new intermittent source of interference on the network, but I'd like to get a more experienced opinion if anyone has one. TY -restore_switchlink-ISY-Events-Log.v5.8.4__Thu 2025.02.13 07.49.44.txt

Always appreciate this community, thank you. @IndyMike you are correct, the older device is the powerline only switch that I have a replacement for but have yet to replace, glad it is not the PLM. @oberkc, I will ID the specific devices that are misbehaving and restore them and report back. Thanks again for insight

I did. It went well for the most part, one powerline device didn't come back but I replaced it. Everything worked fine for about a week after the replacement.

Hello - Very reliable install went south a few weeks ago. Determined problem was a bad PLM. Replaced PLM and things went back to normal for about a week. Now I have a problem where when a scene is triggered, multiple devices that are not part of the scene are switched ON. This happens for two scenes in particular. Should note that these scenes have been part of my install for years. I thought maybe restore of the new PLM would help, but that ran into a "failed to write" error (see log: _restore-ISY-Events-Log.v5.8.4__Wed 2025.02.12 16.46.25.txt). I am able to download the links table, but not sure what it is telling me (file: PLM Links Table.v5.8.4__Wed 2025.02.12 16.57.37.xml). I also captured a log of the scene running and triggering the switchlinks that are not part of it (log: scene-trigger-ISY-Events-Log.v5.8.4__Wed 2025.02.12 16.46.49.txt). The programs are included as well, but I don't believe this is a programming problem - although I'm open-minded. One program has the IF and second one has the THEN. North Gate.v5.8.4__Wed 2025.02.12 16.59.01.iox -> _North Gate.v5.8.4__Wed 2025.02.12 16.59.16.iox Any help is appreciated. @IndyMike, you have been great at helping me understand the logs in the past. Maybe some insight? Thanks in any case. _restore-ISY-Events-Log.v5.8.4__Wed 2025.02.12 16.46.25.txt scene-trigger-ISY-Events-Log.v5.8.4__Wed 2025.02.12 16.46.49.txt PLM Links Table.v5.8.4__Wed 2025.02.12 16.57.37.xml North Gate.v5.8.4__Wed 2025.02.12 16.59.01.iox _North Gate.v5.8.4__Wed 2025.02.12 16.59.16.iox

This is very useful, TY! I've decided to replace the device with a dual-link model.

Hello - I have a previously working switchlink dimmer v.40 that will not accept updates from EISY. This occurred after PLM replacement, not sure if coincidence or not. I have tried hard reset. Logs are attached for an attempt to write to device, and separate log for attempt to restore device. Neither is successful, but it does seem to be some comms between EISY and the device (I think). Comms to other devices in same are seem to be healthy. Let me know if an more info needed to help diagnose. Any insight is appreciated. TY EDIT: attached log from device query _restore-ISY-Events-Log.v5.8.4__Sun 2025.02.09 14.12.35.txt _write-updates-ISY-Events-Log.v5.8.4__Sun 2025.02.09 14.13.38.txt _Query-ISY-Events-Log.v5.8.4__Sun 2025.02.09 14.28.42.txt

Thank you for the decode. Swapped out PLM and looking much better. I am having a problem with the link tables on two devices after the swap out, but working on troubleshooting and will post in new topic if needed.

Hi all, Existing install, having some intermittent problems that seem to point to PLM (device triggers do not reliably run programs all of a sudden, but comms see OK). The PLM shows connected and I can control devices using the admin console, but I cannot read the device links table from the PLM. I have a spare and am going to swap tomorrow. In the meantime, is there another test to check comms between the PLM and the EISY? TY