TRI0N

Ah! That explains it... Great! Now that solves the 2 x Press... Works like a charm. That isn't so bad in my opinion for some needs. Like the Hue recess shower lights, while I have dressing mirror, wash area, etc on Z-wave. I can set 3, 4, 5, to scene colors. Simply find the color arrangement you want and then query the light for the light settings for each light and then make program to assign to the scene button taps. Otherwise I still agree we need a out of Z-Wave easy toggle for other devices that don't use the scene features. TRI0N

What I ended up doing for anything I needed for a toggle that wasn't a Z-Wave for it turned off on one push was make a program that just simply checks if Scene Button # On (it does send this and it does trigger even when it's constantly reporting "On" in Query) and to see if, for example, Govee Under Cabinet Light Strips status is On, Then set Govee Lights to Off, Else set Govee Lights to On. Every time you press the button once it's just sending a On status. TRI0N

Button 2 is NOT the Primary Binary Switch. yes its the small middle button to the right under the big Binary Switch also known as Scene Button 5. See above image map I created. TRI0N

I just provided an example of it working in a scene without programs. It requires that all devices at this time being Z-Wave. It won't work with Z-Wave to Kasa or Z-Wave to Hue... TRI0N

Also do you know how to set the parameter's of a z-wave device? If not, you would right click the one that is Binary Switch > Z-Wave Menu > Set Configuration Parameter I provided a link to the Zooz ZEN32 Advanced Features link above that will explain what parameters are available. You can select a Parameter number then click Query to see what the current setting is for that parameter. TRI0N

Actually you use the Associations as far as I know will only work with other Z-Wave Devices as a Scene Controller. With a Z-Wave Relay that I use for different lights that have no switches, for example, my kitchen pendent lights are wired to a Z-Wave Relay so I can assign it to a scene. I would add the Relay and the Button as responders and then add the corresponding Basic Assoc Only as a controller in a scene. Then I would click the Scene Object Controller "ZY 002 Basic Assoc Only 6" and we need to set the ZY 005 On-Off Power Switch default link type to Z-Wave Basic MC. Now ZY 005 On-Off Power Switch is actually that Z-Wave Relay I was talking about. That is the only way that I'm aware of that you can actually make the button work as a Scene. At this time it does NOT work using other types of devices that I'm aware of. This needing programs to respond to Double Push, Three Push, Four Push and 5 Push options... I can make one push turn on lets say a HUE Recess Light. I would then program it so that two pushes turns it off (right now we have to do 3, the double push option is missing and I'm sure it will be added by UD soon). TRI0N

What are you looking to automate? How much are you looking to do? You might not even need a HUB or anything super special to perform things like smart light switches to work with your Alexa or Google. HUBs like UD are best if you have many different types of hardware you are using like Insteon and Z-Wave where you can do all that in one place. But if you're looking to do just a few lights switches, outlets or some smart bulbs I'd stick to one brand like Kasa TP-Link. This is just for basic needs. It depends on how deep into home automation and needs you desire. TRI0N

Yes did UDAC first then used the link inside UDAC Node Servers Menu for PG3x ... Then tried the reboot from UDAC then tried 6 presses to shutdown but the light never turned red after 2 minutes so I pulled the cord let it set for 30 seconds and plugged it back in. Everything works so far. But what's with the the system not performing with just a Reboot? I guess I'll install a Kasa Power Cube, so I don't have to climb up into the security closet in the attic to cycle power. Will run this a few days before updating the other eisy from 5.5.4 that I was keeping at that version till things smoothed out. TRI0N

Uh... After doing the update once. I got another notifications that updates were ready and to do the Package Updates again.. So I did... Now PG3x won't accept my password. TRI0N

Well that just makes even more puzzling why mongo-c-driver crashed eisy with PG3x if that package isn't even used. Simply downgrading mongo-c-driver on the eisy did indeed fix my issue with multiple node-servers. Everything went back online the moment I did. Didn't even need to reboot. But I did preform a reboot just to see what would happen and nothing. Everything was back in working condition. TRI0N

This also fixed the eisy 5.5.5 and PG3x issue on my home system. However I'm a little confused why eisy and PG3x even needed MongoDB if it was no longer used after PG2? TRI0N

Maybe it was but was missing a yes/no prompt bypass. I did the Upgrade Packages yesterday from isy-5.5.5_1 to is-5.5.5_2 and it hung for hours till I decided to reboot and then go through logs to confirm the mongo-c-driver problem. Made a snapshot of the eisy for backup and preformed the -f Downgrade on mongo-c-driver and everything came back online. Not sure if UD even uses the MongoDB but, that did indeed fix it. Maybe something with the credentials changed if MongoDB is used. Which makes me wonder if I should hook a monitor up to the eisy just to see if a prompt appears there in the future when things hang. TRI0N

Depending on the device such as your "MBR Entrance" it can be setup to be on/off with indicator light working. But it really depends on what the device is in the scene right now. It has to be another z-wave device to get the on/off working correctly which works great for my relay's but not so helpful for my HUE Lights in Shower. Those have to use the 2 tap off. It looks like it imported your programs just fine if they work. I wouldn't change a thing or save changes to those ZEN32 programs. It might have imported the double tap instructions but it is not showing it as an option. So you might not be able to reset that if you goof. I also believe that is the default behavior for the scene buttons based on their internal programing parameters. But you can make them become single push toggles for other Z-Wave products. Also here is a good link to parameter settings. https://www.support.getzooz.com/kb/article/608-zen32-scene-controller-advanced-settings/ For changing lights, click behaviors. For non-toggle I just keep the light on for the multi-press scene needs. TRI0N

What I was able to figure out before 5.5.5 and getting my first Zen32 for the eisy on my mission to eliminate Insteon from my network. I whipped this image up to help people understand the layout of the buttons and scene associations. Hope this helps understand the layout and the buttons assignments. TRI0N

After finally getting 5.5.5 back into working condition I noticed they added on options for the Zooz ZEN32 Scene Controller. However it appears to be missing Double Press (On) or 2 x Press (On) [whichever way the setting is being identified] option for the scene buttons. JUST a FYI TRI0N

What did your power supply look like? Did it come with a Choice of US or European 2 Prong attachments?

Yeah that's REAL important. Should have gone a step further and explain that both Linux and FreeBSD are just a UNIX Flavor because that would no doubt fix all these problems clients are having. I've been doing it wrong, all along... TRI0N

DO AT YOUR OWN RISK Downgrade -f sudo pkg upgrade -f mongo-c-driver After I did several safety measure such as an image snap shot of my eisy to ISO saved to my RedHat Gateway and like I said I also made sure I had the latest isy-5.5.5_2 that caused problems on it's own just doing that. I then performed this step mentioned by shbatm and it did fix EVERYTHING. eisy isy-5.5.5_2 pg3x-3.1.22_3 udx-3.3.6 Keep in mind that Linux command line is not for beginners. TRI0N

Mongo is the problem. With all the Polisys, eisy, PG3, PG3x. I would wait for UD to release a fix. It could make things worse, could make things better. I did some carful backup routines and other stuff before looking at Mongo. Such as making sure I had the latest isy-5.5.5_2 pkg when I had isy-5.5.5_1 installed. That itself caused my eisy to freeze for hours until I issued a reboot and then looked at Mongo. TRI0N

Don't update... I just did a Update Packages in UDAC 2 hours ago and now it's in limbo. Was already on the 5.5.5 boat with the isy-5.5.5_1 and did the Update Package in hopes to get this so called "minor" release isy-5.5.5_2 and it's stuck in limbo ever since. I have no idea if it even updated to isy-5.5.5_2 and just letting it do it's thing (whatever that is) in hopes it fixes itself. I don't want shell in or anything. I'll give it another hour and I'm pulling it's plug. Then I'm going to re-evaluate this company. Sure hope the Super Bowl isn't more important than a reliable product. TRI0N

Wishful thinking to check for a new update after hearing about some users are using a "minor release" isy-5.5.5_2 while I have isy-5.5.5_1, so I did the Update Packages in the UDAC. Oh Boy! Now I'm getting this: I did the update 2 hours ago... PG3x is reporting: No IoX was automatically discovered on your local network. Please configure it in the IoX menu to proceed. Oh Boy! TRI0N

Also, not to push anyone to update right now to 5.5.5 but more Z-Wave functionality was added. You should be able to send parameters to that sensor where you can set the sensor "trigger Interval" from 15 (default) to 255 seconds till it will trigger an event. In a lot of cases this is the BEST way to go on any Battery Operated Sensor so that it will increase battery life. Telling eisy to look if the motion sensor every 5 minutes does not stop the internal motion sensors setting to let say every 15 seconds where you could set that 1-2 minutes internally to save battery consumption. I believe the Perimeter for that is #5 with 1 byte. You have a Maximum with that Zooz Multi Model of 4.25 Minutes. I do set some of my Zooz ZSE18. For example my Garage. If the garage light is on and motion is detected it will reset the counter for 30 minutes but with the "trigger interval" set to 15 minutes (900 seconds). That means the sensor will not check for motion again till 15 minutes has elapsed then this will trigger the reset to the 30 minutes eisy program. This in the long run will save battery life. The Zooz ZSE18 has a Triger Interval range from 3 to 65535 seconds (@ 18.2 hours). With the need to have the type you are using or monitor temp/humidity, light and motion you might want to toy your interval a little to help reduce activity that isn't needed. Cheers, TRI0N

If this is simply a library problem that needs to be removed, I'm not sure why it's not released yet? That just tells me there is more to the problem than a simple library needing removal. No Post Update Either. Remembering why I wanted to automate my property becomes more and more relevant as I walk my property to turn on and off locations that were automated, twice daily for the last week after swapping out all the Insteon Devices to end up completely unfunctional. I'm hiding how happy I am... TRI0N

Polly is PG3x Version 3.1.22 5.5.5 and 3.1.22 are not happy though. Going to the latest version right now might not be the best idea. I can only confirm that 3.1.22 worked flawlessly for 24 hours using eisy 5.5.4. But when I updated packages to 5.5.5 just @ 24hr later, all hell broke lose. It is not happy hosting multiply node servers. I currently have 5 and it really did a number on my daily automations not working and devices not communicating properly. UPDATE: From my understanding you shouldn't be using 3.1.22. It's for eisy only PG3x and Polisy is PG3. So I have no idea what the latest version of PG3 is. I jumped from 944 to eisy and skipped the Polisy. TRI0N

Not sure how that is even possible really. Both ports HTTP (80) and HTTPS (443) run from the main HTTP Server. You literally can't have SSL without a non-SSL server entity for a working web server. Any sever that enforces HTTPS is actually using .htaccess and 301 Redirects to the HTTPS version either by page headers or DNS Redirect. So why the secure site loads before the non-secure site is mind boggling to me. TRI0N