gzahar

After updating I am not able to control the door or light. If I try to turn light on or off the status shows as changed but the light doesn't actually change. Door control won't operate door (or change it's status). I deleted, re-installed, re-discovered; but no difference. Status of door, light, obstruction and motion all show properly when triggered by other means.

You might try these threads:

And make sure the GPS app is allowed to always use your location, not just when you use the app. Although this setting usually doesn’t result in delayed crossings, but misses them altogether. Could depend on the app though.

That may not be a feature available in the visual editor. You might have to do it manually in the YAML editor. Not something I am familiar with. If you can create something similar with another entity and then change the entity to your state variable by editing in YAML, that might be your best bet (unless someone here knows more about HA).

You might check out this thread:

The program will evaluate the conditions anytime one of them changes and run Then or Else depending on the state of the conditions. The one exception is an integer variable which will not cause a program to run when it changes. In you example (assuming the variable is a state variable and you mean 2am the next day) your program will run (then or else) when the variable changes value (setting it to the same value will not cause execution) and at 10 pm and 2 am. So yes, if the variable is 1 at 10 pm it will execute the Then statement(s). At 2am (the next day), if the variable is 1 it will run the Else statement.

Have you tried: If From Sunset to Sunrise the next day And state variable = 1 Then Turn on lights

It would be nice if the Light (and any future nodes) could be grouped under the door device. Thanks, great plugin!

That's nice. Sounds like the 2.0 plugin works differently.

I have been using the Occupancy node server (not 2.0) and the built in nodes/logic it creates for some time. The one problem (at least for that version) is after a reboot the nodes are all undefined until the geo-fences are crossed again (and the main Home node doesn't initialize until all devices go to an away state). This can cause erratic behavior in programs that use those nodes. To get around this, I ended up creating the state variables as @dbwarner5 mentions and using an inti value to holdover during reboots to get around this. Works much better now.

I understand it may be needed for other reasons, but it seems some in this thread were adding just because others had and not because they needed to. Obviously I don't know that for sure, but thought I would mention it just in case.

I don't see where a separate SSD is required for this (maybe I missed it). Given audio files shouldn't be that large, I would try creating a sound directory somewhere on the exiting storage file system.

Because when you open and close the door manually it updates the integer variable which will not trigger your open and close programs. Obviously you will need to manually close the door after you have opened it (and vice versa). Your auto open and close programs will only trigger based on the temperature state variable changes.

You need to create an integer variable the represents the state of the door. Update this variable based on YL Door State (in separate program). Use this variable in the IF statement of your open and close programs and not the direct YL Door State.

Another option that I have used in the past. If you are using PG3 and have any spare IoT devices (webcams, etc.) that respond to pings, you can monitor communications to that device using the ping plug-in. This moves query traffic off the Insteon network.

This may be a good two program solution (continually setting a state variable to the same value will not trigger a program execution): Program freeze warning 1 If Your first weather condition Or Your second weather condition Then Set "freeze warning state variable" to 1 Else Set "freeze warning state variable" to 0 Program freeze warning 2 If "Freeze warning state variable" =1 Then Send notification 'xxx' Resource 'Freeze warning message' Else (optional) Send notification 'yyy' Resource 'Freeze warning over message'

Thinking about the two programs some more; if the weather conditions keeps changes in less than 5 minutes, it will continually restart the 2nd program so you will never get the notification (until/if it stops changing). That does eliminate getting the messages twice though! But you probably want the message when it first hits the threshold though.... Edit: Based on OpenWeatherMap info, data shouldn't change in less than 10 minutes. Short Poll How often to poll the OpenWeatherMap weather service. Note that the data is only updated every 10 minutes. Setting this to less may result in exceeding the free service rate limit.

How often does the forecast node change values? Even with a 5 minute wait, you're still going to continue to get emails every time the value changes. (albeit maybe 5 minutes apart). 25, 24.5, 23, 22, etc. You probably need to set another variable that indicates notification sent (which should also disable further notifications) and then reset it once it's above freezing so it sends again next time below your threshold.

To my understanding, the ‘responding’ statement does not generate a query. You need to do that in another program in a loop of your decision. Keep the ‘responding’ program, but remove any other criteria (>= 3) and no need for a wait. I believe the responding state will be set to false anytime the device fails to reply to any command; on, off, query, etc. I don’t know what it is, but there should be a timeout built in to the protocol or IoX firmware that declares how long after no response from a command it waits before declaring a device as not responding. I also assume that as soon as the device replies to a later command it is declared responding again.

Looking over my notifications, I did get a Failed followed by Connected status for the plugin 3 times today. The PG3x Ecobee logs show roughly the same error each time (different from the error I shared above): 2024-01-12 11:06:21,137 MQTT udi_interface.interface ERROR interface:_startMqtt: MQTT Connection SSLError: EOF occurred in violation of protocol (_ssl.c:2488), Will retry in a few seconds. Traceback (most recent call last): File "/var/polyglot/pg3/ns/000db952c168_13/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 567, in _startMqtt self._mqttc.loop_forever() File "/var/polyglot/pg3/ns/000db952c168_13/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1756, in loop_forever rc = self._loop(timeout) File "/var/polyglot/pg3/ns/000db952c168_13/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1181, in _loop rc = self.loop_write() File "/var/polyglot/pg3/ns/000db952c168_13/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1577, in loop_write rc = self._packet_write() File "/var/polyglot/pg3/ns/000db952c168_13/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 2464, in _packet_write write_length = self._sock_send( File "/var/polyglot/pg3/ns/000db952c168_13/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 649, in _sock_send return self._sock.send(buf) File "/usr/local/lib/python3.9/ssl.py", line 1207, in send return self._sslobj.write(data) ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:2488) 2024-01-12 11:06:21,138 Thread-1 udi_interface.interface ERROR interface:_send: MQTT Publish Error: EOF occurred in violation of protocol (_ssl.c:2488) Traceback (most recent call last): File "/var/polyglot/pg3/ns/000db952c168_13/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 688, in _send self._mqttc.publish(topic, json.dumps(message), retain=False) File "/var/polyglot/pg3/ns/000db952c168_13/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1257, in publish rc = self._send_publish( File "/var/polyglot/pg3/ns/000db952c168_13/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 2693, in _send_publish return self._packet_queue(PUBLISH, packet, mid, qos, info) File "/var/polyglot/pg3/ns/000db952c168_13/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 3016, in _packet_queue return self.loop_write() File "/var/polyglot/pg3/ns/000db952c168_13/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1577, in loop_write rc = self._packet_write() File "/var/polyglot/pg3/ns/000db952c168_13/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 2464, in _packet_write write_length = self._sock_send( File "/var/polyglot/pg3/ns/000db952c168_13/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 649, in _sock_send return self._sock.send(buf) File "/usr/local/lib/python3.9/ssl.py", line 1207, in send return self._sslobj.write(data) ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:2488)

@Jimbo.Automates I'm seeing the same. This was in the PG3x logs (had level on Warning). I can send Plugin log package (info level) if needed. (or increase log levels) 1/12/2024, 24:00:19 [pg3] error: unhandledRejection REPORT THIS!: [object Promise], reason: Error: ENOENT: no such file or directory, access '/var/polyglot/pg3/ns/000db952c168_13/logs/debug.log' 1/12/2024, 03:30:20 [pg3] warn: IoX Response: [Try: 1] [00:0d:b9:52:c1:68] :: [null] :: 7.157462ms - http://localhost:8080/rest/ns/13/nodes/n013_t522635237731/report/status/ST/69.7/17 1/12/2024, 06:15:20 [pg3] warn: IoX Response: [Try: 1] [00:0d:b9:52:c1:68] :: [null] :: 7.195663ms - http://localhost:8080/rest/ns/13/nodes/n013_rs_lbzp/report/status/ST/67.7/17 Running 3.2.17, 5.8.0 w/o recent OS upgrade.

Did you see this: Custom Params change_node_names If set to true the IoX node nodes are changed to match the Kasa device names when the node server is restarted.

Post your program that is controlling the scene(s).

Ditto

sys.node.[node address].BATLVL Use the ZW/ZY address of the device. See: https://wiki.universal-devices.com/ISY-994i_Series:EMail_and_Networking_Substitution_Variables