@tony.fleisher , your fine app seems to have stopped working after the 2.2.9 update. Worked fine before with 2.2.8. Iāve tried rebooting. No errors in the logs. All devices are working, everything on Z-Wave Details seems right. Yes, the Z-Wave SDK seems to have been updated with the 2.2.9 update.
C-7 running 2.2.9.128
Z-Wave Radio/SDK: 7.14/7.15
Any suggestions? Iāve tried HPM Repair, same results.
Its working okay for me.
Perhaps I am just cursed. I just did the soft reset dance, results still as above.
Edit: Uninstalled Mesh Details, Reinstalled, now it works again. 
Only change to break it was 2.2.9 install yesterday.
First time I tried it yesterday after upgrading to 2.2.9 it was blank. Closed the app, and re-entered and everything was back...
My experience differed. I updated yesterday a couple hours after 2.2.9 was released, then checked Z-Wave details this morning after downloading a backup. Blank Mesh details (see screen shot above). I closed and opened the Mesh details several times, rebooted, did soft reset, did HPM repair, none of this helped. Only was able to fix after I uninstalled Mesh Details using HPM, then re-installed.
@672southmain Sorry you were having problems. I checked it a couple times during the beta and didn't see any problems. If you can reproduce this, please see if you can find errors in the browser console to help me troubleshoot it.
As I noted above, I tested various ways to fix the problem (see above posts), and was only able to resolve it by completely removing your app via HPM and then installing it back. āRepairā of the app via HPM, which should have overwritten the Groovy code, didnāt fix it. Seems to me that there must have been some state information that needed to be cleared.
Note above that @thebearmay had the same issue, but it cleared for him by closing the app and reopening. That didnāt work for me.
No errors whatsoever in the console, only the info and trace lines in the log (see above post). The only informative info that might be helpful to you is the āNo Search Panesā line in the screenshot above.
If it helps any, I have a very simple setup, no Hub Mesh with another hub (although I have 2 others). I was not a beta tester for any Hubitat firmware. Note that my Z-Wave Radio SDK firmware seems to have updated with the 2.2.9 update, so it may be related to that update process.
Itās a fine app, and I have never before had any issues whatsoever. I wouldnāt know how to reproduce because it just happened with the 2.2.9.128 update from 2.2.8, same cause as for @thebearmay. Works fine again after I removed then re-installed using HPM.
No issue for me.
Itās truly a nice app btw.
The only thing Iād doesnāt do that you can do in the zwave details screen is to click on a device and have it open a new tab and display that device page. Or maybe I am just missing how to do it.
Tony (@tony.fleisher), Iām still seeing it be hit-or-miss. Sometimes it loads the mesh details page, sometimes it doesnāt. 2.2.9.129 behaves pretty much like 2.2.9.128. About one time in 5 it works. Iām not seeing anything odd in the logs, Iāve tried with debug logging on and off. Iāve tried shutdown, power off, reboot. Iāve tried removing the app, doing a HPM new install, Iāve tried HPM Repair. Iāve tried soft Reset of the Hub. When it fails, it fails as in the screenshot I posted above, with the lines āNo SearchPanesā and āNo data available in tableā. See screenshot above.
Because itās so hit-or-miss, I really canāt correlate the successful operation with any actions taken to troubleshoot / repair. Makes me almost think itās some sort of a timing issue.
Even when it fails, the Z-Wave Topology display is always correct.
I have a very simple setup. 8 repeaters (6 Ring Gen 2, 2 Aeotec Extender 7) and about 15 Z-Wave plus devices.
Here are log entries for a successful display of the details, close the window, hit Done back to Apps page, then re-launch app, display mesh details with fail.
Never saw this with 2.2.8 or before, ever since your Mesh Details was initially released.
@672southmain Ok. Thanks for the update. I will see if i can reproduce this. Since most of the work is done in the browser, the hub logs are not going to show any problems. For this we will need to get the console logs from the browser. (in chrome this is found in More Tools -> Developer Tools)
Ok, I will gather some logs. It still has the same behavior in 2.2.9.130, only works about 1 in 5 times. All the other troubleshooting efforts described above seem to be red herrings, and it doesnāt matter whether mesh details are in same window or new window. When it fails, I just back out with Done to Apps page, re-launch app, click Mesh Details button, and, 1 out of 5 times or so it will work. The failure mode is always the same, as shown in screenshots and log snippets above. When the Mesh Details window shows, all details are perfect. Iām starting to believe itās related to the Z-Wave SDK update that occurred with 2.2.9, because I believe I was able to reproduce if I roll back to 2.2.8. Again, Iāll gather browser console logs.
I played around with this a bit and was not able to easily re-create with current versions of Safari/Firefox/Brave.
Can you go to the app, click on the gear icon, and post the settings and state?
Two other questions come to mind... Do you have hub login security enabled? And are you using HTTP or HTTPS?
I genuinely appreciate the help that everyone is providing to track this down. I have now tested on multiple platforms and browsers, and can report some results. Looks like a browser issue, as @tony.fleisher suspects.
Responding to questions and requests out of order:
No. HTTP.
Sure, but I don't think that provides interesting information. Here is the configuration (default) and the Status page:
Now for the testing results. Previously, all of my testing above was on my iPad, where I saw the issues.
Again, in all cases, Hubitat C-7 with 2.2.9.130 (saw identical results on 2.2.9.128 & 2.2.9.129). No Hubitat beta versions were ever installed. The Z-Wave Radio/SDK were updated to 7.14/7.15 with 2.2.9.x. Very vanilla system.
On the iMac (very vanilla system, no jailbreaks, etc., and almost no extensions):
On the iMac, tested with:
Firefox: 93.0 (64 bit)
Chrome: 94.0.4606.81 (Official Build) (x86_64)
Safari: 15.0 (16612.1.29.41.4, 16612)
I could not reproduce the failure with any of these browsers on the iMac.
Moving to the iPad:
512 GB iPadPro 10.5 inch with iPad OS 15.0.2. Everything is very vanilla, no extensions, jailbreaks,
Safari: can reproduce failure as discussed above about 4 out of 5 times. Because I can't figure out how to get a browser console log on Safari on iOS (even poking through all the Settings > Safari > Advanced settings), I connected the iPad to the iMac using a USB cable to use the Web Inspector through the Safari Develop menu on the iMac.
The only error that occurs on the console occurs when the Mesh Details display window is closed and returns back to the Mesh Details app's starting page, and the console then clears when the Done button is pressed, and the results are the same regardless of whether the Mesh Details display window fails to show the mesh details (see screenshots above for failure mode), or when the Mesh Details window is correct. Here is the console when the Mesh Details window is closed and returns to the Mesh Details app's initial page:
I believe this is normal because the socket is being closed to the iMac inspector when the window is being closed. Again, this error occurs whenever the Mesh Details window is closed, regardless of whether in failure mode or with a successful display. No other errors appear. The console clears when Mesh Details Done button is pressed on the Mesh Details app's initial page.
I have no idea what iOS Safari version this is; it's whatever comes standard with iOS 15.0, 15.0.1, and 15.0.2 (same results with all recent iOS updates).
Moving to Chrome (version 94.0.4606.76) on iPad OS 15.0.2 (which is really the same as Safari on iOS because it's based on WebKit): Same results as Safari on iOS, fails about 4 out of 5 times. I have no idea how to get the console logs on Chrome on iPadOS.
Moving to Firefox (version 38.1) on iPad OS 15.0.2 (which is really the same as Safari on iOS because it's based on WebKit): Same results as Safari on iOS, fails about 4 out of 5 times. I have no idea how to get the console logs on Firefox on iPadOS.
I then repeated the iPad tests on iPhone, same results as on the iPad.
Anyway, it's clearly a browser issue, perhaps the Z-Wave SDK is a red herring unless it introduced a timing issue, because the common factor seems to be the iOS and iPad OS 15.0.x update. If I need to use Mesh Details on the iPad, I will just launch Mesh Details a few times until I get a successful display. Otherwise, I will just use it on the iMac browser.
Thanks everyone for your suggestions and help. Tony (@tony.fleisher) your program is great.
I tried with your settings from an iPhone, but didn't hit the issue. I'll give a try with iPad tomorrow.
Other questions: Any Safari extensions installed / enabled on the iPad and iPhone? Any content blockers? Private Relay? VPN? Are you accessing the hub via hostname or IP address?
I appreciate your effort. I tried again just now, same iPhone results. Success about 1 out of 5 times.
256 GB iPhone 7 with iOS 15.0.2. Happens both in Landscape mode and Portrait mode.
No. Like I said, everything is vanilla.
No.
No.
No. Direct access on the LAN.
IP address. See the screenshots in my initial post above.
It is a stumper. Like I said, Iāve never seen this before, started with 2.2.9. Everything else is working fine.
Note above that @thebearmay reported that he saw it once. I suspect that, if he did it a bunch of times, it might occasionally fail again:
Had it fail a couple of times day 1 and 2 under 2.2.9, but after that it seems to be okay. Do notice that I see the loading devices message longer than I used to (didn't used to see it at all to tell the truth) - so it may be that I timed out on the ones that came up blank. Believe I was on an iPad when having the issue.
Okay, I am able to reproduce it. I can produce it on a 4th generation iPad Pro with 15.0.2 (occasionally), and on an iPhone 11 with 15.0.2 (often). I am not able to reproduce on a 4th generation iPad Air with 15.0.2, an iPhone 13 15.0.2, or on an iMac with 11.6.
@tony.fleisher I'm a little out of my element here with javascript, but when the problem occurs the issue is that in getZwaveList() the value of the "data" field in the axios response is null. See console screen shot below.
Changing the response type from document to stream appears to address the issue. I submitted a pr. Please have a look.
So, did the SDK change the response type?
Download the Hubitat app
