Damn same websocket error continues to show up. Reboot HA and after that I was able to discover devices. Before that I got a spinning circle and nothing happend.
Discovery seems to be too hard task to do. This is the query for the devices.
"httpGetExec([uri:http://192.168.86.48:8123/api/states, headers:[Authorization:Bearer..."
Websocker error sounds like a connection issue but Unifi doesn't show any problems on there. Is there a way to check the HA side and it's connection errors?
EDIT: and right after this message Hubitat says "Hub load is severe" "2.33". Now I'm going to do reboot and remove HADB. I'm not saying it is HADB which causes this but I definitely see that when I'm trying to do discovery on HADB I'm getting really slow response from Hubitat and things go bad.
When is the last time you did a soft reset/download recent backup and restore? When you restart the hub if you click advanced you are given the option to restore backup too.
I do not even remember. Maybe two years ago or something. It sounds so brutal and too exciting for me to reset everything and then try to restore backup. If something goes wrong and automations goes down then I'm having way bigger issue than now.
But...I remember that there has been several times when I have installed Windows again just because everything has slowed down on my computer. So...why wouldn't it work on Hubitat too.
That is not what I am suggesting. The hub database can become corrupted and cause weird issues. I am suggesting you are simply download a database backup and restore immediately. You lose nothing but it might solve your issues.
I was just trying to add some new devices yesterday and the let the Discover page spin for 30 minutes before I gave up. I was going to get back to looking at why tomorrow.
Just now I turned off debug logging and, as you noted, it is now instantaneous.
Yep but I turned debug on because I was trying to understand why it is not discovering devices. So I have same issue whether the debug is enabled or not.
That query makes hub go wild and I did not have any other option than reboot the hub.
FWIW I ran into this when developing the Gmail integration in my community GCal Search app. I was also logging large strings of encoded attachment data and the hub would slow down tremendously and I would have to reboot often. I ended up having to create different log levels so users would experience this by default.
In the next version I plan to forgo with climate --> thermostat translation. Meaning HADB will let climate entity modes and states go through as is, regardless what is supported by Hubitat.
Some implications are:
Extraneous modes won't show up in the list of available modes in RM. (They could be choosen as custom command though)
Thermostat tile in regular dashboard may ehxibit strange behavior when these modes are in effect.
Easy dashboard should make these available on its thermostat tile.
If any of you forsee problems with this change, please let me know.
Previously the Auto mode in HE was mapped to "heat_cool" in HA and auto mode from HA was discarded. If you have rules that select auto as a mode, they either won't work or they will select a different mode then before.
After some time, I’ve revisited this for my Hive (uk) smart thermostats.
I’ve now found that using the latest release the thermostat for heating is working. There is a sensible tile on the hubitat dashboard, and I can access devices through WebCore to respond to events and trigger actions.
The Hive thermostat also handles hot water using a schedule (on/off/auto) or a manual boost. The following screenshot shows the devices available from HA. These attributes can be queried and used in webCore, but can not be changed or cause the triggering of an event. Would it be possible to make these fully operational?
These 2 entities are binary sensors, therefore they only report values and are not actionnable.
The thermostat itself should be a climate entity, which I don't see in your list. Make sure you select it in the HADB app and have it do something somehow (make it generate an event).
The thermostat is there and working well, the list of devices is filtered.
This screen shot shows the water heater in HA, it would be good to get this into HE. I’m not sure if the HA implementation can trigger the boost function, it may just display it, so guess nothing could be done with that?
Has anyone been able to import a Reolink camera and use the person detection entity?
When I first imported the binary_sensor.front_doorbell_person entity, HADB assigned it a Generic Component Unknown Sensor and the value was turning on/off correctly. The device wasn't selectable in automations though, so I changed the driver to Generic Component Motion Sensor, but now the value isn't turning on/off anymore.
EDIT: I don't see the Generic Component Motion Sensor driver in my hub's Drivers Code section. I installed HADB for the first time today through HPM. Did it not import the motion sensor driver correctly perhaps?
It doesn't have any commands available to it either.
If HADB assigned the unknown sensor, it is because your entity did not report a supported device class. As you mention, the unknown device still report a value though (on/off). Changing the component driver to something else will indeed render the device unusable.
With the proper driver (the one assigned by HADB) you can select it for automation by choosing "custom attribute" as a trigger.
Could you point me in the right direction to use the HADB custom call service? I only require to change the timer mode between scheduled, off and on.
Thanks
