oskrypuch

Just trying to get all my ducks in a row. Yes, have read through all the wiki materials, more than once for other hardware migrations, this one is a bit more complicated. This site has a large mature system in place, mainly Insteon, currently running a Polisy with the original ZWave dongle. I started up with ZWave during the time of troubles for Insteon. I have a ZMatter card sitting on the shelf, not in use yet. The Polisy in question is running 5.4.x and would need a OS update to move to 5.8.x. I have performed this on another Polisy I have, but that was a small install with no ZWave, so simple to do with a flash followed by a simple restore. That is principally why this system is "stuck" at 5.4.x. If I expend some time moving the ZWave stuff over, would prefer to move it to up to date hardware. As I understand it, the old ZWave dongle does not have an easy backup route, and it seems a bit up in the air if I can just move it physically to the Eisy, and make it all work. And I would prefer to get the ZMatter card in place. The ZWave part of this is what is holding things up. Ideally I would like to set up the new Eisy/ZMatter, ensure it all works, and then step-wise switch over, with the ability to go back if I absolutely had to. I understand that I would have to remove/reinstall every ZWave device, I would plan to just move one over and play with the new equipment, as a toe test. The other huge question, is what you do with the (serial) PLM replace/migrate. I do have extra PLMs available, and I could use one completely independently of the current in use PLM. I have replaced PLMs before, but that is a bit of pain running around refreshing all the wireless modules. I am familiar with the physical connectivity issue, serial/USB/adapters. I would prefer to restore the Insteon devices and code to the Eisy, and then unplug the old Polisy PLM, and plug it into the Eisy. I understand that should work, following the instructions in the wiki. That would allow be to reverse the steps, and go back to the Polisy if I had to. Then I would have to one by one bring the ZWave modules in, and of course edit all the code because the module numbers won't match up, etc. Very messy. That would leave my Polisy/ZWave dongle undisturbed, and if things blew up or didn't work, I could in the short term still move back to keep the system up. The portal and UD mobile is the other headache. I do have a lot of defined widgets for my Polisy set up, I fear that I will have to go and manually recreate them for the new Eisy once it is in place. I understand that UD mobile can facilitate ZWave additions, so would want to harness that. Also have some Polyglot modules. I may have to buy new licenses for these. The most important one is my Tempest WeatherFlow station support. Thoughts? Suggestions? Oh, and one last item. I purchased a couple of Polisys way back, as it turned out just a few months before the Eisy was announced. I do hope there isn't a Eisy II in the works real soon? Would not want to repeat that mis-step. * Orest

I may be in a similar situation soon. IIRC, the EISY comes set up to only work with the new USB board. BUT, that is a software setting, it can be reset to use the old 700 series dongle. You may have to create a ticket. * Orest

Subject & body have text. Simple text. * Orest

So, this is using the "default" email server in IOX. Messages are just short text compositions. Today I noticed that no email notifications were being sent from one Polisy machine (v5.4.4), and trying a test message gives ... \\ BUT, another Polisy machine that about up to date (v5.8.0), email notifications are still coming. But (again), the other odd thing that I have noticed in the last month or so, is that I would get duplicate notice mails, that were sometimes months old. The message text time stamp was old, but the email time stamp was current. It is like it was resent. * Orest

I have just sat on it, for now. * Orest

@CoLong Just set up some variables, using the system time variables. Roll them over just after midnight. The sky is the limit, add new ones as you need to. I use these in a number of programs in my setup. So, for example, testing for ... $cal_month_of_year = 3 and $cal_day_of_month = 16 ... would give you March 16th. * Orest

UD mobile is fabulous for what it provides, and I use it all the time. But it can't sub for a full UI for initial programming and maintenance, except for the simplest of setups. If you could only use the mobile interface (with all its hardware related limitations), that might be the end of the platform! * Orest

This was just a hypothetical. But from what you are suggesting, data/structure is stored on the ZMatter card, that was what I was wondering. So, is there a factory reset for the ZMatter card? No docs with the card, and the wiki doesn't talk about it. There is a reset command in the AC for the ZWave Zooz 700 USB controller, is there something similar for the ZMatter? * Orest

Anyone? Hate to waste a ticket slot, if someone here knows. * Orest

Best way might be to add a comment ... [FIXED] ... or something like that. * Orest

This unit was new out of the box (but on the shelf for bit), and I already reflashed the image with Michel's help, updates fully done (or so I thought), was running 5.8.0, and even PG3 -> PG3x enabled -- although that never took for whatever reason, hence this thread. I was initially having trouble with accessing it, with the included PS, and substituted a new 12v 3A PS, and that got it going. That was with Michel's suggestion as well. I even tried the old PS, and it stopped booting, so it seemed pretty consistent. Yes, I never got the popups for the updates this time (can't remember if I did initially), but at the last instance I did get a popup saying that a new PG3x was available when I started up the AC, so something has changed. I declined the update for the moment. Perhaps it had got into some kind of intermittent state, as you say, and the multiple power cycles finally got it going. Perhaps I didn't wait long enough for the update, but it was at least a few minutes. I have not tried another three pushes of the m.s. to see if it will reboot. But, it is running now and working, so I'm a bit hesitant to do anything! 😃 It is also at my vacation property, I'm not up there at the moment, so can't do any further poking around. If it still continues to misbehave, I will open a ticket. Thanks much for your thoughts and suggestions. * Orest

I understand that there are migration procedures and all kinds of pitfalls when switching IoX devices, and I have been poring over them as I have some work ahead of me .... But, just speaking of the ZMatter hardware, if you move a ZMatter board to a different Polisy/Eisy in the process of migration (or replacing a dead one, or just moving components around), is there some kind of factory reset procedure required on the Matter board itself, or is it just a passive sender/receiver, and all the smarts and settings data is stored in the Eisy/Polisy OS? For example, let us say I had two Polisys running, one operational and one a test box, both with a ZMatter board. Let us suppose one ZMatter board dies (a bit fanciful, but just a thought experiment), can you just physically swap in the other ZMatter board and keep going, or do you need to do the whole migration procedure? I understand that the old Zooz USB 700 stick does need to be cleared one way or another. * Orest

@Geddy, well mixed results. As suggested ... Commanded an update from the AC. Although the cursor showed non-responsiveness for a bit over the AC, nothing happened. No shutdown, no reboot. Then I tried three pushes of the multi-function, nothing at all happened, and the Polisy continued normal ops. Tried it once more, again no operational change. Finally I tried a power cycle. Of course that closed the Polisy down, but then it became non-responsive. No network connection on attempted restart. I had removed the outer cover, so I could accurately contact the mini-switch. Waited a bit, then tried three pokes of the m-s again. Nothing. So, last thing to try, pulled the power, and waited a bit, then repowered. The unit would not resume operation. I had removed the outer cover, so was familiar with the expected flashes on the mobo. They were not proceeding. I was fearing the thing was bricked. Tried another power cycle, again nothing. OK, one more time, this time I got a single beep almost immediately on power up, but unit remained non-responsive. OK, one last time, did yet another power cycle. This time, it booted normally, I immediately recognized the "normal" power cycle by the mobo LEDs. Finally, it was running, and does appear that PG3x is now accessible as well. BUT, just wondering, is this to be expected as a normal kind of miasma for a simple update on the Polisy? Really makes you think twice about updating! * Orest

Yep, see it in 5.8.0 (on one Polisy), but not on 5.4.4 (my other Polisy). * Orest

Well, (now) my service monitors will catch some of this, and the rest can be remedied by a forced reboot at 3:01AM when DST changes one way or the other. But, my observation is that this has only started recently, as I moved from 994 to Polisy, and through the firmwares to 5.4.4 on one, and 5.8.0 on the other. So, at some time in the past the system seemed more tolerant around the DST changes. Sure, my programming has changed in that time, but not dramatically. But, as I don't have better data than that (it is a hard thing to notice before you know it is going to happen), that observation is not going to be much help I expect. * Orest