New widgets: input slider(horizontal and vertical), input select and light with brightness

i dont know, but did you check the filerights from the custom_widgets folder and all that is beneath that?

you should have:

conf/custom_widgets
conf/custom_widgets/baseselect
conf/custom_widgets/baseselect/baseselect.js
conf/custom_widgets/baseselect/baseselect.html
conf/custom_widgets/baseselect/baseselect.css
conf/custom_widgets/input_select.yaml

and the same for baseslider_new and baseslider_vertical

i know whats missing!
you did update your AD, did you look at the breaking change??

you need to splitt your config into 2 files and you dont have:

/conf/apps.yaml
● appdaemon.service - AppDaemon service for Home Assistant
   Loaded: loaded (/etc/systemd/system/appdaemon.service; enabled)
   Active: active (running) since Mon 2017-09-11 22:46:39 CEST; 5s ago
 Main PID: 13211 (appdaemon)
   CGroup: /system.slice/appdaemon.service
           └─13211 /usr/bin/python3 /usr/local/bin/appdaemon -c /home/pi/appdaemon_dashboard/appdaemon/conf

Sep 11 22:46:39 home-assistant systemd[1]: Started AppDaemon service for Home Assistant.```


so far so good but after a while

```pi@home-assistant:~/appdaemon_dashboard/appdaemon/conf $ sudo service appdaemon status
● appdaemon.service - AppDaemon service for Home Assistant
   Loaded: loaded (/etc/systemd/system/appdaemon.service; enabled)
   Active: failed (Result: exit-code) since Mon 2017-09-11 22:46:49 CEST; 28s ago
  Process: 13211 ExecStart=/usr/local/bin/appdaemon -c /home/pi/appdaemon_dashboard/appdaemon/conf (code=exited, status=1/FAILURE)
 Main PID: 13211 (code=exited, status=1/FAILURE)

Sep 11 22:46:48 home-assistant appdaemon[13211]: Traceback (most recent call last):
Sep 11 22:46:48 home-assistant appdaemon[13211]: File "/usr/local/bin/appdaemon", line 11, in <module>
Sep 11 22:46:48 home-assistant appdaemon[13211]: sys.exit(main())
Sep 11 22:46:48 home-assistant appdaemon[13211]: File "/usr/local/lib/python3.4/dist-packages/appdaemon/admain.py", line 478, in main
Sep 11 22:46:48 home-assistant appdaemon[13211]: conf.app_config_file_modified = os.path.getmtime(conf.app_config_file)
Sep 11 22:46:48 home-assistant appdaemon[13211]: File "/usr/lib/python3.4/genericpath.py", line 55, in getmtime
Sep 11 22:46:48 home-assistant appdaemon[13211]: return os.stat(filename).st_mtime
Sep 11 22:46:48 home-assistant appdaemon[13211]: FileNotFoundError: [Errno 2] No such file or directory: '/home/pi/appdaemon_dashboard/appdaemon/c...ps.yaml'
Sep 11 22:46:49 home-assistant systemd[1]: appdaemon.service: main process exited, code=exited, status=1/FAILURE
Sep 11 22:46:49 home-assistant systemd[1]: Unit appdaemon.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.```

read my last reaction

aaa ok … where can i read breaking changes?

ok got it but input select wont wirk witg foscam :frowning: it doesnt move the cam to the points… if i use the “old” switches it works

does the select work in HA?

great it seems broken :frowning:

i might need to reboot the cam ?
i already rebooted appdaemon… move to left and right works fine so far

LOL Dashboard moves the cam but hass not

i would check your cam itself (if you still have the presets there)
but please lets talk about this in the foscam topic or through PM.
this has nothing to do with the items from this topic anymore :wink:

i made a light with brightness also.

custom_widgets

can be found on the same place

1 Like

Once again great work man! I’m working on adding a slider to the front page to control the volume of whatever active sonos are playing. Now I get to redo my lights page!

1 Like

did u add example? Wanna have this light slider :slight_smile:

its the same as the other ones.
download the files from the link in the first posting and with that link you also have an example :wink:

just restarted cam. what is strange is that i can use dashboard and commands work … but hass not

also i see that in hass it also changes correctly the values … like cruise pointe etc . but from hass the cam wont react .

that can only be a problem in the hass frontend or in the browser.
but i have no clue