rccoleman

The occupancy node is just a node controlled by the Portal that you can change by sending a REST call. You still need an app to make that REST call based on your location. I use Locative for that. There’s an Android app that UDI commissioned to do that, but I don’t think there’s an equivalent iOS app at this time.

Which app are you using to trigger the occupancy node? I'm using Locative and it's working fine on both an iPhone X and XS Max running iOS 12.0. No changes required.

I think this started to be a problem with the migration to the ISY Launcher, which dynamically downloads the admin/dashboard version required. Going back to the old way, as @MWareman describes, is the workaround.

@BigRic Make sure you have a good, recent backup. I had to pull the power on my ISY a few times due to lockups and it eventually started corrupting (truncating) files. Once that happens, future backups will fail, and you'll either need to solve the problem yourself (replace the file from an older backup, like I did) or you may just lose all recent changes.

I don't really know how to answer that, other than to provide the log. The only thing that I see is that the Z-Uno temp sensor, which is asynchronously reporting it's temperature every 5 seconds until it reaches the target temp, all seem to be bunched together. That's a little weird because I can usually watch it report at 5 second intervals, so I don't know what might have caused them to all be reported at once (other than the other discussion that we're having in the other thread, perhaps). To be clear, I set a parameter that tells the temp sensor to start reporting at 5 second intervals when I want hot water, and I tell it to stop when it reaches the right temp (between 1 and 3 mins). I bolded the line around the first "queue full" line in the error log. I'm just surprised that it didn't recover eventually and keeps spewing errors in the error log.

Yes, the Alexa app indicates that the Echo heard the right thing every time. The error log does appear to be interesting. I started getting these errors right around the time of the failed Alexa commands, and they're actually continuing through today, despite the fact that my Alexa commands and everything else is working fine. Mon 2018/09/03 08:15:57 AM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 33 Mon 2018/09/03 08:16:15 AM System -170001 [UDSockets] HTTP:29 error:6 Mon 2018/09/03 11:50:45 AM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 32 Mon 2018/09/03 11:52:21 AM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 33 Mon 2018/09/03 03:34:54 PM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 32 Mon 2018/09/03 04:15:00 PM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 33 Mon 2018/09/03 09:29:50 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 06:52:32 PM System -5012 96 Mon 2018/09/03 09:24:52 PM System -170001 [UDSockets] RSub:22 error:6 Mon 2018/09/03 09:24:57 PM System -5012 87 Mon 2018/09/03 09:30:01 PM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 32 Mon 2018/09/03 09:35:01 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 09:35:37 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 09:41:09 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 09:52:12 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 09:52:54 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 09:53:04 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 09:53:14 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 09:53:25 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 09:53:35 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 09:53:56 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 09:54:06 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 09:54:16 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 09:55:09 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 09:55:19 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 09:55:29 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 09:57:30 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 09:57:40 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 10:03:54 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 10:04:04 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 10:04:14 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 10:03:04 PM System -5011 uuid:0 Mon 2018/09/03 10:04:27 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:04:32 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:04:38 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:04:43 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:04:49 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:04:54 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:04:56 PM System -5006 uuid:0 Mon 2018/09/03 10:05:00 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:05:05 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:05:11 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:05:16 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:05:22 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:05:27 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:05:33 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:05:38 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:05:44 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:05:49 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:05:55 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:06:00 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:06:06 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:06:11 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:06:17 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:06:22 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:06:36 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 10:06:29 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:06:34 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:06:39 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:06:44 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:06:46 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 10:06:56 PM System -170001 UDQ: Queue(s) Full, message ignored Mon 2018/09/03 10:06:49 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:06:55 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:07:00 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:07:06 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:07:07 PM System -5006 uuid:0 Mon 2018/09/03 10:07:15 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:07:21 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:07:26 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:07:32 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:07:37 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:07:43 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:07:48 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:07:54 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:08:00 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:08:05 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:08:11 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:08:16 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:08:17 PM System -5006 uuid:0 Mon 2018/09/03 10:08:22 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:08:27 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:08:33 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2018/09/03 10:08:38 PM System -170001 [UDSockets] PSub:42 error:6 I'm still getting these "error:6" messages every 5-10s this morning. Is that the connection to the portal? At the time, and even now, the portal lists my ISY as online. Here's the tail end of the error log: Wed 2018/09/05 09:02:07 AM System -170001 [UDSockets] PSub:42 error:6 Wed 2018/09/05 09:02:12 AM System -170001 [UDSockets] PSub:42 error:6 Wed 2018/09/05 09:02:17 AM System -170001 [UDSockets] PSub:42 error:6 Wed 2018/09/05 09:02:22 AM System -170001 [UDSockets] PSub:42 error:6 Wed 2018/09/05 09:02:27 AM System -170001 [UDSockets] PSub:42 error:6 Wed 2018/09/05 09:02:32 AM System -170001 [UDSockets] PSub:42 error:6 Wed 2018/09/05 09:02:37 AM System -170001 [UDSockets] PSub:42 error:6 Wed 2018/09/05 09:02:42 AM System -170001 [UDSockets] PSub:42 error:6 Wed 2018/09/05 09:02:47 AM System -170001 [UDSockets] PSub:42 error:6 Wed 2018/09/05 09:02:52 AM System -170001 [UDSockets] PSub:42 error:6 Wed 2018/09/05 09:02:59 AM System -170001 [UDSockets] PSub:42 error:6 Is there any more useful data to be collected on the ISY for this? I'm tempted to reboot to get it out of whatever state it's in, even though it seems to be working.

The issue with ‘good morning’ turned out to be self inflicted when I ‘forgot’ all of my devices and rediscovered them the night before in an attempt to fix the ‘not responding’ issue. That erased the actions in all of my routines and I had to add them back. That’s working now. I really don’t think this is a connectivity problem. I’m using a fully updated, high quality pfSense router and there was no evidence of connectivity issues at the time. In any case, it hasn’t recurred and I’ll do more investigation if it happens again.

This was pretty bad last night and this morning, to the point that I ended up using the keypad in my bedroom instead. Last night, I kept getting "Downstairs lights are not responding" over and over again with it not actually turning off the lights, and then it finally worked after 10-15 mins or so. In the morning, it acted like it recognized "Good Morning", but did nothing over several attempts. I eventually just hit the keypad button that runs the exact same program and it worked immediately. Has anyone else had issues with Alexa in the last 12-24 hours? None of my devices are showing "offline" at alexa.amazon.com, and weren't last night.

This works great. Highly recommended.

If it works like other geofence apps, which are based on the OS location service, it uses cell geolocation to get a rough approximation and to see if GPS is necessary for a more granular result. I use location-based reminders and Locative on my iPhone every day and it doesn’t meaningfully affect my battery life.

You mean outside of the beta? It may still be available as part of the beta.

Interesting! I had both an online and an offline version of "bathroom sink", so I forgot the offline version and I'll keep an eye on it. Thanks for the tip.

I just had this happen again. I said ‘turn on the bathroom sink’, my hot water recirculator turned on as programmed, the Echo’s light ring spun for several more seconds, and then the Echo said ‘sorry, I can’t find a device named bathroom sink in Robert’s profile’. Like before, the command worked, but I also got an error message that doesn’t make any sense. I confirmed that the Echo heard the right command by reviewing the history in the app. This is after unlinking and relinking the v3 skill, and discovering devices, which I did a month or so ago.

I thought that I had saved an event log somewhere, but it looks like it was just the log and error log. Like I said, it would really helpful if I could just point the ISY at my local syslog server (my Synology NAS) and log events that way. For something that's so useful while debugging, they're quite ephemeral and easy to lose.

I considered that and did a heal, but it didn’t help. I then unplugged and plugged back in the sirens that act as repeaters, re-ran the heal, and it still didn’t help. Hopefully all of that is still in the log. I’ll see if I can find anything. Heals tend to show a number of failures because almost all of my Z-Wave devices are battery-operated and fail to wake up for the heal. I have several gen 5 sirens that form the mesh and don’t see a connectivity problem outside of this instance. Edit: I do see the heal attempts in the log and error log, but no indication of any device failures. Is any interesting information Event Viewer lost by rebooting the ISY later? Event Viewer history goes back to when I opened the admin console last night, after I had everything working again. If I could log Event Viewer messages to my syslog server, it would make it a lot easier to capture these failures. The heal shows up in my error log like this: Thu 2018/08/16 05:42:07 PM System -170001 <s:Envelope><s:Body><u:HealNetwork xmlns:u="urn Thu 2018/08/16 05:42:07 PM System -170001 [HTTP:0-41]: POST[1]-->/services Thu 2018/08/16 05:42:07 PM System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u= Thu 2018/08/16 05:42:26 PM System -170001 [HTTP:0-29-5] 192.168.1.244:35162->80 But at the time, it seems to proceed as expected and it completed. I tried it several times without a change to the "route can't be found" message for only my secure devices.

I just had a really weird thing happen. My various Z-Wave locks, motion sensors, etc. have been working fine with the new dongle and 5.0.13C for a while, but today they all stopped working. The event viewer log for each one showed the ISY trying to wake it up, it failed to get a response, retried a few times, and gave up. I rebooted my ISY and that brought the non-secure devices back (a temp sensor and my motions sensors started working), but my three Kwikset locks still failed with the same symptom. I did a "Show all info" on each one and all returned what looked like good data, but it said that the last known route couldn't be found for each one. I manually pulled the power on the ISY for 30s or so, powered it back on, and it was still giving inaccurate route info. I restored the Z-Wave backup that I made the last time I added a device, rebooted the ISY, and now everything is working again (including proper route information for my locks). So, I recommend making a Z-Wave backup right now if you haven't already, but I don't really know what happened in my case. @Michel Kohanim Is there something interesting that I can look for in my error log? There's a lot in there and I can't really tell what's important.

It's a standard Wiki feature that lets users discuss the page contents. Here's an example on Wikipedia:

That would depend on the capabilities and settings of your sensors. My motion sensors default to sending an ‘off’ command after 2 min, but I reconfigure them to only send ‘on’ when they see motion and never ‘off’. This keeps the lights on as long as I’m in the room, and I use a program to start a timer to turn the lights off whenever they turn on. That way, you get the best-instant on with a more flexible ‘off’ program. Edit: and to be clear, there’s no way to code any sort of timer logic into the scene itself. It’s just going to react to what your motion sensors do.

I can't speak to the spontaneous reboot (nothing on my box), but perhaps the strange responses from your Google Home device are related to similar ones from Amazon Echos/Dots: I unlinked and relinked my Smart Home skill and I've gotten a "not responding" once after a long delay.

Yep, just like that. You need to finesse the old board out because the LED protrudes a bit through the case and resists extraction, but the new board does not have an LED and is an easier fit.

Mine came with nothing but the board in an envelope. Yes, you need to unscrew the case of the ISY, pull out the board, remove the old Z-Wave module (connected via a row of pins plugging into the main board horizontally) and plug the new module into the lower-row of the connector on the main board. The Z-Wave board and the main board should be on the same plane when you're finished. Edit: Obviously unplug everything from the ISY first

That confused me too. It stores it internally and restores from the saved file - you’ll never see it.

If you are interested, please send an email:To: sales@universal-devices.comSubject: Z-Wave 500 Series BetaBody: Your address

Done, and will report back. May take a few days or even a week to know for sure.

I just enabled ‘brief mode’ on Friday after being prompted, and this was happening well before that for me.