Andy P

I don't know if it matters, but your finder shows http. Try ADDing an entry with https:// and use port ipaddress:8443

In the finder, is the URL listed as an IP address or some form of the name of the ISY? If it is not listed as the IP address, click on ADD and then enter https://123.123.123.123:8443/desc as the URL where you substitute the correct IP address. oh, @IndyMike just posted the same thing!

I use the Aqara FP2. Unfortunately, it does not connect with the EISY directly. I am using it with Apple Home(kit). I like how you can set up zones and count the number of people and duration of presence.

When referring to a node, the # becomes the node identifier. Besides the insteon address, you can also use polyglot created devices like this Rain Tomorrow ${sys.node.n007_forecast_1.GV18} ${sys.node.n007_forecast_1.GV13} Accumulation ${sys.node.n007_forecast_1.GV8} When you use a program to trigger a notification, the # automatically gets replaced by the ID of the program that called it. ${sys.program.#.address} ${sys.program.#.name} ${sys.program.#.status} ${sys.date} ${sys.time} program[97] Garage Closed True 2025/03/30 06:10:00 AM

This is a shot in the dark, but I had an issue kind of like this where the remote switches work but didn't turn on the load switch. Turns out that in the scene definition, somehow those remote switches were set to turn the remote on to 0% instead of 100%. When I fixed the scene, the remote switches worked as expected. Just another quick thing to check.

My imagination says that they will use what they learned from the U-D mobile app and apply that to a full function console.

Every i3 keypad I get from the factory is incorrectly set with the bottom as the load. I posted previously my interaction with Insteon on this topic and they added a warning to their product page that says this as well. Anyway, you need to factory reset the device to get the load back to the top button. Read the information at these two links. i3 Keypad Setup IMPORTANT: We’ve discovered an issue where some i3 devices may have shipped with a configuration issue that impacts performance and reliability. To ensure best performance and reliability, factory reset before using. How to manually configure Insteon devices Wall Switches and Keypads Air gap the switch by pulling out the set button, LED will turn off Press and hold set button all the way in and hold down. You will hear a long beep. Keep the set button held down until the end of the beep, then release. Switch will double beep. Then, LED and connected fixture will turn on to indicate factory reset is completed. 

The new i3 4 button creates one node for each of the 4 buttons plus a node for the 'flags'. The 4 button nodes work pretty normal - the same as the legacy keypads. Only one of the buttons has the on/off option. The button controlling the load gives you an on level and ramp option, the others do not. When you select the flags node, you have to do a Query to get it to populate. Every keypad I installed had to be factory reset to get the load to be the first button.

I faced the same question. I found that the nice thing is that it is easy to copy all of the devices from one scene to another. Just multiselect all the devices in the first scene and right click and add to scene for the other scenes. Then you have to adjust the dim levels individually, but at least adding the devices goes fast. I created 8 scenes for the living area with 8 devices each so it definitely saved time using the multiselect method. I think I did finally figure out what @larryllix is saying. I used to think that the PLM was sending a command to each device in the scene telling it to 'turn on and dim to level x' but now I believe it is actually just sending out a command like 'turn on scene 12345' and the device knows what it is supposed to do as part of that scene. As a result, I also changed the way I use the keypads. Instead of having a button toggle a scene on and off, I changed the buttons to non-toggle mode so they trigger a scene and then turn off. That way I can have scenes like 'bright', 'cozy', 'dim' and 'off' on the keypad and a single button press sets that scene. I found that sometimes the button gets stuck in the on mode, so I added turning the other buttons off to each scene as well. Not sure if there is a better way, but since I made this change, my wife is a lot happier with how it works.

The link I saw the other day has disappeared. It brought me to a yolink store page that specifically had a hub called Local Hub. Maybe it was a mistake, or maybe it was a leak. But it is gone now. I really don't know if that was the same hub as the ys1605 Hub 3. I assume when it is out of beta all will become clear. They continue to show this status as of today: Does the YoLink Hub 3 Support Local Integration? As of April 2024, the YoLink Hub 3 does not support local integration. It is planned to be completed by end of year along with matter compatibility and once completed, will be through a software update by the Hub 3.

Oh Interesting - I do see they came out with a new so called local hub - which currently shows as Sold Out. Seems the old hubs cost less than $25 each and the new hubs will be over $300 and have a bunch of other features. I have 36 nodes now on my Yolink node server. They all seem pretty responsive, but since a lot of them are checking for leaks and water running, I would rest a bit easier knowing the notifications/actions are not relying on an internet connection and server farm.

Thanks for the link - I checked in the current version of the App (1.40.36) and there is no option YoLink App ([Local Hub] -> [Local Network] -> [Integrations] -> [Local API]) yet. Does anyone else see it? Will keep checking.

So I took a look and here is the code that is failing - it is using the V1 soap API. That is no longer supported. The plugin needs to be recoded to use the V2 api documented here: TotalConnect2 Web API Help Page or use the code from GITHUB here total-connect-client/total_connect_client/partition.py at master · craigjmidwinter/total-connect-client · GitHub. Unfortunately, I don't know how to do that, but maybe someday. # create zone nodes # We are using GetPanelMetaDataAndFullStatusEx_V1 because we want the extended zone info panel_data = self.tc.soapClient.service.GetPanelMetaDataAndFullStatusEx_V1(self.tc.token, loc_id, 0, 0, 1) if panel_data['ResultCode'] == 0: LOGGER.debug("Getting zones for panel {}".format(device_addr)) zones = panel_data['PanelMetadataAndStatus']['Zones']['ZoneInfoEx'] if zones is None: raise Exception("No zones were found for {} - {} \n{}".format(device_name, device_addr, panel_data)) for zone in zones: if not bool(zone.CanBeBypassed) and not bool(strtobool(self.include_non_bypassable_zones)): LOGGER.debug("Skipping zone {} with name {}".format(zone.ZoneID, zone.ZoneDescription)) continue self.add_zone(loc_id, loc_name, device_addr, device['DeviceID'], zone, update) else: LOGGER.warn("Unable to get extended panel information, code {} data {}".format(panel_data["ResultCode"], panel_data["ResultData"])) Here is a good discussion on the topic Switch over to new TotalConnect REST API · Issue #245 · craigjmidwinter/total-connect-client

I have 8 of those 4 button i3 devices now and have been slowly swapping out my old 4 button keypads because my wife like the simplicity of the new devices. One rule - YOU MUST FACTORY RESET THE NEW DEVICES BEFORE USING - there, I said it. Yeah, got burned multiple times and the biggest issue is that the load is almost always assigned to the bottom button coming from the factory instead of the top button. The ground wire is in a better place on the i3 devices, so at least that part of the replacement was nice. I really wish the i3 keypads had back lit buttons instead of just the locator led, but I can live with it.

I did not see any issues at all after I left it alone for a half hour, came back and logged in, then let the admin console do the query all, looked at the devices and programs and seemed normal. Also, no issues with all of my javascript routines that scrape the rest interfaces of nodes, status, log, program, variables. I thought I might have an issue with some of the Polyglot nodes, but it turns out I just had to wait until they did their next polling cycle and then the status of the devices updated. So, all working BAU for me at least. Andy