bradsjm / hubitat-public Goto Github PK

I originally installed the esphome and ratgod packages using HPM and they worked amazingly well, for which I am very grateful. I installed the most recent version as of 3/4/24 using Hubitat Package Manager and the integration broke completely. In 'events' for the device I get the error:

Garage Door is offline: Cannot invoke method multiply() on null object

Looking at the logs I see:

java.lang.NullPointerException: Cannot invoke method multiply() on null object on line 257 (method initialize)

I have not been able to find the exact source of the issue, but I can confirm that manually reverting to the original ratgdo driver by copying the code from the 6015892 commit and pasting it into the drivers code in hubitat solves the issue

Hi, this is a follow up to my post in the Hubitat community forum. Thank you for this amazing driver! I noticed that it correctly pulled down my Tuya devices and even a scene (which I use for turning a socket off and back on to ring a doorbell). However, the On button didn't actually run the scene. I believe it's because my Home ID is too large - 9 digits long - which does not fit in an Int. But, Int shouldn't be needed since it's only used for appending to the URL in the API call anyway.

I got it to work by changing every "Int homeId" to "String homeId", including in the triggerTuyaScene() function definition.

The only thing is that for scenes, it doesn't make a lot of sense to have a "switch" as the default component since they wouldn't have an Off function. Perhaps your code could add Tuya scenes as a push button or similar?

Regards,

Gabriel Mongefranco
Mobile Data Architect
https://gabriel.mongefranco.com

Hi,
I believe this line is wrong. The second rnd number should not be there. It should be */${intervalMin} instead. Is that possible ?

the temperature is scaled but the set point is not, this means the setpoint = x10 more than it should be.
value just needs to be scaled as per the first block of code

if (status.code in tuyaFunctions.temperature) {
Map set = deviceStatusSet[status.code] ?: defaults[status.code]
String value = scale(status.value, set.scale)
String unit = set.unit
if (txtEnable) { LOG.info "${dw} temperature is ${value}${unit}" }
return [ [ name: 'temperature', value: value, unit: unit, descriptionText: "temperature is ${value}${unit}" ] ]
}

    if (status.code in tuyaFunctions.temperatureSet) {
        Map set = deviceStatusSet[status.code] ?: defaults[status.code]
        String value = status.value
        String unit = set.unit
        if (txtEnable) { LOG.info "${dw} heating set point is ${value}${unit}" }
        return [ [ name: 'heatingSetpoint', value: value, unit: unit, descriptionText: "heating set point is ${value}${unit}" ] ]
    }

After the latest hubitat update, my Inovelli Red Series dimmer stopped working. I had to update the driver to get it working again. With that update, my dimmer is no longer getting notifications. I have 3 switches and none of them work. I have red swutcges and blue series dimmers, and the notifications are still working.

The problem is in the call to state.clear() in configure() in the white and CT drivers (the RGBW driver doesn't call state.clear() so it's ok).

When you call setGroupMembership(), state[config] is null for all three states (because of the state.clear() so none of the if statements for removing from a group could ever return true.

You can't simply move the state.clear() after the call to setGroupMembership(), since you would be wiping out the states that may have been set in the add to new group section. I don't think the state.clear() is really needed anyhow.

I would remove the groupstate configuration values completely and delete setGroupMembership(). The bulb already knows what groups it is a member of, and you are reporting that correctly in the groups state variable. If something external adds a bulb to a group (like the Groups app when you enable zigbee group messaging) your driver doesn't know about that so you're not going to have the correct value in your driver's groupstateX config.

Also, the bulbs can have more than three groups. My whites for example report 25 available groups, but you don't have 25 configuration values. I wouldn't bother with any of this. I would add "add group" and "remove group" commands, which would let people configure groups without you needing to try and mirror the correct group state of the bulb in the driver.

I have 5 ESPs running esphome around my house. Each on these is receiving temperature/humidity readings from multiple remote sensors.

When I add one of the esphome devices to C8 I select the specific temperature & humidity for one of the rooms. This is ok.

However, how can I add the same esphome device again to select the 2nd remote sensor temperature & humidity this time? I have tried just adding a second instance but it doesn’t work.

Hey, I’ve been using the Tuya driver for a few weeks and it works great, thanks for writing it. :)

I just picked up a MoesGo IR Blaster and have it working with the Tuya app, but it doesn’t work with the Hubitat driver because it’s a remote device. Any chance you’d accept a pull request to add remote control support?

Esp-home devices doesn't reconnect automatically after a hub update.