Guy Lavoie

I'd like to add something else here, potentially useful in certain programming situations. My phrase "Integer variables won't do anything in If/And/Or statements" isn't quite true: integer variables can be tested in If/And/Or statements, but they won't trigger the program if they're what end up making the program true, They're useful as static conditions that you might want to be true for other triggering conditions that you want to test for. An example: you might want to test that an alarm system is in armed status to allow some triggering actions, like motion detection to trigger an action. But you might not want that action triggered if motion was already detected and you're now just arming the system. By setting the armed status into an integer variable, you can avoid that second condition from happening.

After reading this thread I just thought I'd see how my own portal access would come up. Interestingly, my three Polisys do show the "eisy-ui" menu option, though none of them have portal subscriptions. My eisy, which does have portal access, doesn't show the eisy-ui option. eisy-ui does work fine locally though, and has portal access permission enabled. All my units are running 6.0.5.

Yes, state variables exist for the purpose of triggering actions on their values. Integer variables won't do anything in If/And/Or statements, they're only useful for doing calculations, etc.

Any luck?

I wouldn't rule out a failing PLM.

Well have you tried doing a "restore device" on these problematic devices? Give that a shot first.

I don't think it's an error. It's just telling you to restart your admin console after having made your changes, which is desirable and normal.

Assuming they have enough warning and lead time.

Well UDI has had it's run of bad luck with supply issues. The Polisy got replaced by the eisy because they couldn't get the PC Engines unit anymore. The eisy has had a few periods where it was back ordered. Then they had the import tariff issues, recently the high cost of RAM issue. Now add to that the zmatter dongle (a Z-Wave.me product) that now appears to no longer be available. It's tough when you're not in control of producing your own products.

I beg to differ, at least about zwave. It's well implemented in IoX and is useful for things like locks and a few other safety products. Zigbee is more aimed at low power or battery operated devices, especially sensors. I'm grateful to have it all. Has UDI told you outright that the ZMatter dongle will no longer be available? If so, I'm eager to see what they'll replace it with. I wouldn't be surprised if they said that implementing Thread (Matter) on it won't happen and that they'd just say to use a border router. But, lets wait and see.

You can get zwave motion sensors, why not use those? The Zooz 800 series dongle is very affordable and works fine with the eisy. It's only zigbee that's you can't use without the Zmatter dongle.

Yes, Matter seems aimed at the "shrink wrap" market, where you buy it off the shelf in a store, bring it home, and set it up with a phone app. Meant to work with the consumer products like Alexa, etc. It's still nice to have on a controller like the eisy because it expands the user base who might have started with Alexa and then wants to get more involved control, while preserving his initial investment. It also gives us die hard control freaks more devices we can integrate. Everybody wins.

Well if you only need zwave, you can then get a Zooz 800 series dongle. The ZMatter device, despite it's name, isn't yet used for Matter. Matter uses wifi, and can do Thread through a border router. I've tested this myself, though Matter is still in alpha testing. The only thing without a ZMatter alternative is zigbee.

Was the controller powered off when you replaced the PLM. It's important that you do that. If you didn't, then reboot it, and then do a restore device on those two switches.

Just a wild guess: when you added it, did it show a popup box offering both S0 and S2 security? If so, did you uncheck the S0 box and supply the pin code to enable S2? I've seen devices supporting S2 not adding properly if you don't do that.

Well, Ideally you'd be running 5.0 16C, but if you're not using Zwave, then sticking with whatever works would be ok, with the idea that if you really want to do new things, an upgrade to a eisy would be the proper path forward.

So it was a networking issue. Those can be mysterious in incomprehensible ways. Glad you're back up!

So trying it with the ip address in the finder url still doesn't work? Sounds like some kind of networking issue, in the eisy or the network. Have you been running 6.0.5 for some time already?

No, I'd stick to 1 amp or higher. And use a regulated switching power supply, not an old style transformer and diode one (they're heavier). Splice the cable, observing polarity.

In the isy finder, try creating an entry with it's ip address, eg: https://192.168.0.123:8443/desc See if that works

Messed up my edit... lol

I did it myself. Alarm sensors are generally quite easy to reuse. Almost everything is 12V based, and often you only need to replace the EOL resistors. Elk zone definitions allow you to skip the EOL resistor if you want. Panels only require 4 conductor cable, Ordinary Cat 5 wire works fine.

Many of us have Elk M1 panels (including myself). I'm not sure what you're specifically referring to by "migration", mine was more of an outright new installation, though I did reuse some sensors that were already there. The Elk is very programmable, and the integration with the eisy plugin is very well done.

Having a program set the backlight or the On level of a switch writes to it's EEPROM, which wears out the memory cells. Not a good practice.

Have you actually tried another power supply? That's the first thing I would do.