Guy Lavoie

Here is the main Z-Wave screen. I tried it with both Z-Wave support set to On and Auto: Here is the Inclusion Type screen: And here is the QR code:

I have, on one of my test Polisys.

I got the Shelly device today and wanted to add it as a Long Range device: but the LR option is greyed out in eisy-ui (after loading the QR code image file). I upgraded eisy-ui to 1.4.4 since the release notes mention "Fixed disable of long range inclusion option", Rebooted controller, factory reset the device and tried inclusion again, but the LR option is still greyed out. Adds fine as mesh device. As discussed here, I'm running the ZMatter dongle with firmware 7.46 and the Long Range option enabled (after the Zsniffer tool step). Not what I was hoping for. The device adds fine as a mesh device, and through the parameters, you can set it for momentary contact mode (great for garage door application), but the point was to get it working as a LR device. @Javi , any hints?

Well the eisy supports multiple protocols with the appropriate interfaces (X10, Insteon, Zwave, zigbee, Matter). If the plugin exposes device nodes, then the technology behind those devices shouldn't matter.

Well there is a plugin called "Virtual", which allows you to create virtual switches and dimmers. They appear as regular device nodes. If the Apple home connectivity works as I think it must, then these would appear as switches on your Apple system, and could be turned on and off by it. Then, you can write programs in your eisy that look for these virtual switches being turned on and off, and have it send a matching scene command. For example, if you create a virtual on/off switch called Virtual_basement_scene (pseudo programs): IF Virtual_basement_scene Status is ON Then Set Scene basement_lights On IF Virtual_basement_scene Status is OFF Then Set Scene basement_lights Off

You could use the Virtual plug-in to create "switches " that Apple sees, and write programs that trigger your scenes when the switches are turned on or off.

You could use the Virtual plugin to create a "switch" that appears in UD Mobile, and write a program that does what you want if the switch is turned on, etc

Yes, the X is simply telling you there was nothing to back up in that area.

It's on the to do list, I know that for a fact.

If you go in eisy-ui and bring up the scene, you'll see the controller at the top and the list of responders below it. Now click on the ">" beside (on the left) of the controller and the responders expand to a list of editable boxes. Click on the light you want to configure, and change the Link Type from "Default" to "Command", and a Command box will appear. Pick the setting you want to edit, such as "Set RGB Color", and then you'll be able to set the value to what you want for each parameter. You can really edit everything.

In cases like that, I add the new switch, then use Find/replace (In admin console) to find all references for the old device in programs, to then replace them with the new device.

Amazon "specs" are a source of entertainement of their own! I have no idea where they're getting the 192 watt "wattage" rating either.

Hah, I've also been "shopping" for something to get just to test LR 😄 And the winner is... https://www.amazon.ca/dp/B0FSLD56D9?ref_=pe_125682630_1045605200_t_fed_asin_title&th=1 I'd like to see if I can use that instead of a Insteon IOLinc, to avoid the garage door opening if an Insteon "All on" occurs. I've had two occurences of that in just over 2 years. I should be getting it in 2 days. I'll report back. Yes, I had also thought about your comment, about purchasing the LR update BEFORE the firmware update. Kinda late now. Either way, the Wiki article needs an update because 7.42 is no longer listed, and the feature purchase step should be added if this is the case. Going all the way to 7.46 would also be worthwhile if the update is mostly about improved stability, as the release notes indicate. This should be validated, ideally by UDI.

Thanks for the update. Have you actually added any LR devices, in LR mode? If so, a screenshot of the device node or whatever showing this (indicating LR mode) would be interesting to see. The thing that puzzles me about @Javi 's warning is that with the upgrade performed as per the Wiki instructions, the LR feature in the dongle doesn't get activated, and the upgrade skips over 7.42, going straight to 7.45 instead. So the process at the dongle manufacturer's site has changed since the Wiki article was written, and the extra step with Zsniffer is needed to enable LR. @Javi , can you confirm this?

Well the time interval in your program became false, so it executed the Else statement.

Same here.

I'm in the eastern time zone and the times in the log file are two hours earlier. Same thing with other time zones?

Yup, ticket time. That's really unusual.

For those trying to figure out how to get this done (it's not very intuitive) here are the steps I wnt through with my Windows 11 PC: Use the link provided to download the Zsniffer tool and select the Windows folder, and download the Win32 version (there is no 64 bit version), then unzip it in a directory on your PC, browse to it, and run ZMERadioTools, the very last file at the bottom. You'll get a text window and the Advanced Radio Toolkit Screen, which you'll work in. at the bottom, click on the "+" button to add a port. You'll get a generic port line, named dev00. Now click in the box under "Serial", which will bring up a down arrow on the right. click on the arrow to see a select list, and choose the virtual serial port that you used to upgrade the ZMatter device firmware. I had to click on "Protocol" and choose PTI, and selected the baudrate 115200. Then click on the button with the little "i" at the right of the list. If everything is ok, you'll see the UUID of your dongle and a popup screen showing the features enabled, and that will also update the features that you had previously enabled (long range and ultra uart). Exit the Zsniffer program and go back to the link to start the controller tools, and now you'll see the features enabled and checkboxes telling you that, as explained by @junkycosmos

Just for fun, I upgraded to eisy-ui 1.4.2 minutes ago, and my memory usage shows 97%, but the line is blue. I don't know if it's just a change they made to make it feel more normal, or if there's a meaning to the color.

I don't really have any other suggestions. Hopefully others have suggestions.

So nothing out of the ordinary. The screenshot in your original post seems to indicate a possible hardware issue with the controller's built-in storage controller. mmcsd0 is normally the primary flash storage. It's as if it was not responding and timed out. Hardware failures are rare, but not impossible. If it was a driver issue (from an update) I would think that others would have reported it. Is your eisy in a confined space? Does it get very hot?

There are some overnight tasks that might have used up some of the available memory. 90%+ memory usage is what everyone pretty well sees on a running system. A Polisy or a eisy-lite only has 4 GB of RAM and get along just fine. As for the lock ups, do you have any particular plugins or other programming that sets your controller apart?

It should be recoverable, I'd think. It could also be the power supply. I've seen that happen.

So the Polisy will fall farther behind.