Understanding logs about a missing device

Topics (not sure which fora)
when not sure where to post, post here and mods will move it to right forum.

Moderators: leecollings, remb0

Post Reply
capitalT
Posts: 11
Joined: Thursday 30 May 2019 9:51
Target OS: Linux
Domoticz version:
Contact:

Understanding logs about a missing device

Post by capitalT »

Hi,

Domoticz does not show an air quality value or text from my IKEA VINDSTYRKA Air quality monitor.
I want to understand what the logs are trying to tell me here:

Code: Select all

Error: DeConz: Unknow device type ZHAAirQuality
Who doesn't know this device type? Deconz or Domoticz?

And to help me a little further, where in the code should this device type have been defined?
User avatar
waltervl
Posts: 5851
Joined: Monday 28 January 2019 18:48
Target OS: Linux
Domoticz version: 2024.7
Location: NL
Contact:

Re: Understanding logs about a missing device

Post by waltervl »

This is a message from the integration. Plugin or MQTT AD. It seems the integration wants to use or create a device with a device type that does not exist. So probably a type error somewhere.

What zigbee integration in Domoticz do you use?
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
capitalT
Posts: 11
Joined: Thursday 30 May 2019 9:51
Target OS: Linux
Domoticz version:
Contact:

Re: Understanding logs about a missing device

Post by capitalT »

waltervl wrote: Monday 19 February 2024 22:06 What zigbee integration in Domoticz do you use?
I use the default deconz plugin. I see an air quality device in Domoticz, so something going wrong in the plugin with the translation, right?
edit: I see that this plugin is from its own repo which hasn't been updated for a while.

Thanks for pointing me in the right direction!
Thorgal789
Posts: 851
Joined: Wednesday 15 August 2018 14:38
Target OS: -
Domoticz version:
Contact:

Re: Understanding logs about a missing device

Post by Thorgal789 »

Try updating your plugin version, this device type is supported since 2022, or there is a problem with this device.
And look if you are on the good github page because the repo is updated 3/4 time by year.
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest