-
Posts
4650 -
Joined
-
Last visited
Everything posted by Jimbo.Automates
-
Sorry, been traveling and busy. The Alarm-Elk is the folder I store all the elk nodes in. I'll try to take a look on my home computer when I have a chance. Submitting a support ticket likely won't help since they'll just ask me to take a look. Sent from my Pixel 8 Pro using Tapatalk
-
Did you install the PG3x ELK plugin and configure it? Sent from my Pixel 8 Pro using Tapatalk
-
Ecobee reverting back to Home settings due to motion
Jimbo.Automates replied to Tim.Sto's topic in Ecobee
Turn off smart home and away mode in the ecobee app under eco+ settings Sent from my Pixel 8 Pro using Tapatalk -
-
It should be there, I'll look into it. Sent from my Pixel 8 Pro using Tapatalk
-
new install, disconnected, and no logs (logs folder doesn't even exist)
Jimbo.Automates replied to carteriii's topic in ELK
Awesome, glad it worked! Hope you are happy with the elk plugin, I know converting from the old method can be painful. Sent from my Pixel 8 Pro using Tapatalk -
new install, disconnected, and no logs (logs folder doesn't even exist)
Jimbo.Automates replied to carteriii's topic in ELK
There have been issues with Python installs during the updates. Please submit a support ticket and they'll get you fixed. I've not seen anyone with this issue post the solution and previously @Michel Kohanim just mentioned it was a Python install issue. Sent from my Pixel 8 Pro using Tapatalk -
new install, disconnected, and no logs (logs folder doesn't even exist)
Jimbo.Automates replied to carteriii's topic in ELK
The install.log is in your screenshot when you show the listing of the plugin directory. Sent from my Pixel 8 Pro using Tapatalk -
new install, disconnected, and no logs (logs folder doesn't even exist)
Jimbo.Automates replied to carteriii's topic in ELK
Probably a system issue, can you cat the install.log? Are you on the latest versions? Try "Upgrade Packges" in Admin Console, and when complete reboot, then delete and install Elk plugin again. If you are on the latest, then probably have to submit a support ticket, we have seen this issue before. -
I'm not sure it's possible, I'd have to look. As mentioned in the documentation, there is no official API for Kasa devices, a bunch of smart people have reverse engineered the communication and released a library that I reference. The communication can change at any time and break that library, and in fact new devices use different methods, so they have been releasing changes to their library to try and keep up. I plan to update the plugin to the new version of this library now that it seems to have stabilized. Sent from my Pixel 8 Pro using Tapatalk
-
Sorry, Kasa scenes are not supported at this time. Sent from my Pixel 8 Pro using Tapatalk
-
Sorry, I never said it supported the smart hose timer. Please set plugin log mode to debug, then restart and let it run for a couple minutes and 'Download Log Package" and PM it to me.
-
Likely just a temporary Internet connection issue, or their service is flooded and not responding. If it happens frequently please report to their mailing list or create a support ticket. Lately they have become horrible at responding to support tickets, but did respond to the mailing list. Sent from my Pixel 8 Pro using Tapatalk
-
Sorry, haven't had a chance to look yet, just to confirm there was an event on the day you did the download log package? The log is rolled over at midnight so it needs to have happened that day. Sent from my Pixel 8 Pro using Tapatalk
-
Please download log package and PM or email it to me. Sent from my Pixel 8 Pro using Tapatalk
-
PG3 Airthings Consumer node server 1.2.6
Jimbo.Automates replied to Jimbo.Automates's topic in Airthings-C
PG3 Airthings Consumer Plugin 1.2.6. released, see OP - 1.2.4: 08/11/2024 -
A couple of minor issues with 1.2.3 update today
Jimbo.Automates replied to macjeff's topic in Airthings-C
Should be fixed in 1.2.6 -
Important! If you are running a 5.0.x version please upgrade to 5.0.4.
-
Important! If you are running a 5.0.x version please upgrade to 5.0.4.
-
A couple of minor issues with 1.2.3 update today
Jimbo.Automates replied to macjeff's topic in Airthings-C
Did you change it in the PG3 UI? If so, the Plugin has no idea that you changed it until you restart. I asked @bmercier if this could be added so hopefully it can be. Change it in the AC of UDM. Sent from my Pixel 8 Pro using Tapatalk -
I have 2 wired and one wireless pet immune motion sensors, not sure the model... They are configured as "Burglar Interior" "Normally Closed" and I see their status change in UDMobile when they are activated they show "OPEN" and when not they show "SHORT". The "Send On" & "Send Off" do not matter for "Status", that only configures when to send a DON/DOFF if you want to add them to a scene. If nobody else has any ideas, then put the Plugin log in Debug+Modules mode, then activate a motion sensor, let it timeout then "Download Log Package" and email that to me.
-
This was a known issue with older versions of PG3. Are you running: PG3x Version 3.2.27 ? If not please do a "Upgrade Packages" from Admin Console -> Configuration -> System Tab.
-
PG3 Airthings Consumer node server 1.2.6
Jimbo.Automates replied to Jimbo.Automates's topic in Airthings-C
PG3 Airthings Consumer Plugin 1.2.4. released, see OP - 1.2.4: 08/11/2024 - Restore "Auto Short Poll" and "Short Poll" values as saved in PG3 DB -
A couple of minor issues with 1.2.3 update today
Jimbo.Automates replied to macjeff's topic in Airthings-C
Version 1.2.4 should fix this until PG3X is fixed: - 1.2.4: 08/11/2024 - Restore "Auto Short Poll" and "Short Poll" values as saved in PG3 DB -
A couple of minor issues with 1.2.3 update today
Jimbo.Automates replied to macjeff's topic in Airthings-C
The 1.2.3 version issue is fixed. But there are 2 issues with PG3 that I've notified @bmercier about. 1. On upgrade install PG3 is resetting shortpoll back to default. 2. If you change Controller -> "Auto Set Short Poll" = True, then on restart it will put it back to False I created programs to set mine back to desired value to get around this issue until we can resolve.