What am I missing. I am getting this:
WARNING AppDaemon: check_config: Entity sensor.config_result not found in AppDaemon
Can you paste your appdaemon configuration (from apps.yaml) and your Lovelace configuration?
What code should I add to apps.yaml for check-config to work?
That???
check_config:
module: checkconfig
class: CheckConfig
Does the apps.yaml file have to be in the / config / appdaemon / apps / check-config directory?
That is correct on the code in apps.yaml.
You have flexibility on where to put the yaml file. The “default” configuration is for an apps.yaml file to be under /config/appdaemon/apps with the yaml for all of your AppDaemon apps. However, AppDaemon looks at all yaml files in the apps directory or any of its subdirectories, so you could put the configuration in any yaml files you want. If you’re just getting started with AppDaemon, though, for simplicity’s sake and for ease of having questions answered if you run into trouble, I’d put everything in /config/appdaemon/apps/apps.yaml.
Unfortunately. I do everything as described. I don’t have sensor config result. APPdeamon installed. Check Config Installed. It lights up green.
I’m not certain what you mean by “it lights up Green”.
You are using AppDaemon as a Hass.io add on? Do you have any other AppDaemon apps set up successfully?
I don’t have another APPDEAMON application.
Did you add the configuration for the app to apps.yaml? Do you see anything in the AppDaemon addon logs? (I’m assuming you’re using the Hassio addon)
Whera are AppDeamon logs?
Must appdeamon.yaml file be made? I do not have such a file.
AppDaemon logs are in the AppDaemon Hassio addon.
You should have the appdaemon.yaml file automatically in config/appdaemon if you have the Hassio addon installed.
Config Check 0.3.1 Released!
- This is a minor release to fix an issue that prevented the check from working if it was called via script on AppDaemon 4.
- Going forward, I will only be testing my scripts against AppDaemon 4, though they should continue to work on AppDaemon 3.
Side note, this thread’s been pretty quiet for awhile but I finally have time to start working on Home Assistant some more. I moved into a new position at work in August which really cut into my spare time to work on Home Assistant (my GitHub commit history dries up at pretty much the exact time I started the new role). I’m doing quite a bit more programming and dev work in my new role as well, which has been awesome, but it also means I’m not quite as motivated to spend time outside of work hours doing more programming. Now that I’ve settled into the new role, though, I’m sinking my teeth into Home Assistant some more and am excited to have more to post here this year.
All good and working again… Thanks!
Stbutton version 2.0 released! Available in HACS or at https://github.com/apop880/SmartThings-Button/releases/tag/v2.0
- Added support for switch and input_boolean entities.
- Improved error handling. The app will now check at startup to make sure entities specified are valid and are in a supported domain (light/light group, switch, input_boolean) and will log an error if they are not.
Hi apop - for https://github.com/apop880/White-Noise
a few questions:
(1) Is this configuration added to configuration.yaml in HA or an apps.yaml file?
(2) Also - how do I call this white noise from an automation? (I assume I need to change ’ input_boolean: white_noise’ from false to true).
(3) How do I configure multiple media players?
Thanks!
-
The configuration will go into apps.yaml. If you’re not familiar with apps.yaml, I’m guessing you have not used AppDaemon previously. If this is the case, let me know I can help walk you through getting that set up.
-
You can turn on the input_boolean through the frontend, or through an automation that uses the input_boolean.turn_on service call.
-
You can add the configuration to apps.yaml multiple times, one for each media_player you want to use as a white noise machine.
Thanks @apop !
a few more questions:
-
Could you Please help with the format - for each media player, would the configuration be as shown below? (I get an error for ‘duplicate mapping key’ warning in File editor).
-
Do I need to add anything to my configuration.yaml to indicate that I am using this app daemon after installing in HACS?
-
Do you know if alexa devices will work with this
#apps.yaml
white_noise:
module: whitenoise
class: WhiteNoise
media_player: bedroom
input_boolean: white_noise
filename: 03-White-Noise-60min.mp3
white_noise:
module: whitenoise
class: WhiteNoise
media_player: office_wifi
input_boolean: white_noise
filename: 03-White-Noise-60min.mp3
white_noise:
module: whitenoise
class: WhiteNoise
media_player: kids_room
input_boolean: white_noise
filename: 03-White-Noise-60min.mp3
-
Each app needs its own name. That’s the cause of the duplicate mapping key warning. So, the top unindented line for each app needs to be unique (i.e.
white_noise_1
,white_noise_2
, etc… - orwhite_noise_bedroom
,white_noise_office
, etc… you get the picture). Also, the filename needs to be the full URL path to the file. -
This goes back to my previous reply - you need AppDaemon installed to execute the script. If you’re running Home Assistant with add-ons, the easiest way is to install the AppDaemon add-on.
-
I’ve not tested with Alexa, only Google Home, but it should most likely work with Alexa. If it does not, I can try and troubleshoot.
thanks!
for my configuration, should i write the code below or w/out “1”? unfortuantely, my input boolen is not triggering the white noise.
input_boolean:
white_noise:
name: White Noise1
I assume this excerpt is from your configuration.yaml file? If you have one input_boolean.white_noise
you should be fine. Based on your configuration from your prior post, you would trigger all three speakers to start the white noise when the input boolean is turned on. Do you have anything in your AppDaemon logs? And would you be able to repost exactly what your apps.yaml file looks like now?