Guy Lavoie

Good idea, a separate Favorites tab.

I tried a Zooz to ZMatter migration: it doesn't work, despite the instructions given (make a migration backup, etc) And there is no ZWave backup option when you have the Zooz stick. Truth is, you'll need to re-include your Zwave devices. Though if it's the same physical stick, just moving it over to the eisy sounds like it should work.

How about maintaining a list of the plugins that are working fine, vs ones that need adjustments?

That looks more like a 64 GB SSD getting full available capacity.

The reflash instructions that several of us got last year didn't mention the resize32 script! Better late than never 🙂

Yes, I've done that: make a new image file. 32 GB is plenty of space for everything, including eisy-ui, plugins etc. The screenshot of my df command above is my test Polisy with all the latest versions. Since you say you have 2 Polisys, why not make a new image file from the not reimaged one instead of the recovery image you got from UDI. It's that recovery image (I think it was 5.9.1) that had the problematic small image. But post your df screenshot. I'd like to see it.

No, the hardware can handle both 32 and 64 GB SSDs. If you do have a spare SSD as you seem to saying try this: make a backup of your current system, then take out the SSD. Flash the new SSD the way you did it to recover and put that in your Polisy, then restore your backup. Now you're running a clone of your system, and do the filesystem expansion process as shown in the video. No risk for your original SSD.

Reallocating the drive to use the full 64 MB is more work, because another partition has to be moved (partitions have to be contiguous). I also have a 64 GB SSD in one of my Polisys, but I left it configured as a 32 GB. The whole UDI software only requires about 6 GB.

Thread here:

It does have value as a test platform for a nerd like me! Post an asking price and where you are. I'm sure someone will be interested.

Bingo, telltale sign. You can ssh into it and then do: df This will show the disk space. It should look like this: Let me find the forum thread about this and I'll post it.

eisy-ui from the middle ages, when knights were bold! Do you have one of those reimaged Polisys that end up with a small filesystem? There was a problem with that a while back, requiring some unix commands to reallocate disk space properly.

Essentially, the Polisy will be following the same path as the eisy for now: no new updates to admin console and gradually switching over to eisy-ui, which is gaining in functionality steadily every few days. Initially UDI had wanted to reduce support for the Polisy and any updates would have been done manually through ssh. Instead, they relented and brought back updates through eisy-ui, just like for the eisy. The main constraint is that it is limited in the version of FreeBSD it can run, so there might come a time when something new might not work. Support for Matter might also be affected, something to do with IPv6 functionality being problematic.

I have it working here. I right click on the main lock node, and select "Configuration" at the top of the list.

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.