This is a text capability. Only boolean capabilities will show up in the log (if log is enabled in capability definition).
If you need a log, then you have to add the entity again using a boolean capability (alarm*) and add a converter that returns true or false based on your possible entity states.
My installed app continues to crash with the following error message. I am hoping there is a possible solution without removing and reinstalling the app and imported devices.
Overall free memory has been an issue for about a year. Even removing apps only temporarily solve the problem. HAC has not been problematic until about a month ago. I am also playing with a NAS version of Homey Self-Hosted, same HAC error with 1.9GB of 8.2GB used. May just have to remove HAC and then start building back up. Thank you
Iām guessing that my home assistant instance is likely far too large to be used on a homey pro, but I would be curious to know what has caused the crash (happens once I confirm IP, PORT and API).
If there is a workaround, please advise, would be keen to try it.
And the home assistant instance is sitting at about 80,000 entities. Have rebooted the homey pro, but that didnt make a difference. if there is a number of entities constraint, I can spin off the entities i need to import into a different instance. no sense in duplicating homeassistant and homey parts.
The Homey app listens to all Entity changes on HA. Perhaps the full entity state list (sent on 1st reading) is too big.
The Homey app uses the standard HA websocket API. I donāt think, you can filter the content on HA side. And two instances would help, but will mess up your system(?)
I will check if I can find a reason for the errorā¦
I asked on Slack. We donāt know an exacd cause, but it seems itās caused by an HA entity state/event.
I already saw some entity states including huge JSON strings. Especially from some kind of network state entities including all kinds of found network devices.
Can you check in HA developer tools it there is an entity with such s big state content?
Edit: It seems to be a memory limit. Perhaps your amount of entities results in a high memory consumption for the homey app. Letās wait for an answer from Athomā¦
it would appear that I had 250,000,000 or so known devices in a configuration file. Never got to the bottom of why this file enlarges on home assistant, but I deleted it, and now everything is working.
I will have to knock up a script that deletes the file once a week, and I think I will be back in business.
Oh, so an integration is spamming duplicated entities? Try to check every day what entities got added.
If you have other integrations importing/exporting entities Like MQTT auto discovery, Alexa etc. they can re-add exported entities counting up the entity ID with a trailing number.
something to do with bluetooth I think, at some point iāll get around to stripping that out (once I remember if I actually use bluetooth for anything useful in Home Assistant).
@RonnyW Now that thereās a Home Assistant add-on for Homey SHS, I wonder about the possiblity to integrate directly with Home Assistant, rather than communicating over IP?
are not devices with capabilities:
Is it possible to somehow sync an input_datetime helper with a Homey Alarm?
I mean, itās not a problem to send the input_datetime values to a custom device, but the other way round, to pick a timestamp/alarm on Homey, which updates the H.A. input_datetime, isnāt possible (yet).