Everything posted by JTsao
-
Support thread for: PG3x 3.1.25
Ha - I just posted about what you wrote in the IoX 5.6.0 thread - I did not open a ticket back then because nothing appeared to happen except a browser error - will open a ticket now - thanks for replying
-
Support thread: IoX 5.6.0 Release
So no one else got bumped to PG3x 3.1.25? I have a theory that because I clicked on this https://polisy.local:8443/rest/pg3x.enable a few weeks ago (from the flirc / IR page), that this may have done something which caused me to go to PG3x - although, at the time, it did nothing... may be opening a ticket, or I may have to try to migrate to PG3x from my latest PG3 backup using the "migrate from PG3 backup" option - has anyone else tried to migrate a Polisy to PG3x?
-
Support thread: IoX 5.6.0 Release
I performed the update on my Polisy from 5.5.9 to 5.6.0 - this also updated the Polisy to PG3x 3.1.25 and now all my node servers are disconnected - rebooting, power cycling and restarting PG3x do not fix this - is this because the Polisy has now crossed over to PG3x? vs PG3? - do I need to re-install all node servers or what?
-
Support thread for: PG3x 3.1.25
I updated my Polisy to IoX 3.6.0 this morning and PG3 also updated to 3.1.25 but now all of my node servers are disconnected - rebooting, power cycling and restarting PG3x are NOT fixing this - any suggestions?
-
iAquaLink PG3 Node Server Released
The salinity reading does work for me via the iAqualink app - for various reasons, such as climate, rainfall, evaporation or whatever, I have to add salt a few times each year - to do so, I use the iAqualink app to see if the ppm is below 3000 or so at which point I add salt - the fact that it works in the app, implies to me that it could work with the node server, in which case I could write a handy program to send a push notification to add salt (another way to making chores a bit easier) EDIT: Goose66 - I sent you a couple of PMs
-
iAquaLink PG3 Node Server Released
Question: Salinity doesn't work for me - it reads 0 all the time - this would be very useful if it were to work so I could generate a notification to add salt - should I try deleting all nodes except the iAqualink service and run "discover devices"?
-
Support thread for: PG3x 3.1.25
I did the update on my eisy (which I am not yet using) and I can no longer log into the web page at :3000 - I never changed the eisy credentials from admin:admin - and they no longer work - any suggestions how I can get in? Nevermind - power cycle fixed it
-
PG3x on Polisy
I completely relate and understand - my Polisy is my active controller = mission critical (with an eISY/Zmatter on standby for future migration) I rely on it too much so I don't want to break anything or take unnecessary risks...
-
PG3x on Polisy
To be clear, did you just click on the link "https://polisy.local:8443/rest/pg3x.enable"? and it worked?
-
PG3x on Polisy
Yes I actually did an update a few days ago and am now on IoX 5.5.9
-
PG3x on Polisy
Has anyone been able to update PG3 to PG3x on the Polisy? There is a link to do this on this page: https://www.universal-devices.com/eisyir-flirc/ - I clicked on it and it didn't work - I get "This XML file does not appear to have any style information associated with it. The document tree is shown below." The link is this https://polisy.local:8443/rest/pg3x.enable - but more importantly, I haven't seen that anyone else has tried this or if PG3x has any issues...
-
Z Wave roll back
A few weeks ago, I attempted to migrate from a Polisy/Zooz dongle to the eISY/ZMatter and ended up going back (I have around 30 ZWave devices and 11 PG3 node servers) - I did not have to do a restore to go back to the Polisy
-
Support thread: IoX 5.5.9 Release
Yes, my Polisy is on 3.1.18 now - I also have an eISY/ZMatter (for future migration) and it updated IoX/PG3x with no apparent issues
-
Support thread: IoX 5.5.9 Release
OK - I got everything working - after the initial update, IoX was not indicating any further updates required but PG3 was at 3.1.17 - did restart from PG3 web page and could not access PG3, tried sudo service pg3 restart and still could not access, tried power cycle and still could not access, then tried another update from IoX (even though it was not indicating updates available) and I think that fixed it
-
Support thread: IoX 5.5.9 Release
I am now in the same situation - I updated to 5.5.9 and everything was working except PG3 didn't update - I did a system->restart in PG3 and now I can't access PG3 - I power cycled the Polisy and still can't get to PG3 - may be opening up another ticket soon - I really dread updating my system in recent months as it has caused a lot of problems and multiple tickets...
-
Support thread: IoX 5.5.9 Release
I just did this on the Polisy and I can't get into PG3 either
-
Support thread: IoX 5.5.9 Release
I was on IoX 5.5.5 and PG3 3.1.17 - I pushed the update packages button and left the room for a while - not sure about the beeps but it appears IoX is now 5.5.9 and working but PG3 is still at 3.1.17 - do I need to push the button again? Edit: IoX is not telling me that there are any updates available
-
New locks
It was early January of this year when I added the 3rd Ultraloq
-
New locks
-
New locks
No, I am pretty sure that this lock cannot do that with current IoX capabilities - only basic lock/unlock and it does appear to have a way to set and delete user codes (but I haven't used that, I did that with their app) - I switched to this lock because it has multiple ways to enter including fingerprint, code, key or bluetooth (auto-unlock) feature - you might be able to accomplish what you are describing above with geo-fencing to determine who left the house (and who is at home) There is also a minor issue in re-keying this lock as it doesn't accept a typical lock cylinder, but for me that is not a big deal because you can power it via an external USB port if the battery dies - despite the negatives, I am happier with these locks than with the Schlage, but everyone's use case is different...
-
New locks
I just switched from 3 Schlage locks after 8 years of use (both Z-wave 300 and 500 versions) - they are a good company and will stand behind their product, even sending me a replacement well beyond the warranty expiration, but, I always had minor communications issues with their locks, mainly with receiving the status, even with beaming repeaters and a lot of z-wave devices, and limited distances to the Z-wave device (z-wave 300 board and Zooz dongle) - I switched to Ultraloq and communications are good now
- New locks
-
Is this a bad time to press the upgrade packages button?
It seems like there are a lot of current problems with IoX, PG3, PG3x or the various packages that they depend on - I have a Polisy that works, that I would like to keep working, and an eisy and Zmatter that I eventually want to move to (currently test units that are not controlling anything) - I am running IoX 5.5.5 on both and PG3 3.1.17 and PG3x at 3.1.22 - it's too time consuming to read all of the forums to figure out what works and what doesn't - I think I need a green, yellow or red light based on user consensus to indicate if I should push the button on either box - so, what does everyone recommend as of today, 2/14/2023? Push, or wait? Can UDI add something to the forums indicating if there are significant problems if I push the button?
-
PG3x minor release?
I had to do this after migration attempt #1 to go from the Polisy to eisy
-
PG3x minor release?
I guess that confirms that there was an update earlier this week It might be useful to have a thread where users can update each other on what versions they are running and if there are any issues: I've got eisy: udx 3.3.6, pg3x 3.1.22_3, isy 5.5.5_2 and Polisy: udx 3.3.5_4, pg3 3.1.17, isy 5.5.5_1 My eisy is experimental at this point and my Polisy needs to be working - is anyone running anything newer on their Polisy?