-
Posts
4640 -
Joined
-
Last visited
Everything posted by Jimbo.Automates
-
Can't it use localhost instead of an IP address when it sees ISY and PG3 are on the same machine? I actually changed all mine to localhost per Michel when I reconfigured my network addresses a while back. Sent from my Pixel 6 Pro using Tapatalk
-
You can only create tickets using the web interface, sending to support email doesn't work anymore, or it hasn't worked for me for a while. Sent from my Pixel 6 Pro using Tapatalk
-
This can't be a random number, it needs to be a valid user code defined in your ELK system. Personally I create a specific user code for PG3 so I know who is arming/disarming the system.
-
Did you reinstall in same slot? If so, will need need help from @bpwwer for these error.
-
Please update to the latest PG3, reinstall in the same slot and try again. Sent from my SM-X808U using Tapatalk
- 1 reply
-
- 1
-
-
KASA starts but fill the log with errors
Jimbo.Automates replied to jkosharek's topic in Kasa (TP-Link)
Sorry I have no idea. My eisy had issues last weekend so I wasn't able to test. It's all good now so hopefully I have time this weekend to test. Sent from my SM-X808U using Tapatalk -
Update to latest PG3 then reinstall in the existing slot should resolve this. Sent from my SM-X808U using Tapatalk
-
Update to latest PG3 should resolve this. Sent from my SM-X808U using Tapatalk
-
Sorry I have no idea. My eisy had issues last weekend so I wasn't able to test. It's all good now so hopefully I have time this weekend to test. Sent from my SM-X808U using Tapatalk
-
I just tried this and it worked fine to arm the system. However I don't use this method, I created a program for stay and away which arms when on and disarms when off. I've actually thought about just creating a node for each arm status so you can just add the node as a favorite. Sent from my SM-X808U using Tapatalk
-
I had issues bringing up my eisy last weekend so I wasn't able to try it out. Hopefully this weekend I will have free time, it's been a busy few weeks at work and home so I'm way behind around here. Sent from my SM-X808U using Tapatalk
-
Need help from @Michel Kohanim or @bpwwer Sent from my Pixel 6 Pro using Tapatalk
-
As I mentioned two posts above yours, this is currently not supported and I provided the links to the current discussions. Sent from my Pixel 6 Pro using Tapatalk
-
Makes sense, hopefully others using ELK outputs can chime in with their opinion. Sent from my Pixel 6 Pro using Tapatalk
-
No worries, that's why I apologized for the process not being fully explained. Sent from my Pixel 6 Pro using Tapatalk
-
Something else must be using port 8081? What other node servers or programs do you have running on your Polisy? You can change it to something else, like 8082 and restart the node server.
-
There should be a button that says reinstall in slot #. Where # is the current slot. If not, then you are on a pretty old version of PG3. Sent from my Pixel 6 Pro using Tapatalk
-
The nodes were deleted because you uninstalled the node server. That always deletes the nodes in PG3 and the ISY. Sent from my Pixel 6 Pro using Tapatalk
-
Unable to upgrade to version v1.0.6 from v1.0.5
Jimbo.Automates replied to Bumbershoot's topic in ST-Sonos
This is a bug in PG3 where it doesn't properly recognize a new version of a node server that was previously released with a very old version of PG3. But, do not delete and reinstall. You can reinstall in the same slot from the store or purchases page. Sent from my Pixel 6 Pro using Tapatalk -
Yes, you will have to use the "Turn on For" inside UDI Mobile. But, if everyone using the ELK would like that to be the default On action, I could be convinced to change it or make it an option.
-
PG3 Airthings Consumer node server 1.2.6
Jimbo.Automates replied to Jimbo.Automates's topic in Airthings-C
PG3 Airthings Consumer node server 1.0.1 released. -
Do not uninstall then install again, you can re-install in the same slot from the node server store, or by going to the purchases tab. Sorry Bob did not make that clear enough.
-
Version 1.0.1 released to force an upgrade of the udi_interface which was out of date on your system.
-
Are there any errors in the node server log? Sent from my Pixel 6 Pro using Tapatalk
-
Sorry, I see the exception now, missed that. I'll review your log and see if I can get it fixed tonight. Sent from my Pixel 6 Pro using Tapatalk