ISY4Me

@joembz Thank you for the inputs… I guess at this point, I am simply happy that the UD Mobile SmartAdd method worked with adding the ZEN17 to the EISY with ZMatter. I had tried with and without s2 security on the EISY and some of the basic nodes appeared, but I struggled with not being able to get the binary sensor to show with Parameter 2/3 setting 10. The odd thing in all of history in using the ZEN17 with Polisy and Zooz USB, I never had any issues with nodes installing (including the binary sensor) and there was no security mode inclusion on the Polisy. I tried numerous migrations from Polisy to EISY on every EISY firmware up to and including 5.6.0 and only rarely saw the binary sensor node show, but it would disappear after sync with interview. Attempts to include with security on the EISY with ZMatter worked, but the sensor nodes still did not load as expected. My EISY has been on the shelf waiting for some new insight. @Chris Jahnindicated he would continue to examine the issues I had with including the ZEN17 using the AC, but there was no timeline. Using the UD Mobile SmartAdd was the first positive result since my first migration and for that I am thankful. It was your post that encouraged me to try it, so thanks for documenting your work.

I have much empathy for what @joembz has gone through as I have had the same frustration for 3 months on getting the ZEN17 to include properly to activate the sensor node and simply install correctly. My main limitation was getting Parameter 2 & 3 setup with Setting 10 and every time I would attempt inclusion I would get alarm node and basic nodes, but never the binary sensor nodes... alarm nodes do not even apply to simple parameter 2/3 setting 10 configuration. I had been doing all inclusions and exclusions with the Java AC interface and migration tools and just as @joembz had tried endless attempts so did I and nothing worked. Over the last 3 months, I had been working with @Chris Jahnand tried all of his suggestions and there were a few times I successfully achieved getting the binary sensor node to show, but the node was not persistent and with various actions they would disappear. Today, I tried the UD Mobile SmartAdd method and the very first time all the nodes for the Parameter 2/3 setting 10 configuration showed immediately and in the correct node/subnode. This was a first. Why the standard exclude/include methods failed most of the time is still a mystery. At least the UD Mobile method with scanning the QR code as shown a very positive result.

Same for me. If they announce (implied) they are going to have all pre-orders shipped by 4/13 then they need to follow through or send another email with more accurate predictions.

@Goose66 Thank you for your original advice. It took a little time to understand the direct communication with the API, but in the end I have the curl commands working and a version installed as a network resource. Sadly we are having too many power outages and we just had another and the commands operated as designed and the fan lights that misbehave with an outage return to normal now with the program that addresses this issue.

This issue is closed. I just arrived home and I have a 3rd tool to detect faults at the main. There was apparently a power glitch. My apologies, I should have waited to post until I saw the Main Fault monitor.

The time stamps are too close to tell, but my only reference is my v5.4.5 Polisy has never ever rebooted on its own.

I received a notification in UD Mobile that the Portal went offline. At the same time the Polisy rebooted. Why? Since all the changes to UD Mobile I have not changed any settings, so I am curious as to why the Portal triggered the reboot!

@residualimages Thank you again. You have a way of making all of this seem so logical. You have made a great impact on my baseline understanding of converting a working curl command to a working ISY Network Resource. At this point I am fully functional. With the help I have received from you, the Bond API documentation and all the trial and error learning, I hope that I can deal with any needs that arise going forward.

@residualimages Thank you for your help here and also over on the Bond Forum. I was able to find your original discussion in the Bond Forum and that provided a little more information… every little bit helps. So, if I want to extend this method to do an action to TurnLightOff, do I use an "_m": x format or use the standard curl format -X PUT -d "{}" for the body command in ISY Network:Resources? I tried a few variants and all failed.

@residualimagesThank you for the response, I had a hard time finding any guidance on setting up this resource. I went through the process of understanding the exact terminal command I needed to issue to accomplish my task. In the end, the following is what proved to work... this was all based on the Bond Bridge API Documentation. My goal was to change the state of the light in the Bond Bridge to On... curl -H "BOND-Token: BondTokenHere" -i http://BondBridgeIPHere/v2/devices/DeviceIDHere/state -X PATCH -d "{\"light\": 1}" Based on what you did in your example I tried to modify what worked in the terminal command above. This is what I came up with... and it did not work(also failed with the escape characters used -X PATCH -d "{\"light\": 1}"). Your body command is different than mine, but I only copied what worked from the terminal command. I don't know what the "_m": 4 is that you used. Where did you learn that this was what was the format required? I went back and tried another variation based on what you did... and your format worked just fine. I am happy that there is a working solution, but being a nerd, I really strive to understand why a particular format is used. Any information you can provide on how you learned to do what you did will be greatly appreciated. Thank you

@Goose66 I am making progress understanding the use of the Curl command for the Local API. But I am finding very little documentation on how to configure such a request in the UD Network Resources. Is it possible you can PM me an import file for resources that demonstrates the setup for executing a CURL command? I have looked at the UD Network Wiki and they seem to dwell on the popular things and not the non-standard implementations as this would be. Any help will be appreciated.

@Goose66 Thank you for the explanation. I agree that my situation is probably unique… having a light like this always power on with light on does seem odd. I will try your suggestion… I have not worked with network resources, but it will be a good excuse to learn.

I have two ceiling fans that always power up with lights on after a power outage. I have written some programs to detect this power on state and then turn off the lights, but they don't work. After further digging, I have determined that the light will not programmatically turn off because the sync state is off. When I go to the Bond App and sync the light state, then let the Post Power Outage program run, the light turns off. If we can fix/correct the sync state with the Bond iOS App, is it possible to that we can have the option to add this ability to the Node Server so we can take these odd situations and sync that feature via changing a node state in ISY?

When I was going through this today, I had multiple power downs and multiple reboots and while I can't be exact there was always some time between re-powering and rebooting, but PG3x login always failed. This time I had ~30 minutes power down, powered back up and waited as you suggested and I was able to login to PG3. What a mystery that this time it worked? Thank you

I thought it was time to try to start fresh again... factory reset the ZMatter and EISY and fresh package updates on the EISY. Restored the migration backup file and cleaned it up what came in (that all looked normal), then went to look at PG3x and I can't log in without getting the 401 Unauthorized message. I have tried two different computers and both Safari and FireFox browsers with cleared history and no matter which I get the 401 message. I have no trouble connecting to the PG3x login screen, I then log in to the Portal and then admin/admin for the PG3x and hit login and that is where the failed login appears. I had this problem some time ago, but Firefox seemed to be the solution, now it is failing too... I just checked I am on 5.5.9_1 and PG3X is at 3.1.24_4. I am not sure where to go with this.

In monitoring much of the forum activity during the first month or two after its release I remember a number of posts regarding the ZEN34. I don’t know how helpful it will be, but I suggest you search the forum on “ZEN34” (magnifying glass toward the top of the forum home window) and see if you can extract anything helpful. The one other suggestion is related to my experience with the Zooz small format water sensor. It too is a battery device and I had issues getting it to include all the nodes properly. What I discovered by trial and error is that tapping the wake up sequence just once was not enough to get it to include the device properly. What I did was tap the wake up sequence, start the include and then tap the wake up sequence every 10 seconds until they include process was finished. It also seemed to help to have the EISY within a short distance… in my case they were about 8’ apart.

Having had similar issues with a different Zooz device, I found a solution was to factory reset device before including. So first exclude it, then factory reset and then include.

I run the desktop every time I work on any EISY issue and I have never seen that behavior. Hopefully, someone has and can assist.

When I started using the desktop, I did not have to configure anything. It recognized my HDMI monitor, keyboard and mouse… that was visible during the boot display text. Just to be sure… you are typing “start.win” with no spaces?

I am not completely sure if I am addressing your question, but I have found that the HDMI monitor has to be turned on before the EISY is powered up to avoid getting that message. As the unit boots you will see all the start up actions and will end with a login: prompt. From there you type start.win and the desktop should start within a few seconds.

In addition to @philgood comments, there have been multiple discussions about how to physically get everything into the enclosure. The simple answer is, the top half of the ZMatter board has to be snapped off. Then the board will fit in the bottom and attached with the included screws in the package. That leaves room in the top half of the enclosure for the antenna mounts and wires. See the photo in the linked discussion.

Thanks, I saw the thermostat on eBay. I will be curious about responsiveness/lag, features/control points that you feel are missing, etc.

Please keep us up-to-date on how it goes with the Thermostat. I had been wanting to switch over to a local controlled z-wave thermostat. I tired the Honeywell T6 Pro and I was disappointed, so I am always trying to learn more about other models.

How did you verify that the parameter 64 was set correctly?

Fresh migration configuration for EISY just finished and that went well. Restored the Polisy PG3 Backup into EISY PG3x, but I had to power cycle the EISY in order to be able to log into PG3x. Restore PG3x from PG3 went fine. My ISY configuration is mainly z-wave (lighting, motion, relays) and node servers. I went through all the devices this morning and here are what I saw as still residual issues. AeoTec MultSensor 6 devices are still showing the Centigrade Temperature. In Polisy they were all showing Fahrenheit which is what the programming is configured on. Manually setting/changing the parameter 64 did NOT change the displayed temperature to Fahrenheit. Zooz ZEN17 is used as a dry contact sense on S1-C. There are three nodes installed (same as existed before on Polisy)... Monitor, Monitor S1 and Monitor S2. For the S1-C Dry Contact, when it was contacted or shorted it would register as "ON" in the S1 Sensor sub-node on the Polisy. On the EISY there is a only the S1 Binary Switch and S1 - V1 Alarm. When manually evaluating the dry contact, I could not get a valid dry contact response on the V1 Alarm on EISY 5.5.5