oskrypuch

Is that a PG2 service, or has it been moved over? Is it still supported? * Orest

That is what I understand. I have had three service calls now, with improvement for a bit after each. They detected an issue at the CO, then with a connector outside the house. I expect that the cable (somewhere) is just not up to 3.1 connectivity. I had nil issues with my 3.0 modem -- but of course they will not enable it now, I should have never "upgraded"! So, until this gets remedied (perhaps switching to fiber, which is on our street), I need something to reawaken the error overwhelmed modem from time to time. I do have a quick keypad button set to do this, and when we go away I have it run on spec every six hours. It would be more slick if the connectivity outage were detected somehow, and the power cycle triggered. I would be even MORE slick to have a properly working internet connection! (sigh) * Orest

Having issues with our internet connection, a real pain to try to sort out with the provider, but I digress. (docsis 3.1 modem develops a high level of uncorrecteds after a while, and then ceases to pass packets) I have set up a dual-band insteon switch that I can turn OFF, and hold OFF for ten minutes, cold power cycling the modem. This seems to clear the loss of internet for a while. My question is, is there an easy way for Polisy/IoX to detect that the internet has gone down, and trigger a program? I have a couple of weather nodes on PG3, but these still indicate a connection as they are running locally. Clearly I could detect unchanging values, but that is a bit dodgy and not 100%. Any other clever way, perhaps interrogating some system variable? * Orest

Thanks, polisy.local has never resolved to my local IP for the polisy, but using the actual policy IP doesn't work either. Yes, that is why I need to run a ticket. But, no I was asking about the 5.7.0 "disabled programs" fix. I am currently running 5.4.x, and PG 3.0, mainly a large Insteon system but do use the Z-Wave dongle (not the matter board) for a few Z-Wave items. I have been reluctant to upgrade until we get an update that is running smoothly for a while -- as all seems to be working for me well as is. Moving to 5.7.x, and then PG 3.0x, and then possibly shifting to the matter board for my Z-Wave, are the dominos that need to sequence at some point. So, that is where I am. * Orest

It will be nice to see confirmations "out in the field" for the fix. * Orest

After the usual certificate dialog and a log in prompt, I get ... ./FILES/WEB/sysconfig.txt not found So, am I set up for a 10% brick? If I want to upgrade, I will need to run a ticket? Hopefully there is a way to do it at some point! * Orest

I kind of thought so. Was looking at doing so, but holding off for the moment given the current ".0" issues. * Orest""

So, I am on Polisy, running 5.4.4, and using a Z-Wave dongle (no matter board) Any issues with upgrading to PG3x with this combo? Only use PG3 nodes at present. * Orest

Is the last 5.6.x version still available to upgrade to? I have been on the fence for a while, running 5.4.x. Would prefer to grab the "last" release in a series. * Orest

Oh well.

Oh cool, the Load keeps the theme settings. Handy. * Orest

Bingo! Thanks much, that worked. * Orest

Get the unknown engine .. Tried with the start linking method, as well as the new device both with auto discover and specifying the type. Curiously on the back of the device, it shows the type as 2342-2, no "42" at the end. It shows v1.8 2311 for the version/manu date. Is this device not yet supported? Running Polisy with 5.4x firmware. * Orest

IIRC, there is a geolocation function. What else of note? * Orest

I am currently on Polisy with v5.4x running, mostly Insteon but with a Z-Wave dongle and some devices, and PG3, and everything is running 100%. I am vacillating as to when/if to make a firmware (+/- Matter board) update move. It is kind of, when do I want to create work for myself. 😁 Plan to stay with the Polisy, bought two just before the eisy was announced. * Orest

If I read it right, currently there isn't an upgrade path Polisy/PG3x -> eisy/PG3x. There is a path for Polisy/PG3 -> eisy/PG3. So a move to eisy would be complicated if you moved to PG3x on the Polisy. * Orest

So, basically, if on Polisy -- stick with PG3? * Orest

You can search, but use the RAW checkbox ticked. I find it easier to dump the whole listing to a text file, and use an editor outside of the UI. The listing is of course static, but usually does the trick, and can be easily refreshed as needed. A great fallback when a restore is needed in a FUBAR situation. * Orest

So, I understand that the Z-matter board must have the USB connectors for the new eisy. But, I have the Polisy, actually two of them, yes bought a pair two months before the eisy was announced -- oh well. In any case, do want to keep the Polisys running as long as practical. I have the Zooz USB dongle, dipped into Z-Wave during the Insteon time of troubles, actually delighted that Insteon is back, can even buy PLMs. My mixed setup is working great, mobile UD, PG3 (older) have some weather nodes as well. I have frozen it at IOX 5.4x. Wish there was a LTS concept in these firmwares. But, I digress. My question is, does the Z-matter board "pop-out" of the USB box, and can it then be inserted into the Policy box as it was prior? Or, do you need to use one of the USB slots on the back of the Polisy? I understand I will have to update to the latest firmware, and so on, read through all the wiki stuff (and some of the trouble reports here) -- so I remain a bit reluctant. That said, eventually I may get firmware "orphaned", so will need to do it some time. * Orest

With the consistency of the error, sure sounds like a bad/failing SD card. The other really weird issue I've seen, is if you have any open UDP ports. It doesn't need to have anything to do with your ISY itself. Open UDP ports (vice TCP) will allow a lot of junk to flood your network. It likely won't get anywhere, but the extra traffic can overwhelm the NIC on the ISY. Unlikely that you'd get such consistency in that error, but worth a shot. * Orest

I hate the Spring forward thing, but I think that settling on "summer" time as a single zone is a big mistake. Instead ... We should just settle on the "standard" time zone for each. That way, noon will have the sun more overhead, like it was designed for, and we won't have dark & gloomy mornings in the winter. * Orest

... like a default color for negative values!? 😉 Well, the app specific PIN is different from the main system PIN, and quick and easy to punch in. I am not too worried about this mobile app, but personally would not use a higher risk app that didn't have an app specific PIN. Thanks for putting it on the list, even if lower priority. * Orest

Perhaps it is there already, but I can't find it. I'm thinking an optional four to six digit PIN before a user gets access to the app. The access permission should timeout after a bit, and any time the app shutdowns now. * Orest

I had seen the same thing. It was fixed, even before I reported it. Thanks. * Orest

Isn't IoX == IoP, just the new name for the cross device version? (still sitting on Polisy with an empty slot, with 5.4.x) * Orest