Great video as always! I appreciate all your effort learning all this stuff and putting it together. Also, you forgot to blur your location starting at 13:24.
Thank you!! Yeah, the map is zoomed WAY out at that point, so I didn't think it was that big of an issue. Wanted to leave some part of that map visible so people could see what it was, but without giving too much away.
Here is my dashboard idea. Using an ultra-wide monitor, the background is streamed in the background. The lower third of the screen has a gradient that has each sensor card displayed.
Is the website logon the same as the app logon? I can’t seem to use my app logon on the site. Wondering if anyone else has seen a workaround. Thanks for the video!
Extremely useful video! I pretty comfortable with code (30+ years in development), but new to homeassistant and was able to got most of this up and running from the video - so thanks!. My one struggle has been with the configuration code for the weather_forecast sensor. From what I can gather the syntax may have changed in how template, trigger, and platform are declared with time pattern. Either that or I'm way off on something. -platform: time_pattern is the first issue. ("string does not match the pattern of legacy syntax") and I've read in the forums about "old way" vs "new way" syntax with platform being no longer necessary? Any suggestions?
Yeah, there were syntax changes made to everything a few months back. I went through and updated all my stuff, but AFAIK it's not necessary. The old syntax still works (and according to the docs will NOT be deprecated), even if Studio Code does bark at you. There are several spots in my config file where it complains with one update, then stops complaining with another. All my stuff keeps working just fine. :) Just have to remember that studio code is an add-on, and is NOT part of Home Assistant, so the things it complains about are not *Home Assistant* complaining, it's just a third-party IDE. As long as HA continues to interpret it correctly, it doesn't really matter was Studio Code thinks (even though my OCD says otherwise). Not to mention that even once you fix the trigger/platform thing, Studio Code is STILL going to complain about the code for the sensor (or at least, mine does) - but again, it still works just fine. :) If you want to update your config file for triggers, the release notes from 2024.10 has the info: www.home-assistant.io/blog/2024/10/02/release-202410/#improved-yaml-syntax-for-automations I actually meant to do a video about this when I ran into it and fixed it all, but time just got away from me. Maybe next month? Thanks for watching!
Awesome graphs Jeff
Thanks, Simon!
Great video as always! I appreciate all your effort learning all this stuff and putting it together. Also, you forgot to blur your location starting at 13:24.
Thank you!!
Yeah, the map is zoomed WAY out at that point, so I didn't think it was that big of an issue. Wanted to leave some part of that map visible so people could see what it was, but without giving too much away.
Here is my dashboard idea. Using an ultra-wide monitor, the background is streamed in the background. The lower third of the screen has a gradient that has each sensor card displayed.
Smart Home Sense would be a great name
Is the website logon the same as the app logon? I can’t seem to use my app logon on the site. Wondering if anyone else has seen a workaround. Thanks for the video!
Extremely useful video! I pretty comfortable with code (30+ years in development), but new to homeassistant and was able to got most of this up and running from the video - so thanks!. My one struggle has been with the configuration code for the weather_forecast sensor. From what I can gather the syntax may have changed in how template, trigger, and platform are declared with time pattern. Either that or I'm way off on something. -platform: time_pattern is the first issue. ("string does not match the pattern of legacy syntax") and I've read in the forums about "old way" vs "new way" syntax with platform being no longer necessary?
Any suggestions?
Yeah, there were syntax changes made to everything a few months back. I went through and updated all my stuff, but AFAIK it's not necessary. The old syntax still works (and according to the docs will NOT be deprecated), even if Studio Code does bark at you. There are several spots in my config file where it complains with one update, then stops complaining with another. All my stuff keeps working just fine. :) Just have to remember that studio code is an add-on, and is NOT part of Home Assistant, so the things it complains about are not *Home Assistant* complaining, it's just a third-party IDE. As long as HA continues to interpret it correctly, it doesn't really matter was Studio Code thinks (even though my OCD says otherwise).
Not to mention that even once you fix the trigger/platform thing, Studio Code is STILL going to complain about the code for the sensor (or at least, mine does) - but again, it still works just fine. :)
If you want to update your config file for triggers, the release notes from 2024.10 has the info: www.home-assistant.io/blog/2024/10/02/release-202410/#improved-yaml-syntax-for-automations
I actually meant to do a video about this when I ran into it and fixed it all, but time just got away from me. Maybe next month?
Thanks for watching!
Channel Name: The Drunk Smarthome!
Channel name: Smart home made easy
Yada Yada HA
How about "My Smart Opinion" for a name