After I upgraded v. 0.83 Occusim start everytime

I configured Occusim to start when my alarm system is in AWAY mode and time is over 17:00 and until 23:59
But after upgrade to v. 0.83 it is always active.
Before upgrade it worked fine for a month with this configuration

Occupancy Simulator:
  class: OccuSim
  module: occusim
  log: 1
  notify: 1
  enable: alarm_control_panel.ha_alarm,armed_away
  dump_times: 1
  reset_time: 00:00:00

  step_starttime_name: Start_time
  step_starttime_start: "17:00:00"

  step_stoptime_name: Stop_time
  step_stoptime_start: "23:59:59"

Any help???

anything in the logs?

there are known connection problems with 0.83, so check if there is another update.
and make sure you dont use ha_key but token in appdaemon.yaml

Ok, I checked it and discovered I had both ha_key and token …
then I removed ha_key from appdaemon.yaml

No I have this warning…

2018-12-02 13:35:14 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 172.30.33.5
2018-12-02 13:35:19 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 172.30.33.5
2018-12-02 13:35:24 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 172.30.33.5
2018-12-02 13:35:29 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 172.30.33.5
2018-12-02 13:35:34 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 172.30.33.5
2018-12-02 13:35:39 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 172.30.33.5
2018-12-02 13:35:39 WARNING (MainThread) [homeassistant.components.http.ban] Banned IP 172.30.33.5 for too many login attempts

what HA version did you download. 0.83 has problems but i think it was fixed in 0.83.1
and i dont know how to go on after you have banned yourself.

and when you want to find out things about appdaemon you should look in the appdaemon logs, this is from the homeassistant logs.

Now Occusm problem seem is solved after I removed ha_key from appdaemon.yaml
Thank you ReneTode!!!

1 Like

@ReneTode
im having a similar issue. running hassio on virtualbox.
Installed appdaemon, all seemed ok. however i get the Login attempt or request with invalid authentication from x.x.x.x which is my tablet with the dash running.

If i remove the token from the appdaemon yaml it automatically puts one back in. When this hppens hassio also issues new tokens for my axis cameras (which are on the dash main page), so i also lose camera feeds. yet the buttons etc i have on the dash all work ok.

been scratching my head for a couple of days on and off.

in your case thats something that is because you use hassio with the addon.
i cant help you there you better contact frenck about that.

Apologies, I always get you and @frenck mixed up.

freck created the addon, i dont have it installed and no knowledge about it.
i am there for every other appdaemon and dashboard question.

and its in most of the times hard to know if a problem is caused by the addon or AD, for other people.
i can tell because i have seen all the questions :wink:

I’ll bare that in mind :stuck_out_tongue_winking_eye::+1:

Thanks again

1 Like

@frenck, hi could you help me with the above ?

thanks in advance