All Activity

@Hawkspoint, We are not going to do that. The reason we removed this feature was because of massive tech support issues. You can easily have your router provide eisy the same address EVERY TIME by using DHCP Reservations. Please check your router's configuration instructions. With kind regards, Michel

Looks like my estimation was fairly accurate. However, I don't find any API description document on that website, mostly only sales info for their silabs chip. There seems to be some discussion of some code but no actual code or links to anything. Am I missing something?

Long press? In UD mobile? You should look for them in the Admin console.

You can find Matter command stuff here: https://community.silabs.com/s/article/Implementing-custom-commands-for-the-Matter-CLI?language=en_US And no, we don't necessarily need new hardware to send and receive commands. Matter is implemented using IPv6 over hardwired, wifi, or Zigbee physical layers. No new physical layer has been introduced along with Matter. Yes, it is a standardized way of interrogating a device to find out what it is, and what parameters it will accept. That's the whole attraction. Up until recently, each protocol had it's own, often proprietary way of doing things. Serial bytes to a PLM to send Insteon, various command implementations sending data over Zigbee and Zwave. Raw bytes to an IP port to send data to various hubs. Then things started to use more similar network layer implementations to save on costs, like HTTP for Venstar and Ecobee thermostats, Hue hubs, etc. Various forms of security too. The physical layers also become more common (like Zigbee and Zwave), but the commands sent across these physical layers were still proper to each device, and often undocumented. Then in 2019 (from the wikipedia article on Matter): In December 2019, Amazon, Apple, Google, Samsung SmartThings and the Zigbee Alliance announced the collaboration and formation of the working group of Project Connected Home over IP. The goal of the project is to simplify development for smart home product brands and manufacturers while increasing the compatibility of the products for consumers. Finally, lets get our stuff to talk to each other! The idea was to create a high level API that allowed common commands to be sent to each other's platforms. It might not implement every single feature, but each one could decide what to allow (expose) to be done by "foreign" controllers. That way they could still compete on finer exclusive features. For example allow lights to be turned on and off, dimmed, and set to a color. But things like animation, scenes etc could be restricted to the native platform. We often see that in product feature descriptions. Now with a controller like the eisy, UDI does the implementation of the commands needed for each protocol. They first did Insteon and X10, then added Zwave, then Zigbee, and now Matter. For us users, it always comes down to the same simple command, such as Turn <device node name> On That's what we pay them to do for us 😀

I have 2 Scheduled programs that eisy says are not found. It suggests that I should synchronize but even after that, the programs are still not found. The cursor is empty. can someone tell me how to delete these zombies from the listing? I have tried a long press but nothing seems to work. thank you

Excellent info with a compact delivery! Thank you!

Here's an example If you want to partially disable the light sensor (see attached screen shot example): Put the sensor into the lnking mode In your EISY on the tri-sensor device window: Set parameter number to 24 Set parameter value to 32767 Set byte size to 2 Then click on set configuration I use the Zooz temperature and humidity sensors. They're small and compatible with the EISY Zooz 800 Series Z-Wave Long Range XS Temperature | Humidity Sensor ZSE - The Smartest House

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.

You can't use the setting parameters from another device for your tri-sensor. Attached are the available advanced configuration settings for the (discontinued) Aeotec tri-sensor Aeotec-Trisensor Engineering Specification.pdf

Where is the local API? I haven't seen anybody that even knows what Matter is, let alone why we would need a new piece of hardware to broadcast a protocol over WiFi hardware that is already built into every router EISY is attached to. From what I can deduce, Matter is just a standardized way of interrogating a device to find out what it is, and what parameters it will accept. That sounds like a huge database to handle every style of device that can be thrown at the EISY. However, I detect the same secrecy for Matter, no different than every other protocol that was destined to fail because the manufacturer always tried to keep it a secret, or was too lazy to write an API document, that programmers could understand and support their products. "Total control...end to end" (we won't mention the EU threat of banning that one! ) I sure hope I am wrong in some of these assumptions.

That's the whole reason why we (UDI controller users) are interested in Matter: because it's the first industry lead effort in interoperability. Go look at the dozens of smart bulb products available. They all boast "Works with Alexa" and "Works with Google Home". They all show a free phone app that you need to create an account for. But count how many of those have an open, local API? How many can you include into a scene command launched locally by your controller? Very few. Right now, Matter compatible products are rare. But give it a year or two and they should become as common as those Alexa compatible products. Many smart products are already IP compatible, so they just need new software. The Hue hub is a good example of acquired Matter compatibility. Having Matter compatibility in our favorite controller now gives us futureproofing.

Modbus JSON is a standard, you need to define the file based on your modbus network so that eisy plugin can consume the data and read/write modbus devices. UDI, I believe, wants to integrate with it but not create modbus tools. You can web search tools either GitHub python or excel macros for a solution, or maybe the file already exists for you installation? My guess is once you've created the correctly named file and stored it in the correct location, the plugin will load that data and have related nodes for you to work with it

I'm happy to report that after working up the courage ( and making ample backups), I pulled the trigger and the upgrade appears to to have worked without a hitch. This has however led to a number of other questions: 1) I now see the ability to add matter devices via the ios app with a QR code. I might be wrong but I beleive if a matter devices has already been added to Apple Home, for example, adding it to another controller is done by using a code. I'm not seeing a way to do that that though. Am I missing it? 2) I see the matter menu in the admin console now. Is there an explanation of what these menu items actually do and when to use them?

That's the right approach. You've hit upon the one exception with true/false testing: a test for a state variable being greater than or less than a value will retrigger true every time that the variable itself changes value, along with the logic test itself being true. So you are doing the right thing by setting a second variable to one of two values, as a flag that your conditions are met.

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.

I'm very happy there is now (hopefully) a straight forward was to use MODBUS with eISY, the plugin I found on Polyglot is ModbusTCP Modbus TCP allows you to define your Modbus registers in a JSON file, upload it and leave the rest to IoX. No coding is necessary. Make sure the file is named modbus.iox_plugin.json Now I cannot find ant help or examples or documentation on how to configure this JSON file, or how to actually access the registers in the admin console or tie them to command/statuses. This plugin is built by UD, so I expect some guidance. I understand it's free, but at least and example please. Thank you so much.

Got it! Thanks, as I do not have the dongle.

Perhaps it is no big deal. Since hearing about it and the possibility of ISY support, I was excited about the possibility that some of these alexa/homekit/google devices would work at a local level (no cloud reliance), not require the use of inceasingly limited wifi bandwidth, and the possibility that these various matter hubs (including the ISY) would expose their respective devices to the various other hubs and border routers….one happy family…all at the local network level. I do have one of those Brilliant switches. At one point, they were promising matter support but I suspect they are out of business at this point. I was hopeful that the promises of matter would ultimately bring exposure of ISY devices to he brillianr switch. Probably not going to happen now. yes, much of this capability is available with node servers and portal, but this remains too dependent on the cloud for my preferences.

I have a Govee LED curtain light set and it supports BT, WiFi, and Matter. Alexa sets up with it automatically when permitted. That is over WiFi via the Alexa server through my fibre router and Wifi. Router is a few years old and belongs to the ISP. Just the same old 2.4GHz WiFi AFAICT. Nothing special about this router so I don't understand what the big deal about Matter is.

I have the same two devices, plus two thread border routers (echo hub and google nest hub 2nd gen). No luck so far. Same, or similar, errors, depending on how I try to add it. They both add fine to google and Alexa, and both can be shared between the two and with apple HomeKit.

You can't have a scene trigger another scene (though it can be done with a program and using the Virtual plugin). Instead, you should simply create a new 3rd scene, that involves all the lights that you want it to control. Individual lights can be responders to dozens of scenes if you wish.

To my knowledge (from what I've read on the forum since the release of 5.9.1) no one has successfully added a Matter device yet. We all get that kind of error when reading the QR code. I have these two test subjects on hand myself: the Cync bulb is Matter over wifi, the Nanoloeaf is Matter over thread. They both work with their phone apps (Nanoleaf over blutooth) For the Thread bulb, I don't have a border router yet (keeping an eye open for a deal on a used 4th gen. Amazon Echo) though I would think that eventually, the ZMatter dongle should be able to do that directly.

How do you call a scene from a scene without using a program? I currently have 2 3-way scenes where I use 1 Keypad button and a separate switch in a 3-way operation. This already works correctly. Now, I want to use a 3rd kepad button to trigger both of these scenes. The application is that I have some lights over my bed. 1/2 controlled by one 3-way circuit, 1/2 by the other. While I sometimes want these controlled separately, other times I would prefer to have a single control that would activate all the lights. I tried to create a scene with the 3rd button, and then drag the other scene into it, but the UI didn't let me do that. I tried to add all 5 devices (3 KPL buttons and 2 dimmer switches) to the scene, but it seemed to complain that the devices were already controllers in other scenes, so it wanted me to configure them as responders. I tried to group the 3 KPL buttons together, and this kinda worked (meaning the 3 KPL buttons correctly linked), but the 3-way operation with the dimmer didn't work. I thought that since KPL.A worked with the scene to turn on Switch1, that if I had a new scene with KPL.A, KPL.B, and KPL.C, if KPL.C turned on KPL.A, it would also trigger the scene that KPL.A controlled Thanks.