landolfi

I'm definitely using 2.0, but the PIN looks like a relic of a previous UD Mobile version. Something is definitely wrong with my Locative setup, because the ISY Portal and admin console will update properly if I send the in and out URLs from a browser, so thanks for that tip. I'm copying and pasting the URL twice to get it into Locative, so something may be getting lost in translation or I'm picking up some extraneous characters.

It’s definitely the portal config, it’s not updating. This is after I decided to try starting over. So here’s what I’ve done: 1. Created and uploaded node definition. 2. Created a geofence and a device and assigned the device to the geofence. 3. Copied the in and out geofence URLs and pasted them into GET on Locative (but maybe this should be POST?) I noticed there is a link to generate a PIN for UD Mobile but I don’t see any place to enter it in UD Mobile, so maybe that’s obsolete? Anything else I need to do?

Thanks for the reply. My question is specifically how to get Locative to change the IoX node status. Locative is using the ISY portal URLs and the portal correctly shows in and out of geofence but the admin console never updates for some reason.

Same situation here with wanting to use Occupancy 2.0. I upgraded from Polisy to eISY and I configured in ISY portal. I have nodes in IoX (5.7.0) with On and Off, although I'm not sure what On and Off mean in this context. Anyway, both Locative and ISY portal accurately reflect going in and out of geofence, but IoX doesn't seem to get updated, it is always showing True even when I'm away. Any ideas what could be wrong? EDIT: I realized after posting this that it's probably in the wrong place. @admin (@Geddy?), please move as appropriate. I put it here because it was the only recent reference to Occupancy 2.0 I could find.

Hi @Panda88, can you please take a look at the logs above from my Blink NS setup and tell me if there's anything I need to do?

Thanks, Bob. It was working before the crash and I don’t think the version has changed but I did just reinstall it so maybe it’s a setup issue.

Here's the entire log in debug mode with sanitized credentials. Blink_10-5-2023_90003-AM.zip

Hi, Setting up Blink node server after a system crash that wiped out all my configurations. I know the username and password are correct, but no nodes show up. The log in Debug mode only shows the following. I assume if there were an authentication issue we would see it here? 2023-10-04 19:34:38,802 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-10-04 19:34:38,804 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-10-04 19:34:38,806 Thread-25 udi_interface INFO udiBlinkController:systemPoll: System Poll - Waiting for all nodes to be added 2023-10-04 19:35:38,834 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-10-04 19:35:38,836 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-10-04 19:35:38,838 Thread-26 udi_interface INFO udiBlinkController:systemPoll: System Poll - Waiting for all nodes to be added 2023-10-04 19:36:38,835 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-10-04 19:36:38,837 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-10-04 19:36:38,839 Thread-27 udi_interface INFO udiBlinkController:systemPoll: System Poll - Waiting for all nodes to be added 2023-10-04 19:37:38,838 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-10-04 19:37:38,838 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-10-04 19:37:38,839 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-10-04 19:37:38,839 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-10-04 19:37:38,841 Thread-28 udi_interface INFO udiBlinkController:systemPoll: System Poll - Waiting for all nodes to be added 2023-10-04 19:37:38,841 Thread-28 udi_interface INFO udiBlinkController:systemPoll: System Poll - Waiting for all nodes to be added 2023-10-04 19:38:38,840 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-10-04 19:38:38,840 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-10-04 19:38:38,842 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-10-04 19:38:38,842 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-10-04 19:38:38,843 Thread-29 udi_interface INFO udiBlinkController:systemPoll: System Poll - Waiting for all nodes to be added 2023-10-04 19:38:38,843 Thread-29 udi_interface INFO udiBlinkController:systemPoll: System Poll - Waiting for all nodes to be added

This all sounded promising until I read that I need a special USB cable that I don't have, will have to order for $20, and wait several days to get, and then spend at least another half hour on an SSH session with or without UD. 2 months ago, the 5.6.3 update hosed my Zwave. I spent 2 hours on the phone with UD support and another 5 or 6 adding all the devices back and modifying programs. I didn't even want the 13.2 update because I knew bricking was a possibility on Polisy, but Update Packages doesn't give a choice of what gets updated. So you might imagine my frustration now that I am here again with a non-functioning Zwave network. This time I can't even use my Insteon devices or node servers, and best case is I'm offline for several days.

Thanks for this! What were the implications, did you have to rebuild anything?

For anyone who hasn't yet upgraded to 13.2, I have a dead Polisy here after the update. Completely unresponsive after multiple power cycles and attempts to reset with the MFB. IoX and Portal don't see it and I can't SSH to it, but it does have an IP and it responds to pings. I opened a ticket but I don't know how UD can help in the short term if I can't connect to the box. Looks like I may be moving everything to Home Assistant, painful as that will be with all the Zwave devices I have. I love to tinker, but I'm getting tired of having to recover from official updates.

I rebooted and did Reinstall Here. Now the Yolink NS shows as 0.9.63 but still disconnected, and Start results in "Node Server Start: Already running".

Does this help? It's from the PG3 log. 10/2/2023, 18:43:30 [pg3] info: startNs:: YoLink 10/2/2023, 18:43:30 [pg3] info: startNs:: YoLink is valid 10/2/2023, 18:43:30 [pg3] info: checkLicense:: YoLink Valid perpetual license found. 10/2/2023, 18:43:30 [pg3] info: startNs:: YoLink finished update check 10/2/2023, 18:43:30 [pg3] info: Received commands on topic udi/pg3/frontend/system/admin: getStoreEntry 10/2/2023, 18:43:30 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:5d:9b:24] :: - http://127.0.0.1:8080/rest/nodes/n002_8b4c010004a629 10/2/2023, 18:43:30 [pg3] info: IoX Response: [Try: 1] [00:0d:b9:5d:9b:24] :: [200] :: 14.191932ms - http://127.0.0.1:8080/rest/nodes/n002_8b4c010004a629 10/2/2023, 18:43:30 [pg3] info: Getting Node Server store entry for nsid 78312440-23ea-4ed6-9361-9cdc2d5e7c6b from store Production 10/2/2023, 18:43:30 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:5d:9b:24] :: - http://127.0.0.1:8080/rest/nodes/n002_8b4c01000560b0 10/2/2023, 18:43:30 [pg3] info: IoX Response: [Try: 1] [00:0d:b9:5d:9b:24] :: [200] :: 12.402224ms - http://127.0.0.1:8080/rest/nodes/n002_8b4c01000560b0 10/2/2023, 18:43:30 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:5d:9b:24] :: - http://127.0.0.1:8080/rest/nodes/n002_8b4c010005ad2c 10/2/2023, 18:43:30 [pg3] error: IoX Response: [Try: 1] [00:0d:b9:5d:9b:24] :: [404 - OK] :: 10.028043ms - http://127.0.0.1:8080/rest/nodes/n002_8b4c010005ad2c 10/2/2023, 18:43:30 [pg3] error: [00:0d:b9:5d:9b:24_2] getNode failed :: TypeError: Cannot read properties of undefined (reading 'data') 10/2/2023, 18:43:30 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:5d:9b:24] :: - http://127.0.0.1:8080/rest/nodes/n002_8b4c010005dea5 10/2/2023, 18:43:30 [pg3] info: IoX Response: [Try: 1] [00:0d:b9:5d:9b:24] :: [200] :: 11.314377ms - http://127.0.0.1:8080/rest/nodes/n002_8b4c010005dea5 10/2/2023, 18:43:30 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:5d:9b:24] :: - http://127.0.0.1:8080/rest/nodes/n002_8b4c0100060595 10/2/2023, 18:43:30 [pg3] error: IoX Response: [Try: 1] [00:0d:b9:5d:9b:24] :: [404 - OK] :: 10.395288ms - http://127.0.0.1:8080/rest/nodes/n002_8b4c0100060595 10/2/2023, 18:43:30 [pg3] error: [00:0d:b9:5d:9b:24_2] getNode failed :: TypeError: Cannot read properties of undefined (reading 'data') 10/2/2023, 18:43:31 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:5d:9b:24] :: - http://127.0.0.1:8080/rest/nodes/n002_8b4c020002abcf 10/2/2023, 18:43:31 [pg3] info: IoX Response: [Try: 1] [00:0d:b9:5d:9b:24] :: [200] :: 11.807533ms - http://127.0.0.1:8080/rest/nodes/n002_8b4c020002abcf 10/2/2023, 18:43:31 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:5d:9b:24] :: - http://127.0.0.1:8080/rest/nodes/n002_8b4c020002abd0 10/2/2023, 18:43:31 [pg3] info: IoX Response: [Try: 1] [00:0d:b9:5d:9b:24] :: [200] :: 11.193565ms - http://127.0.0.1:8080/rest/nodes/n002_8b4c020002abd0 10/2/2023, 18:43:31 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:5d:9b:24] :: - http://127.0.0.1:8080/rest/nodes/n002_8b4c020002b231 10/2/2023, 18:43:31 [pg3] info: IoX Response: [Try: 1] [00:0d:b9:5d:9b:24] :: [200] :: 11.177191ms - http://127.0.0.1:8080/rest/nodes/n002_8b4c020002b231 10/2/2023, 18:43:31 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:5d:9b:24] :: - http://127.0.0.1:8080/rest/nodes/n002_8b4c020002f11b 10/2/2023, 18:43:31 [pg3] info: IoX Response: [Try: 1] [00:0d:b9:5d:9b:24] :: [200] :: 11.447724ms - http://127.0.0.1:8080/rest/nodes/n002_8b4c020002f11b 10/2/2023, 18:43:31 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:5d:9b:24] :: - http://127.0.0.1:8080/rest/nodes/n002_8b4c0200031535 10/2/2023, 18:43:31 [pg3] info: IoX Response: [Try: 1] [00:0d:b9:5d:9b:24] :: [200] :: 11.242035ms - http://127.0.0.1:8080/rest/nodes/n002_8b4c0200031535 10/2/2023, 18:43:31 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:5d:9b:24] :: - http://127.0.0.1:8080/rest/nodes/n002_setup 10/2/2023, 18:43:31 [pg3] info: IoX Response: [Try: 1] [00:0d:b9:5d:9b:24] :: [200] :: 10.842269ms - http://127.0.0.1:8080/rest/nodes/n002_setup 10/2/2023, 18:43:31 [pg3] info: startNs:: Starting YoLink 10/2/2023, 18:43:31 [pg3] info: call_udx: Making request to socket with url /rest/pg3.start.ns 10/2/2023, 18:43:31 [pg3] info: startNs:: YoLink starting polls 10/2/2023, 18:43:31 [pg3] info: Starting YoLink Info timer 0 10/2/2023, 18:43:31 [pg3] info: startNs:: YoLink updating database (enabled, timestarted) 10/2/2023, 18:43:31 [pg3] info: startNs:: YoLink started. 10/2/2023, 18:43:31 [pg3] info: Received commands on topic udi/pg3/frontend/system/admin: getStoreEntry 10/2/2023, 18:43:31 [pg3] info: Getting Node Server store entry for nsid 78312440-23ea-4ed6-9361-9cdc2d5e7c6b from store Production 10/2/2023, 18:43:33 [pg3] info: Received commands on topic udi/pg3/frontend/ns/admin: startLogging 10/2/2023, 18:43:33 [pg3] info: Is client running? /var/polyglot/pg3/ns/000db95d9b24_2/logs/debug.log does not exist. 10/2/2023, 18:43:40 [pg3] info: Received commands on topic udi/pg3/frontend/ns/admin: setLogLevel 10/2/2023, 18:43:40 [pg3] info: Received commands on topic udi/pg3/frontend/system/admin: getStoreEntry 10/2/2023, 18:43:40 [pg3] info: Getting Node Server store entry for nsid 78312440-23ea-4ed6-9361-9cdc2d5e7c6b from store Production 10/2/2023, 18:43:41 [pg3] error: downloadLog: Error: File not found: /var/polyglot/pg3/ns/000db95d9b24_2/logs/debug.log at Object.addLocalFile (/var/polyglot/node_modules/adm-zip/adm-zip.js:258:23) at /var/polyglot/node_modules/@universaldevices/pg3x/lib/routes/log.js:94:16 at async /var/polyglot/node_modules/@universaldevices/pg3x/lib/services/https.js:48:9 10/2/2023, 18:43:46 [pg3] info: Received commands on topic udi/pg3/ns/command/00:0d:b9:5d:9b:24_

I tried Reinstall Here, Stop/Start, and Restart. Version still shows 0.8.99 and Disconnected.

I'm quoting myself because this same Sengled RGBW bulb became unresponsive today with 5.7.0 after working for over a month. I decided to delete it and move it to Home Assistant where I already have Zigbee devices running.

Was about to say the same, except shortly after the reboot following the update I noticed all programs disabled. Not a problem for me because all programs except 4 were originally enabled, but I haven't yet checked to see if the re-enabling survives a restart.

Does "Zigbee occupancy cluster" referred to in the release notes include the Tuya mmWave Presence Sensor (ZY-M100)?

Just FYI, HA myQ users in the East region are still reporting trouble with this 403 error on the myQ integration to Home Assistant, so if you're in an area served by the East myQ servers, it is possible it could turn out to be nothing to do with the NS and it will just start working soon on its own, although since it's a node server you might need to restart when it does start working again. I don't know how to tell what region I'm connecting to, but since my HA integration is working, there's a good chance I'm connecting to the West.

I'm in Chicagoland, the HA MyQ integration is rock solid since yesterday at this time. Maybe something else needs to be done to reset the NS, or maybe we're in different regions and yours isn't fixed yet.

Where are you located? Last I heard there were still some people who couldn't get in, but the theory was that the load balancing was only fixed for certain regions. I'm most likely in US-East.

I don't use the MyQ node server but the Home Assistant integration, which was similarly not working, is now. There have been no updates to the integration, implying as discussed above that the issue was on the MyQ side.

In the latest discussion on Github about this problem, which is also occurring on the MyQ Home Assistant integration, a Homebridge MyQ developer says that this is the result of a load balancing issue at MyQ: https://github.com/home-assistant/core/issues/99947#issuecomment-1712966435

The Hue setting uses the 360 color wheel: https://dawnsbrain.com/the-rgb-color-wheel/ I don't understand saturation but I'm using 80%, it doesn't seem to differ much from higher saturations. Beyond that, I am mystified by the other controls.

For me the main limitation if you can call it that was the price, but it looks like that was reduced. On the other side of your question, what does the node server do for me that the node.js implementation doesn't? One thing I can think of offhand is not having to monitor the node.js instance on a separate server. In my case, all I use it for is to play clips in response to sensor events.

I think you should be using GET instead of POST. Here's a working NR that plays a clip when my mailbox motion sensor detects motion: