Just thought I would check back with you on this still image problem. Have you had any success finding the issue here?
LJ
Sorry, I forgot to update - I believe it's some form of cross-origin rendering issue, as the link referenced in the html attribute is valid.
I haven't followed up in a bit... Not sure if there's anything that can be done to facilitate this on the Hubitat side, or if it's being blocked by Google. Open to suggestions if anybody knows of something - will dig back in to see if I find a solution.
1 Like
Got lucky with my Google search tonight... Likely related to these changes w.r.t. Google Drive and 3rd-party cookies... Google Workspace Updates: Upcoming changes to third-party cookie requirements in Google Drive
I'll play with their suggestions to see how best to recover this functionality in Hubitat
3 Likes
App version 1.1.1 has modified the "image" attribute based on the recommendations from Google above -- it is now an iframe of the "preview" from Google Drive.
3 Likes
Thanks for the update. I am not sure I understand what this means. I no longer see the broken image icon but I now see nothing on the image state. Should I? Should I be able to display the image attribute on a dashboard? Or, has this method changed?
LJ
Hmm, yes - it should work, and displays on my device pages and dashboard (even in incognito mode, so no cookies required). My hub is a couple releases behind (2.3.5.152) - haven't had a reason to upgrade, and every time I decide I'm ready they drop a brand new one 
. Not sure if that is even related....
All the logs are clean when you receive an event? What browser are you using?
Ok, so I tore down my entire setup on Google and Hubitat app and devices and deleted everything again. I started from scratch following the install instructions and now the doorbell device image field shows an image. I don’t know what got messed up. Ut that seems to be fixed.
However, when I try to display the image on a dashboard using the attribute image I see a very small image. It used to fill the tile.
LJ
Awesome! I finally decided to check this and then got a nice surprise. Their Nest Doorbell Gen 2 also shows the short clip here (like it does in the phone notifications):
@dkilgore90 i don’t know if you saw this part. Is there any way to get this new frame to fill a tile on a dashboard?
LJ
Thanks for the reminder -- I'm quite scatterbrained these days and lose track of things if I don't do them right away.
Easy fix, I applied a height/width to the iframe html of "95%" so that it scales with the dashboard tile. Update to app:1.1.2, just pushed to github.
2 Likes
I am having trouble with the HPM package. I have tried, Repair, uninstall, update, and nothing works. I always get a fatal error. I have totally uninstalled manually, and still it gives a fatal error.
For now I will install manually from the import, but I thought I would let you know.
LJ
Got it working and the new image looks great. Thanks for the help!,
LJ
@dkilgore90: Just circling back to mention that I tried resetting WWN on my early gen Nest E stats. It didn’t fix the issue I was having where the devices weren’t showing up in the Hubitat app.
Anyway, it dawned on me that those devices were registered in the Nest Field Test (NFT / beta) app. Sure enough, if I paired the stat with the public app version, they instantly showed up when I pressed the Discover button in the Hubitat Google SDM API.
Thanks for helping me troubleshoot!
I feel like I have asked this, but in my searching I came up blank. Maybe the coffee hasn't kicked in. I am getting duplicate Thermostat devices added into HE and not sure why. The "Nest Thermostat" device (ID 1651) is the real one, and is online. The remaining "Downstairs" items are a mix of Online and Offline devices (IDs 1679, 1680, 1681, and so on.)
How should I go about finding the root cause of the additional devices and stop them from happening? In the past I had this from accidently discovering one too many times. When I was initially setting things up. But I haven't clicked the discover button for some time now and the "Downstairs" devices keep appearing, over a period of time. It's been a while, and a few hub updates, since I looked at the discovered devices. Is there a new device added with every hub update?
EDIT: I captured this secondary screenshot after I started removing the phantom Nest's. The last activity time isn't consistent and doesn't appear to coincide with any HE platform updates either. The last entry, updated 7/4 at 11:31 is the real device and not a phantom one.
EDIT 2: Every hub reboot adds a device. I just rebooted twice and two new devices are present. This helps explain why I was thinking it was hub updates causing it. How should I go about preventing new devices from being added with every reboot?
Can anyone please provide any info on this error I see in my logs?
updateEventSubscription returned status code 404 -- { "error": { "code": 404, "message": "Resource not found (resource=hubitat-sdm-api).", "status": "NOT_FOUND" }}
@3rdStng I'll look into it - if it's not too inconvenient, enabling debug logs for the App, and the rebooting - and providing the App logs for that period, would help.
@jkudave seems like somehow the event subscription was not created successfully, and the App is trying to update to the latest model. You should be able to use the Debug Button (subscribe to events) to address this...
1 Like
I pretty much started from scratch because I seemed to be having multiple issue. Everything appears to be working normally. I'll post if anything changes. Thanks.
Not inconvenient at all. I have the debug logs for the app, but is there a way to debug the reboot as well? I've been looking for that and don't see it.
Also, anything sensitive within the debug logs that I shouldn't post, but rather DM or email you?
I don't think the hub itself logs much (that we can access). The logs from the App across the reboot should be enough.
I don't think any secrets are logged - but feel free to DM me if you're more comfortable. It might be a lot for a public post, anyways. We can follow up here with what we find.
It didn't look like it, but I sent the DM just to be safe. Here are my steps:
- 0824 - Enabled SDM debug
- 0825 - Rebooted
- Confirmed additional Thermostat was created (Downstairs)
- Refreshed new therm (Downstairs)
- Refreshed existing therm (Nest Thermostat)
- Collected logs for the app (reboot1)
- 0841 - Rebooted
- 0843 - Confirmed I had a second new "Downstairs" thermostat
- Collect only the new logs for SDM app from time of reboot to current. (reboot2)
