If you are asking me, this is what five columns looks like. Now in this case it’s not that bad, but longer text or graphs would be unreadable. (Theme and ui heavily influenced by Dwains theme)
After upgrading to 0.118, I’m getting the following error:
Logger: homeassistant.components.automation.update_alexa_timers_on_remote_kitchen_led_display
Source: components/automation/__init__.py:402
Integration: Automation ([documentation](https://www.home-assistant.io/integrations/automation), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+automation%22))
First occurred: 9:16:08 AM (1 occurrences)
Last logged: 9:16:08 AM
Error rendering variables: TypeError: the JSON object must be str, bytes or bytearray, not NoneType
Here is the associated automation. The alexatimerjson variable contains a JSON string which is dynamically built up via template. I verified that the JSON string is still correct, in fact the automation still works and publishes to mqtt, so its not broken. I would just like to modify as needed to get rid of the error message that is logged. Since alexatimerjson is a string, I’m not sure what is complaining about being NoneType
automation:
- id: '7fbd36d5-1d46-4dd5-ac55-ad495c36283a'
alias: Update alexa timers on remote kitchen led display
description: ''
trigger:
- platform: state
entity_id:
- sensor.front_room_dot_next_timer
- sensor.kitchen_next_timer
- sensor.tv_room_next_timer
- platform: state
entity_id: binary_sensor.rpialexa1_online
to: 'on'
- platform: homeassistant
event: start
variables:
alexatimerjson: >
{% set deviceNames = [ "tv_room", "kitchen", "front_room_dot" ] -%}
{% set ns = namespace() %}
{% set ns.hasOutput = false %}
{ "timers": [
{%- for deviceName in deviceNames -%}
{% set timers = state_attr('sensor.'+deviceName+'_next_timer', 'sorted_active') | from_json -%}
{% set process_timestamp = state_attr('sensor.'+deviceName+'_next_timer', 'process_timestamp') -%}
{%- for timerTokenData in timers -%}
{%- set timerData = timerTokenData[1] %}
{{- ", " if ns.hasOutput -}}
{% set ns.hasOutput = true %}
{
"id": "{{ timerTokenData[1].id }}",
"deviceName": "{{ deviceName }}",
"expireTime": "{{ (as_timestamp(process_timestamp) | round(0, 'ceil') + timerData.remainingTime/1000) | timestamp_custom("%Y-%m-%dT%H:%M:%S%z") }}"
}
{%- endfor %}
{%- endfor %}
] }
action:
- service: mqtt.publish
data_template:
topic: 'yukon/device/alexa/kitchen/rpialexa1/display/timers'
payload: "{{ alexatimerjson }}"
Just upgraded from 0.117 to 0.118.1 and it went smoothly except for the MQTT Cover Tilt arrows and stop buttons have disappeared. Did the cache reload and many other things, but they don’t show up. Went ahead and enter a github issue on it.
Workday sensor has started misbehaving since 0.118.
It’s Saturday morning in Australia right now and the workday sensor’s state is ‘on’ which is an error as sat and sun are exclusions in my config - see below.
I did a restart with debug logging on the workday component and there are no errors. See below;
Is anyone else have a similar issue?
I’ve been using this sensor for quite a while without issue.
I noted in the comments above that there is a date time issue somewhere?
- platform: workday
country: AU
province: QLD
workdays: [mon, tue, wed, thu, fri]
excludes: [sat, sun]
Logs;
2020-11-20 20:07:45 INFO (SyncWorker_6) [homeassistant.components.zwave] Stopping Z-Wave network
2020-11-20 20:07:45 INFO (SyncWorker_6) [openzwave] Stop Openzwave network.
2020-11-20 20:08:29 INFO (SyncWorker_1) [homeassistant.loader] Loaded workday from homeassistant.components.workday
2020-11-20 20:08:30 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.workday
2020-11-20 20:08:30 DEBUG (SyncWorker_3) [homeassistant.components.workday.binary_sensor] No custom holidays or invalid holidays
2020-11-20 20:08:30 DEBUG (SyncWorker_3) [homeassistant.components.workday.binary_sensor] No holidays to remove or invalid holidays
2020-11-20 20:08:30 DEBUG (SyncWorker_3) [homeassistant.components.workday.binary_sensor] Found the following holidays for your configuration:
2020-11-20 20:08:30 DEBUG (SyncWorker_3) [homeassistant.components.workday.binary_sensor] 2020-01-01 New Year's Day
2020-11-20 20:08:30 DEBUG (SyncWorker_3) [homeassistant.components.workday.binary_sensor] 2020-01-26 Australia Day
2020-11-20 20:08:30 DEBUG (SyncWorker_3) [homeassistant.components.workday.binary_sensor] 2020-01-27 Australia Day (Observed)
2020-11-20 20:08:30 DEBUG (SyncWorker_3) [homeassistant.components.workday.binary_sensor] 2020-04-10 Good Friday
2020-11-20 20:08:30 DEBUG (SyncWorker_3) [homeassistant.components.workday.binary_sensor] 2020-04-11 Easter Saturday
2020-11-20 20:08:30 DEBUG (SyncWorker_3) [homeassistant.components.workday.binary_sensor] 2020-04-12 Easter Sunday
2020-11-20 20:08:30 DEBUG (SyncWorker_3) [homeassistant.components.workday.binary_sensor] 2020-04-13 Easter Monday
2020-11-20 20:08:30 DEBUG (SyncWorker_3) [homeassistant.components.workday.binary_sensor] 2020-04-25 Anzac Day
2020-11-20 20:08:30 DEBUG (SyncWorker_3) [homeassistant.components.workday.binary_sensor] 2020-05-04 Labour Day
2020-11-20 20:08:30 DEBUG (SyncWorker_3) [homeassistant.components.workday.binary_sensor] 2020-08-12 The Royal Queensland Show
2020-11-20 20:08:30 DEBUG (SyncWorker_3) [homeassistant.components.workday.binary_sensor] 2020-10-05 Queen's Birthday
2020-11-20 20:08:30 DEBUG (SyncWorker_3) [homeassistant.components.workday.binary_sensor] 2020-12-25 Christmas Day
2020-11-20 20:08:30 DEBUG (SyncWorker_3) [homeassistant.components.workday.binary_sensor] 2020-12-26 Boxing Day
2020-11-20 20:08:30 DEBUG (SyncWorker_3) [homeassistant.components.workday.binary_sensor] 2020-12-28 Boxing Day (Observed)
2020-11-20 20:09:17 INFO (SyncWorker_32) [homeassistant.components.zwave] Starting Z-Wave network...
2020-11-20 20:09:17 INFO (SyncWorker_32) [openzwave] Start Openzwave network.
2020-11-20 20:09:57 INFO (Dummy-20) [homeassistant.components.zwave] Z-Wave network is complete. All nodes on the network have been queried
Workday fine here in NZ.
Working fine for me in Sydney
I did indeed!
There was already an issue about this and it has been closed instantly after reported…
Maybe you can try to reply on this issue, don’t know why it has been closed immediately after we reported it… https://github.com/home-assistant/frontend/issues/7745
My workday flipped over to off at 10am this morning (Sat). So clearly a timezone issue.
I’m running Hassio on a Raspberry Pi 4.
If I terminal into it, and run date right now I get Sat Nov 21 03:34:53 2020
Yet the HASS date time sensor reports 2020-11-21, 13:36.
I saw in another discussion that this sensor gets its date/time from the host, and not from the HA date time sensor so I guess that’s the issue.
Maybe when I upgraded the OS (which I also did yesterday), it now doesn’t use my local timezone but uses UTC??
Does anyone know how to change the timezone of the Host? I’m a linux noob…
Thx
JP
Wow you guys are killin it. Excited to play with grid (!!!) and H/F.
Do you really need to post a picture of a github discussion? We can all follow the link.
link has been posted in post I answered to.
but I removed the post anyway
After update to 0.118 (previous version 0.118.6) solaredge integration has stopped working properly… the export power just went to down to a random number
had tried twice… first time 0.117.6 to 0.118 then restored from backup… solar edge went back to normal operation… just updated again from 0.117.6 to 0.118.2 and have same issue
first time exported power went down from 30kw (30000something watts) to 1kw…
second time went down to 0.42kw
There’s definitely something weird going on with timezones at the moment on 118, some of my automations are being read as utc also. I’ve had to revert for now.
UTC / Local time issue in 0.118
Yes, see Taras’s (@123) post near the top of the thread.
This would affect probably 40%of my sensors and automations so I’ll just sit on 0.117.6 until this is addressed
1 Like
My HACS version was already at 1.6.2 before upgrading HA to 0.118. I’ve updated HACS manually, nothing changes. It complains that it can’t install a package, apparently it cannot fetch the versions?
Unable to install package queueman==0.5
ERROR: Could not find a version that satisfies the requirement queueman==0.5 (from versions: none)
Same for Node-Red:
Unable to install package integrationhelper
ERROR: Could not find a version that satisfies the requirement integrationhelper (from versions: none)
Any clue what to do?
Edit:
Rebooting the entire system for a second time seemed to solve the issue for Node-Red
Edit 2:
Rebooting the entire system for a third time fixed the issue for HACS
I have a column of temperatures defined in state-label-card within picture-elements. Prior to 0.118.0 all the temperatures aligned perfectly. If the temperature contains a decimal greater than 0 it displays as before with the decimal amount. When the decimal is .0, the .0 is dropped from the display causing the column to lose alignment. The state of the temperature still contains the .0, it’s just missing in lovelace. Any way to force the .0?
For me not 
If I reinstall via integrations, it asks again for api key