Guy Lavoie

Others have reported issues with Firefox. Try Chrome.

With Chrome? Post a screenshot.

No need to specify a port, it's just the standard port for http. http://eisy.local Or hard-code the ip address

You mean upgrading by using eisy-ui? Go in eisy-ui and scroll down to System, and then after selecting the repository you're using, just click on "Upgrade Packages". This will now work the same for eisy or Polisy.

Ah cool, just tested it ok. Yes, would be more intuitive on the node page. I like how the node numbers of LR devices start at 256, reflecting the way Z-Wave node expansion was implemented above mesh. I see that Shelly also has input modules. Let's hear it from others who are now testing this new LR thing.

Quick summary of testing done so far with firmware 7.46 and eisy-ui 1.4.4: Inclusion and operation of a LR device (Shelly module) Inclusion and operation of a regular (mesh) S2 device using QR code (Weiser Smartcode 620 lock) Inclusion and operation of a common mesh device (Jasco module) Testing of LR range: a bit disappointing. I don't know how this compares to a Yolink device, but going through concrete foundation walls seems to really limit range. I first tried it where I usually plug in my pool pump, which is the corner of my property. Two inside walls, two concrete foundation walls (the house has been expanded) and through two walls of an aluminium above ground pool. Total distance, about 80 feet. No go. Next was in the standalone garage, which subtracts the two pool walls but adds steel cladding, About 60 feet. No go. Next was inside the basement workshop, which brings it down to just the two inside walls and one concrete foundation wall. That works. Now I'm testing this with my trusty test Polisy, which is near my computer in the basement, and the dongle is at desktop level. I suspect that moving the dongle higher up, ideally above ground, would help. I'll test that when I implement the LR function on my production eisy, it's dongle is almost at ground level. Also missing in eisy-ui is the ability to edit Users for the locks.

Yes, I had noticed that 5.0.0_8 had never showed up. But now there's 5.1.0 (but no release notes...please?) 🙂

Eureka, it works!! Took a bit of fiddling, but I got there...we have the technology! I first tried selecting the "US LR" Z-Wave Region (it's at the bottom of the list) but the setting wouldn't stick. So I turned Z-Wave support off and back on again, and there it was: US LR. So I deleted the nodes and factory reset the module, and did the inclusion process again, and the Long Range button was now the default selection. Interview went fine and it works. 🙂 Thanks to @Javi and @junkycosmos for getting us this far! The Wiki on this needs a good update, to incorporate all the little things we've uncovered in this thread (if you want to avoid a bunch of support tickets). - The process to update the firmware on the ZMatter dongle, including enabling the LR feature (ideally without needing the Zsniffer step) - Indicate that updating the dongle to 7.46 and the bootloader to 2.04.00.05 is fine, by doing the firmware updates to 7.45, then the bootloader, then 7.46. Also indicate not to go beyond 7.46. - The need to update eisy-ui to 1.4.4 - The need to manually change the Z-Wave region to US LR (it's at the bottom of the list) and restarting Z-Wave Support plus any other tidbits I might have forgotten. Btw, that Shelly unit is a nifty little device. The documentation is rather poor and hard to find on shelly's web site.

Ok I'll try that...tomorrow! Thanks.

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.