What card are you using for that tap_action?
no repairs at all, but I had this copied from the docs before, and just about the only non custom:button-card service_data in my DashboardsâŚ:
- type: service-button
title: ""
service: remote.send_command
service_data:
entity_id: remote.xboxone_remote
command: Up
on the XBOX remote.
this would need to be:
- type: service-button
title: ""
service: remote.send_command
data:
entity_id: remote.xboxone_remote
command: Up
now? Sorry for asking, but I can not find the service-button in the docs to check the official options
__
edit
nevermind, its here: Picture Elements Card - Home Assistant
and still using service_data
Created in issue:
1 Like
mushroom chip, mushroom entity and i tried with the regular entity card
thanks for that, I added a line on the picture elements
Please be more careful testing the betas.
Thereâs no infrastructure for easy beta testing. If for my particular operating system, there would be such support, Iâd be happy to enable it.
Since there is no support, I donât see the point of doing something manually, which could have been automated.
This is nevertheless rude. Please stop.
11 Likes
Schedule! Finally! This is a good start, but to make it really useful and powerfull it must allow defining custom attributes, that could be used in automations to define conditions.
Sample use case:
- themperature control: attribute: temperature - Iâd define a condition that if temperature is above or eaualt this defined temperature then the automation does nothing, otherwise e.g. turn on the heater. This would prevent heating is sumemrtime for example
In this particular case Iâd define two attributes - daytime temperature, nighttime temperature with different time periods to support day and night thermo comfort and spare energy
- brightness attribute - for defining automations that should turn on/off some lights based on brightness as an additional condition
In general defining custom attribute values per each day& time interval should be possible to make this helper really powerful and easy to use in defining powerful & useful autoamations.
And one more tip - some button for copying time periods across days would also be very nice feature.
Keep up the good work guys!
2022.9.6 ?
Attempt 7 to get it right?
Please, âcamera.stop_recordingâ service
Is this the PR?
1 Like
Meross lan - switches donât work on 2022.9.6 (via MQTT)
Also broadlink rm3?
Reverted back to 2022.9.5 - all fine.
I also do not like the new automations list format. I saw it just now for the first time when I needed to disable an automation and was utterly confused, I thought something had broken. Moving everything that was previously available via a single interaction (click) on this list (info, edit, enable/disable, run etc.) to under a 3 dots menu so it takes 2 interactions is a massive and pointless backward step in usability.
It is all very well saying âitâs odd you are doing this so oftenâ or âyou can create a card if you want toâ but that is not the point. Experienced users with well-bedded-in systems up and running may indeed not use this list much, but newer users learning and developing automations use it a lot. It is also very useful to be able to quickly disable/enable automations when there are problems, such as the recent alexa media integration problems. Please consider putting the list back the way it was. If people donât use that list much, it doesnât affect them. If they do, it is hugely less user friendly now.
1 Like
The latest 2022.9.6 or maybe .5 for sure very recentlyâŚ
I now get these errors when I start HA
2022-09-23 12:51:12.176 ERROR (MainThread) [homeassistant.components.device_tracker] Platform mqtt does not generate unique IDs. ID ble-button-kenneth1 already exists - ignoring device_tracker.ble_button_kenneth1
2022-09-23 12:51:12.180 ERROR (MainThread) [homeassistant.components.device_tracker] Platform mqtt does not generate unique IDs. ID ble-button-diane1 already exists - ignoring device_tracker.ble_button_diane1
2022-09-23 12:51:12.181 ERROR (MainThread) [homeassistant.components.device_tracker] Platform mqtt does not generate unique IDs. ID ble-button-kenneth2 already exists - ignoring device_tracker.ble_button_kenneth2
2022-09-23 12:51:12.182 ERROR (MainThread) [homeassistant.components.device_tracker] Platform mqtt does not generate unique IDs. ID ble-button-diane2 already exists - ignoring device_tracker.ble_button_diane2
2022-09-23 12:51:12.183 ERROR (MainThread) [homeassistant.components.device_tracker] Platform mqtt does not generate unique IDs. ID ble-button-kenneth3 already exists - ignoring device_tracker.ble_button_kenneth3
2022-09-23 12:51:12.184 ERROR (MainThread) [homeassistant.components.device_tracker] Platform mqtt does not generate unique IDs. ID ble-button-diane3 already exists - ignoring device_tracker.ble_button_diane3
2022-09-23 12:51:12.185 ERROR (MainThread) [homeassistant.components.device_tracker] Platform mqtt does not generate unique IDs. ID ble-button-kenneth4 already exists - ignoring device_tracker.ble_button_kenneth4
2022-09-23 12:51:12.186 ERROR (MainThread) [homeassistant.components.device_tracker] Platform mqtt does not generate unique IDs. ID ble-button-diane4 already exists - ignoring device_tracker.ble_button_diane4
The definitions all all 8 are setup in yaml
device_tracker:
- name: "BLE Button Kenneth1"
unique_id: "ble-button-kenneth1"
state_topic: "blescan/1/kenneth"
payload_home: "on"
payload_not_home: "off"
source_type: "bluetooth_le"
- name: "BLE Button Diane1"
state_topic: "blescan/1/diane"
unique_id: "ble-button-diane1"
payload_home: "on"
payload_not_home: "off"
source_type: "bluetooth_le"
- name: "BLE Button Kenneth2"
state_topic: "blescan/2/kenneth"
unique_id: "ble-button-kenneth2"
payload_home: "on"
payload_not_home: "off"
source_type: "bluetooth_le"
- name: "BLE Button Diane2"
state_topic: "blescan/2/diane"
unique_id: "ble-button-diane2"
payload_home: "on"
payload_not_home: "off"
source_type: "bluetooth_le"
- name: "BLE Button Kenneth3"
state_topic: "blescan/3/kenneth"
unique_id: "ble-button-kenneth3"
payload_home: "on"
payload_not_home: "off"
source_type: "bluetooth_le"
- name: "BLE Button Diane3"
state_topic: "blescan/3/diane"
unique_id: "ble-button-diane3"
payload_home: "on"
payload_not_home: "off"
source_type: "bluetooth_le"
- name: "BLE Button Kenneth4"
state_topic: "blescan/4/kenneth"
unique_id: "ble-button-kenneth4"
payload_home: "on"
payload_not_home: "off"
source_type: "bluetooth_le"
- name: "BLE Button Diane4"
state_topic: "blescan/4/diane"
unique_id: "ble-button-diane4"
payload_home: "on"
payload_not_home: "off"
source_type: "bluetooth_le"
Why is this happening now? it is almost as if the mqtt integration loads the same file twice
There is no autodection happening.
The entities work. It is just errors in the log and only at startup
Note that tese BLE items are not connected to the HA box. They come from 4 ESP32s running code I have written myself with no auto discovery. It is all manually run via mqtt.
Please note that since this update, the Velbus VMB1TS sensor values are not displayed.
I had to roll back to earlier version. Kind regards
You should probably post an issue on github.
I really liked the new type of automation, thank you very much. Found such a problem that the sequence is not displayed in parallel actions
Hi, I have moved to python 3.10 and having some issues. Running core via venv on Ubuntu. All latest updates applied. 2022.9.6 being deployed into a fresh folder under venv. Has been this way for all relases of 2022.9. I also switched to Python 3.10 around the same time. I get an error for smartthings here :
File â/srv/homeassistant/lib/python3.10/site-packages/Crypto/PublicKey/RSA.pyâ, line 585
except ValueError, IndexError:
^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: multiple exception types must be parenthesized
I think I can fix this by doing the following but then lots of other things break like google-home and a few other modules
python3.10 -m pip uninstall cryptography pycrypto pycryptodome pycryptodomex cffi
python3.10 -m pip install --no-cache-dir cryptography
python3.10 -m pip install --no-cache-dir cffi
python3.10 -m pip install --no-cache-dir PyJWT
python3.10 -m pip install --upgrade homeassistant
Also- having issues with bimmer-connected as follows
File â/srv/homeassistant/lib/python3.10/site-packages/Crypto/Util/number.pyâ, line 139
value |= 2L ** (N-1) # Ensure high bit is set
^
SyntaxError: invalid decimal literal
Crypto from :-
Requirement already satisfied: cryptography==37.0.4 in /srv/homeassistant/lib/python3.10/site-packages (from homeassistant) (37.0.4)
@Cereal2nd
Are you aware of this?
Could it be that the VMB1TS hasnât broadcasted its current temperature?
(How long did you wait for a value to appear?)