On the device page, choose “Device Info”. At the bottom you will see the “Device Data” section in bold.
On the integrations page, look at the far right of the line for HADB, there will be a circle with an i in it. This will open the info page for the app.
For the app it is the settings I’m interested in. Not the application state (which normally is empty).
Hi. I'm fooling around with rtl_433.
My LaCrosse fridge temp monitor was working great until the freezer sensor got to, around, zero F. Then it went crazy with the significant numbers. Can anything be done about it on the HADB end? Reads fine in the HA device page. Thanks.
It seems to have squared itself away after getting below 0F.
Replace the HADB app code with this one:
See if it fixes your problem.
Your screenshot is showing your access token… perhaps it would be good idea to remove it.
yes it fixed the issue and now all the devices that are supposed to be on the list are there and it seams to be workin again .
Thanks for all your help greatly appreciated. And I did remove that post, thanks for pointing that out as well.
Regards.
Sal
ymeri, Yes it fixed it, however this am I got a message to update it via the HPM I will wait i think it’s the same update that broke it. Am I correct On 2.2.4 asking to go to 2.2.5. Just wondering if that will cause the same issue.
Your problem was not cause by the update. I can’t tell was caused it. Somehow the app lost its include list. The file I made for you was specifically to restore the list from the driver’s copy.
So I should be able to update it then ? Thanks for the help and I don’t really know what caused it was just guessing on my end!
Yes
yep all good it worked thank you for the help greatly appreciated. I am wondering if Home Assistant may have caused this issue the updates kind of happened in the same day one on Home assistant and then Hubitat. In any event all is good now.
@ymerj Minor bug and fix:
I created an input_text entity on HA and imported it via HADB. When I went to the HE device and tried to use "set variable" to change the value, I got this error:
The code in the HADB Generic Component Text driver only implements setText for the capability "Variable":
void setText(variable)
{
parent?.componentSetVariable(this.device, variable)
}
I duplicated that to setVariable and now it works. (I wasn't sure if I should rename setText, so I left it).
I needed that fix use HA to speak arbitrary messages on my Alexa devices from HE.
[RELEASE] Home Assistant Device Bridge (HADB) - #2077 by jlv
I first added the Alexa Devices integration to link my Alexa devices.
Then I created two helpers (Setttings -> Devices & Services -> Helpers tab).
details:
Then under Automations & Scenes, I added two routines:
There are two: the difference is one uses Announce and one uses Speak against Echo device.
Now anytime I change the text variable, the selected Alexa speaks (or announces, with a ding) the text.
The Message box contains this, which interpolates the value of the string:
{{ states('input_text.kitchen_echo_show_speak_this_message') }}
alias: Kitchen Echo Show Announce This
description: ""
triggers:
- trigger: text.changed
target:
entity_id: input_text.kitchen_echo_show_announce_this_message
options: {}
conditions: []
actions:
- action: notify.send_message
metadata: {}
target:
entity_id: notify.kitchen_echo_show_announce
data:
message: " {{ states('input_text.kitchen_echo_show_announce_this_message') }}"
- action: input_text.set_value
metadata: {}
target:
entity_id: input_text.kitchen_echo_show_announce_this_message
data:
value: ""
mode: single
alias: Kitchen Echo Show Speak This
description: ""
triggers:
- trigger: text.changed
target:
entity_id: input_text.kitchen_echo_show_speak_this_message
options: {}
conditions: []
actions:
- action: notify.send_message
metadata: {}
target:
entity_id: notify.kitchen_echo_show_speak
data:
message: "{{ states('input_text.kitchen_echo_show_speak_this_message') }}"
- action: input_text.set_value
metadata: {}
target:
entity_id: input_text.kitchen_echo_show_speak_this_message
data:
value: ""
mode: single
(I specifically set the string back to empty so that I can speak the same message repeatedly. To do this correctly, I needed to edit that block in the YAML editor, not the visual one.)
End result is that I can import those text entities via HADB. Now whenever I set the variable on HE, I get an it spoken on the selected Alexa.
As a hack, I created a copy of HADB Generic Component Text adding just this:
capability "Notification"
and
def deviceNotification(message) {
parent?.componentSetVariable(this.device, message)
}
I then switched to the two devices to use this driver and and now I can use them everywhere that takes notifications.
Thanks for reporting the bug.
That tells how much this entity is in use. It’s been like that for a year and a half and nobody reported it.
It will be corrected in the next version.
Wouldn’t be easier to use a TTS or the notify entity directly from HE through the HADB custom service call ?
To be honest, I couldn't figure out to invoke the notify entity via the service call! There is only 1 or 2 examples in this thread.
