@123 and thanks for taking the time to help me!
RF Motion sensor key E565EE
retain: false
RF Garage Door contact sensor
- platform: mqtt
qos: 1
retain: false
Found them in allot of places
Okay for some reason I dont get the line numbering on the errors anymore so its hard to find what needs to be changes
Reading the links it looks like ratin is ok for switches…so most be for all the others
MQTT Switch publishes messages to a topic (via command_topic) therefore it makes sense this component offers the retain option (although there are valid reasons for setting this to retain: false which happens to be the default setting).
Ok so it should be enough to remove this from binary sensors
binary_sensor:
# RF Motion sensor
- platform: mqtt
state_topic: "tele/RF_Bridge1/RESULT"
name: 'Garage Motion'
value_template: '{{value_json.RfReceived.Data}}'
payload_on: ''
payload_off: ''
device_class: motion
qos: 1
# retain: false
just removed from every binary sensor and I got “Configuration valid!”
so everything should be back up and running after a reboot
Thanks for your help!
1 Like
last question I promise! 
the switch for the garageport now changed after the removal, and now it looks like this
but I still have my:
cover.sonoff_sv_garage:
device_class: garage
homebridge_cover_type: garage_door
friendly_name: Garageport
Could this be related to another change, and not the removal of retain & optimistic
I can’t make sense of this:
Please post the entire formatted configuration for the cover. Is the cover’s friendly_name in the customize.yaml file?
no I have everything in the configuration yaml file
customize:
cover.sonoff_sv_garage:
device_class: garage
homebridge_cover_type: garage_door
friendly_name: Garageport
# Garageport switch DIY
cover:
- platform: mqtt
name: "Sonoff SV Garage"
state_topic: "cmnd/garagestate/POWER2"
command_topic: "cmnd/Sonoff_SV_Garage/POWER"
payload_open: "ON"
payload_close: "ON"
payload_stop: "ON"
state_open: "ON"
state_closed: "OFF"
##########################
### Garage Switch ###
##########################
- platform: template
switches:
garage:
value_template: "{{ is_state('cover.sonoff_sv_garage', 'open') }}"
turn_on:
service: cover.close_cover
data:
entity_id: cover.sonoff_sv_garage
turn_off:
service: cover.open_cover
data:
entity_id: cover.sonoff_sv_garage
icon_template: >-
{% if is_state('cover.sonoff_sv_garage', 'open') %}
mdi:garage-open
{% else %}
mdi:garage
{% endif %}
group:
garage_door:
name: Garageport
view: no
control: hidden
icon: mdi:garage
entities:
- cover.sonoff_sv_garage
- switch.garage
That should be everything, and some notification on the state
That’s a weird configuration.
You have a group, that includes both the cover and a template switch, that uses the cover to provide the switch. Why?
According to documentation retain and optimistic are still available for cover MQTT.
I’m confused by your setup
I made a switch for the garageport and also created the “real” garage function in home assistant.
- cover.sonoff_sv_garage
- switch.garage
The switch was needed to get it working as a switch in google assistant or Siri - can’t remember
Is this a problem?
Its not different than having all the switches defined as both switches and lights
Its still there
So wouldnt the friendly name be changed by:
customize:
cover.sonoff_sv_garage:
device_class: garage
homebridge_cover_type: garage_door
friendly_name: GarageportGoogle assistant sees covers just fine.
I don’t know if it’s a problem but it seems like redundant work for no benefit
Any input to why Home assistant dosent see it as Garage port?
Deleting the switch dosent solve it…
And for some reason it ignores the:
customize:
cover.sonoff_sv_garage:
device_class: garage
homebridge_cover_type: garage_door
friendly_name: Garageport
The icon worked before showing open and closed correctly?
This update really calls for many changes 
Can’t you just rename it?
Maybee I misunderstod but I changed all the names for the switch to port…
group:
garage_door:
name: Garageport
view: no
control: hidden
icon: mdi:garage
entities:
- cover.sonoff_sv_garage
- switch.port
switch:
##########################
### Garage Switch ###
##########################
- platform: template
switches:
port:
value_template: "{{ is_state('cover.sonoff_sv_garage', 'open') }}"
turn_on:
service: cover.close_cover
data:
entity_id: cover.sonoff_sv_garage
turn_off:
service: cover.open_cover
data:
entity_id: cover.sonoff_sv_garage
icon_template: >-
{% if is_state('cover.sonoff_sv_garage', 'open') %}
mdi:garage-open
{% else %}
mdi:garage
{% endif %}
I think its all related to the customize settings?
I have always had this to hidden
customize:
sensor.nina_ipad_battery_level:
hidden: true
sensor.nina_ipad_battery_state:
hidden: true
but now they are shown again even if they are supposed to be hidden
and the same for the garage port customize setting
cover.sonoff_sv_garage:
device_class: garage
homebridge_cover_type: garage_door
friendly_name: Garageport
for some reason this dosent work anymore?
could this be a lovelace issue?
no - lovelace only changes how things are displayed
Hi David
Sorry but then it must mean that the customize settings is broken?
the sensor name is the same as always:
And the customize settings are correct
customize:
# Add an entry for each entity that you want to overwrite.
sensor.nina_ipad_battery_level:
hidden: true
sensor.nina_ipad_battery_state:
hidden: true
Same goes for the cover icon on the garage door?
Also I read some of your post and I am really confused isn’t lovelace the new standard?
what’s this storage mode? so far I have just kept it as is and kept upgrading it.
I can see in my string that I am now using the lovelace as default (No changes from me)
So this should be ok?
I now we are in a transition but it its very hard to find out how to fix things? 
especially when things worked perfectly and then they dont
Any help you can provide is greatly appreciated
Thanks
Lovelace will ignore hidden: true. In lovelace if you don’t want to see something, don’t add it to the card. If you have not ‘taken control’ of lovelace, it will use an autogenerated mode which will mimic old groups etc (but still will ignore hidden: true)
At some point, when you click on edit UI (3 dots top right) you take control and then you move from autogenerated to storage mode in lovelace and it will only show what you add to cards. Everything else will be hidden.
Hope that makes sense.
@DavidFW1960 So you’re telling me that I have to take control in order to Hide stuff, because the autogenerated mode is not working with the Hide rules in the customize group?
So taking the plunge is there a easy way to fix this in the editor
Basically remove or hide “Badges” I dont want top row
And changing the MDI to get back to the Icon that would change when openeing and closing the garagedoor?
I think this would give me a good start to fix the rest by hand.
Just got HAromey remote back online JUHU!
UPDATE:
Ended up just deleting the lines in the config I didnt want
But the MDI for the garageport is still eluding med?