@dopecoder wrote:
Hi all, i have a Hassos running in a virtual box on a windows 10 machine. i have RS232 serial connected to a usb port on the windows machine. i would like to access that in hassos but cant figureout how. anyone know how to setup usb in virtual box.
Thanks
Posts: 1
Participants: 1
@SeanA wrote:
I’d like to integrate some events from a particular google calendar. There are multiple unrelated events in the calendar but I want to filter on 4 specific all-day events.
In this instance they are “B1”, “B2”, “D1”, “D2”.
Is there a way to combine all those searches into a single entry in google_calendars.yaml, something logically (not syntactically) like this?
- cal_id: <MY_CAL_ID>@group.calendar.google.com entities: - device_id: found_event ignore_availability: true name: Found Event track: true search: OR("B1","B2","D1","D2")or is it going to have to be all separate and then make use of multiple triggers for the automation, like this:
- cal_id: <MY_CAL_ID>@group.calendar.google.com entities: - device_id: found_d1 ignore_availability: true name: Found D1 track: true search: D1 - device_id: found_d2 ignore_availability: true name: Found D2 track: true search: D2 - device_id: found_b1 ignore_availability: true name: Found B1 track: true search: B1 - device_id: found_b2 ignore_availability: true name: Found B2 track: true search: B2Or should I just use a single calendar entity and then do a conditional template filter on the automation
- cal_id: <MY_CAL_ID>@group.calendar.google.com entities: - device_id: all_events ignore_availability: true name: All Events track: trueHappy to hear all ideas. Thanks!
Posts: 1
Participants: 1
@Kezza wrote:
I’ve attempted to setup using ESP8266/CC2530, they are both flashed and I think working but I’m getting errors in HA, is the following tcp option supported with built in zigbee2MQTT addon?
serial: port: 'tcp://192.168.2.13:20108'I’m getting the following error but not sure if it HA addon not supporting tcp option or the ESP not working as it should
zigbee2mqtt:info 2020-05-18 13:45:12: Logging to console and directory: ‘/share/zigbee2mqtt/log/2020-05-18.13-45-12’ filename: log.txt
zigbee2mqtt:info 2020-05-18 13:45:12: Starting zigbee2mqtt version 1.13.0 (commit #unknown)
zigbee2mqtt:info 2020-05-18 13:45:12: Starting zigbee-herdsman…
zigbee2mqtt:error 2020-05-18 13:45:15: Error while starting zigbee-herdsman
zigbee2mqtt:error 2020-05-18 13:45:15: Failed to start zigbee
zigbee2mqtt:error 2020-05-18 13:45:15: Exiting…
zigbee2mqtt:error 2020-05-18 13:45:15: Error: Error while opening socket
at Socket. (/zigbee2mqtt-1.13.0/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:162:28)
at Socket.emit (events.js:228:7)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:81:21)
npm
ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR!
zigbee2mqtt@1.13.0 start:node index.js
npm ERR!
Exit status 1
npm ERR!
npm ERR! Failed at the zigbee2mqtt@1.13.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm
ERR! /root/.npm/_logs/2020-05-18T01_45_15_690Z-debug.log
2020-05-18T13:45:17: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2020-05-18T13:45:17: PM2 log: App [npm:0] starting in -fork mode-
2020-05-18T13:45:17: PM2 log: App [npm:0] onlinezigbee2mqtt@1.13.0 start /zigbee2mqtt-1.13.0
node index.js
zigbee2mqtt:info 2020-05-18 13:45:18: Logging to console and directory: ‘/share/zigbee2mqtt/log/2020-05-18.13-45-18’ filename: log.txt
zigbee2mqtt:info 2020-05-18 13:45:18: Starting zigbee2mqtt version 1.13.0 (commit #unknown)
zigbee2mqtt:info 2020-05-18 13:45:18: Starting zigbee-herdsman…
Posts: 1
Participants: 1
@bphillips921 wrote:
I’m trying to find a way to trigger scripts or automation based on a code entered on an exterior keypad, preferably something like a Schlage deadbolt lock
Ex 1.My house cleaner would have a code 1234. When she enters that code the alarm would disarm, the garage door would open, my security cameras would start recording, and I would get a notification on my phone. This code would only work on Wednesdays from 8am to noon.
Ex 2. My daughter would have a code 6789. When she enters that code the garage would open, alarm would disarm, and I would get a notification that she is home
EX 3. My UPS driver would have the code 4567. When that code is entered my garage opens then closes 30 seconds later.
Can this be done? My thought was to buy a smart deadbolt lock and just use the keypad portion, but I’m open to any other weatherproof keypad. I would need the keypad to send the code to HA, I wasn’t sure if smart deadbolts will do that.
Posts: 1
Participants: 1
@ha_time wrote:
I am trying to feed commands from Rhasspy to my home assistant, but I am having issues with the automation.
I am able to read the trigger fine, but the rgb_color seems to be giving me an issue. I have read numerous posts with various examples, but none of them are working for me. I have tried referencing the individual values of rgb_color, parsing to build a list, and many variations with no success. I have even tried to use light.toggle with rgb_color and color_name since color_name is not available for the yeelight service.
I am also not sure how I can check to see what values the automation is actually seeing in the data template when it runs…I did not see it in the homeassistant log file.
Here is the error I am getting with rgb_color: Invalid data for call_service at pos 1: expected int for dictionary value @ data[‘rgb_color’]
Here is my current config. Any help would be much appreciated.
- id: 'xxxxxx' alias: Rhasspy Lights trigger: - event_data: {} event_type: rhasspy_TriggerColor platform: event condition: [] action: - data_template: brightness: 255 rgb_color: - '{{ trigger.event.data.color.split()[0] | int }}' - '{{ trigger.event.data.color.split()[1] | int }}' - '{{ trigger.event.data.color.split()[2] | int }}' entity_id: light.yeelight1 service: yeelight.set_color_sceneAny assistance is much appreciated.
Posts: 1
Participants: 1
@joe_blow wrote:
I’m trying to trigger an automation based on a sensor value AND an input_boolean state. The idea is that a given value AND a certain input_boolean would trigger the automation. So far, I have tried about 6-8 different syntax variations on:
trigger: - platform: template value_template: "{{ states('sensor.meat' > '86') and states('input_boolean.cooking_smoking_pork' == 'on') }}" action: - data: message: Meat is Done title: Maverick ET-732 service: notify.mobile_app_iphoneIdeally, I’d like to use an if statement that allowed me to trigger the automation based on the user defined input_booleans. So, it would also trigger the automation if ‘input_boolean.cooking_grilling_steak’ == ‘on’ AND ‘sensor.meat’ > ‘120’ … as an example.
All of the above variations of the above syntax have failed to trigger the automation.
Posts: 1
Participants: 1
@mkanet wrote:
I decided to move my Phillips Hue Motion from my Hue Controller to my HUSBZB-1/Zigbee controller temporarily. After I moved it back to my Hue controller, I noticed that the Phillips Hue Motion device is still showing under my Zigbee Integration.
I even went through the hassle of removing any entries I could find related to this device under .storage
core.entity_registry
core.device_registry
core.config_entriesSo… what’s the trick to force Home Assistant to only see the devices that are actually there? Had I known it was going to get stuck like this, I would have never moved the device over.
Posts: 1
Participants: 1
@mkanet wrote:
Currently, my luminance sensor sometimes has some ridiculous peaks (when there’s direct sunlight); which completely messes up the history graph scale (see below). Can anyone think of a way to set a maximum value to display in the graph?
I have an Aeon Labs Multisensor 6. I tried looking for setting that might help me do this, but couldn’t find one.
Posts: 1
Participants: 1
@andreasc wrote:
Hi i hey this error with the latest release
Unable to prepare setup for platform cast.media_player: Platform not found (No module named 'pychromecast.quick_play').Any ideas why? It doesn’t discover casting devices any more. I also tried to specify them manually.
Posts: 1
Participants: 1
@dreamzboy wrote:
I’ve wasted a full Sunday trying to figure out the SSL stuff with no luck. I’ve followed this Documentation.
I’ve created the certificates according to the documentation. Note, the “config” directory wasn’t there so I had to create it to match the docs.
$ pwd /usr/share/hassio/homeassistant $ ls -lh total 14M -rwxrwxr-x. 1 root root 1.3K May 17 18:33 automations.yaml drwxr-xr-x. 2 root root 44 May 17 19:34 config -rwxrwxr-x. 1 root root 523 May 17 22:37 configuration.yaml -rwxrwxr-x. 1 root root 282 May 8 20:38 customize.yaml drwxrwxr-x. 2 root root 6 May 7 22:53 deps -rwxrwxr-x. 1 root root 0 May 7 22:53 groups.yaml -rwxrwxr-x. 1 root root 140 May 17 22:37 home-assistant.log -rwxrwxr-x. 1 root root 14M May 17 22:55 home-assistant_v2.db -rwxrwxr-x. 1 root root 0 May 7 22:53 scenes.yaml -rwxrwxr-x. 1 root root 0 May 7 22:53 scripts.yaml -rwxrwxr-x. 1 root root 163 May 17 22:40 secrets.yaml drwxr-xr-x. 2 root root 44 May 17 21:47 ssl drwxrwxr-x. 2 root root 6 May 7 22:53 tts $ ls -lh config total 8.0K -rw-------. 1 root root 2.1K May 17 19:28 fullchain.pem -rw-------. 1 root root 3.2K May 17 19:28 privkey.pemConfiguration.yaml:
# Configure a default setup of Home Assistant (frontend, api, etc) default_config: # Uncomment this if you are using SSL/TLS, running in Docker container, etc. http: base_url: https://myhomeassistant.com:8123 ssl_certificate: /config/fullchain.pem ssl_key: /config/privkey.pem # Text to speech tts: - platform: google_translate group: !include groups.yaml automation: !include automations.yaml script: !include scripts.yaml scene: !include scenes.yaml homeassistant: customize: !include customize.yamlThere are 2 problems I’m experiencing:
- With the current configuration settings, my hassio will start up in Safe Mode
- I can access http://myhomeassistant.com:8123 but not https://myhomeassistant.com:8123.
I’m not using Let’s Encrypt Add-On. I’m OK with the nagging unsecured connection just as long as it’s “https”.
Posts: 1
Participants: 1
@Bionic-Bean wrote:
Hi Guys,
Having trouble with a simple template sensor subtraction. My end result ends up at 2.150000000076398 as an example and unable to round down to 2 decimal places.platform: template sensors: todays_export: friendly_name: 'Todays Export kWh' value_template: "{{ states('sensor.modbus_export_kwh') | float - states('input_number.today_export_consumption') | float | round(2) }}" unit_of_measurement: kWh device_class: powerBoth
Sensor.modbus_export_kwhandinput_number.today_export_consumptionreturn a nice 1234.56 format. No matter what I do with the round (2) doesnt seem to change the end result.
Interestingly if I add ( + ) the two variables in the same template then the format result is perfect complete to 2 decimal places. !!! Any ideas appreciated
Thanks Dave
Posts: 3
Participants: 3
@hajo62 wrote:
Someone out there using Glances (best with and in docker environment) and able to use the API as Rest Sensors?
The call http://192.168.1.12:61208/api/3/mem/used results in
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data.Therefore I need to go with http://192.168.1.12:61208/api/3/mem or http://192.168.1.12:61208/api/3/docker instead, but typically the result is longer than 255 chars and so it does not work with HomeAssistant.
How could I use the glances API and extract some values?
Posts: 1
Participants: 1
@Bojkas wrote:
Hi, I need to create an automation, if the state of the temperature sensor does not change for one hour, then just call the URL 192.168.0.240/reboot. How can I monitor the functionality of a sensor and then simply enter the send URL? This address works as a “button”, if I enter it into the browser, it simply triggers a restart of the device, nothing more, nothing less.
Thank you
Ivica
Posts: 4
Participants: 2
@phischmi wrote:
Hi all,
I’m looking for a way, to send a notification to group of users based on their status in that group.
E.g. I have a group “family” where the status is either home or not_home - depended on whether at least one member of the group is home or not.
Now i want to send a notification to only those members of that group, who are at home at the time being.
How could i achieve that?Thank you all very much!
Philipp
Posts: 1
Participants: 1
@maxym wrote:
Recently while editing Lovelace yaml I noticed that when I order yaml items in specific order, after reopening editor those items are re-ordered (in a manner I don’t like).
I could accept that eventually. What I cannot accept is the fact, that commented lines disappear. Really? Do we have another “smart” application which “knows better”?
Posts: 1
Participants: 1
@aristosv wrote:
So this plug is under the lid of my AC. I think it’s used to power the LCD that shows the temperature in front of the AC. I figure I can splice into it and connect some sort of device which will connect on my WiFi when the AC is powered on.
I can then configure a binary sensor in Home Assistant that will detect if this device is connected to the network, so I’ll know if the AC is powered on or not.
Theory is good, but I have no idea what device I can connect on this plug or how much voltage it outputs.
Any suggestions on what can I use to do this?
Posts: 2
Participants: 2
@chris1bass wrote:
### Project Energy Effeciency ### - alias: PEE Outdoor Lights trigger: platform: state entity_id: - group.household to: 'home' condition: - condition: state entity_id: 'group.household' state: 'home' action: service: homeassistant.turn_off entity_id: - group.lightsoutdoorsAutomations: https://pastebin.com/jZJqUM9y
Groups: https://pastebin.com/xJxWvekZSo I am trying to keep the outside lights on if it is dark and not everyone is home but it does not seem to work. Currently someone is not home, and it is showing the group.household as home. When only two out of three individuals are home.
Posts: 5
Participants: 3
@idofr wrote:
I’ve set an mqtt light strip with is controlled by a Python script on a Pi Zero (using paho-mqtt and rpi-ws281x).
Everything is working fine (on/off, brightness, transitions, etc.) but the Lovelace card doesn’t seem to register the status change. When i change something (colour, brightness, status), it quickly changes back to the default status.I found a few resources online saying that i need to send a response after having applied the changes, yet I can’t find anything on how and what to respond.
For the moment, I’ve changed to yaml config tooptimisticand everything is working just fine, but this shouldn’t be the permanent solutionMy config (based on https://www.home-assistant.io/integrations/light.mqtt/):
light: - platform: mqtt schema: json name: "Test RGBW Strip" state_topic: "ido/test_rgbw_strip" command_topic: "ido/test_rgbw_strip/set" brightness: true rgb: true white_value: true optimistic: true qos: 1The python side is based on the examples from
where I’ve implementedon_message()to handle the light stripMany thanks for the help
Posts: 1
Participants: 1
@mixedup wrote:
I can’t quite seem to find out how to “maximise” a “History Graph Card” in the UI. For example if I create a History Graph Card in a dedicated page using “Panel” mode the graph expands out horizontally but not vertically? Any tips on how to get it to maximise/expand vertically?
Posts: 3
Participants: 2
@tom_l wrote:
Is there a theme option for card background images?
I can set a card background with card mod:
style: ha-card { background: url('/local/images/background/card_bg_night.png'); }But I would need this image to change when I change to my “day” theme.
I found that the paper-card web element only seems to have a header image,
paper-card-header-imagebut I can’t get this to display anything in my cards when I set it in my themes.The home assistant entities card header supports an image but again not only is that hard coded and unable to be changed with the theme, it also appears above the title text not behind it, as I can and want do with a card background.
Posts: 1
Participants: 1
