Hubitat™ Dashboard Documentation


#405

Sorry. iOS 11.4.latest. iPhone 7+.


#406

my Yale Lock is now unresponsive. The iPad that was able to control it now does the same nothing as my iPhone. (Dashboard app works, but the commands to the lock vanish.)

UPDATE:
Changed the batteries. Hope 56% isn't a rest-of-my-life end of battery life value.

Either the new batteries OR the resulting power cycle cleared up the non-responsiveness. I'm getting locking and unlocking from dashboard on the iPhone or iPad.

dev:806 2018-08-14 10:53:40.248:debug zw device: 6B, command: 9881, payload: 00 71 05 19 01 00 FF 06 04 00 00 parsed to ['name':'lock', 'value':'unlocked']
dev:806 2018-08-14 10:53:40.247:info  Yale DoorLock: alarm event 4[6:default]
dev:806 2018-08-14 10:53:40.245:debug alarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:25, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:4, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:806 2018-08-14 10:53:40.240:debug parse: zw device: 6B, command: 9881, payload: 00 71 05 19 01 00 FF 06 04 00 00
dev:806 2018-08-14 10:53:39.837:debug zw device: 6B, command: 9881, payload: 00 62 03 00 00 02 FE FE parsed to ['name':'lock', 'value':'unlocked', 'descriptionText':Yale DoorLock is unlocked]
dev:806 2018-08-14 10:53:39.836:info  Yale DoorLock is unlocked
dev:806 2018-08-14 10:53:39.834:debug DoorLockOperationReport: DoorLockOperationReport(doorCondition:2, doorLockMode:0, insideDoorHandlesMode:0, lockTimeoutMinutes:254, lockTimeoutSeconds:254, outsideDoorHandlesMode:0)
dev:806 2018-08-14 10:53:39.829:debug parse: zw device: 6B, command: 9881, payload: 00 62 03 00 00 02 FE FE
app:306 2018-08-14 10:53:39.006:info  Perimeter Trigger - Open Triggered
app:625 2018-08-14 10:53:38.619:debug Sending DEVICE Event (Yale DoorLock | LOCK: unlocked) to Homebridge at (192.168.7.129:8005)
app:306 2018-08-14 10:53:38.574:info  Perimeter Trigger - Open: Yale DoorLock lock unlocked
dev:806 2018-08-14 10:53:38.515:debug zw device: 6B, command: 9881, payload: 00 62 03 00 00 02 FE FE parsed to ['name':'lock', 'value':'unlocked', 'descriptionText':Yale DoorLock is unlocked]
dev:806 2018-08-14 10:53:38.514:info  Yale DoorLock is unlocked
dev:806 2018-08-14 10:53:38.507:debug DoorLockOperationReport: DoorLockOperationReport(doorCondition:2, doorLockMode:0, insideDoorHandlesMode:0, lockTimeoutMinutes:254, lockTimeoutSeconds:254, outsideDoorHandlesMode:0)
dev:806 2018-08-14 10:53:38.503:debug parse: zw device: 6B, command: 9881, payload: 00 62 03 00 00 02 FE FE
app:178 2018-08-14 10:53:34.660:debug For Device : Yale DoorLock
app:178 2018-08-14 10:53:34.656:debug Command Recieved : unlock : 806
app:178 2018-08-14 10:53:33.335:debug For Device : Yale DoorLock
app:178 2018-08-14 10:53:33.333:debug Command Recieved : unlock : 806
dev:806 2018-08-14 10:53:19.366:debug zw device: 6B, command: 9881, payload: 00 62 03 FF 00 00 FE FE parsed to ['name':'lock', 'value':'locked', 'descriptionText':Yale DoorLock is locked]
dev:806 2018-08-14 10:53:19.363:info  Yale DoorLock is locked
dev:806 2018-08-14 10:53:19.362:debug DoorLockOperationReport: DoorLockOperationReport(doorCondition:0, doorLockMode:255, insideDoorHandlesMode:0, lockTimeoutMinutes:254, lockTimeoutSeconds:254, outsideDoorHandlesMode:0)
dev:806 2018-08-14 10:53:19.354:debug parse: zw device: 6B, command: 9881, payload: 00 62 03 FF 00 00 FE FE
dev:806 2018-08-14 10:53:17.132:debug zw device: 6B, command: 9881, payload: 00 71 05 18 01 00 FF 06 03 00 00 parsed to ['name':'lock', 'value':'locked']
dev:806 2018-08-14 10:53:17.131:info  Yale DoorLock: alarm event 3[6:default]
dev:806 2018-08-14 10:53:17.129:debug alarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:24, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:3, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:806 2018-08-14 10:53:17.125:debug parse: zw device: 6B, command: 9881, payload: 00 71 05 18 01 00 FF 06 03 00 00
app:307 2018-08-14 10:53:16.926:info  Perimeter Trigger - Closed Triggered
dev:806 2018-08-14 10:53:16.723:debug zw device: 6B, command: 9881, payload: 00 71 05 18 01 00 FF 06 03 00 00 parsed to ['name':'lock', 'value':'locked']
dev:806 2018-08-14 10:53:16.722:info  Yale DoorLock: alarm event 3[6:default]
dev:806 2018-08-14 10:53:16.721:debug alarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:24, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:3, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:806 2018-08-14 10:53:16.717:debug parse: zw device: 6B, command: 9881, payload: 00 71 05 18 01 00 FF 06 03 00 00
app:625 2018-08-14 10:53:16.499:debug Sending DEVICE Event (Yale DoorLock | LOCK: locked) to Homebridge at (192.168.7.129:8005)
app:307 2018-08-14 10:53:16.447:info  Perimeter Trigger - Closed: Yale DoorLock lock locked
dev:806 2018-08-14 10:53:16.341:debug zw device: 6B, command: 9881, payload: 00 62 03 FF 00 00 FE FE parsed to ['name':'lock', 'value':'locked', 'descriptionText':Yale DoorLock is locked]
dev:806 2018-08-14 10:53:16.340:info  Yale DoorLock is locked
dev:806 2018-08-14 10:53:16.339:debug DoorLockOperationReport: DoorLockOperationReport(doorCondition:0, doorLockMode:255, insideDoorHandlesMode:0, lockTimeoutMinutes:254, lockTimeoutSeconds:254, outsideDoorHandlesMode:0)
dev:806 2018-08-14 10:53:16.303:debug parse: zw device: 6B, command: 9881, payload: 00 62 03 FF 00 00 FE FE
app:178 2018-08-14 10:53:14.158:debug For Device : Yale DoorLock
app:178 2018-08-14 10:53:14.153:debug Command Recieved : lock : 806
app:178 2018-08-14 10:53:11.122:debug For Device : Yale DoorLock
app:178 2018-08-14 10:53:11.118:debug Command Recieved : lock : 806

However, the issue was Dashboard and double popup prompt.. and that's still occurring.


#407

This happens with me as well. Ipad Mini Safari. Latest build


#408

Same Yale lock and same driver


#409

Driver really shouldn't matter as Dashboard really doesn't care which driver, its all template driven. Template determines the command to send.

The good news is it seems to be isolated to iOS devices and wouldn't you know, Apple likes to do things a bit different... Fix is scheduled for the next release pending testing.


#410

I have noticed double prompting too...but can't remember under what circumstances. Not running any Apple stuff, just Edge and Android (Fully Kiosk). Will test when I get home and report back...


#411

Don't worry about it, the fix for iOS does fix the double event on android as well. But that was a separate issue believe it or not.


#412

OK, thanks! :smiley:


#413

I created 2 dashboards but now when i try to open them they keep loading and eventually stop with the error "something went wrong". Does someone know what could be happening? It's with the local and cloud links


#414

Try rebooting the hub to start. Also, if that doesn't work, try creating a new dashboard from scratch. Last resort, if everything else on the system is working fine, export your dashboard layouts and note your settings. Remove Dashboard and reinstall, import your layouts and see if it works.


#415

Already tried all of them..... Recreating dashboard, reinstalling dashboard. After adding a few devices the page freezes and when reopening it, it doesn't load anymore


#416

Is a custom attribute tile with image in it on the dashboard? There have been a few isolated reports of this causing a lockup, but I am unable to recreate the conditions.


#417

Yep custom attribute for rooms occupancy.


#418

Does it have an image? Try removing that and seeing if it still works. Also, what OS, browser, etc.? Trying to track this down.


#419

Yep it has an image, tried using windows 10 - chrome, IOS - safari. @bangali do you have any issues with this? We might be able to test this together


#420

make sure the image size is smaller than the tile size. which is why i publish a few different sized icons.


#421

Did you have the same problem when using a image size bigger then the tile size?


#422

no … someone else did … which caused me to publish those different sizes for use with different sized tiles


#423

@patrick might be possible to add a check if the image is to big? Might be the problem?


#424

I'll test again, but like I said, I couldn't reproduce but will test this specifically. Can't imagine why a larger image than a div would crash a browser let alone all of the ones you said you have the issue on.

I suspect something else is going on. But until I can get the exact steps to reproduce its hard to solve.