Can't get the Appdaemon 3.0.b3 widgets in HaDashboard to work... with java console errors

aimc · February 26, 2018, 9:32pm

A lot of those seem to be random cruft in the various libraries I am using.

Check the exact entity name using the HASS Developer tools just to be sure.

lightmind · February 26, 2018, 9:35pm

In the HaDashboard panel shows “widget definition not found” …

ReneTode · February 26, 2018, 9:38pm

in home assistant all entities are lowercase.
in dev tools you can check out which entities you have active in home assistant and how they are called.

and i think that because of this line:

sensor NodeMCU_1_temperature_1:

the sensor is called sensor.sensor_nodemcu_1_temperature_1

lightmind · February 26, 2018, 10:05pm

Great, that did it. The gauges have appeared.

-The gauge titles are not showing…

-Do you know how to remove the leading 0 from the sensor reading?
For example, shows 070.35 instead of 70.35

I really appreciate all the help and such short response time. You guys are great.
I have spent hours trying to get to the bottom of the problem. I came here because I got to the point where what I was doing was probably going to make matters worse.

And nice to know that the sensor entries need to be lower case for HA as it converts them to lowercase anyway…

lightmind · February 26, 2018, 10:21pm

Gauge titles are showing…

ReneTode · February 26, 2018, 10:57pm

create a template sensor in HA for that.

lightmind · February 26, 2018, 11:33pm

Thanks! Will try that, everything going as expected now.

lightmind · February 27, 2018, 7:38am

Maybe help someone in the future when searching this forum.

for appdaemon 3.0.0.3b3 radial widget

I was able to remove the leading 0 in the radial widget temperature display by adding …

valueInt: ()
valueDec: 2

to the widget settings: area in the dash file for the widget type (radial gauge).

Before the change it was reading 060.44 for example, now it reads just 60.44.

I sent the dash a sensor state of 160.44 and it reads out correctly as well.

Put in some integers up to 5 digits and they all worked.

ReneTode · February 27, 2018, 11:20am

searching on the forum is something every one can do for hisself in my eyes. (and i hope people do that before asking questions)
i didnt know that the options from the radial are all exposed and setable like that.
but even then there are so many options for the radial that i dont know them all, and really didnt think about this one as a possibility.

for others that read this, its only possible for the radial and temperature widget (in all other cases you need to create a template sensor)
for all other options from the radial and temperature is a list here:

@aimc can you add that link to the docs?

lightmind · February 27, 2018, 3:40pm

Hello again,

I am trying to finish out my radial gauge widget dashboard so I can move on to the next tasks. It all works great except for one thing. There seems to be a problem with the OnStateUpdate(self, state) function in the baseradial.js. When the gauge initially is called from HAD or on a page refresh the gauge properly loads and reads the OnStateAvailable(self, state) data from HA. But it does not update after that. I don’t think that the function OnStateUpdate(self, state) is getting triggered. I don’t know enough about how the data exchange is taking place, whether appdaemon polls the HA or if HA initiates the exchange. But having the data update on the dashboard automatically is a priority feature. Any ideas on how to fix it or perhaps another method to trigger updates such as a timer with get_state()? I know for my purpose that a simple timer loop would be sufficient and only one function would be needed to replace the OnStateAvailable and OnStateUpdate, the script is simply reading HA values and updating the gauge.

Thx !

ReneTode · February 27, 2018, 3:55pm

the data is normally updated automaticly, so if that isnt happening there is an error somewhere.

what browser do you use? some browser dont function like they should.
with google chrome i am sure it should function.

you shouldnt use any triggers to update, or loops to create. every time that an entity in HA is updated it also will update the dashboard if there are no errors.

if your dashboard isnt updating, then we need to figure out where the error is.
so first start by using chrome.
if it still isnt updating we have to look at log files and at the javaconsole for errors.

lightmind · February 27, 2018, 6:16pm

Hello,

I tried Firefox, IE11 & Chrome. None of them will update. . .

Here’s the appdaemon log in DEBUG mode…

Blockquote
homeassistant@HomeAuto:~/.homeassistant$ appdaemon -c /home/homeassistant/.homeassistant/config -D DEBUG
2018-02-27 11:12:02.980024 INFO AppDaemon Version 3.0.0b3 starting
2018-02-27 11:12:02.980289 INFO Configuration read from: /home/homeassistant/.homeassistant/config/appdaemon.yaml
2018-02-27 11:12:02.980389 DEBUG AppDaemon Section: None
2018-02-27 11:12:02.980479 DEBUG HADashboard Section: None
2018-02-27 11:12:02.981197 INFO AppDaemon: Starting Apps
2018-02-27 11:12:02.981375 DEBUG AppDaemon: Creating worker threads …
2018-02-27 11:12:02.983062 DEBUG AppDaemon: Done
2018-02-27 11:12:02.983193 DEBUG AppDaemon: Entering run()
2018-02-27 11:12:02.983359 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2018-02-27 11:12:02.992322 INFO AppDaemon: HASS: HASS Plugin Initializing
2018-02-27 11:12:02.992655 INFO AppDaemon: HASS: HASS Plugin initialization complete
2018-02-27 11:12:02.992845 DEBUG AppDaemon: Starting utility loop
2018-02-27 11:12:02.992961 INFO Starting Dashboards
2018-02-27 11:12:02.996683 INFO Starting API
2018-02-27 11:12:02.997262 DEBUG Start Loop
2018-02-27 11:12:03.003055 INFO AppDaemon: HASS: Connected to Home Assistant 0.64.0
2018-02-27 11:12:03.005297 DEBUG AppDaemon: HASS: get_ha_config()
2018-02-27 11:12:03.005449 DEBUG AppDaemon: HASS: get_ha_config: url is http://127.0.0.1:8123/api/config
2018-02-27 11:12:03.009907 DEBUG AppDaemon: HASS: get_ha_state: url is http://127.0.0.1:8123/api/states
2018-02-27 11:12:03.014488 DEBUG AppDaemon: HASS: Got state
2018-02-27 11:12:03.014949 INFO AppDaemon: Got initial state from namespace default
2018-02-27 11:12:03.611527 INFO HADashboard: New dashboard connected: Hot Water Solar Status
2018-02-27 11:12:04.357744 INFO HADashboard: New dashboard connected: Hot Water Solar Status
2018-02-27 11:12:05.054680 DEBUG AppDaemon: Starting timer loop
2018-02-27 11:12:05.054981 DEBUG AppDaemon: Reading Apps
2018-02-27 11:12:05.055951 INFO AppDaemon: Reading config
2018-02-27 11:12:05.056186 DEBUG AppDaemon: Reading /home/homeassistant/.homeassistant/config/apps/apps.yaml
2018-02-27 11:12:05.057687 INFO AppDaemon: /home/homeassistant/.homeassistant/config/apps/apps.yaml added or modified
2018-02-27 11:12:05.057892 INFO AppDaemon: /home/homeassistant/.homeassistant/config/apps/apps.yaml added or modified
2018-02-27 11:12:05.057993 INFO AppDaemon: App ‘hello_world’ added
2018-02-27 11:12:05.058162 INFO AppDaemon: Adding /home/homeassistant/.homeassistant/config/apps to module import path
2018-02-27 11:12:05.058402 INFO AppDaemon: Found module /home/homeassistant/.homeassistant/config/apps/hello.py
2018-02-27 11:12:05.058568 INFO AppDaemon: Loading Module: /home/homeassistant/.homeassistant/config/apps/hello.py
2018-02-27 11:12:05.064066 INFO AppDaemon: Initializing app hello_world using class HelloWorld from module hello
2018-02-27 11:12:05.129986 INFO hello_world: Hello from AppDaemon
2018-02-27 11:12:05.130996 INFO hello_world: You are now ready to run Apps!
2018-02-27 11:12:05.131492 INFO AppDaemon: App initialization complete
2018-02-27 11:12:05.132545 DEBUG AppDaemon: Util loop compute time: 0.0ms
2018-02-27 11:12:05.911247 INFO HADashboard: New dashboard connected: Hot Water Solar Status
2018-02-27 11:12:06.001565 DEBUG AppDaemon: Scheduler loop compute time: 0.0ms
2018-02-27 11:12:06.135608 DEBUG AppDaemon: Util loop compute time: 2.0ms
2018-02-27 11:12:07.003545 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:07.137552 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:08.003306 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:08.141541 DEBUG AppDaemon: Util loop compute time: 2.0ms
2018-02-27 11:12:09.002998 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:09.145290 DEBUG AppDaemon: Util loop compute time: 2.0ms
2018-02-27 11:12:10.003298 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:10.149574 DEBUG AppDaemon: Util loop compute time: 2.0ms
2018-02-27 11:12:11.003568 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:11.152388 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:12.002364 DEBUG AppDaemon: Scheduler loop compute time: 0.0ms
2018-02-27 11:12:12.155115 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:13.002969 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:13.156785 DEBUG AppDaemon: Util loop compute time: 0.0ms
2018-02-27 11:12:14.003762 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:14.160250 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:15.003203 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:15.161997 DEBUG AppDaemon: Util loop compute time: 0.0ms
2018-02-27 11:12:16.002670 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:16.164457 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:17.003449 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:17.167232 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:18.003197 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:18.170032 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:19.002862 DEBUG AppDaemon: Scheduler loop compute time: 0.0ms
2018-02-27 11:12:19.173719 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:20.003792 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:20.175864 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:21.002848 DEBUG AppDaemon: Scheduler loop compute time: 0.0ms
2018-02-27 11:12:21.180706 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:22.003695 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:22.182427 DEBUG AppDaemon: Util loop compute time: 0.0ms
2018-02-27 11:12:23.004107 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:23.184908 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:24.002826 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:24.187681 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:25.003630 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:25.190419 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:25.574073 DEBUG AppDaemon: Event type:state_changed:
2018-02-27 11:12:25.574268 DEBUG AppDaemon: {‘entity_id’: ‘sensor.nodemcu1_temp_1’, ‘new_state’: {‘entity_id’: ‘sensor.nodemcu1_temp_1’, ‘attributes’: {‘friendly_name’: ‘NodeMCU1_temp_1’, ‘unit_of_measurement’: ‘°F’}, ‘last_updated’: ‘2018-02-27T18:12:25.563255+00:00’, ‘last_changed’: ‘2018-02-27T18:12:25.563255+00:00’, ‘state’: ‘67.55’}, ‘old_state’: {‘entity_id’: ‘sensor.nodemcu1_temp_1’, ‘attributes’: {‘friendly_name’: ‘NodeMCU1_temp_1’, ‘unit_of_measurement’: ‘°F’}, ‘last_updated’: ‘2018-02-27T18:10:25.561378+00:00’, ‘last_changed’: ‘2018-02-27T18:10:25.561378+00:00’, ‘state’: ‘67.66’}}
2018-02-27 11:12:25.574416 DEBUG AppDaemon: {‘entity_id’: ‘sensor.nodemcu1_temp_1’, ‘new_state’: {‘entity_id’: ‘sensor.nodemcu1_temp_1’, ‘attributes’: {‘friendly_name’: ‘NodeMCU1_temp_1’, ‘unit_of_measurement’: ‘°F’}, ‘last_updated’: ‘2018-02-27T18:12:25.563255+00:00’, ‘last_changed’: ‘2018-02-27T18:12:25.563255+00:00’, ‘state’: ‘67.55’}, ‘old_state’: {‘entity_id’: ‘sensor.nodemcu1_temp_1’, ‘attributes’: {‘friendly_name’: ‘NodeMCU1_temp_1’, ‘unit_of_measurement’: ‘°F’}, ‘last_updated’: ‘2018-02-27T18:10:25.561378+00:00’, ‘last_changed’: ‘2018-02-27T18:10:25.561378+00:00’, ‘state’: ‘67.66’}}
2018-02-27 11:12:25.574609 DEBUG HADasboard: Sending data to 3 dashes: {‘time_fired’: ‘2018-02-27T18:12:25.563334+00:00’, ‘origin’: ‘LOCAL’, ‘data’: {‘entity_id’: ‘sensor.nodemcu1_temp_1’, ‘new_state’: {‘entity_id’: ‘sensor.nodemcu1_temp_1’, ‘attributes’: {‘friendly_name’: ‘NodeMCU1_temp_1’, ‘unit_of_measurement’: ‘°F’}, ‘last_updated’: ‘2018-02-27T18:12:25.563255+00:00’, ‘last_changed’: ‘2018-02-27T18:12:25.563255+00:00’, ‘state’: ‘67.55’}, ‘old_state’: {‘entity_id’: ‘sensor.nodemcu1_temp_1’, ‘attributes’: {‘friendly_name’: ‘NodeMCU1_temp_1’, ‘unit_of_measurement’: ‘°F’}, ‘last_updated’: ‘2018-02-27T18:10:25.561378+00:00’, ‘last_changed’: ‘2018-02-27T18:10:25.561378+00:00’, ‘state’: ‘67.66’}}, ‘event_type’: ‘state_changed’}
2018-02-27 11:12:25.574772 DEBUG HADasboard: Found dashboard type Hot Water Solar Status
/usr/local/lib/python3.5/dist-packages/appdaemon/rundash.py:392: RuntimeWarning: coroutine ‘WebSocketResponse.send_str’ was never awaited
ws.send_str(data)
2018-02-27 11:12:25.575598 DEBUG HADasboard: Found dashboard type Hot Water Solar Status
2018-02-27 11:12:25.575753 DEBUG HADasboard: Found dashboard type Hot Water Solar Status
2018-02-27 11:12:25.577112 DEBUG AppDaemon: Event type:state_changed:
2018-02-27 11:12:25.577303 DEBUG AppDaemon: {‘entity_id’: ‘sensor.nodemcu1_temp_2’, ‘new_state’: {‘entity_id’: ‘sensor.nodemcu1_temp_2’, ‘attributes’: {‘friendly_name’: ‘NodeMCU1_temp_2’, ‘unit_of_measurement’: ‘°F’}, ‘last_updated’: ‘2018-02-27T18:12:25.564929+00:00’, ‘last_changed’: ‘2018-02-27T18:12:25.564929+00:00’, ‘state’: ‘47.53’}, ‘old_state’: {‘entity_id’: ‘sensor.nodemcu1_temp_2’, ‘attributes’: {‘friendly_name’: ‘NodeMCU1_temp_2’, ‘unit_of_measurement’: ‘°F’}, ‘last_updated’: ‘2018-02-27T18:11:25.562434+00:00’, ‘last_changed’: ‘2018-02-27T18:11:25.562434+00:00’, ‘state’: ‘47.64’}}
2018-02-27 11:12:25.577445 DEBUG AppDaemon: {‘entity_id’: ‘sensor.nodemcu1_temp_2’, ‘new_state’: {‘entity_id’: ‘sensor.nodemcu1_temp_2’, ‘attributes’: {‘friendly_name’: ‘NodeMCU1_temp_2’, ‘unit_of_measurement’: ‘°F’}, ‘last_updated’: ‘2018-02-27T18:12:25.564929+00:00’, ‘last_changed’: ‘2018-02-27T18:12:25.564929+00:00’, ‘state’: ‘47.53’}, ‘old_state’: {‘entity_id’: ‘sensor.nodemcu1_temp_2’, ‘attributes’: {‘friendly_name’: ‘NodeMCU1_temp_2’, ‘unit_of_measurement’: ‘°F’}, ‘last_updated’: ‘2018-02-27T18:11:25.562434+00:00’, ‘last_changed’: ‘2018-02-27T18:11:25.562434+00:00’, ‘state’: ‘47.64’}}
2018-02-27 11:12:25.577595 DEBUG HADasboard: Sending data to 3 dashes: {‘time_fired’: ‘2018-02-27T18:12:25.564979+00:00’, ‘origin’: ‘LOCAL’, ‘data’: {‘entity_id’: ‘sensor.nodemcu1_temp_2’, ‘new_state’: {‘entity_id’: ‘sensor.nodemcu1_temp_2’, ‘attributes’: {‘friendly_name’: ‘NodeMCU1_temp_2’, ‘unit_of_measurement’: ‘°F’}, ‘last_updated’: ‘2018-02-27T18:12:25.564929+00:00’, ‘last_changed’: ‘2018-02-27T18:12:25.564929+00:00’, ‘state’: ‘47.53’}, ‘old_state’: {‘entity_id’: ‘sensor.nodemcu1_temp_2’, ‘attributes’: {‘friendly_name’: ‘NodeMCU1_temp_2’, ‘unit_of_measurement’: ‘°F’}, ‘last_updated’: ‘2018-02-27T18:11:25.562434+00:00’, ‘last_changed’: ‘2018-02-27T18:11:25.562434+00:00’, ‘state’: ‘47.64’}}, ‘event_type’: ‘state_changed’}
2018-02-27 11:12:25.577747 DEBUG HADasboard: Found dashboard type Hot Water Solar Status
2018-02-27 11:12:25.577855 DEBUG HADasboard: Found dashboard type Hot Water Solar Status
2018-02-27 11:12:25.577955 DEBUG HADasboard: Found dashboard type Hot Water Solar Status
2018-02-27 11:12:26.001379 DEBUG AppDaemon: Scheduler loop compute time: 0.0ms
2018-02-27 11:12:26.194267 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:27.003300 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:27.196226 DEBUG AppDaemon: Util loop compute time: 0.0ms
2018-02-27 11:12:28.002005 DEBUG AppDaemon: Scheduler loop compute time: 0.0ms
2018-02-27 11:12:28.199743 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:29.002700 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:29.202838 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:30.002777 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:30.206109 DEBUG AppDaemon: Util loop compute time: 2.0ms
2018-02-27 11:12:31.003532 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:31.209362 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:32.003249 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:32.213115 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:33.003016 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:33.216261 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:34.003248 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:34.219431 DEBUG AppDaemon: Util loop compute time: 1.0ms
2018-02-27 11:12:35.003422 DEBUG AppDaemon: Scheduler loop compute time: 1.0ms
2018-02-27 11:12:35.221218 DEBUG AppDaemon: Util loop compute time: 0.0ms
2018-02-27 11:12:36.001925 DEBUG AppDaemon: Scheduler loop compute time: 0.0ms
^Z[1] Killed appdaemon -c /home/homeassistant/.homeassistant/config -D DEBUG

Blockquote

Stopped manually after update processing from HA***

lightmind · February 27, 2018, 6:30pm

Here is Chrome Console-

Blockquote
jquery-3.1.1.min.js:3 [Violation] Added non-passive event listener to a scroll-blocking ‘touchstart’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
add @ jquery-3.1.1.min.js:3
(anonymous) @ jquery-3.1.1.min.js:3
each @ jquery-3.1.1.min.js:2
each @ jquery-3.1.1.min.js:2
xa @ jquery-3.1.1.min.js:3
on @ jquery-3.1.1.min.js:3
fn.events @ jquery.gridster.js:572
fn.init @ jquery.gridster.js:552
Draggable @ jquery.gridster.js:540
(anonymous) @ jquery.gridster.js:898
each @ jquery-3.1.1.min.js:2
each @ jquery-3.1.1.min.js:2
$.fn.dragg @ jquery.gridster.js:896
fn.draggable @ jquery.gridster.js:2233
fn.init @ jquery.gridster.js:1226
Gridster @ jquery.gridster.js:1094
(anonymous) @ jquery.gridster.js:5092
each @ jquery-3.1.1.min.js:2
each @ jquery-3.1.1.min.js:2
$.fn.gridster @ jquery.gridster.js:5089
(anonymous) @ test_init.js:11
j @ jquery-3.1.1.min.js:2
k @ jquery-3.1.1.min.js:2

Blockquote

no other errors, but firefox threw a bunch of errors.

lightmind · February 27, 2018, 6:45pm

I am reconfiguring my configuration.yaml for HA and my MQTT sensors to get rid of the caps in names, state topic and titles.

lightmind · February 27, 2018, 6:52pm

Still not updating after sensor name and state changes- got rid of all capitalization

lightmind · February 27, 2018, 6:59pm

Here is the HA console output-

Blockquote

DEBUG:roku:/query/active-app
DEBUG:homeassistant.components.mqtt:Received message on nodemcu_1/temperature_1: b’69.12’
DEBUG:homeassistant.components.mqtt:Received message on nodemcu_1/temperature_2: b’49.44’
DEBUG:homeassistant.components.mqtt:Received message on nodemcu_1/temperature_3: b’69.12’
DEBUG:homeassistant.components.mqtt:Received message on nodemcu_1/temperature_4: b’77.45’
DEBUG:homeassistant.components.mqtt:Received message on nodemcu_1/temperature_5: b’70.14’
INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=sensor.nodemcu1_temp_1, old_state=<state sensor.nodemcu1_temp_1=69.24; unit_of_measurement=°F, friendly_name=nodemcu1_temp_1 @ 2018-02-27T11:56:32.437196-07:00>, new_state=<state sensor.nodemcu1_temp_1=69.12; unit_of_measurement=°F, friendly_name=nodemcu1_temp_1 @ 2018-02-27T11:57:32.437770-07:00>>
INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=sensor.nodemcu1_temp_2, old_state=<state sensor.nodemcu1_temp_2=50.00; unit_of_measurement=°F, friendly_name=nodemcu1_temp_2 @ 2018-02-27T11:56:32.438709-07:00>, new_state=<state sensor.nodemcu1_temp_2=49.44; unit_of_measurement=°F, friendly_name=nodemcu1_temp_2 @ 2018-02-27T11:57:32.439302-07:00>>
INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=sensor.nodemcu1_temp_3, old_state=<state sensor.nodemcu1_temp_3=69.24; unit_of_measurement=°F, friendly_name=nodemcu1_temp_3 @ 2018-02-27T11:56:32.440145-07:00>, new_state=<state sensor.nodemcu1_temp_3=69.12; unit_of_measurement=°F, friendly_name=nodemcu1_temp_3 @ 2018-02-27T11:57:32.440702-07:00>>
INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=sensor.nodemcu1_temp_4, old_state=<state sensor.nodemcu1_temp_4=77.68; unit_of_measurement=°F, friendly_name=nodemcu1_temp_4 @ 2018-02-27T11:56:32.441566-07:00>, new_state=<state sensor.nodemcu1_temp_4=77.45; unit_of_measurement=°F, friendly_name=nodemcu1_temp_4 @ 2018-02-27T11:57:32.442066-07:00>>
DEBUG:homeassistant.components.websocket_api:WS 140635282552144: Sending {‘event’: {‘data’: {‘entity_id’: ‘sensor.nodemcu1_temp_1’, ‘old_state’: <state sensor.nodemcu1_temp_1=69.24; unit_of_measurement=°F, friendly_name=nodemcu1_temp_1 @ 2018-02-27T11:56:32.437196-07:00>, ‘new_state’: <state sensor.nodemcu1_temp_1=69.12; unit_of_measurement=°F, friendly_name=nodemcu1_temp_1 @ 2018-02-27T11:57:32.437770-07:00>}, ‘origin’: ‘LOCAL’, ‘event_type’: ‘state_changed’, ‘time_fired’: datetime.datetime(2018, 2, 27, 18, 57, 32, 437814, tzinfo=)}, ‘type’: ‘event’, ‘id’: 1}
DEBUG:homeassistant.components.websocket_api:WS 140635282552144: Sending {‘event’: {‘data’: {‘entity_id’: ‘sensor.nodemcu1_temp_2’, ‘old_state’: <state sensor.nodemcu1_temp_2=50.00; unit_of_measurement=°F, friendly_name=nodemcu1_temp_2 @ 2018-02-27T11:56:32.438709-07:00>, ‘new_state’: <state sensor.nodemcu1_temp_2=49.44; unit_of_measurement=°F, friendly_name=nodemcu1_temp_2 @ 2018-02-27T11:57:32.439302-07:00>}, ‘origin’: ‘LOCAL’, ‘event_type’: ‘state_changed’, ‘time_fired’: datetime.datetime(2018, 2, 27, 18, 57, 32, 439355, tzinfo=)}, ‘type’: ‘event’, ‘id’: 1}
DEBUG:homeassistant.components.websocket_api:WS 140635282552144: Sending {‘event’: {‘data’: {‘entity_id’: ‘sensor.nodemcu1_temp_3’, ‘old_state’: <state sensor.nodemcu1_temp_3=69.24; unit_of_measurement=°F, friendly_name=nodemcu1_temp_3 @ 2018-02-27T11:56:32.440145-07:00>, ‘new_state’: <state sensor.nodemcu1_temp_3=69.12; unit_of_measurement=°F, friendly_name=nodemcu1_temp_3 @ 2018-02-27T11:57:32.440702-07:00>}, ‘origin’: ‘LOCAL’, ‘event_type’: ‘state_changed’, ‘time_fired’: datetime.datetime(2018, 2, 27, 18, 57, 32, 440747, tzinfo=)}, ‘type’: ‘event’, ‘id’: 1}
DEBUG:homeassistant.components.websocket_api:WS 140635282552144: Sending {‘event’: {‘data’: {‘entity_id’: ‘sensor.nodemcu1_temp_4’, ‘old_state’: <state sensor.nodemcu1_temp_4=77.68; unit_of_measurement=°F, friendly_name=nodemcu1_temp_4 @ 2018-02-27T11:56:32.441566-07:00>, ‘new_state’: <state sensor.nodemcu1_temp_4=77.45; unit_of_measurement=°F, friendly_name=nodemcu1_temp_4 @ 2018-02-27T11:57:32.442066-07:00>}, ‘origin’: ‘LOCAL’, ‘event_type’: ‘state_changed’, ‘time_fired’: datetime.datetime(2018, 2, 27, 18, 57, 32, 442111, tzinfo=)}, ‘type’: ‘event’, ‘id’: 1}
DEBUG:homeassistant.components.websocket_api:WS 140635282472016: Sending {‘event’: {‘data’: {‘entity_id’: ‘sensor.nodemcu1_temp_1’, ‘old_state’: <state sensor.nodemcu1_temp_1=69.24; unit_of_measurement=°F, friendly_name=nodemcu1_temp_1 @ 2018-02-27T11:56:32.437196-07:00>, ‘new_state’: <state sensor.nodemcu1_temp_1=69.12; unit_of_measurement=°F, friendly_name=nodemcu1_temp_1 @ 2018-02-27T11:57:32.437770-07:00>}, ‘origin’: ‘LOCAL’, ‘event_type’: ‘state_changed’, ‘time_fired’: datetime.datetime(2018, 2, 27, 18, 57, 32, 437814, tzinfo=)}, ‘type’: ‘event’, ‘id’: 2}
DEBUG:homeassistant.components.websocket_api:WS 140635282472016: Sending {‘event’: {‘data’: {‘entity_id’: ‘sensor.nodemcu1_temp_2’, ‘old_state’: <state sensor.nodemcu1_temp_2=50.00; unit_of_measurement=°F, friendly_name=nodemcu1_temp_2 @ 2018-02-27T11:56:32.438709-07:00>, ‘new_state’: <state sensor.nodemcu1_temp_2=49.44; unit_of_measurement=°F, friendly_name=nodemcu1_temp_2 @ 2018-02-27T11:57:32.439302-07:00>}, ‘origin’: ‘LOCAL’, ‘event_type’: ‘state_changed’, ‘time_fired’: datetime.datetime(2018, 2, 27, 18, 57, 32, 439355, tzinfo=)}, ‘type’: ‘event’, ‘id’: 2}
DEBUG:homeassistant.components.websocket_api:WS 140635282472016: Sending {‘event’: {‘data’: {‘entity_id’: ‘sensor.nodemcu1_temp_3’, ‘old_state’: <state sensor.nodemcu1_temp_3=69.24; unit_of_measurement=°F, friendly_name=nodemcu1_temp_3 @ 2018-02-27T11:56:32.440145-07:00>, ‘new_state’: <state sensor.nodemcu1_temp_3=69.12; unit_of_measurement=°F, friendly_name=nodemcu1_temp_3 @ 2018-02-27T11:57:32.440702-07:00>}, ‘origin’: ‘LOCAL’, ‘event_type’: ‘state_changed’, ‘time_fired’: datetime.datetime(2018, 2, 27, 18, 57, 32, 440747, tzinfo=)}, ‘type’: ‘event’, ‘id’: 2}
DEBUG:homeassistant.components.websocket_api:WS 140635282472016: Sending {‘event’: {‘data’: {‘entity_id’: ‘sensor.nodemcu1_temp_4’, ‘old_state’: <state sensor.nodemcu1_temp_4=77.68; unit_of_measurement=°F, friendly_name=nodemcu1_temp_4 @ 2018-02-27T11:56:32.441566-07:00>, ‘new_state’: <state sensor.nodemcu1_temp_4=77.45; unit_of_measurement=°F, friendly_name=nodemcu1_temp_4 @ 2018-02-27T11:57:32.442066-07:00>}, ‘origin’: ‘LOCAL’, ‘event_type’: ‘state_changed’, ‘time_fired’: datetime.datetime(2018, 2, 27, 18, 57, 32, 442111, tzinfo=)}, ‘type’: ‘event’, ‘id’: 2}

aimc · February 27, 2018, 6:59pm

What version of python are you running? I just put some fixes in for version 3.6 that might be related to this - they will be in the next beta.

lightmind · February 27, 2018, 7:17pm

Python version:
Python 3.5.3
Python3-VENV

Do you see the problem?

aimc · February 27, 2018, 7:28pm

This is indicative of a problem that didn’t show up in python 3.5.2. I upgraded yesterday to 3.6.3 and saw this, so it could be that the change happened in 3.5.3 - I believe there were some async fixes.

So, it’s possible that the next beta will fix the problem for you.

ReneTode · February 27, 2018, 9:55pm

there is another thing i notice.
if you want to debug, you need to close everything first.
it seems you have the same dashboard active 3 times at the moment you start appdaemon.

that way you can never be sure that there isnt something cashed wrongly and a problem keeps hanging.
best practice:

close all dashboards on all devices
clear cash at all devices
close appdaemon
clear the logs
clear the subdirs in compiled (so html, css and js) but leave the structure
to be absolutely sure, restart the device running appdaemon
restart appdaemon in debug mode
load 1 (and only 1) dashboard, preferably with only 1 sensor that changes regularly in chrome
if it still not changes the sensor recheck the logs.

if you leave out 1 of these steps there can be an old problem that you already corrected still bugging you.