Wrong date, my addons stopped working. Now i cant even connect to my server.
I completely blocked out the date when I looked at it, was focusing on the TZ & time. 
Seems a little off, 231 daysâŚ
Yes I see that now.
Whatâs your actual time and whatâs the time from the template editor?
Anyone know if it is possible to add Presets to the dialog page for WLED lights? Currently it shows Power, Color and Effects but I primarily adjust my WLED lights using Presets.
When I took the screenshot it was 16:08 utc+1.
Now Iâm trying to reach my servers ip, but refused to connect. I can ping the IP but cant reach it.
Probably because of the dead duckdns addonâŚ
The encryption DuckDNS uses will not work if the time is not correct.
1 Like
So the difference in time doesnât seem to be significant in computing, so Iâm not sure what could cause your issue. Are you allowing HA access to set the time from the internet? To set up HA, you need to provide it with internet access. After itâs set up, it doesnât need internet access anymore.
Edit - I thought I was having an issue with the precision because it wasnât showing correctly on my dashboard (and it wasnât related to the user number settings mentioned earlier). However after continuing to play around with it the issue seems to be the custom button card and the multiple-entity-row I was using. I was able to use math.round on the button card to get that displaying how I wanted but still looking for solutions to the multiple entity row; regardless, it doesnât appear to be a release issue.
Hi.
I have had some really strange issues with my skyconnect, and this sometimes helped me: Delete the integration, reboot the host (not just HA), reinstall the integration.
Do you have other USB devices attached? If you have the âTerminalâ addon do âls -la /dev/serial/by-id/â to get a list of USB devices and their address if you are unsure if you have multiple devices.
Dear friends, I am new in this forum. Iâm not sure if this is the right place to post my problem. I just updated H.A. to version 2023.3 (docker version in a raspberry pi4). I have received all the improvements of the update but the new ârestart home assistant menuâ does not appear, the shutdown button does appear but no option, just restart stopping automations and scripts. I have cleared browser cache. Any idea what could be happening? thanks in advance.- A cordial greeting to all
Experiencing problems with Tibber Pulse after upgrade, anyone else?
Edit. Works like a charm now after last update. Thanks 
If youâve recently added any USB3 peripherals, interference caused by that that may have knocked your devices off. I recently swapped to a SSD which killed everything Zigbee until I got a powered USB hub and 1.5m extension cable.
Using the new âQuick Reloadâ service does that reload only (reload supportedâŚ) YAML configurations that have changed since the last reload as the description under the button implies or does it reload every yaml config even if they havenât changed?
to be more precise, if I only make a change to one template sensor yaml config will it only reload that one template sensor config, will it reload all of the other yaml configured template sensors or will it reload all of the various yaml domains as well?
During the release party stream Frenck mentioned that only changed configs would be reloaded. If nothing changed then nothing is reloaded.
1 Like
The restart dialog can have 4 items :
- quick reload only if you have advanced mode enabled
- restart home assistant
- reboot system only if you are on supervised or hass os
- shutdown system only if you are on supervisor or hass os.
If you doesnât have advanced mode and run a docker installation, you will only have the restart item so we donât display the dialog but only the restart confirmation.
3 Likes
"In the case of Chrome, Edge, and Firefox (all latest versions) on a Windows computer with NVDA, the new vertical sliders work correctly. Bingo! Hereâs my appreciation.
Unfortunately, Android 13 and Google TalkBack 13.1 do not allow for adjusting the brightness slider. Only the current set level is read aloud, so we have a problem to solve here. I have checked and the problem exists with both vertical and horizontal sliders in the HomeAssistant Companion app and in Chrome and Edge browsers on the Android system. Both vertical and horizontal sliders could be improved here."
The âToggleâ button that allows turning the light on and off always has the label âToggleâ, which doesnât provide feedback on the current state of the light. It would be helpful to improve this by describing the states of the light as on/off.
Thank you for the info.
I restored my backup from two days ago. The update went well to the new version, like in the afternoon. After two restarts the date is again 2022-07-13 13:58.
e[32m23-03-02 20:06:45 INFO (MainThread) [supervisor.host.control] Initialize host reboot using loginde[0m
e[32m23-03-02 20:06:45 INFO (MainThread) [supervisor.docker.monitor] Stopped docker events monitore[0m
e[32m23-03-02 20:06:45 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.APPLICATION' stopping 6 add-onse[0m
e[32m23-03-02 20:06:45 INFO (SyncWorker_1) [supervisor.docker.interface] Stopping addon_core_configurator applicatione[0m
e[32m23-03-02 20:06:50 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning addon_core_configurator applicatione[0m
e[32m23-03-02 20:06:50 INFO (SyncWorker_2) [supervisor.docker.interface] Stopping addon_a0d7b954_nodered applicatione[0m
e[32m23-03-02 20:06:51 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Received message 257:None is not WSMsgType.TEXTe[0m
e[32m23-03-02 20:06:51 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closede[0m
e[32m23-03-02 20:06:55 INFO (SyncWorker_2) [supervisor.docker.interface] Cleaning addon_a0d7b954_nodered applicatione[0m
e[32m23-03-02 20:06:55 INFO (SyncWorker_0) [supervisor.docker.interface] Stopping addon_45df7312_zigbee2mqtt applicatione[0m
e[32m23-03-02 20:07:07 INFO (SyncWorker_0) [supervisor.docker.interface] Cleaning addon_45df7312_zigbee2mqtt applicatione[0m
e[32m23-03-02 20:07:07 INFO (SyncWorker_7) [supervisor.docker.interface] Stopping addon_cebe7a76_hassio_google_drive_backup applicatione[0m
e[32m23-03-02 20:07:08 INFO (SyncWorker_7) [supervisor.docker.interface] Cleaning addon_cebe7a76_hassio_google_drive_backup applicatione[0m
e[32m23-03-02 20:07:08 INFO (SyncWorker_6) [supervisor.docker.interface] Stopping addon_a0d7b954_wireguard applicatione[0m
e[32m23-03-02 20:07:13 INFO (SyncWorker_6) [supervisor.docker.interface] Cleaning addon_a0d7b954_wireguard applicatione[0m
e[32m23-03-02 20:07:13 INFO (SyncWorker_4) [supervisor.docker.interface] Stopping addon_5c53de3b_esphome applicatione[0m
e[32m23-03-02 20:07:17 INFO (SyncWorker_4) [supervisor.docker.interface] Cleaning addon_5c53de3b_esphome applicatione[0m
e[32m23-03-02 20:07:18 INFO (SyncWorker_5) [supervisor.docker.interface] Stopping homeassistant applicatione[0m
e[32m23-03-02 20:07:57 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SERVICES' stopping 3 add-onse[0m
e[32m23-03-02 20:07:57 INFO (SyncWorker_0) [supervisor.docker.interface] Stopping addon_a0d7b954_adguard applicatione[0m
e[32m23-03-02 20:08:02 INFO (SyncWorker_0) [supervisor.docker.interface] Cleaning addon_a0d7b954_adguard applicatione[0m
e[32m23-03-02 20:08:02 INFO (SyncWorker_1) [supervisor.docker.interface] Stopping addon_a0d7b954_influxdb applicatione[0m
e[32m23-03-02 20:08:08 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning addon_a0d7b954_influxdb applicatione[0m
e[32m23-03-02 20:08:08 INFO (SyncWorker_2) [supervisor.docker.interface] Stopping addon_core_duckdns applicatione[0m
e[32m23-03-02 20:08:13 INFO (SyncWorker_2) [supervisor.docker.interface] Cleaning addon_core_duckdns applicatione[0m
e[32m23-03-02 20:08:13 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SYSTEM' stopping 1 add-onse[0m
e[32m23-03-02 20:08:13 INFO (SyncWorker_3) [supervisor.docker.interface] Stopping addon_core_mosquitto applicatione[0m
e[32m23-03-02 20:08:19 INFO (SyncWorker_3) [supervisor.docker.interface] Cleaning addon_core_mosquitto applicatione[0m
e[32m23-03-02 20:08:19 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.INITIALIZE' stopping 0 add-onse[0m
e[32m23-03-02 20:08:19 INFO (MainThread) [supervisor.plugins.cli] Stopping cli plugine[0m
e[32m23-03-02 20:08:19 INFO (SyncWorker_7) [supervisor.docker.interface] Stopping hassio_cli applicatione[0m
e[32m23-03-02 20:08:24 INFO (SyncWorker_7) [supervisor.docker.interface] Cleaning hassio_cli applicatione[0m
e[32m23-03-02 20:08:24 INFO (MainThread) [supervisor.plugins.dns] Stopping CoreDNS plugine[0m
e[32m23-03-02 20:08:24 INFO (SyncWorker_6) [supervisor.docker.interface] Stopping hassio_dns applicatione[0m
e[32m23-03-02 20:08:28 INFO (SyncWorker_6) [supervisor.docker.interface] Cleaning hassio_dns applicatione[0m
e[32m23-03-02 20:08:29 INFO (MainThread) [supervisor.plugins.audio] Stopping Audio plugine[0m
e[32m23-03-02 20:08:29 INFO (SyncWorker_4) [supervisor.docker.interface] Stopping hassio_audio applicatione[0m
e[32m23-03-02 20:08:33 INFO (SyncWorker_4) [supervisor.docker.interface] Cleaning hassio_audio applicatione[0m
e[32m23-03-02 20:08:33 INFO (MainThread) [supervisor.plugins.multicast] Stopping Multicast plugine[0m
e[32m23-03-02 20:08:33 INFO (SyncWorker_5) [supervisor.docker.interface] Stopping hassio_multicast applicatione[0m
e[32m23-03-02 20:08:37 INFO (SyncWorker_5) [supervisor.docker.interface] Cleaning hassio_multicast applicatione[0m
s6-rc: info: service legacy-services: stopping
e[32m23-03-02 20:08:37 INFO (MainThread) [supervisor.docker.monitor] Stopped docker events monitore[0m
e[32m23-03-02 20:08:37 INFO (MainThread) [supervisor.misc.scheduler] Shutting down scheduled taskse[0m
e[32m23-03-02 20:08:37 INFO (MainThread) [supervisor.api] Stopping API on 172.30.32.2e[0m
e[32m23-03-02 20:08:37 INFO (MainThread) [supervisor.hardware.monitor] Stopped Supervisor hardware monitore[0m
e[32m23-03-02 20:08:38 INFO (MainThread) [supervisor.dbus.manager] Closed conection to system D-Bus.e[0m
e[32m23-03-02 20:08:38 INFO (MainThread) [supervisor.core] Supervisor is down - 0e[0m
e[32m23-03-02 20:08:38 INFO (MainThread) [__main__] Closing Supervisore[0m
[19:08:38] INFO: e[32mWatchdog restart after closinge[0m
s6-svwait: fatal: supervisor died
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
[19:08:38] INFO: e[32mSupervisor restart after closinge[0m
I have the same issue. Iâm not sure if all the comments are read by the developers. Maybe also create a ticket or add to this existing ticket? Energy dashboard weird values (negative gas usage?) ¡ Issue #88854 ¡ home-assistant/core ¡ GitHub
Or is this a specific integration problem?
So itâs a bit frustrating that I can no longer interact w/ dimmers directly and have to add a click.
I assumed that I just had to redo my lights to get the slider out front, seems this is not true AND that when you try to add an entity on the new light card, if you click the entity from the drop down, it inserts its human readable name rather than the light.blahblah name.
1 Like