Posting in this thread will not net any changes or fixes to code. If you have an issue, open it up on github and follow the directions. Right now, you’ve provided nothing useful in regards to fixing any error. Simply saying “XYZ does not work” does not help anyone figure out what’s wrong. So please write an issue on github with a longer description than “Does not work”. This can be done simply by supplying logs from config\homeassistant.log with some screenshots showing the issues.
1 Like
I did. In August. I provided my logs and a detailed description of the issue on Reddit and Github. I have received no responses. On Reddit I got one comment that said I have the same issue. So if somebody wants to assume HA users don’t know how to ask for help I can assume nobody cares about fixing the issue.
Then you have to wait until a developer of that integration picks up the issue and fixes it. If that integration has no code owner, you have to wait. You’re always welcome to bump the issue to get more eyes on it. Posting here or reddit will get you none of that. The people making changes use github.
There is a breaking change in this release affecting several custom integrations:
This is affecting Magic Areas, Adaptive Lighting, Programmable thermostat and several others.
I see no issues on github linked to anthem av or any combination of letters that make up anthem av. Are you sure you created an issue? Did you create the issue against core?
September. I’m sorry
Wrong location for the support issue (GitHub Support Community forum is for issues with Github). You should probably create one here:
1 Like
That’s a support community for github itself, no affiliation with home-assistant. You also didn’t include any logs. Create your issue against home-assistant/core located here:
Please post logs in the issue after you update and the entity appears as unavailable.
Thank you. I will do this.
Hello,
I have a raspi 4 with zwavejs2mqtt and deconz running on it. HA is a VM in VMware connecting via the websocket. Every time I update HA it requires an updated version of zwavejs2mqtt which breaks my zwave devices. All of my devices are still connected to zwavejs2mqtt but they always show up as generic devices in HA. Even if I name them within zwavejs they still show as generic node 26 et cetera.
How can I do this so that all the devices retain their device names during an HA upgrade or zwavejs2mqtt upgrade?
On a side note - I have to keep them separate because the raspi 4 is located near the center of my house and provides the best experience this way.
Thanks!
Anyone having problem in restore backup on the fresh install HA Supervised? I forget about this during my recovery process after breaking changes. The link is basically unclickable.
is the xiaomi hub broken since 2011.11.1 ? had to update to the new version for tuya but broke xiaomi integration in the meant time
Lee B
I’m not sure if this is something that happened as a result of the 2021.11 update or the ZWave JS update from 0.1.45 to 0.1.46 (as I basically did both at the same time) but some of my Aeotec Multisensors are no longer updating the lux level, however motion etc are still updating fine.
Anyone else noticed this?
Someone else mentioned something similar iirc
Sounds like you didn’t setup the persistent storage properly for your container.
I did not have the atomic-calendar-revive integration installed, I had it previously but it was removed some versions ago. Now after installing it again al my card in some of my views have returned.
After 2021.11.2 the BMW Connected integration doesn’t work anymore…
2021-11-09 22:02:13 ERROR (MainThread) [homeassistant.components.sensor] bmw_connected_drive: Error on device update!
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/entity_platform.py”, line 431, in _async_add_entity
await entity.async_device_update(warning=False)
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 651, in async_device_update
await task
File “/usr/local/lib/python3.9/concurrent/futures/thread.py”, line 52, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/src/homeassistant/homeassistant/components/bmw_connected_drive/sensor.py”, line 528, in update
self._attr_native_value = getattr(vehicle_state, sensor_key).value
AttributeError: ‘NoneType’ object has no attribute ‘value’
2021-11-09 22:02:13 ERROR (MainThread) [homeassistant.components.binary_sensor] bmw_connected_drive: Error on device update!
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/entity_platform.py”, line 431, in _async_add_entity
await entity.async_device_update(warning=False)
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 651, in async_device_update
await task
File “/usr/local/lib/python3.9/concurrent/futures/thread.py”, line 52, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/src/homeassistant/homeassistant/components/bmw_connected_drive/binary_sensor.py”, line 251, in update
self._attr_is_on = self.entity_description.value_fn(
File “/usr/src/homeassistant/homeassistant/components/bmw_connected_drive/binary_sensor.py”, line 102, in _is_vehicle_charging
extra_attributes[“charging_status”] = vehicle_state.charging_status.value
AttributeError: ‘NoneType’ object has no attribute ‘value’
I would like to propose for one of the next releases the ability to separate Automations and Scripts into groups, for example all automations that involve lighting will be grouped in a group called Lighting. Since I have around 150 automations, this would help me a lot when searching for a certain automation or script.
1 Like
Good idea, but this belongs in the feature request section of the forum.
Also there is an existing feature requests for this. Please vote for it rather than opening a new one.
https://community.home-assistant.io/t/grouping-automations-on-frontend-for-organization/102771