Repository navigation
Token validity #1772
bodos67-dev
started this conversation in
General
Token validity
#1772
Replies: 1 comment
|
which firmware version are you using? ah, the reason is that the HA discovery is an extra one-time option for a token that yours doesn't have yet according to your post. If you want, I can add it to your token by shortening the duration a bit. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I have purchased a token (2years update, HA integration, serial 8cfd4905fc40). I have been able to integrate the micro-ebusd with bai and 700 circuits once into HA, but my HA instance crashed.
Now the sensors of the auto discovery of the bai and 700 circuits are no longer published in the binary_sensors or the sensors topic and hence not found by HA. Only the adapter sensors are announced.
The state of the C6 adapter is:
Free heap: 151448 / 336852
micro-ebusd: running
eBUS signal: acquired
MQTT connected: yes, topic: ebusd
Home Assistant: online
The micro-ebusd shows:
Protocol: Token authorized, updates until 29.4.2028
Parameters
User Level
Poll interval, seconds
Log Level
Home Assistant Discovery Filter
all messages, without string/time fields (default)
Home Assistant Discovery for eBUS messages is not (yet) authorized by token
MQTT:
MQTT: On with Home Assistant
Broker/Topic
URI
Version
QoS
HA Discovery prefix (if other than default 'homeassistant')
HA Birth topic (if other than 'homeassistant/status')
HA Birth payload (if other than 'online')
I really wonder about the inactive Discovery Filter and the not authorized token. I spend nearly 50€ for a non working feature.
Best Regards Stefan
All reactions