How do you think that will help?
if you use certs, you should see a whole bunch of SSL errors in your logs. you can connect to your hass using local IP instead. e.g. https://192.168.#.#:####
In version 108, I started to get a lot of problems with the bayesian sensors in combinations with inputs based on templates. In fact, my HA system get totally unresponsive when a template evaluates to true.
Here is the bayesian sensor config:
- platform: bayesian
name: 'Panelovner stue'
prior: 0.35
probability_threshold: 0.5
observations:
- entity_id: input_boolean.travel_enabled
prob_given_true: 0.001
platform: 'state'
to_state: 'on'
- entity_id: binary_sensor.vindu_2_etg_a
prob_given_true: 0.001
platform: 'state'
to_state: 'on'
- entity_id: binary_sensor.vindu_2_etg_b
prob_given_true: 0.001
platform: 'state'
to_state: 'on'
- entity_id: binary_sensor.noen_er_hjemme
prob_given_true: 0.7
platform: 'state'
to_state: 'on'
- entity_id: input_boolean.sleeptime
prob_given_true: 0.32
platform: 'state'
to_state: 'on'
- entity_id: binary_sensor.soonsleeptime
prob_given_true: 0.32
platform: 'state'
to_state: 'on'
- entity_id: binary_sensor.preheat_day
prob_given_true: 0.66
platform: 'state'
to_state: 'on'
- entity_id: binary_sensor.preheat_night_weekend
prob_given_true: 0.64
platform: 'state'
to_state: 'on'
- entity_id: binary_sensor.heatlimit_morning
prob_given_true: 0.4
platform: 'state'
to_state: 'on'
- entity_id: input_boolean.soonhome
prob_given_true: 0.66
platform: 'state'
to_state: 'on'
- entity_id: input_boolean.visitors_comfort_temp
prob_given_true: 0.64
platform: 'state'
to_state: 'on'
- entity_id: sensor.pricelevel
prob_given_true: 0.3
platform: 'state'
to_state: 'VERY_EXPENSIVE'
- prob_given_true: 0.64
platform: 'template'
value_template: >-
{{ states('binary_sensor.preheat_night') == 'on' and states('input_boolean.home_office') == 'on' }}
And here is the error in the log. The template used as input, evaluates to true at 03:10
2020-04-14 03:10:01 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.2755669936] Unable to serialize to JSON: Object of type Template is not JSON serializable
{'id': 85, 'type': 'event', 'event': {'event_type': 'state_changed', 'data': {'entity_id': 'binary_sensor.panelovner_stue', 'old_state': <state binary_sensor.panelovner_stue=off; observations=[None, None, None, {'entity_id': 'binary_sensor.noen_er_hjemme', 'prob_given_true': 0.7, 'platform': 'state', 'to_state': 'on', 'id': 3}, {'entity_id': 'input_boolean.sleeptime', 'prob_given_true': 0.32, 'platform': 'state', 'to_state': 'on', 'id': 4}, None, None, None, None, None, None, None, None], occurred_observation_entities=['input_boolean.sleeptime', 'binary_sensor.noen_er_hjemme'], probability=0.37, probability_threshold=0.5, friendly_name=Panelovner stue @ 2020-04-13T20:00:01.123377+02:00>, 'new_state': <state binary_sensor.panelovner_stue=on; observations=[None, None, None, {'entity_id': 'binary_sensor.noen_er_hjemme', 'prob_given_true': 0.7, 'platform': 'state', 'to_state': 'on', 'id': 3}, {'entity_id': 'input_boolean.sleeptime', 'prob_given_true': 0.32, 'platform': 'state', 'to_state': 'on', 'id': 4}, None, None, None, None, None, None, None, {'entity_id': 'binary_sensor.preheat_night', 'prob_given_true': 0.64, 'platform': 'template', 'value_template': Template("{{ states('binary_sensor.preheat_night') == 'on' and states('input_boolean.home_office') == 'on' }}"), 'id': 12}], occurred_observation_entities=['input_boolean.sleeptime', 'binary_sensor.noen_er_hjemme', 'binary_sensor.preheat_night'], probability=0.51, probability_threshold=0.5, friendly_name=Panelovner stue @ 2020-04-14T03:10:01.114390+02:00>}, 'origin': 'LOCAL', 'time_fired': datetime.datetime(2020, 4, 14, 1, 10, 1, 114451, tzinfo=<UTC>), 'context': {'id': 'b93ee2ccd5dc4e65b726fe917fbbd62f', 'parent_id': None, 'user_id': None}}}
The home-assistant.log grows to 200-300MB within minutes and are filled up with these âUnable to serialize to JSON: Object of type Template is not JSON serializableâ messages. Does someone know what is causing this?
Hi,
I canât update to 0.108.3, iâve tried loads of times with no success.
This is the section of my log from start of update to end.
Iâm just using the standard setup for a RPI4.
20-04-14 06:37:23 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.108.3
20-04-14 06:37:23 INFO (SyncWorker_1) [supervisor.docker.interface] Update image homeassistant/raspberrypi4-homeassistant:0.107.7 to homeassistant/raspberrypi4-homeassistant:0.108.3
20-04-14 06:37:23 INFO (SyncWorker_1) [supervisor.docker.interface] Pull image homeassistant/raspberrypi4-homeassistant tag 0.108.3.
20-04-14 06:40:03 INFO (SyncWorker_1) [supervisor.docker.interface] Stop homeassistant application
20-04-14 06:40:14 INFO (SyncWorker_1) [supervisor.docker.interface] Clean homeassistant application
20-04-14 06:40:14 INFO (MainThread) [supervisor.homeassistant] Update pulse/client.config: /data/tmp/homeassistant_pulse
20-04-14 06:40:15 INFO (SyncWorker_18) [supervisor.docker.homeassistant] Start homeassistant homeassistant/raspberrypi4-homeassistant with version 0.108.3
20-04-14 06:40:35 ERROR (MainThread) [supervisor.homeassistant] Home Assistant has crashed!
20-04-14 06:40:35 CRITICAL (MainThread) [supervisor.homeassistant] HomeAssistant update fails -> rollback!
20-04-14 06:40:35 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.107.7
20-04-14 06:40:35 INFO (SyncWorker_19) [supervisor.docker.interface] Update image homeassistant/raspberrypi4-homeassistant:0.108.3 to homeassistant/raspberrypi4-homeassistant:0.107.7
20-04-14 06:40:35 INFO (SyncWorker_19) [supervisor.docker.interface] Pull image homeassistant/raspberrypi4-homeassistant tag 0.107.7.
20-04-14 06:40:36 INFO (SyncWorker_19) [supervisor.docker.interface] Clean homeassistant application
20-04-14 06:40:36 INFO (MainThread) [supervisor.homeassistant] Update pulse/client.config: /data/tmp/homeassistant_pulse
20-04-14 06:40:37 INFO (SyncWorker_6) [supervisor.docker.homeassistant] Start homeassistant homeassistant/raspberrypi4-homeassistant with version 0.107.7
20-04-14 06:40:57 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation in progress
20-04-14 06:41:42 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation done
Any help would be greatly appreciated.
I suspected that a newer version of Zigbee2MQTT (mine must have been 2 years old) would have a correctly formatted message that matched what HA wanted.
And I was right! It also means it is simpler to update so all good 
Yeah, had to roll back to v107.7 myself, as v108.3 looks like it also broke the âalexa-remote2â node in Node Red⌠since it handles nearly every single one of my routines due to its enhanced features, that makes this HA version a no-go for me. 
Updated a 2nd time, and now everything works⌠go figure. After everything I tried before, I can only deduce that something glitched perhaps during the update process, and that it somehow broke a dependency that the node relied on. 5am educated guess only⌠
Serial modbus work in 0.108.4?
1 Like
thanks, missed that (dont know howâŚsorry) added my bits. hope this gets solved soon, because really miss the optional parameters nmap offers, and eg asuswrt doesnt allow
Temp solution to broadlink issue is to download 0.107.7 or earlier, extract the broadlink component folder and place it in your custom components folder.
Mine is working again after doing that.
2 Likes
OK I didnât realise you were also updating zigbee2mqtt. Glad that worked out for you 
1 Like
Why not just download it from github?
1 Like
Thats exact the problem.
I found out by checking the www.duckdns.org site. Which was not reachable.
It was down severall times this weekend.
Itâs up again now
I have same problem but have seen it reported here
https://community.home-assistant.io/t/unable-to-serialize-to-json/186378/3
Any luck on this?
I see a similar one has been reported
https://github.com/home-assistant/core/issues/34134
How is that possible? Home Assistant and Node-Red are independent systems.
1 Like
I have also reported it on github.
As a workaround, I removed the template on the bayesian sensor, created an identical template binary sensor and used that sensor as an input on the bayesian sensor
Am I the only one that canât find in docker hub the image for 0.108.4?
That was my thoughts exactly⌠Iâm not sure what happened, but I tried updating again using a HDD backup copy (run everything on VM and keep all version copies), and it appears this time itâs working. After my previous attempt to update it wouldnât initialize/validate my Amazon account. I tried everything I could think of to get it to work to include reinstalling the nodes, flows, and all my account info to no avail. Jumped back to v107.7, and everything ran fine so I figured it was the update. Node Red is independent, but itâs still an integration⌠maybe something just didnât update correctly during the process that it depended on. 
At most it can be an add-on to Home Assistant (formerly known as Hass.io) but itâs not an integration. In fact, I run Node_Red on a separate machine from Home Assistant.
To be clear, Iâm not questioning your observation that 0.108.3 appears to be negatively affecting your Node-Red flow. Iâm just clarifying that the difficulties you are experiencing with the alexa-remote2 node are just a symptom of a (as yet unidentified) underlying problem in Home Assistant 0.108.3. If you are running Node-Red as an add-on then that arrangement is slightly âless independentâ and perhaps thatâs where the glitch was accidentally introduced.