Delete the Lytmi app, pair Neo 3 with tuya/smart life app, same GUI.
1 Like
mine:
Thank you! Works perfectly.
How did you set up a number entity as a slider? After i set it up as a number it displays a number with and up/down arrow
Also, in case this is helpful to anyone else
80000000000000000000000000000000 = Video Video
81000000000000000000000000000000 = Video Recreation
82000000000000000000000000000000 = Video Game
9B000000000000000000000000000000 = Music absolute
9C000000000000000000000000000000 = Music Electro
9D000000000000000000000000000000 = Music Ambience
98000000000000000000000000000000 = Music Classic
99000000000000000000000000000000 = Music Pop
9A000000000000000000000000000000 = Music Rock
mushroom-number-card for example, like mine
yeah, i could convert it in a card, but I’m wanting to know how to get it as an entity that shows a slider; Like vzoltan example controls. It means less work later If i can get the entity correct.
My current controls as i figure this out…
How did you create your hdmi button? To get its status too?
Bc mine is kind of a fake button, since its originally a input number entity, and i crrated button with the helper and then an automation that triggered by the press of this helper button…
I think i set the steps to 5 rather than 1 and then it became a slider
Still got the same result, unfortunately
That did it , thank you
This is my HDMI 1 button, look how it points to “value: 0”
number.hdmi is my entity for neo3 hdmi input number
Simply call a service to change the number of that entity and if the value is 0 (in this case, hdmi 1 input), apply color. No automation needed.
Same with other buttons but changing values to 1, 2, 3 on call-service and the color.
I think you can do this with regular button or tile card, but I like this HACS card, more flexible. The key is “call-service” action on tap.
type: custom:button-card
name: Fire Tv
entity: number.hdmi
icon: mdi:hdmi-port
color: rgb(85, 85, 85)
size: 100%
styles:
card:
- height: 55px
name:
- font-weight: bold
- font-size: 13px
- color: rgb(85, 85, 85)
state:
- value: '0'
color: lime
styles:
name:
- color: rgb(255, 255, 255)
tap_action:
action: call-service
service: number.set_value
target:
entity_id: number.hdmi
data:
value: '0'
This is the code for my sliders, if you like it (mushroom-number-card and car-mod needed).
- type: custom:mushroom-number-card
entity: number.neo_3_brightnes
icon: mdi:brightness-6
layout: horizontal
primary_info: none
secondary_info: none
display_mode: slider
- type: custom:mushroom-number-card
entity: number.neo_3_diffuser
icon: mdi:speedometer
layout: horizontal
primary_info: none
secondary_info: none
display_mode: slider
card_mod:
style:
mushroom-shape-icon$: |
.shape {
--shape-color: none !important;
}
mushroom-number-value-control$:
mushroom-slider$: |
.slider {
height: 11px !important;
margin-top: 15px !important;
--main-color: #999999 !important;
--bg-color: #333333 !important;
}
.: |
ha-card {
height: 35px !important;
}
ha-state-icon {
color: #bdbbbb;
}
type: custom:button-card
this breaks it, everyting else ok, but without this, there wont be visual feedback on the button state
found it
thanks, works
Is it possible to create a switch or “device”
For these sliders and fake-buttons?
So i could expose these to google home and be able to control via voice?
The first 4 in the first row are switches by default from local tuya, so those can be controlled vie google home and voice
Also the brightness works via google home/voice but thisone comes form offica tuya integration with google home
Make a script with the command you want to send, then expose the script to google home.
I’m still testing this out, but I’m using a simple fold entity row card nested underneath my TV Media card in a grid card
type: custom:fold-entity-row
head:
type: section
label: Neo Pro Lytmi 3
entities:
- switch.neo_pro_power
- number.neo_pro_hdmi_selector
- select.neo_pro_video_mode
- number.neo_pro_brightness
- number.neo_pro_degree_of_diffusion
I also have an automation to switch things depending on what kodi or my htpc is doing…in theory, I should never have to touch the neo pro
automation triggered on media type attribute
alias: Kodi- Neo Pro 3 Video/Music/Gaming Mode
description: ""
trigger:
- platform: state
entity_id:
- media_player.kodi_mediaplayer
attribute: media_content_type
to: music
id: Kodi - Music Playing
- platform: state
entity_id:
- media_player.kodi_gameroom
attribute: media_content_type
to: tvshow
id: Kodi - TV Show Playing
- platform: state
entity_id:
- media_player.kodi_mediaplayer
attribute: media_content_type
to: movie
id: Kodi - Movie Playing
- platform: state
entity_id:
- sensor.htpc_hyperspin_running
to: "1"
id: Hyperspin Running
- platform: state
entity_id:
- sensor.htpc_hyperspin_running
to: "0"
id: Hyperspin Not Running
condition: []
action:
- choose:
- conditions:
- condition: trigger
id:
- Kodi - Movie Playing
- Kodi - TV Show Playing
- Hyperspin Not Running
sequence:
- device_id: 2f051e202a75e30027aedc400bedeef1
domain: select
entity_id: a9c6ff0a2cfcbd053e264a4a26cea359
type: select_option
option: Video
- device_id: 2f051e202a75e30027aedc400bedeef1
domain: number
entity_id: 377f48841e6e17c9df2e775bac17c744
type: set_value
value: 1000
- device_id: 2f051e202a75e30027aedc400bedeef1
domain: number
entity_id: e2dc53255c9e35b41042fde573aa67a9
type: set_value
value: 184
alias: Movie or TV Show Mode
- conditions:
- condition: trigger
id:
- Kodi - Music Playing
sequence:
- device_id: 2f051e202a75e30027aedc400bedeef1
domain: select
entity_id: a9c6ff0a2cfcbd053e264a4a26cea359
type: select_option
option: " Music Rock"
alias: Music Mode
- conditions:
- condition: trigger
id:
- Hyperspin Running
sequence:
- device_id: 2f051e202a75e30027aedc400bedeef1
domain: select
entity_id: a9c6ff0a2cfcbd053e264a4a26cea359
type: select_option
option: Game
- device_id: 2f051e202a75e30027aedc400bedeef1
domain: number
entity_id: 377f48841e6e17c9df2e775bac17c744
type: set_value
value: 700
alias: Gaming Mode
mode: single
I have not yet seen/discovered values to specify a “Scene” in the Neo Pro
update
I found a way to find the values in IOT…this should be all of them.
Name:
Video;
Recreation;
Game;
Music Absolute;
Music Electro;
Music Ambience;
Music Classic;
Music Pop;
Music Rock;
Scene Rainbow;
Scene Fire;
Scene Read;
Scene Fireworks;
Scene Star;
Scene Drip;
Scene Particle;
Scene Flow;
Scene Ball;
Scene Swing;
Scene Breath;
Scene Pure
Value:
80000000000000000000000000000000;
81000000000000000000000000000000;
82000000000000000000000000000000;
9B000000000000000000000000000000;
9C000000000000000000000000000000;
9D000000000000000000000000000000;
98000000000000000000000000000000;
99000000000000000000000000000000;
9A000000000000000000000000000000;
86000000000000000000000000000000;
87000000000000000000000000000000;
88000000000000000000000000000000;
89000000000000000000000000000000;
90000000000000000000000000000000;
91000000000000000000000000000000;
92000000000000000000000000000000;
93000000000000000000000000000000;
94000000000000000000000000000000;
95000000000000000000000000000000;
96000000000000000000000000000000;
97000000000000000000000000000000
it was easier to create input_bulean toggle and add automation to it then expose iput_bulean to google assistant
google_assistant:
project_id: *****************
service_account: !include SERVICE_ACCOUNT.JSON
report_state: true
exposed_domains:
- switch
- light
- sensor
- input_boolean
Only small issue/problem with this, that when i say hey google turn on HDMI1
and then i say hey google turn on HDMI2
well it turns that on and Lytmi changes the input, but HDMI1 stays ON for google home so when i say again hey google turn on hdmi1 it wont change to hdmi1 since its already on, and lytmi stays on hdmi2
unfortunatelly there is no voice command for “flip” wich would do the trick, since the automation changes the source on flip not on change.
but i found the voice command that google understands for this:
hey google Toggle …
and like this it works, but toggle is a strange word to say for me since english is not my native language, flip is much easier to say:)
Uhm… you can try to put a timer on the switches to turn it off, for example 2 seconds, this way when you say “hey google, flip hdmi 1”, the toogle is switched ON on google home, and after 2 seconds turned off waiting for new commands, because there is no action (hdmi switch to other input) with “power off switch”.
It’s not the most elegant solution but I think that will work.