KeviNH

Without having seen your post, I happened to order a Zac38 from their Black Friday sale. So there's no advantages (e.g. range improvement) from adding an 800 Series range extender to eISY instead of an older 500 series extender? Standalone repeaters, in my experience, work about as well as a plug-in multi-sensor (e.g. Aeotec), but better than an in-wall light switch -- I think this is mostly because my grounded steel junction boxes attenuate the signal from the in-wall device.

Cool. I needed something as a repeater, my goal is to plug this into the other outlet by my fridge, to get an alarm if the breaker serving the refrigerator is tripped.

This new Zooz 800 series repeater has a battery, can report power loss, however the official specs state that ISY support is only for the repeater functionality. Anybody tried ZAC38 and determined if power loss can be reported to eISY? Their FAQ states "When the ZAC38 switches to battery, it will send the AC main disconnected report to alert for the outage, and will no longer be a signal repeating device.". So I guess the question is whether eISY can act on the "AC main disconnected" report?

I switched to EISY and manually moved over my Honeywell VisionPRO native Z-wave thermostats (model Th8320Zw1000). Thermostats started to act oddly after joining them to the Z-Wave network and controller, the heat relay would cycle quickly (clicking on and off). Doing a Z-wave "remove" cleared the problem. Does anybody have a Th8320Zw working reliably on EISY?

Lucky me, I have the EISY on a web-controlled smart plug, so I was able to remotely power-cycle it even though Z-Wave was offline. Shout out to "Digital Loggers" for their web-controlled smart plug -- DLI has been making smart power strips for decades, saved my bacon more than once.

New EISY, was initially working fine, after adding a couple of Z-Wave devices it would no longer bring up the add new device dialog, and after a reboot it now shows the "ZMatter Z-Wave not responding" error. Using the reboot menu item does not clear the error What is the correct way to resolve this -- is a power cycle the only fix?

Thanks, that's a good sign of compatibility. Kasa, being WiFi, is a no-go for us. While "outdoor rated" isn't a hard requirement, physical robustness doesn't hurt, especially when more cheaply made "cube" modules with Z-wave are only a few bucks cheaper.

We're looking for plug-in modules with energy reporting so we can monitor devices remotely, turn them off if they are left on, and still allow local control (by pressing the button on the module). The MP22ZP seems to fit our needs and budget, anybody tried it? Vendor site states ".Outdoor smart plug designed for use for most residential lighting and motor applications...Compatible with SmartThings, Wink, Vera, Fibaro and all Z-Wave certificated hubs."

That's how I do timers on the ISY994 today. The first program calls "Run program Timer (then)". Because the "Timer" program has no conditions applied, it only ever runs when called, and runs to completion unless stopped (manually or by another program which explicitly calls "stop program ..."). Another trick I use involves a third program, "Timer called recently", which has a condition like this: Timer Called Recently - [ID 0083][Parent 002A] If From Last Run Time for 'Timer' For 1 hours Then - No Actions - (To add one, press 'Action') So by adding a condition the the first program of "Program 'Timer called recently is False' I can keep the first program from running again within an hour of when 'Timer' was last executed. (This convoluted approach wouldn't be necessary if we had negation within program conditions or a condition of "is/is not running".)

Network resource substitutions can use some, but not all, of the substitutions documented in the Wiki, and there may be some (rare) race conditions which you may encounter (specifically, calling a resource using variables from within a program which modifies the value of those same variables). Regarding the "valve status" mentioned above, I've had great results using node status substitutions in network resources.

I open the ISY interface in a web browser and browse to the node itself (e.g. /rest/nodes/ZW003_143) to see the properties exposed in the XML, like so: To confirm, you could also grab one specific property, just add the property to the end of the URL (So it becomes "/rest/nodes/ZW003_143/ST"): <properties> <property id="ST" value="681" formatted="0.681 Watts" uom="73" prec="3"/> </properties> In this case the .raw would give you the "value" field. If your tool or report needs the formatted decimal version of the value but without the " Watts" or "°F" suffix, one option to get this is to have the ISY994 program assign that device property to a variable, then have your report send the variable value instead of sending the device property. Looks like InitialState supports "realtime expressions" so you can have their tool convert the raw value on-the-fly. Given the recurring cost of that service, I'd be more likely to roll my own with InfluxDB+Grafana.

Good point -- they do make compact adapters which go from NEMA-6-20P to Euro-style sockets, then you could plug in a "Schuko" 240VAC rated charger

Never seen a USB charger mated to a NEMA-6-20P, 20A/250V seems like overkill for charging your phone?

If you were feeling really paranoid, had a dual-band PLM, and a nearby 2992-222 (or other dual-band repeating device), you could get away with having the PLM surge-protected or even on a UPS. Assuming 2413S PLMs start showing up in 1Q2023, then maybe paranoia will become less justifiable...

I currently use the "Luminance" value from a Multisensor 6 in this way -- e.g. living room lights come on when the room gets dark, like yesterday's heavy mid-afternoon thunderstorms.