jkraus Posted March 1 Posted March 1 I don't have any Matter devices, so does that mean I do not need to do a Zwave backup prior to upgrading? Quote
Techman Posted March 1 Posted March 1 @jkraus If you have any zwave, zigbee or matter devices installed and you're using the UD Zwave/matter dongle then you should do a Zwave backup prior to updating your firmware. It's your insurance policy. Quote
JohnC Posted Thursday at 08:27 AM Posted Thursday at 08:27 AM I had an issue of not being able to access the Eisy after the 5.9.1 upgrade. Accessing the terminal mode with HDMI connect and using ifconfig command showed that Eisy was not producing IPv4 address after the upgrade. A good-enough fix of this problem was to always reboot the router AFTER rebooting the Eisy. I might put my Eisy in a UPS power supply so the power never goes out and never has to rebboot. Quote
GHenry Posted Thursday at 02:43 PM Posted Thursday at 02:43 PM 6 hours ago, JohnC said: using ifconfig command showed that Eisy was not producing IPv4 address after the upgrade You'll eventually have to reboot. Would a fixed LAN address assignment in the router solve the problem? Quote
Techman Posted Thursday at 02:56 PM Posted Thursday at 02:56 PM You can't use a static IP address. You need DHCP enabled in the router, and you can then use a reserved IP address for the EISY in the router. Quote
Konamob Posted Sunday at 02:35 PM Posted Sunday at 02:35 PM Hi everyone - wondering the reason I don't see the add Matter device via the UD mobile app on iOS when clicking the "+" button on the summary page. Have the latest version of the eISY software, ZMatter dongle, Matter, Zigbee and Z-Wave enabled in the admin console and iOS app version 1.2.2. Appreciate any assistance. Thank you. Quote
737simguy Posted Sunday at 02:45 PM Posted Sunday at 02:45 PM 9 minutes ago, Konamob said: Hi everyone - wondering the reason I don't see the add Matter device via the UD mobile app on iOS when clicking the "+" button on the summary page. Have the latest version of the eISY software, ZMatter dongle, Matter, Zigbee and Z-Wave enabled in the admin console and iOS app version 1.2.2. Appreciate any assistance. Thank you. The only place I have found it is on the Settings page. Quote
Guy Lavoie Posted Monday at 04:54 PM Author Posted Monday at 04:54 PM Update: I just went ahead and updated my production eisy (I had only updated my test Polisy up until now). Then I tried adding my Cync wifi bulb to it. Still not working, but got farther. I first deleted the bulb from the google home mini (as told by the Matter adding function in UD Mobile). It detected the bulb and prompted me for my wifi ssid and password. I entered those, and the screen was showing "adding Matter device" with an animated radio wave pattern, but then ended in an error saying "Could not get ZMatter RX Requested ISY not online. 500". Interesting that it mentioned "ZMatter" since this is a wifi bulb. I also don't have a ZMatter dongle on my eisy (It's the board version I have, installed in my test Polisy). Quote
Guy Lavoie Posted Monday at 05:56 PM Author Posted Monday at 05:56 PM (edited) Hear ye hear ye! I managed to configure my Matter Cync bulb!! (start 15 minutes of fame) 🤩 Following my post above, I thought I'd look into the eisy upgrade I just did, looking at version numbers, etc. This is because the Matter addition process had gotten further than on my test Polisy before ending in the error I mentioned. The sysconfig.txt file showed me that I had IoX version 5.9.1_12. So I checked the Polisy, which I had upgraded just after the release announcement had come out in February. It had 5.9.1_7. So UDI has been quietly updating it. So back to the Polisy, since it does have the ZMatter board in it. I click on "Update Packages", and nothing updates, being on 5.9.1 already. Ok...so I ssh into it and run "sudo pkg install -f isy". That did identify that there was an update to install. Updated and rebooted it. Did an ssh back into it to view the sysconfig.txt file and...(funny stuff) it shows 5.9.1_13! Did UDI just issue an update in the last couple of hours? I factory reset my Cync bulb and fire up UD Mobile, and try the add. Same process, entering my wifi ssid and password to configure the bulb. The admin console also pops up a message saying it's adding a Matter device. Crossed fingers, toes, anything I could cross...and it successfully added the bulb! Interesting that it appears as a ZM device, even though it's wifi. Next I'll try the Nanoleaf Thread bulb (in case the dongle is really able to talk to it directly). Just before posting this, I also ran the pkginstall command on my eisy, and it did upgrade to 5.9.1_13. So I'll be testing that too. Maybe the ZMatter dongle is really needed, even for wifi. Other notes: - Looks like they fixed the ssh access, so "ssh admin@eisy.local" works again - Matter device addition really seems to be a bluetooth thing, which would explain why it's done only in UD Mobile. - The Cync bulb only shows up as an on/off device, even though it's a color bulb. Edited Monday at 06:16 PM by Guy Lavoie Quote
Guy Lavoie Posted Monday at 07:29 PM Author Posted Monday at 07:29 PM A few more notes: - Following the eisy upgrade from 5.9.1_12 to 5.9.1_13, I was able to add the bulb to that controller too. So make sure you have 5.9.1_13 before trying anything else. So Matter over wifi works without needing the ZMatter dongle, as it should (though the default device name will start with ZM...). Deleting the bulb from the Polisy wasn't enough to make it configurable, I really needed to factory reset the bulb itself. So it looks like Matter devices can only belong to one main controller, and then shared by that device. So choose your main controller carefully if you have more than one that can add Matter devices. - I tried adding the Thread bulb to the Polisy (because it has the dongle) but that didn't work. In fairness, the release announcement does say that a border router is needed, at least at this time. - When adding a Matter device, it does take a bit of time to first find the device after scanning the QR code, and then you will see that your controller does an "interview" process in a pop up window of the admin console. - It would be handy to allow the UD Mobile app to also accept a pairing code instead of just the QR code. Some devices like the Hue hub only offer a pairing code for doing the share process. 2 Quote
oberkc Posted yesterday at 01:24 AM Posted yesterday at 01:24 AM Once added to the ISY, can one share a matter device to google or Alexa or apple home? 8 hours ago, Guy Lavoie said: I first deleted the bulb from the google home mini (as told by the Matter adding function in UD Mobile). I have not seen this instruction. Is this unique to the new (quietly released) software version? Quote
jkraus Posted yesterday at 01:29 AM Posted yesterday at 01:29 AM OK, I know this is kind of minor, but anoying to me. I upgraded my Poliy to 5.9.1 and had to get the new IoX launcher start.jnlp, but this one does NOT show a nice icon nor can I put it in my taskbar for easy launching. Am I doing soemthing wrong or is this just the way the new upgreded launcher is? Quote
Guy Lavoie Posted yesterday at 01:31 AM Author Posted yesterday at 01:31 AM 2 minutes ago, oberkc said: Once added to the ISY, can one share a matter device to google or Alexa or apple home? I have not seen this instruction. Is this unique to the new (quietly released) software version? The ISY doesn't seem to have a Matter sharing function, yet. That's why you need to choose your root device wisely. I still need to test some other things, one of which is to encode the Hue hub's Matter sharing pin code into a QR code, and try adding it to the eisy using UD Mobile. I'm looking into a QR code encoding utility for that. I don't have a border router yet (looking into getting a used 4th gen. Alexa Echo for this), so the Thread bulb will have to wait. 2 minutes ago, jkraus said: OK, I know this is kind of minor, but anoying to me. I upgraded my Poliy to 5.9.1 and had to get the new IoX launcher start.jnlp, but this one does NOT show a nice icon nor can I put it in my taskbar for easy launching. Am I doing soemthing wrong or is this just the way the new upgreded launcher is? Not sure I understand your question. The Iox launcher hasn't changed. Still the same as it has been with 5.8.4. Quote
jkraus Posted yesterday at 01:36 AM Posted yesterday at 01:36 AM nevermind, I think I did not clear all of my java caches, working now! 1 Quote
oberkc Posted 20 hours ago Posted 20 hours ago 9 hours ago, Guy Lavoie said: The ISY doesn't seem to have a Matter sharing function, yet. That is a little disappointing. I assume that matter devices added to ISY can be shared with other hubs through the portal, at least. Ultimately, I was (am) hoping that the ISY will become a matter "bridge", where it would expose all linked devices (matter or otherwise) to other hubs via the matter standard or be able to incorporate devices shared by other hubs via the matter standard. I have the same hope that the Echos and Nest hubs also become matter bridges. I assume that the _13 version will soon be published. I will wait. I don't do enough of the ssh stuff to be fluent. I have to look up how to do this each time. Quote
Guy Lavoie Posted 18 hours ago Author Posted 18 hours ago 2 hours ago, oberkc said: That is a little disappointing. I assume that matter devices added to ISY can be shared with other hubs through the portal, at least. Ultimately, I was (am) hoping that the ISY will become a matter "bridge", where it would expose all linked devices (matter or otherwise) to other hubs via the matter standard or be able to incorporate devices shared by other hubs via the matter standard. I have the same hope that the Echos and Nest hubs also become matter bridges. I assume that the _13 version will soon be published. I will wait. I don't do enough of the ssh stuff to be fluent. I have to look up how to do this each time. I'm sure most of that will become clear over time. This is still beta. Just getting the communications and device linking working reliably is certainly the most important first step. UDI is arriving at that. Most of us here already have working systems so going to an all-matter setup would be the exception. I want to enjoy learning and understanding the topology early on. I'm in no rush to set up anything in particular at this point. I'm quite confident that the eisy will indeed be able to make all device types work together. We already see it with scenes. Insteon is the "mother tongue" it's designed around, but you can put zwave, zigbee, Matter devices in scenes and they work. I did test the Matter bulb as a scene responder yesterday, worked fine. For other things, programs can be used. It will be interesting to see if as you say, other devices can be mapped to a Matter equivalent directly. If not, as scenes or through programs. Quote
oberkc Posted 8 hours ago Posted 8 hours ago 9 hours ago, Guy Lavoie said: Most of us here already have working systems so going to an all-matter setup would be the exception. I want to enjoy learning and understanding the topology early on. I'm in no rush to set up anything in particular at this point. I am certainly in that boat as well. I have most of what I want and don't need matter to add anything that is missing. I would just prefer local control for my voice assistants (at least when I am using the touch screens of the assistants) and access to a couple of items on google and Alexa that don't integrate with ISY. Regardless, my system is quite useful. Quote
marksidell Posted 6 hours ago Posted 6 hours ago (edited) This release bricked my eisy. Oh well. Now what? Update: I am able to ssh into the eisy. Any way to diagnose what's wrong? Edited 6 hours ago by marksidell Quote
marksidell Posted 6 hours ago Posted 6 hours ago I was able to ssh into the dead eisy. This looks bad: [admin@eisy /var/log]$ tail messages Mar 11 18:15:33 eisy kernel: pid 64484 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 11 18:15:54 eisy kernel: pid 65354 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 11 18:16:14 eisy kernel: pid 66177 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 11 18:16:35 eisy kernel: pid 66928 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 11 18:16:56 eisy kernel: pid 67800 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 11 18:17:17 eisy kernel: pid 68624 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 11 18:17:38 eisy kernel: pid 69385 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 11 18:17:58 eisy kernel: pid 70248 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 11 18:18:19 eisy kernel: pid 71071 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 11 18:18:40 eisy kernel: pid 71828 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Quote
grossmd Posted 6 hours ago Posted 6 hours ago Apologies if this is a stupid question but can’t you just factory reset it and load a back up? Quote
Guy Lavoie Posted 5 hours ago Author Posted 5 hours ago If you can ssh into it, you might try this (though it's not UDI's preferred official approach...your judgement call). It worked for me. Scroll down to tokenworker's post, describing the pkg install commands in bold. Please read the whole thread first. Quote
marksidell Posted 4 hours ago Posted 4 hours ago Michel got back to me (very quickly!) with a fix: sudo pkg install -f udx sudo service udx restart (wait two minutes) sudo service isy status Spouse is happy again Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.