[Smart Meter Interface] Setting smlj=0 on boot breaks Home Assistant discovery

[lippertmarkus]

PROBLEM DESCRIPTION

I'm using the Smart Meter Interface to read data from my heat meter. As it takes a few seconds after boot until data is available I disabled MQTT publish on boot by setting smlj=0 and activating it after 30 upsecs with smlj|=1 like mentioned in the docs.

This however leads to Home Assistant not discovering the sensors, also not after the first MQTT publish after TelePeriod.

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

• Read the Contributing Guide and Policy and the Code of Conduct
• Searched the problem in issues
• Searched the problem in discussions
• Searched the problem in the docs
• Searched the problem in the chat
• Device used (e.g., Sonoff Basic): ESP-01
• Tasmota binary firmware version number used: 13.4.0
  • Pre-compiled
  • Self-compiled
• Flashing tools used: Tasmotizer
• Provide the output of command: Backlog Template; Module; GPIO 255:

19:26:56.944 CMD: Backlog Template; Module; GPIO 255
19:26:56.968 MQT: stat/tasmota_7BC431/RESULT = {"NAME":"Generic","GPIO":[1,1,1,1,1,1,1,1,1,1,1,1,1,1],"FLAG":0,"BASE":18}
19:26:57.193 MQT: stat/tasmota_7BC431/RESULT = {"Module":{"1":"Sonoff Basic"}}
19:26:57.448 MQT: stat/tasmota_7BC431/RESULT = {"GPIO0":{"32":"Button1"},"GPIO1":{"0":"None"},"GPIO2":{"0":"None"},"GPIO3":{"0":"None"},"GPIO4":{"0":"None"},"GPIO5":{"0":"None"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO12":{"224":"Relay1"},"GPIO13":{"320":"Led_i1"},"GPIO14":{"0":"None"},"GPIO15":{"0":"None"},"GPIO16":{"0":"None"},"GPIO17":{"0":"None"}}

• If using rules, provide the output of this command: Backlog Rule1; Rule2; Rule3:

No rules

• Provide the output of this command: Status 0:

19:28:13.931 MQT: stat/tasmota_7BC431/STATUS = {"Status":{"Module":1,"DeviceName":"tasmota_7BC431","FriendlyName":["tasmota_7BC431"],"Topic":"tasmota_7BC431","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0,"StatusRetain":0}}
19:28:13.936 MQT: stat/tasmota_7BC431/STATUS1 = {"StatusPRM":{"Baudrate":2400,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota.bin.gz","RestartReason":"Software/System restart","Uptime":"1T19:27:08","StartupUTC":"","Sleep":50,"CfgHolder":4617,"BootCount":34,"BCResetTime":"1970-01-01T00:00:00","SaveCount":61,"SaveAddress":"F7000"}}
19:28:13.940 MQT: stat/tasmota_7BC431/STATUS2 = {"StatusFWR":{"Version":"13.4.0(tasmota)","BuildDateTime":"2024-02-20T14:14:48","Boot":31,"Core":"2_7_6","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8266EX","CR":"408/699"}}
19:28:13.945 MQT: stat/tasmota_7BC431/STATUS3 = {"StatusLOG":{"SerialLog":0,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["SplashNSurf-IoT",""],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00008009","2805C80001000600003C5A0A192800000000","00000080","00006000","00004000","00000000"]}}
19:28:13.957 MQT: stat/tasmota_7BC431/STATUS4 = {"StatusMEM":{"ProgramSize":697,"Free":304,"Heap":15,"ProgramFlashSize":1024,"FlashSize":1024,"FlashChipId":"14605E","FlashFrequency":40,"FlashMode":"DOUT","Features":["0809","879AC787","043E8001","000000CF","010013C0","C000F989","00004004","00001000","54000020","00000080","00000000"],"Drivers":"1,2,!3,!4,!5,!6,7,!8,9,10,12,!16,!18,!19,!20,!21,!22,!24,26,!27,29,!30,!35,!37,!45,62,!68","Sensors":"1,2,3,4,5,6,53","I2CDriver":"7"}}
19:28:13.964 MQT: stat/tasmota_7BC431/STATUS5 = {"StatusNET":{"Hostname":"tasmota-7BC431","IPAddress":"192.168.40.23","Gateway":"192.168.40.1","Subnetmask":"255.255.255.0","DNSServer1":"192.168.10.10","DNSServer2":"0.0.0.0","Mac":"DC:4F:22:7B:C4:31","Webserver":2,"HTTP_API":1,"WifiConfig":4,"WifiPower":17.0}}
19:28:13.970 MQT: stat/tasmota_7BC431/STATUS6 = {"StatusMQT":{"MqttHost":"192.168.10.10","MqttPort":1883,"MqttClientMask":"tasmota_7BC431","MqttClient":"tasmota_7BC431","MqttUser":"tasmota_7BC431","MqttCount":1,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}}
19:28:13.977 MQT: stat/tasmota_7BC431/STATUS7 = {"StatusTIM":{"UTC":"1970-01-02T19:28:13Z","Local":"1970-01-02T19:28:13","StartDST":"1970-01-01T00:00:00","EndDST":"1970-01-01T00:00:00","Timezone":"+00:00","Sunrise":"20:13","Sunset":"05:47"}}
19:28:13.985 MQT: stat/tasmota_7BC431/STATUS10 = {"StatusSNS":{"Time":"1970-01-02T19:28:13","WAERME":{"Zählernummer":123456789,"Energie":0.959,"Volumen":383.896,"Durchfluss":0,"Leistung":0,"Durchflusstemperatur":0.0,"Rücklauftemperatur":0.0,"Temperaturdifferenz":0.000}}}
19:28:13.992 MQT: stat/tasmota_7BC431/STATUS11 = {"StatusSTS":{"Time":"1970-01-02T19:28:13","Uptime":"1T19:27:08","UptimeSec":156428,"Heap":15,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"POWER":"OFF","Wifi":{"AP":1,"SSId":"SplashNSurf-IoT","BSSId":"72:A7:41:9F:8B:02","Channel":6,"Mode":"11n","RSSI":68,"Signal":-66,"LinkCount":1,"Downtime":"0T00:00:04"}}}

• Set weblog to 4 and then, when you experience your issue, provide the output of the Console log:

With setting smlj (correctly publishes first after TelePeriod after setting smlj|=1 but Home Assistant sensor discovery doesn't work - see screenshot below)

00:00:08.060 MQT: Attempting connection...
00:00:08.070 MQT: Connected
00:00:08.074 MQT: tele/tasmota_7BC431/LWT = Online (retained)
00:00:08.076 MQT: cmnd/tasmota_7BC431/POWER = 
00:00:08.083 MQT: tele/tasmota_7BC431/INFO1 = {"Info1":{"Module":"Sonoff Basic","Version":"13.4.0(tasmota)","FallbackTopic":"cmnd/tasmota_7BC431_fb/","GroupTopic":"cmnd/tasmotas/"}}
00:00:08.086 MQT: tele/tasmota_7BC431/INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-7BC431","IPAddress":"192.168.40.23"}}
00:00:08.088 MQT: tele/tasmota_7BC431/INFO3 = {"Info3":{"RestartReason":"Software/System restart","BootCount":35}}
00:00:08.091 MQT: stat/tasmota_7BC431/RESULT = {"POWER":"OFF"}
00:00:08.093 MQT: stat/tasmota_7BC431/POWER = OFF
00:00:08.175 QPC: Reset
00:00:12.357 MQT: stat/tasmota_7BC431/STATUS1 = {"StatusPRM":{"Baudrate":2400,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota.bin.gz","RestartReason":"Software/System restart","Uptime":"0T00:00:11","StartupUTC":"","Sleep":50,"CfgHolder":4617,"BootCount":35,"BCResetTime":"1970-01-01T00:00:00","SaveCount":62,"SaveAddress":"F6000"}}
00:00:12.366 MQT: tele/tasmota_7BC431/STATE = {"Time":"1970-01-01T00:00:12","Uptime":"0T00:00:12","UptimeSec":12,"Heap":16,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":658,"MqttCount":1,"POWER":"OFF","Wifi":{"AP":1,"SSId":"SplashNSurf-IoT","BSSId":"72:A7:41:9F:8B:02","Channel":6,"Mode":"11n","RSSI":72,"Signal":-64,"LinkCount":1,"Downtime":"0T00:00:04"}}
00:00:13.390 MQT: stat/tasmota_7BC431/STATUS11 = {"StatusSTS":{"Time":"1970-01-01T00:00:13","Uptime":"0T00:00:12","UptimeSec":12,"Heap":19,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":729,"MqttCount":1,"POWER":"OFF","Wifi":{"AP":1,"SSId":"SplashNSurf-IoT","BSSId":"72:A7:41:9F:8B:02","Channel":6,"Mode":"11n","RSSI":72,"Signal":-64,"LinkCount":1,"Downtime":"0T00:00:04"}}}
00:00:14.413 MQT: stat/tasmota_7BC431/RESULT = {"Time":"1970-01-01T00:00:14","Uptime":"0T00:00:13","UptimeSec":13,"Heap":20,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":795,"MqttCount":1,"POWER":"OFF","Wifi":{"AP":1,"SSId":"SplashNSurf-IoT","BSSId":"72:A7:41:9F:8B:02","Channel":6,"Mode":"11n","RSSI":72,"Signal":-64,"LinkCount":1,"Downtime":"0T00:00:04"}}
00:00:15.564 MQT: stat/tasmota_7BC431/STATUS10 = {"StatusSNS":{"Time":"1970-01-01T00:00:15"}}
00:00:30.005 read meter (debug log 30s)
00:00:30.007 wakeup start
00:00:33.183 wakeup end
00:00:33.185 wait for the meter
00:00:33.538 Init MBus 1040004016; SCAN for Device 00
00:00:33.896 request data 107BFE7916 aktuelle Werte!!!
00:00:33.904 request data finished
00:01:03.643 read meter (WebUI update 60s)
00:01:03.645 wakeup start
00:01:05.822 wakeup end
00:01:05.824 wait for the meter
00:01:06.178 Init MBus 1040004016; SCAN for Device 00
00:01:06.536 request data 107BFE7916 aktuelle Werte!!!
00:01:06.544 request data finished
00:05:17.638 MQT: tele/tasmota_7BC431/STATE = {"Time":"1970-01-01T00:05:17","Uptime":"0T00:05:12","UptimeSec":312,"Heap":18,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"POWER":"OFF","Wifi":{"AP":1,"SSId":"SplashNSurf-IoT","BSSId":"72:A7:41:9F:8B:02","Channel":6,"Mode":"11n","RSSI":64,"Signal":-68,"LinkCount":1,"Downtime":"0T00:00:04"}}
00:05:17.647 MQT: tele/tasmota_7BC431/SENSOR = {"Time":"1970-01-01T00:05:17","WAERME":{"Zählernummer":123456789,"Energie":0.959,"Volumen":383.896,"Durchfluss":0,"Leistung":0,"Durchflusstemperatur":0.0,"Rücklauftemperatur":0.0,"Temperaturdifferenz":0.000}}

Without setting smlj in the script (0 values are published to MQTT the first time which should be prevented but sensors are correctly discovered in Home Assistant - see screenshot below):

RSL: RESULT = {"Time":"1970-01-01T00:00:00","SML":{"CMD":"sml_globs.ser_act_LED_pin: 255"}}
SNS: Hardware Serial
meters: 1 , decode lines: 8, memory used: 1982 bytes
WIF: Connecting to AP1 SplashNSurf-IoT Channel 6 BSSId 72:A7:41:9F:8B:02 in mode 11n as tasmota-7BC431...
WIF: Connected
HTP: Web server active on tasmota-7BC431 with IP address 192.168.40.23
MQT: Attempting connection...
MQT: Connected
MQT: tele/tasmota_7BC431/LWT = Online (retained)
MQT: cmnd/tasmota_7BC431/POWER = 
MQT: tele/tasmota_7BC431/INFO1 = {"Info1":{"Module":"Sonoff Basic","Version":"13.4.0(tasmota)","FallbackTopic":"cmnd/tasmota_7BC431_fb/","GroupTopic":"cmnd/tasmotas/"}}
MQT: tele/tasmota_7BC431/INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-7BC431","IPAddress":"192.168.40.23"}}
MQT: stat/tasmota_7BC431/RESULT = {"POWER":"OFF"}
MQT: stat/tasmota_7BC431/POWER = OFF
QPC: Reset
MQT: stat/tasmota_7BC431/STATUS1 = {"StatusPRM":{"Baudrate":2400,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota.bin.gz","RestartReason":"Software/System restart","Uptime":"0T00:00:11","StartupUTC":"","Sleep":50,"CfgHolder":4617,"BootCount":31,"BCResetTime":"1970-01-01T00:00:00","SaveCount":56,"SaveAddress":"F4000"}}
MQT: tele/tasmota_7BC431/STATE = {"Time":"1970-01-01T00:00:12","Uptime":"0T00:00:12","UptimeSec":12,"Heap":16,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":674,"MqttCount":1,"POWER":"OFF","Wifi":{"AP":1,"SSId":"SplashNSurf-IoT","BSSId":"72:A7:41:9F:8B:02","Channel":6,"Mode":"11n","RSSI":70,"Signal":-65,"LinkCount":1,"Downtime":"0T00:00:04"}}
MQT: tele/tasmota_7BC431/SENSOR = {"Time":"1970-01-01T00:00:12","WAERME":{"Zählernummer":0,"Energie":0.000,"Volumen":0.000,"Durchfluss":0,"Leistung":0,"Durchflusstemperatur":0.0,"Rücklauftemperatur":0.0,"Temperaturdifferenz":0.000}}
MQT: stat/tasmota_7BC431/STATUS11 = {"StatusSTS":{"Time":"1970-01-01T00:00:13","Uptime":"0T00:00:12","UptimeSec":12,"Heap":19,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":744,"MqttCount":1,"POWER":"OFF","Wifi":{"AP":1,"SSId":"SplashNSurf-IoT","BSSId":"72:A7:41:9F:8B:02","Channel":6,"Mode":"11n","RSSI":76,"Signal":-62,"LinkCount":1,"Downtime":"0T00:00:04"}}}
MQT: stat/tasmota_7BC431/RESULT = {"Time":"1970-01-01T00:00:14","Uptime":"0T00:00:13","UptimeSec":13,"Heap":19,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":817,"MqttCount":1,"POWER":"OFF","Wifi":{"AP":1,"SSId":"SplashNSurf-IoT","BSSId":"72:A7:41:9F:8B:02","Channel":6,"Mode":"11n","RSSI":76,"Signal":-62,"LinkCount":1,"Downtime":"0T00:00:04"}}
MQT: stat/tasmota_7BC431/STATUS10 = {"StatusSNS":{"Time":"1970-01-01T00:00:15","WAERME":{"Zählernummer":0,"Energie":0.000,"Volumen":0.000,"Durchfluss":0,"Leistung":0,"Durchflusstemperatur":0.0,"Rücklauftemperatur":0.0,"Temperaturdifferenz":0.000}}}
MQT: tele/tasmota_7BC431/STATE = {"Time":"1970-01-01T00:05:17","Uptime":"0T00:05:12","UptimeSec":312,"Heap":19,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"POWER":"OFF","Wifi":{"AP":1,"SSId":"SplashNSurf-IoT","BSSId":"72:A7:41:9F:8B:02","Channel":6,"Mode":"11n","RSSI":66,"Signal":-67,"LinkCount":1,"Downtime":"0T00:00:04"}}
MQT: tele/tasmota_7BC431/SENSOR = {"Time":"1970-01-01T00:05:17","WAERME":{"Zählernummer":123456789,"Energie":0.955,"Volumen":381.049,"Durchfluss":0,"Leistung":0,"Durchflusstemperatur":0.0,"Rücklauftemperatur":0.0,"Temperaturdifferenz":0.000}}

TO REPRODUCE

Steps to reproduce the behavior:

1. Setup & configure MQTT
2. Add the following script:

   >D
   ;start, define variables
   wkup=1
   >B
   smlj=0
   ;setup sensor
   ->sensor53 r
   ->sensor53 d0
   ->sensor53 l255
   ;tper=300 
   >S
   ; this device is powered by battery
   ; frequent requests will lead to blocking and reduces lifetime
   ; starting sequence:
   ;- press button on device once
   ;- restart Tasmota with script sctivated (you have 5 minutes to do this)
   ;- after 30s first data is retrieved and logged (including SYSLOG depending on Tasmota log config)
       ;- after 60s WebUI is updated first time
   ;- now every 45min a new request is done, updated in WebUI (and transferred by MQTT every TPER period); polling period needs to be less 60min to avoid sleep mode of device!
   if upsecs==30 {
       ->sensor53 d1
       print read meter (debug log 30s)
       =#readmeter
       smlj|=1
   }
   if upsecs==60 {
       ->sensor53 d0
       print read meter (WebUI update 60s)
       =#readmeter
   }
   if upsecs%2700==0 {
       print read meter (modulo 2700s)
       =#readmeter
   }
   
   >M 1
   +1,3,rE1,0,2400,WAERME,1
   ; note that maximum of chars per line is 8 so set buffer to 8 to get non-delayed decoding
   1,=so3,8
   1,68080072bcd8@1,Zählernummer,,Zählernummer,0
   ; note that 16 = 0+16 means that this particular value has 0 comma places but is transferred immediately by MQTT
   1,0406uuUUuuUUs@1000,Energie,MWh,Energie,3
   1,0413uuUUuuUUs@1000,Volumen,m³,Volumen,3
   1,043buuUUuuUUs@1,Durchfluss,l/h,Durchfluss,0
   1,042buuUUuuUUs@1,Leistung,W,Leistung,0
   1,025auuUU@10,Durchflusstemperatur,°C,Durchflusstemperatur,1
   1,025euuUU@10,Rücklauftemperatur,°C,Rücklauftemperatur,1
   1,0360uuUU@1000,Temperaturdifferenz,K,Temperaturdifferenz,3
   #
   
   #readmeter
   print wakeup start
   ;set serial protocol
   sml(-1 1 "2400:8N1")
   ;send 0x55 for 2,2 seconds with 8N1 (53x), 2400 baud (wakeup sequence)
   for wkup 1 53 1
   sml(1 1 "55555555555555555555")
   next
   print wakeup end
   wkup=1
   print wait for the meter
   ;wait for the meter to wake up
   delay(350)
   ;switch serial protocol
   sml(-1 1 "2400:8E1")
   print Init MBus 1040004016; SCAN for Device 00
   sml(1 1 "1040004016")
   delay(350)
   print request data 107BFE7916 aktuelle Werte!!!
   sml(1 1 "107BFE7916")
   ;print request data 105BFE5916
   ;sml(1 1 "105BFE5916")
   print request data finished
   #

3. Verify in Home Assistant that no sensors are discovered, also not after the first MQTT publish after TelePeriod (screenshot see below)
4. Modify the script and remove the two lines setting smlj
5. Verify in Home Assistant that the sensors are correctly discovered (screenshot see below) but 0-values are published on the first time which should be prevented.

EXPECTED BEHAVIOUR

Sensors should be discovered in Home Assistant but stay in "unavailable"/"unknown" until first publish happens after smlj|=1 after TelePeriod.

SCREENSHOTS

If applicable, add screenshots to help explain your problem.
Home Assistant when setting smlj in the script like above (Stays like this also after the first MQTT publish after TelePeriod):

Home Assistant without setting smlj in the script (correctly discovers sensors but gives 0 values directly after boot):

ADDITIONAL CONTEXT

Add any other context about the problem here.

(Please, remember to close the issue when the problem has been addressed)

[Jason2866]

As designed. Device discovery is done one time during startup. If you disable mqtt it can not work.

[lippertmarkus]

I just tested it with manually publishing MQTT messages. The behavior should be as follows:

1. Publish discovery message to tasmota/discovery/DC4F227BC431/sensors on startup but include the sensor also when smlj=0:

   {
     "sn": {
       "Time": "1970-01-01T00:00:18",
       "WAERME": {
         "Zählernummer": 0,
         "Energie": 0,
         "Volumen": 0,
         "Durchfluss": 0,
         "Leistung": 0,
         "Durchflusstemperatur": 0,
         "Rücklauftemperatur": 0,
         "Temperaturdifferenz": 0
       }
     },
     "ver": 1
   }
   

2. When smljj=0 no data is published to tele/tasmota_7BC431/SENSOR or tele/tasmota_7BC431/STATE

3. Home Assistant correctly shows the tasmota device as online and shows previous sensor values (e.g. before last reboot):
   

   (If there are no previous sensor values Home Assistant will correctly show the sensor values as "unavailable").

4. As soon as values are available and smlj|=1 these are published to tele/tasmota_7BC431/SENSOR

I see no reason why the tasmota discovery message shouldn't include the sensors if we just want to delay when we first send the sensor values.

[lippertmarkus]

@sfromis Thanks! Would it be possible to add an option so that smlj=0 just prevents publishing to tele/tasmota_7BC431/SENSOR but still allows retrieving the sensor value when constructing the discovery payload for tasmota/discovery/DC4F227BC431/sensors?

[sfromis]

You may prefer a different behavior, but there is no "should" there. And I already explained why the discovery message will not include sensors when they are not being published.

The architecture does not include sensor metadata existing "somewhere" before actually being generated, meaning published. Whether an option could be introduced is not something I'm involved in.

One potential strategy could be that you have logic to do an extra restart when circumstances are "right".

[lippertmarkus]

Thanks for the explanation, could you point me to the code where the discovery message is constructed?

[sfromis]

https://github.com/arendst/Tasmota/blob/development/tasmota/tasmota_xdrv_driver/xdrv_12_discovery.ino#L244-L250

That includes calling all of potentially many drivers each generating the JSON part for a reading of the sensors.

[Stefan8615]

Any solution on this in the meantime? I have the same issue - thanks!

[nikito7]

Maybe

So19 1
So19 0

[sfromis]

Or shorter, just the last command. SetOption19 0 will do a publish of the discovery payloads, even if the setting was already off.

[Stefan8615]

Thanks!
And how do I include this in my Tasmota Script?

[JohnyPeaN]

Hi, sorry for reviving this old thread, but somebody might find this useful.
I was trying to solve the same problem and @nikito7 had a good idea. Didn't work exactly as intended with both commands, but just running "setoption19 0" reruns autodiscovery which solves the problem. This is how I used it in script:
>B smlj=0 =>sensor53 r

>R smlj=0

>S if upsecs>60 then if smlj=0 then =>setoption19 0 smlj=1 endif endif

...

I set smlj=0 on boot or script restart, wait for 60 seconds when the data from meter driver are populated and enable smlj=1 and also run the so19 0 which triggers autodiscovery. Nested condition is used so the so19 command runs only once. There is still a slight annoyance with this solution where the entities in HA dissapear for 60 secconds (first AD after boot erases them and so19 rediscovers them back after 60s).