TypeError: Entity.set_state() takes 1 positional argument but 2 were given

[Mike-Allen]

What happened?

This is interesting.

The code is scheduled to run every 15 minutes. The night before last the app was started about 7:40 PM and ran fine until midnight. Then it started throwing the errors. Each 15 minutes it would attempt to run again but fail. (Failing at midnight is a coincidence and isn't part of the problem. The problem has occurred at other times.)

Sometimes the error occurs sooner after the app is started, maybe after a half-hour or so.

The problem code is: (There's some more context below in the code section)
self.high_temp_ent.set_state(fTemperature)

Changing the code to the following seems to fix the problem:
self.high_temp_ent.set_state(state = fTemperature)

As can be seen self.high_temp_ent.set_state is an AppDaemon entity.

It's odd that it works for a while. Although the log entry says that the app and thread are pinned I did not explicitly pin either of them. (It's probably the default behavior but I thought I'd mention it.)

It's not a problem for me. The fix works. The app has now been running for over 24 hours and hasn't had any problems.

I would add that I saw the deprecation notice by Frenck and I understand and support AppDaemon's position. Home Assistant wouldn't have the same value without AppDaemon. Home Assistant provides the building blocks. AppDaemon allows me to create... magic.

I have two Home Assistant instances. One is "old" running Home Assistant and AppDaemon in Python virtual environments. (I need to upgrade but dread the z-wave upgrade.) The other instance is new and uses Frenck's add-on. I can use AppDaemon in a virtual environment or I can add AppDaemon through Docker if I need to. There's no way that I'm running Home Assistant without AppDaemon.

Version

4.4.2

Installation type

Home Assistant add-on

Relevant log output

2025-01-20 08:15:00.007032 WARNING GetWeather: ------------------------------------------------------------
2025-01-20 08:15:00.007286 WARNING GetWeather: Unexpected error in worker for App GetWeather:
2025-01-20 08:15:00.007399 WARNING GetWeather: Worker Ags: {'id': '5f43680bacec4282b24d83f56c8ffb39', 'name': 'GetWeather', 'objectid': 'f8d6794d75da4007a3c321a3e2b3d137', 'type': 'scheduler', 'function': <bound method CabinWeather.getWeather_CB of <getWeather.CabinWeather object at 0x7faecbe56190>>, 'pin_app': True, 'pin_thread': 1, 'kwargs': {'interval': 900, '__thread_id': 'thread-1'}}
2025-01-20 08:15:00.008364 WARNING GetWeather: ------------------------------------------------------------
2025-01-20 08:15:00.008888 WARNING GetWeather: Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/appdaemon/threading.py", line 1022, in worker
    funcref(self.AD.sched.sanitize_timer_kwargs(app, args["kwargs"]))
  File "/config/apps/getWeather.py", line 230, in getWeather_CB
    self.processWeather()
  File "/config/apps/getWeather.py", line 254, in processWeather
    self.high_temp_ent.set_state(fTemperature)
  File "/usr/lib/python3.11/site-packages/appdaemon/utils.py", line 231, in inner_sync_wrapper
    f = run_coroutine_threadsafe(self, coro(self, *args, **kwargs))
                                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: Entity.set_state() takes 1 positional argument but 2 were given
2025-01-20 08:15:00.009100 WARNING GetWeather: ------------------------------------------------------------

Relevant code in the app or config file that caused the issue

sTemperature  = self.temperature_ent.get_state()
    fTemperature  = float(sTemperature)

    if float(self.high_temp_ent.get_state()) < fTemperature:
      self.high_temp_ent.set_state(fTemperature)

Anything else?

No response

[acockburn]

Hi there - This sounds like a weird one, I'm not sure how time could affect this particular error at all ... Having said that you found a fix. And in fact, the fix is the way the docs say to do it so we will go with that 🙂 The actual error I think may have been fixed in dev, I just wouldn't expect it to work then stop for no reason other than time. Thanks for your kind comments about AD - they are really appreciated! I built AD for the exact reasons you mentioned, and rest assured, it isn't going anywhere, as I often say, I still use it myself every day. Releases have been slow mainly because it does everything I need at the moment, however, I have been lax and I know that updates to python and out of date packages are important. There has been a holdup (all due to me and my workload) in that we had some large changes going through and I didn't get around to vetting them. In future, I'll keep large changes separate so I can easily and quickly rev a package or even add support for a new python version - this has been a learning experience for me! I do hope that frenck will reconsider and continue to release his addon when we get a new version out, but that is his choice. If he does not we will look for volunteers to pick it up and probably move it under the AD umbrella. Andrew