yeah i did this. with 0 sec . doesnt have to wait. its good enough solution for voice controll, on the dash it still stays indicated as ON with your solution with that custom button card, thanks:)
I have an even better solution:)
My tv is a Sony tv, android tv and im using external sound system, so the tvs speakers are turned off, even if/when i change the tvs volume
(Bc im using optical out not hdmi eArc)
So i made an automation that checks the tvs volume
When i set it to 1-2-3 it changes the hdmi source on Lytmi
This is the most convenient way to change input on lytmi
I dont have to say anything nor open any app and press any button
For eg for hdmi 3:
alias: HDMI 3 (Volume 3)
description: ""
trigger:
- platform: state
entity_id:
- media_player.sonytv
attribute: volume_level
to: 0.03
for:
hours: 0
minutes: 0
seconds: 2
condition: []
action:
- service: number.set_value
metadata: {}
data:
value: "2"
target:
entity_id: number.hdmi_source
mode: single
Hey there! Sorry for ressurecting this thread.
I have Lytmi for 2 years now, and always complained the fact that I couldnât add on HA, so through this thread, I am already in a nicer place then before now that instead of using the Lytmi App, my lights are on SmartLife app and therefore, on HA. So thank you all!
My case: Differently from whatâs discussed here, I have the Neo (the one withouth HDMIs). And when discovered through HA, I just have 3 controls available: On/Off, Colour, Bright.
Which is ok, and I can work/be happy with, but you all know, once you start, you want all features. Specifically, be able to change from HA, the modes Screen / Music / Scene (and the option inherith from each one of this first option, for exampe, Screen, Weak / Normal / High).
My question to the brain trust:
Me having just these 3 controls (power/bright/color), is due:
- The model of the product (Neo, instead of Neo3), or
- Due me using âTuyaâ integration, not âLocal Tuyaâ (one day I will migrate to local tuya, but not todayâŚ)
Thanks in advance for any reply!
Tried hard, and found the solution.
After adding the âmainâ device into the Local Tuya, it asks if you want to add another entity. Realised I could add a âSelectâ type (instead of light):
Thatâs when I thought I could finally add the numbers shared before. But for mine, after using several times the âQuery Propertiesâ on Tuya Cloud, Iâve added:
# Valid Entries:
80000000000000000000000000000000;81000000000000000000000000000000;82000000000000000000000000000000;83000000000000000000000000000000;84000000000000000000000000000000;85000000000000000000000000000000;86000000000000000000000000000000;87000000000000000000000000000000;88000000000000000000000000000000;89000000000000000000000000000000;90000000000000000000000000000000;91000000000000000000000000000000;92000000000000000000000000000000;93000000000000000000000000000000;94000000000000000000000000000000;95000000000000000000000000000000;96000000000000000000000000000000;97000000000000000000000000000000;01000000000000000000000000000000
# Their respectives Friendly names (you can set whatever you want)
Screen: Weak;Screen: Normal;Screen: Strong;Music: Spectrum;Music: Electronic;Music: Listen;Scene: Rainbow;Scene: Fire;Scene: Read;Scene: Firework;Scene: Star;Scene: Drip;Scene: Particle;Scene: Flow;Scene: Ball;Scene: Swing;Scene: Breath;Scene: Pure;Solid
That did the trick, hope it helps someone.
This is exactly what I was looking for, I have options 22 and 24 but canât get to it work nicely.
How did you setup the rest, like power, brightness and color select?
EDIT:
I ended up using Tuya-Local instead and that required no setup, it was able to pull everything directly from the device.
Just throwing out there that it would be nice if someone could make a full fledged integration for this thing if possible. I struggle a lot with getting this thing configured correctly via the local tuya integration.
have to agree Tuya Local works a treat, i have a nvidia shield pro running via the FancyLED sync box,
have set up automations when switching to plex to run the sync box in video mode at a set % and another automation when tivimate is running to switch to a solid colour (pure) again at a set %
both switch scene mode perfectly but when switching to solid colour (pure mode) it always defaults to the last colour used in pure mode , this can be adjusted via the ha or tuya apps manually but what i am a little stumped at is there a way in my script i can tell it to also select a set colour when choosing the solid colour (pure mode)
as an example for the automations i run (all with voice command also)
plex on: turns on tv, amp , NVidia shield pro then selects plex app sync box turns on a goes into video mode .
tv on: turns on tv, amp , NVidia shield pro then selects tivimate app sync box turns on a goes into pure mode colour say i want is red.
bbc on: turns on tv, amp , NVidia shield pro then selects bbc iplayer app sync box turns on a goes into pure mode colour say i want is blue.
youtube on: turns on tv, amp , NVidia shield pro then selects youtube app sync box turns on a goes into pure mode colour say i want is green.
music on: turns on tv, amp , NVidia shield pro then selects Spotify app sync box turns on a goes into music mode ambient.
this is where i am stuck if i chose red manually on the tv automation in pure mode both bbc on and youtube on automation also is red unless i manually change
there must be a way and i am just overlooking it
After messing about with it last night i sussed it out all working as i want
Try tuya local 10x easier than local tuya
reeeeEEEHEEEHEEEEEEEALLY⌠well I just may have to check it out, thanks for the suggestion!
update
I installed the Tuya Local integration i got a connect errorâŚusing all the same info that i was able to connect with in the local tuya integration. Is there a trick to it?
update
Ok, finally got itâŚmanâŚwhat a real pain in the ass. These integration setups sometimes are infuriating.
So, I tried to do a manual setup because I thought it would be the easiest and transfer previous information. That did not work as I found (after the fact) that the Key seems to rotate, so the previous key was not workingâŚwas the issue i found out in the end.
What did work was setting the device up using the app method instead of manually, but only AFTER I previously removed the local tuya integration.
So far, it in fact does look like this tuya local installation is a more seamless intigration than manually entering everything. Very nice, thank you!