You are running 2022.2.3? They fixed some Spotify stuff.
I am, but the media browser isn’t showing anything from spotify nonetheless.
Core-2022.2 appears to have broken localtuya.
No longer visible in Integrations. Devices no longer available.
Logs say: “Setup failed for localtuya: Integration not found”.
Have I missed something?
I’ve been looking at the button-card. Why should i use the input_button in stead?
Im’ just trying to find out a use-case for it. No reason to feel attacked.
was looking for that too, but then found one:
input_button:
wake_synology_nas:
name: Wake Synology Nas
icon: mdi:nas
which is a simple button to execute a script directly:
automation:
- alias: Wake Synology Nas
id: Wake Synology Nas
trigger:
platform: state
entity_id: input_button.wake_synology_nas
action:
service: wake_on_lan.send_magic_packet
data:
mac: !secret synology_mac
and, you Shouldn’t, but you could. Only a single press required. Nice.
Ofc, many other ways available too, like a single script. Or Button, or, button row, or, custom:button-card, or…
the beauty of things, is you have a choice 
Still works for me.
See reply by Mariusthvdb.
No reason to feel I am being attacked.
ok, in that case, it looks fine. (although, I would still choose a button-card, sorry 
, as it offers more choices… )
Thanks!
(probably a case of professional habit. I’m a professional analyst programmer. (not python) When creating programs for clients, you know, they always want just a bit more . In this case, I would probably get the question :"Pressing once, starts the nas? And pressing twice, stops it again? )
Anyway, thanks for answering!
Excellent! You should have no difficulty submitting a Feature Request for your ideas to improve input_button. The community will appreciate your contribution. 
4 Likes
do you know what it should fix? Still nothing under “tracks” and “albums”, and the tracks under “playlists” only show 100 first tracks…
While looking around for info about the input_button, I’ve read that there were problems exporting it to Google assistant. Tested it, and it seems to work now.
It’s available as a “scene” in google assistant. I think when adding more features, you’ll loose this, because you just “activate” a scene.
I’ll think about it…
What’s with all the Tuya errors? The Core log is nothing but continuous lines of this error since last Core update:
2022-02-07 08:57:15 ERROR (Thread-15) [tuya_iot] Unexpected disconnection.7
[2022-02-07 08:57:16,715] [tuya-openmq] Unexpected disconnection.7
Thank you! Upgrading to tasmota 10.1.0 fixed the issue where the lights did not connect to MQTT after upgrading to 2022.2
(adding verbose response to make it easier for others to find via search)
Got exact same error here, did you get your problem fixed? Thanks.
I see a lot of people had problems with the energy management, this is a bit related. My energy usage all seems to be working fine because it was set to state_class: total_increasing even before the update. But the cost sensor that was generated by the system was not. Before I was running 2021.12 and was working fine, updated to 2022.2.2 two days ago at 5/2 and now the cost sensor seems to be running haywire. It is being reset all the time.
Is there any way to set it back to OFF, even with no state change? I need it initially OFF.
Beta version always have a “b” and then the beta version number at the end, so for this release it started with 2022.2.0b0, then 2022.2.0b1, … until then a week later 2022.2.0 (the stable version) was released.
EDIT: Corrected numbering. First beta is indeed “b0”.
1 Like
2022.2.0b0
It seems no error with Chrome.
Thanks Philip. I suspected as much, but since I hadn’t seen a beta release yet, I wasn’t sure. I didn’t want things to start being installed automatically!
Is there a general stable release target (like the 8th of each month, or first Tuesday? Or is it really a “check the release page every day” kind of thing? Cheers.