-
Posts
4634 -
Joined
-
Last visited
Everything posted by Jimbo.Automates
-
The other issue being discussed is that a query of a nodeserver node doesn't always send back the status to the ISY if it thinks there is no change. If you restart ISY and have Query on Restart enabled then all current node status should come back to ISY, but currently it does not.
-
The Polyglot Version 3 Node server for IFTTT Maker Webooks https://ifttt.com/maker_webhooks version 3.0.3 is released. See the README for more information. The Release Notes are also available.
-
Trying to setup Occupancy v2.0 (with UD Mobile)
Jimbo.Automates replied to photogeek54's topic in UD Mobile
Yes, I understand your hesitancy, but for me it has been extremely robust with some simple bounce detection, and I'd really like it to be integrated into UD Mobile. My trials with using geofencing were horrible, many false exits for me, but of course I haven't tried it in a couple years, and still the battery drain from a simple wifi check must be better than geofencing I don't use if for anything security related, just changing HVAC settings, sending notificaitons if doors/windows are open, if everyone is gone let us know we didn't arm the alarm, ... -
PG3 CAO Wireless Tag Node server 3.1.7
Jimbo.Automates replied to Jimbo.Automates's topic in WirelessTag
Thanks, looks like Leak Sensors report lux and light state, I can add that. 2022-02-26 16:51:37,791 Command udi_interface ERROR Tag:set_lux: 5:34:ca8f9c951a6968:Leak Sensor 5: does not have lux but was sent 3.388070821762085 2022-02-26 16:51:37,803 Command udi_interface ERROR Tag:set_list: 5:34:ca8f9c951a6968:Leak Sensor 5: Is not configured for light state, let the author know it is needed value=0 Added issue: https://github.com/UniversalDevicesInc-PG3/udi-wirelesstag-poly/issues/51 -
PG3 CAO Wireless Tag Node server 3.1.7
Jimbo.Automates replied to Jimbo.Automates's topic in WirelessTag
PG3 Nodeserver for CAO Wireless Tags version 3.1.3 is released, see the Release Notes. -
Polyglot 3 Flume Water Node server 3.0.11
Jimbo.Automates replied to Jimbo.Automates's topic in FlumeWater
FlumeWater Nodeserver 3.0.8 released, see the Release Notes -
Trying to setup Occupancy v2.0 (with UD Mobile)
Jimbo.Automates replied to photogeek54's topic in UD Mobile
Personally I just use Tasker to set Home/Away for each person based on connection to the WiFi, there has to be a small wait time on disconnect since phones occasionally loose connection for short periods of time. Using geofences had to many false triggers and this wifi method has been very robust for me for a long time. Anyone on Android can grab my Tasker share if they are interested JimboISY Tasker Share @Javi I would prefer UD Mobile implement this method as an option. I already tell it what my WiFi networks are, so it could set a variable or define toggle a node based on that -
PG3 HarmonyHub Node Server 3.0.5 Released. See Release Notes
-
Currently PG3 doesn't give you any visual indication that an upgrade is available, that's coming in the future. (remember this is Alpha) Just cross reference your version with the one shown on the store page for now. To upgrade you just have to restart the nodeserver.
-
Essentially that's what I use controller for. Send DON/DOF for heartbeat. I didn't want the extra overhead of yet another node just for heartbeat, but we could if that's what we agree to. Or we had a special command like HBT that would probably be better?
-
I was wrong, this NS does give status while the discover is running with the "Profile Status" on the HarmonyHub Controller node.
-
Event State status gone and no longer detected in a program
Jimbo.Automates replied to stevehoyt's topic in WirelessTag
Fixed in 3.1.2 Sent from my Pixel 6 Pro using Tapatalk -
PG3 CAO Wireless Tag Node server 3.1.7
Jimbo.Automates replied to Jimbo.Automates's topic in WirelessTag
Released 3.1.2 which fixes a bug where EventState was not being reported. -
Strange that it comes back with the old name, the code tries to remember things because Harmony likes to change ID's associated with activities and devices so I have to account for that. Could be a bug, or a feature The purge is documented: https://github.com/UniversalDevicesInc-PG3/udi-harmony-poly/blob/master/README.md#purge Purge Check just does the check to see what it will do, and Purge Execute actually does it. You have to watch the log to see what it's doing, and watch the log to see what discover is doing and when it's done. I could add a status on the controller to say what discover is doing, which I do in some, but not in this one. Yes, discover from the Controller and PG3 do the same thing.
-
Please try latest PG3 3.0.41 and see if that fixes the issue.
-
I think it works in PG3 now, but not home to confirm. Either way you can delete the node in PG3 UI then run discover. Sent from my Pixel 6 Pro using Tapatalk
-
Event State status gone and no longer detected in a program
Jimbo.Automates replied to stevehoyt's topic in WirelessTag
Thanks for the log, I'll check it out. I see it's a GitHub issue now as well, thanks. Sent from my Pixel 6 Pro using Tapatalk -
@bpwwer Looks like backup restore must have deleted slot 12? Sent from my Pixel 6 Pro using Tapatalk
-
The HarmonyHub NS is meant to control Harmony devices with the ISY. The HueEmulator NS is used to control ISY devices with the Harmony Hub Remotes. The Harmony API does not expose the Home Control buttons, you must use the HueEmulator NS.
-
Log into your polisy and see if the directory is really gone: ls -l /var/polyglot/pg3/ns But, as Bob said, if you did ever run 3.0.39 the database may have been corrupted. But we can give you commands to fix that if you did.
-
Oh that's bad... Not sure how the NS directory would get removed. We will need help from @bpwwer on this.
-
Trouble finding AIR after move from PG2 to PG3
Jimbo.Automates replied to tmorse305's topic in WeatherFlow
I think you have to restart ISY then resync UDMobile Sent from my Pixel 6 Pro using Tapatalk -
The Polyglot Version 3 node server for Camect 3.0.9 is released. See the README for more information, including information on moving from PG2. The Release Notes are also available. If you have issues are requests please check Camect PG3 GitHub Issues to see it has already been listed. Please confirm you are on the latest version of PG3 which is 3.0.40 right now.
-
You can not have multiple copies of the NS running, no matter if it's V2 or V3, you can only have one for that very reason.
-
Yes, I intended to create a new Oauth App for using PG3, but forgot to do that, so PG2 and PG3 are using the same one, which really doesn't matter. Not sure why you had to revoke access, any should work. I have multiple copies running with different auth keys. I could still add a new OAuth App for PG3, but then everyone will have to re-auth. Or I could just change the name of the App...