Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: 'The option options must be used together with device class enum, got device_class 'None' #180

Open
timbba80 opened this issue Dec 8, 2024 · 4 comments

Comments

@timbba80
Copy link

timbba80 commented Dec 8, 2024

I've seen these error messages in the home assistant logs for a while now. Everything works fine though. Am I the only one?

Home Assistant 2024.11.3

Logger: homeassistant.components.mqtt.entity
Source: components/mqtt/entity.py:155
integration: MQTT (documentation, issues)
First occurred: 19:54:01 (2 occurrences)
Last logged: 19:54:01

Error 'The option options must be used together with device class enum, got device_class 'None'' when processing MQTT discovery message topic: 'homeassistant/sensor/go-e_xxxxxx/car_state/config', message: '{'value_template': "{{ ['Unknown','Idle','Charging','WaitCar','Complete','Error'][value_json|int ]}}", 'state_topic': 'go-eCharger/xxxxx/car', 'options': ['Unknown', 'Idle', 'Charging', 'WaitCar', 'Complete', 'Error'], 'command_template': "{% set o = {'Unknown': 0,'Idle': 1,'Charging': 2,'WaitCar': 3,'Complete': 4,'Error': 5} %}{{ o[value] if value in o else value }}", 'unique_id': 'go-e_xxxxx_car_state', 'name': 'Car State', 'device': {'model': 'go-eCharger_V4', 'identifiers': ['go-e_xxxxx'], 'sw_version': '56.8', 'name': 'go-eCharger_xxxxxx', 'manufacturer': 'go-e'}}'

Error 'The option options must be used together with device class enum, got device_class 'None'' when processing MQTT discovery message topic: 'homeassistant/sensor/go-e_xxxxxx/error_state/config', message: '{'value_template': "{{['None','FiAc','FiDc','Phase','Overvolt','Overamp','Diode','PpInvalid','GndInvalid','ContactorStuck','ContactorMiss','StatusLockStuckOpen','StatusLockStuckLocked','FiUnknown','Unknown','Overtemp','NoComm','CpInvalid'][value_json|int ]}}", 'state_topic': 'go-eCharger/xxxxxx/err', 'options': ['None', 'FiAc', 'FiDc', 'Phase', 'Overvolt', 'Overamp', 'Diode', 'PpInvalid', 'GndInvalid', 'ContactorStuck', 'ContactorMiss', 'StatusLockStuckOpen', 'StatusLockStuckLocked', 'FiUnknown', 'Unknown', 'Overtemp', 'NoComm', 'CpInvalid'], 'command_template': "{% set o = {'None': 0,'FiAc': 1,'FiDc': 2,'Phase': 3,'Overvolt': 4,'Overamp': 5,'Diode': 6,'PpInvalid': 7,'GndInvalid': 8,'ContactorStuck': 9,'ContactorMiss': 10,'StatusLockStuckOpen': 11,'StatusLockStuckLocked': 12,'FiUnknown': 13,'Unknown': 14,'Overtemp': 15,'NoComm': 16,'CpInvalid': 17} %}{{ o[value] if value in o else value }}", 'unique_id': 'go-e_xxxxxx_error_state', 'name': 'Error State', 'device': {'model': 'go-eCharger_V4', 'identifiers': ['go-e_xxxxxx'], 'sw_version': '56.8', 'name': 'go-eCharger_xxxxxx, 'manufacturer': 'go-e'}}'

@AndreasLehmann
Copy link

same here

@syssi
Copy link
Owner

syssi commented Dec 28, 2024

It looks like you aren't using this integration/project. The error is triggered by the mqtt integration because the auto-discovered MQTT topics of the Go-e charger aren't well defined.

@AndreasLehmann
Copy link

AndreasLehmann commented Dec 30, 2024

@syssi : You are right. The go-e charger is listed in the MQTT Integration and in the goecharger-Integration. Can I disable the MQTT Integration without affecting the goecharger-Integration ?

@syssi
Copy link
Owner

syssi commented Dec 30, 2024

The MQTT integration is an important dependency/requirement. You can disable or remove the auto-discovered MQTT device instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants