DaveStLou

I still have an Insteon contact sensor on my garage door that I took offline when I installed MyQ. I'm thinking about re-enabling it so I could use it to trigger Force Query. It does make the value of the MyQ less than I had hoped. It ends up being a belts-and-suspenders solution.

Still a work in progress. I'm still scratching my head on how to trigger the Force Query in those scenarios and others.

Same thing I did to get from 3.06 to 3.08. All is well.

Tasker is another option although not as easy to set up as MacroDroid.

I don't see an impact in the AC but my WeatherPoly is showing a couple of errors in the Node server log on startup: 2022-03-29 08:02:59,865 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'light', 'success': False, 'error': "Cannot read properties of undefined (reading 'status')"}] 2022-03-29 08:02:59,914 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'lightning', 'success': False, 'error': "Cannot read properties of undefined (reading 'status')"}]

Makes sense. I was attempting to run a purge in HarmonyHub and when it didn't successfully complete, I discovered the Node server had crashed and wouldn't restart. That's why I regretfully attempted to reinstall it after apply updates in Polisy to make sure everything else was up to date.

I attempted to reinstall my HarmonyHub Node server and I'm getting the same error @macjeff reported above. I've kind of lost track as we've gone through the progression from PG3 3.0.50 to 3.0.53 but I thought it was running before I upgraded to 3.0.53. I am seeing this in the Polyglot log repeating every minute: 3/26/2022, 07:42:49 [pg3] error: unhandledRejection REPORT THIS!: [object Promise], reason: TypeError: store.getPurchaseEntry is not a function

Yep. Same error in log I just reported under HarmonyHub Node server.

Since updating to 3.0.50, my HarmonyHub Node server is failing to start. Below is from the log: 2022-03-24 09:13:07,156 MainThread udi_interface INFO Controller:__init__: HarmonyController: Initializing 2022-03-24 09:13:07,158 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: harmonyctrl not found in database. 2022-03-24 09:13:07,160 MainThread udi_interface.interface INFO interface:addNode: Adding node HarmonyHub Controller(harmonyctrl) [None] 2022-03-24 09:13:07,162 MainThread udi_interface.interface INFO interface:setController: Using node "harmonyctrl", driver "ST" for connection status. 2022-03-24 09:13:11,038 MQTT udi_interface.interface INFO interface:_message: custom data response {'customparamsdoc': ''} 2022-03-24 09:13:11,086 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparamsdoc 2022-03-24 09:13:11,115 Command udi_interface ERROR udi_interface:write: Exception in thread 2022-03-24 09:13:11,117 Command udi_interface ERROR udi_interface:write: Command 2022-03-24 09:13:11,117 Command udi_interface ERROR udi_interface:write: : 2022-03-24 09:13:11,119 Command udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-03-24 09:13:11,120 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner 2022-03-24 09:13:11,128 Command udi_interface ERROR udi_interface:write: self.run() 2022-03-24 09:13:11,129 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 870, in run 2022-03-24 09:13:11,132 Command udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2022-03-24 09:13:11,133 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/interface.py", line 678, in _parseInput 2022-03-24 09:13:11,136 Command udi_interface ERROR udi_interface:write: self._handleInput(key, input[key], None) 2022-03-24 09:13:11,137 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/interface.py", line 684, in _handleInput 2022-03-24 09:13:11,141 Command udi_interface ERROR udi_interface:write: self._inConfig(item) 2022-03-24 09:13:11,141 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/interface.py", line 598, in _inConfig 2022-03-24 09:13:11,144 Command udi_interface ERROR udi_interface:write: LOGGER.setLevel(self.currentLogLevel) 2022-03-24 09:13:11,145 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/logging/__init__.py", line 1421, in setLevel 2022-03-24 09:13:11,151 Command udi_interface ERROR udi_interface:write: self.level = _checkLevel(level) 2022-03-24 09:13:11,152 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/logging/__init__.py", line 198, in _checkLevel 2022-03-24 09:13:11,154 Command udi_interface ERROR udi_interface:write: raise ValueError("Unknown level: %r" % level) 2022-03-24 09:13:11,155 Command udi_interface ERROR udi_interface:write: ValueError 2022-03-24 09:13:11,156 Command udi_interface ERROR udi_interface:write: : 2022-03-24 09:13:11,156 Command udi_interface ERROR udi_interface:write: Unknown level: 'NULL' 2022-03-24 09:13:16,667 MQTT udi_interface.interface INFO interface:_message: Profile installation finished I've tried restarting the Node server several times. Also restarting Polyglot and reinstalling the Node server to no avail. HarmonyHub Version: 3.0.6

Thanks for the explanation, @Goose66 You're right, my door starts moving nearly immediately. It's only the state as shown in the AC and UD Mobile app that is not timely. With this understanding about polling, it makes the most sense for me NOT to use the MyQ app to open the door but instead use my ISY whenever possible whether that's via the UD Mobile app or by a REST call to trigger the door through the portal. By the way, the link in the PG3 store for the MyQ Node server generates a 404 error as it points to https://github.com/Goose66/NSDocs/blob/main/MYQ-PG3.MD instead of the correct url: https://github.com/Goose66/NSDocs/blob/main/myq-pg3.md You might fix that store link and the link in your reply above too, since it has a trailing "." which also ends up as a 404 error as well. Thanks again!

I'm using to the MyQ Node server to open and close my garage door, set variables, trigger Blue Iris cameras and send me notifications. The status of the door as reported by the MyQ Node server has some peculiarities that noticed: Opening the door using ISY programs the status changes to "Opening" for about 10 seconds and then back to "Closed" for 10-20 seconds before it changes finally to "Open". Closing the door using ISY programs is similar. The status changes to "Closing" for about 10 seconds then back to "Open" for another 10-20 seconds before it changes finally to "Closed". When opening the door externally via the app, the status never shows "Opening" but reports "Closed" for 90 seconds or more before it reflects the "Open" status. Similarly, when closing the door via the app, the status never shows "Closing" but reports "Open" for a minute or more before it reflects the "Closed" status. I have the short poll set the default of 10 seconds and 60 for the long poll. My question is what the recommended poll setting to have the timely status updates? Also, what are best practices, recommendations, lessons learned, or examples for programs to have variables, cameras, notifications quickly let me know if the door is open (or opening/closing) and then again when the door is closed? Thanks!

I may not have solved this but at least I've got it down to only the "Stopped" not sticking in the AC issue. I was running two instances of the PG3 Volumio Node server - one attached to my ISY94i and the other to IoP for testing. I uninstalled all instances and reinstalled only one (2.03) attached to my production ISY94i. I'm now on the same page as what you're seeing @bpwwer. All sections are reporting the correct status. @kzboray I cannot reproduce the error you're seeing in the Volumio Android app.

I have experienced these same things. I'm talking about the upper status display. I seldom look at the lower section since I've found it not reliable indication of status on many node servers. Here's an example side-by-side AC and the Volumio UI, paused, repeat and shuffle on:

I confirmed both are fixed through the Volumio UI. I discovered the status of both Shuffle and Repeat in ISY does not show the current status. Shuffle always shows "Off" and Repeat always show "On". The other thing I noticed that when stopped State doesn't show "Stopped" but shows "Paused" instead. Thanks for addressing the shuffle issue so quickly!

I don't turn off shuffle too often but today I tried and noticed that it didn't work. No matter what I select, shuffle stays on. In the log it seems to show that the value on cmd=random is set to true when I select shuffle off or on: 2022-03-20 17:23:43,626 Command udi_interface DEBUG player:process_cmd: ISY sent: {'address': 'volumio_18', 'cmd': 'SHUFFLE', 'value': '0', 'uom': '25', 'query': {}} 2022-03-20 17:23:43,627 Command udi_interface DEBUG player:send_command: sending: http://10.42.8.18/api/v1/commands?cmd=random&value=true 2022-03-20 17:23:43,728 Command udi_interface DEBUG player:send_command: send_command retuned: {"time":1647815023679,"response":"random Success"} 2022-03-20 17:24:02,979 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2022-03-20 17:24:02,981 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2022-03-20 17:24:02,982 Command udi_interface DEBUG player:process_cmd: ISY sent: {'address': 'volumio_18', 'cmd': 'SHUFFLE', 'value': '1', 'uom': '25', 'query': {}} 2022-03-20 17:24:02,982 Command udi_interface DEBUG player:send_command: sending: http://10.42.8.18/api/v1/commands?cmd=random&value=true 2022-03-20 17:24:03,170 Command udi_interface DEBUG player:send_command: send_command retuned: {"time":1647815043068,"response":"random Success"} When I entered http://10.42.8.18/api/v1/commands?cmd=random&value=false in a browser, shuffle turned off. The Node server is on version 2.0.2 Polyglot is on version 3.0.48 ISY version is 5.3.4

I'm trying to set it up for Weewx and am seeing the disappearing nodes as well.

Here's another idea that I've used: Break it into two programs. First one sets a state variable to 1 when the motion sensor is on (or, if you want, control is on). Second one sends the message when the state variable is 1 and then waits (as long as you want) before setting the variable back to 0. That way you can test the notice by manually setting the variable to 1 and separately watch the variable turn to 1 when you set off the motion detector. Here's what it would look like: Program1 - If 'Sensor Z006 / Motion' Status is On Then $State_01 = 1 Else - No Actions - Program2 - If $State_01 is 1 Then Send Notification to 'Email' content 'Alert' Wait 1 minute $State_01 = 0 Else - No Actions -

Not sure why the status would fluctuate like that but try Control instead of Status to get your trigger even. Status is a state and the program then is only true when it is on. As soon as it goes off the program is no longer true and the then will stop.

There's nothing like trace that I'm aware of. If you click [Test] on the SLPPhone Group on the Configuration > Email/Notifications > Settings/Groups tab, do you get the test message?

Since I already own TImedata, I pulled the screen from another nodeserver as an example. Sorry if that's not true for Timedata.

I'm getting the Authentication Error too. I can't speak for the developer, @glarsen, but I can tell you the PG3 version works. The instructions are the same as the versions that runs on Polyglot (Raspberry Pi) , Polisy (Polyglot V2) and Cloud (PGC): You can always try it under the trial license that pops up after you click the Purchase button in the store:

Enjoy your vacation. I have moved to the Kasa NodeServer on Polisy V3 but pulled up the Network Resources I used prior just to compare and mine looks the same except I have timeout set to 1,000 but 500 works as well (YMMV): Since the Network Resources still work, below is the response I get when I test them (both on and off have the same response):

UDI Mobile is a different app entirely (see link below). I don't see it in the Google Play store either.

I was just considering mounting my Polisy today.

I renewed two today (Kasa and NOAA) and received an authentication error afterwards. I did receive the receipts from UDI on both and they both work but they are still showing the Renew button under Purchases.