Hi
I’ve integrated a Sonoff Pow 16. But it’s entity_id is switch.sonoff.
How do I change it to be usable, for instance in automation:
- id: '1556478149400'
alias: Heater_Winter_On
trigger:
- at: '07:30'
platform: time
condition:
- condition: state
entity_id: input_select.seasons
state: Winter
action:
service: switch.turn_on
entity_id: switch.sonoff
to for instance switch.sonoff_dressing_room?
Thanks in advance
If the switch was auto-discovered:
Clicking on the switch name in the front end to get the more information dialogue box up may reveal a cog icon at the top of the box you can use to change the settings. If no cog icon is available, change the name of the device in the device. Then restart HA to force a discovery update.
If you manually added the device. Change the switch name in it’s Home Assistant configuration.
yes, it’s in auto-discovery.
I tried to change on the device tasmota page but the only place I could find sonoff (lowercase) was on the topic:
changed it, but I don’t see any difference.
Do you know where I can change it?
Pretty sure you have to change the Client field to:
sonoff_dressing_room
Unfortunately no, this didn’t work:
- id: '1556478149400'
alias: Boiler_and_Heater_Winter_On
trigger:
# - at: '07:30'
- at: '11:05:00'
platform: time
condition:
- condition: state
entity_id: input_select.seasons
state: Winter
action:
service: switch.turn_on
entity_id: switch.sonoff_dressing_room
# entity_id: switch.Sonoff_vestiario
# entity_id: switch.sonoff
# add Boiler and second heater
And still this:
Any Ideas?
Change Friendly Name
Yes, but I was unable to use the friendly name as an entity_id
I will be adding 2 other Sonoff devices this week, and it would be nice to be able to set their entity_id
I wounder how they will show…
You didnt comment on this. What version you are running (HA)?
This is what I have right now
I can’t find the name sonoff lower case anywhere, or am I missing something in this configuration?
Once MQTT discovery sees a device, the entity_id given will stick. In order to change it, normally, you can use the cog in the upper right hand corner of the more info panel. But, this has been broken since 0.90. So, instead, you have to go to Configure->Entity Registry, search for the entity id there, click, and change.
Thanks, that did it
As I’m new with hassio, hadn’t explored that tab
No worries. Home Assistant is huge. And in a constant state of flux. At any given time, not everything works correctly. So it’s a moving target to navigate the current list of bugs and figure out how to do something.
Thankfully, the features MOST people use are working MOST of the time. This is just one of those times when it isn’t.
I’m still on 0.91.4 because 0.92.x isn’t stable enough yet for me. I was hoping this bug would be fixed by 0.92.1, but, I guess it isn’t. The fix for this was supposedly merged on 4/10. So either the fix didn’t fix it, or that particular merge hasn’t made it into a release yet.
you seem to be an advanced user, so maybe you can answer a few questions that I don’t understand?
I installed this version of hassio on raspberry pi 1B+:
hassos_rpi-2.11.img.gz
I figured that it’s an alphine linux:
core-ssh:/backup# cat /etc/*release
3.9.0
NAME=“Alpine Linux”
ID=alpine
VERSION_ID=3.9.0
PRETTY_NAME=“Alpine Linux v3.9”
HOME_URL=“https://alpinelinux.org/”
BUG_REPORT_URL=“https://bugs.alpinelinux.org/”
does it use doker?
if so, for my understanding, doker is a virtual environment. Is hassio running as a virtual machine?
in the installation manuals the say doker installation, do I follow those, or the manual?
I tried to manually install some software:
apk add python3
pip3 install --upgrade pip
apk add gcc
apk add python3-dev musl-dev linux-headers libffi-dev
pip3 install --upgrade appdaemon
after reboot, no trace of the installation
How do I install anything that is not on the add-on store?
How do I get a script to run at startup?
How do I get commands run at the start of any session?
like:
alias ll=‘ls -lah --color=auto’
alias dir=‘ls -lash --color=auto’
If you have the patience I would appreciate 
