ISY4Me

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?

The log files from the original work to setup WiFi using UD Mobile are in the ticket we were using.

@Javi Should the manual WiFi configuration remove any issues related to the OS/device that the user uses for normal UD Mobile connection? As an iOS user, I have continued to fail getting WiFi mode working. I had comments about trying manual WiFi configuration using Firefox on macOS in my recent ticket response, but that appeared to fail too. Is there a command line method to set up WiFi in a direct EISY connection (using hdmi monitor and usb keyboard)?

What is the manufacturer of the WiFi router you are connecting to. Just curious if it is also an Apple or something else.

@zorax2 I just wanted to let you know that my issues continue and I am working with @Javivia a ticket to try to get some insight. My house is almost pure Apple and UD Mobile is running on an iPhone X on iOS 16.2… there have been some questions in my mind if this issue is iOS or other… the point in question is that my WiFi AP is an Apple Time Capsule 2Gb. All my WiFi APs in the house are Apple Extremes or Apple Time Capsules. I had a very old (1990s) Belkin so I ran a test with the iPhone connecting to the Belkin and then the Belkin connecting with the network. The Belkin was so slow to set up, age has not treated it well, but I was successful in using UD Mobile on the iPhone to set up the EISY AP. However, I removed the Belkin since it was so wacky and to get all back to normal I had to reset the EISY network and that killed the EISY AP. However, that one result was encouraging, but I don’t have a quality WiFi Router that is not Apple to permanently try a different setup. Trying UD Mobile WiFi Config on an Android is also not an option. So, is iOS on the iPhone part of the issue? Is the problem related to the router it connects through? An interesting problem to deconstruct. @Javiis starting with analyzing what the iPhone is doing and I am giving him what he needs (log files), but that work is just starting.

Thanks for the reminder… I was aware of that, but since I have had issues with previous migration tries and still fight issues with configuring WiFI on the EISY (I am already working with UD on this) I was hesitant to change a system that is fully working.

I have yet to update my Polisy to 5.5.3… it is still on 5.4.5. So, to clarify this is the migration click on the Polisy to create the migration backup file that will be used to restore on the EISY?

@asbrili just saw your message regarding your migration results after a help session with the UDI. Do you understand what was different from the recommended migration steps that you initially performed and what was different in the help session? Another way to ask the question… do you think updates to the recommended migration steps will result from your help session and that we should wait?

@Javi I looked at this link and there is one statement in that documentation that bothers me. There is a statement... First put eisy in WiFi configuration mode by double pressing the front power button. Then connect to eisy's WiFi network, the password is the text under eisy's QR Code. Finally send the following command in a browser http://172.26.18.3:60018/setwifi/<SSID>/<Passphrase> where SSID is your home WiFi SSID and Passphrase is your home WiFi password. That statement in bold says the EISY password is under the EISY's QR code. When I look at the back of my unit, there is no text under the QR code. So how does one know it?

I don't know which step of the attempts to connect with Wifi that the connection to the portal was broken. I don't think it fair to submit a ticket without me providing some suggestions. Let me try to repeat the some of the work and see if I can define when the connection broke. With the ethernet disconnected during most of the wifi configuration I don't think it was in that work... I was sporadically checking the portal during most of that work and I had not lost it. Let me see if I can determine when... but this is the 2nd day that this happened. Later today, I went through and manually setup the EISY - UD Mobile > System... I manually setup the portal and tested, manually setup the local using the finder (and it came up eisy.local, manually added the wifi and turned off always use local connection. All the connection tests worked with ethernet plugged in... I did not try the tests with the ethernet unplugged. Let me look at that and also examine the manual way to add credentials. The SSID and password are widely used in my network and they are always copied and pasted from my password tool and they have not changed. The only odd character in my SSID is a hyphen, the WiFI password is only upper case characters and numbers, but it is a long string. Is there a character limit to the password length? I am surprised that this is becoming such a project. I tend to have measurable patience for this kind of thing, so I will keep at it.