ISY4Me

@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

@bpwwerThank you for resetting me. I think the problem may have been me... I believe initially I "restored" the PG3 Polisy backup... I missed the "Migrate Backup from PG3" button. I did the migrate function and it indicated the ISY had to be manually reconfigured, so I did that. There were numerous system pop-up messages and after all the system messages finished, the paid node servers went from "unmanaged" to "connected". Only the Node from the Polisy Portal remained "unmanaged", but as I said, the licenses have not been moved yet for Portal or the node servers. I tried restarting the node servers and they all gave me the message that there was no valid license... I suspect that means all is OK except for me to actually migrate the license, then the restart should be fine. I think everything is OK at this point but if there is anything else users need to watch out for after the migration, please comment.

@bpwwerUpgraded everything yesterday and PG3x running on 3.1.21 and migrated from Polisy to EISY and Restored Polisy PG3 file into EISY. I am still trying to review if there are any basic problems after the migration, so I am not yet ready to transfer the Portal and NS licenses. I noticed that the PG3x showed the Node Servers in the dashboard, but they were all labeled “unmanaged “. I assume this is normal since the licenses have not been transferred, is that correct?

If you assembled the z-wave dongle yourself, please be aware the full zmatter board does not really fit in the dongle. Please see this post, the final recommendation that came from a ticket with Michel is that the top of the zmatter board has to be removed or snapped off to achieve a proper fit into the connector and easily screwed into place with the screws that were provided. It is possible that is your board isn’t probably seated it might account for your problems.

I have read (somewhere) that the EISY does not have a speaker, so no sounds. if you have a hdmi monitor and keyboard on the EISY you can monitor the update by viewing the log after you login sudo tail -f /var/udx/logs/log If you don’t have a monitor and you are comfortable with it, you can ssh into the EISY and then view the log. When updating is complete the last line in the log will actual state that the update is complete. Another option is… if the update is still in progress, you will see a warning when you start the AC for the EISY, but I have never confirmed that the update is complete if the message is not visible.

First, the Ethernet connector on the EISY is for Ethernet. If your PLM has an RJ-45 on it, you will have to acquire a USB adapter cable… there are multiple threads discussing this issue. There have been improvements in the UD Mobile WiFi Configuration process. UD Mobile is now on version 1.0.14. There were some improvements in version EISY 5.5.4 that also help Wi-Fi Configuration for some users… especially if you hide your SSID in your router. After these latest updates I had no issues using UD Mobile to configure EISY WiFi with an iPhone. Your last question. YES you can hook up an HDMI monitor to the EISY. Add a USB keyboard and mouse and you can directly interface with the EISY… this is covered in one of the EISY Wikis. When it boots. You can login and start a GUI interface with command start.win. There is a lot of info in forums… keep on reading.

Working with @Michel Kohanimand @Javi changes/improvements have been added to the UD Mobile Wifi configuration process and some changes to how the credentials are set during the UD Mobile WIFI Configuration process. If you were having similar issues, assure UD Mobile is on 1.0.14 and EISY is on 5.5.4. With these improvements I was able to setup the WiFI.

I went through something similar. It sounds like you already have a license for that unit, which was one of my problems Did you go to Manage Modules menu on the EISY Help Menu in the AC? There is another action there that has to be completed for the approval to work. Do that, then go back to Portal Approval box in Configuration > Portals

This should not fail, however it is possible the OS will not route network requests to a network without internet. This works with Chrome on a Mac but I have not tried Safari/Firefox. I have tried the manual method multiple times with FireFox on macOS. I can see the eisy.setup AP and join it with no issues. I then go to FireFox and issue the setup URL and it executes and responds with "eisy.home AP setup". I don't know if that response indicates a success or not. Within a few minutes of that message on the screen, the eisy.setup AP shuts down and if I plug the ethernet back in and wait a few minutes the EISY with re-connect with the Portal. If I then try the EISY on WiFi... disconnect the ethernet cable, wait a few minutes and restart the launcher... the EISY will not show in the launcher. To me this indicates the EISY did not connect to the SSID WiFi successfully when the ethernet cable was disconnected. Is this an appropriate way to test?