markus-li / hubitat Goto Github PK

When I set up a Sonoff basic or a wemo d1 mini and have a button switch to turn on the lights, it's is very intermittent. Tasmota itself has the same issue I think. Any suggestions?

Display child devices with direct links to the Driver Config pages together with their respective Parent device.

Heya Markus. Since I don't have a way to submit a proper PR (as you rightly pointed out the last time) thought an issue might be better.

It looks like the attempt to implicitly cast String to BigDecimal fails in the Aqara Vibration Sensor driver. The fix is to explicitly create BigDecimals:

void setClosedPosition() {
    BigDecimal cX = new BigDecimal(device.currentState("currentX")?.value)
    if(cX != null) {
        state.closedX = cX
        BigDecimal cY = new BigDecimal(device.currentState("currentY")?.value)
        state.closedY = cY
        BigDecimal cZ = new BigDecimal(device.currentState("currentZ")?.value)
        state.closedZ = cZ
        sendPositionEvent("closed")
        logging("Closed position set to $cX$DEGREE, $cY$DEGREE, $cZ$DEGREE", 100)
    } else {
        logging("Closed position NOT set because no 3-axis accelerometer reports have been received yet", 100)
    }
}

void setOpenPosition() {
    BigDecimal cX = new BigDecimal(device.currentState("currentX")?.value)
    if(cX != null) {
        state.openX = cX
        BigDecimal cY = new BigDecimal(device.currentState("currentY")?.value)
        state.openY = cY
        BigDecimal cZ = new BigDecimal(device.currentState("currentZ")?.value)
        state.openZ = cZ
        sendPositionEvent("open")
        logging("Open position set to $cX$DEGREE, $cY$DEGREE, $cZ$DEGREE", 100)
    } else {
        logging("Open position NOT set because no 3-axis accelerometer reports have been received yet", 100)
    }
}

https://tasmota.github.io/docs/devices/YTF-IR-Bridge/

I added it as Generic Parent Devices, but Child device is not appearing

First of all, thanks for all the remarkable work you have done. It is very impressive.
Secondly, if this is not the correct place to provide feedback, please let me know where I should.

I have followed the instructions here: https://community.hubitat.com/t/release-tasmota-7-x-firmware-with-hubitat-support-tuya-and-sonoff-drivers/29368 and loaded Tasmota Hubitat 7.1.2 onto a Globe 34207 800lm RGBCCT and configured it as per https://templates.blakadder.com/globe-34207.html. All the controls work correctly when set using the Tasmota web page by browsing to the IP address of the bulb.

I have loaded both the Tasmota Connect App and Tasmota - Generic RGB/RGBW Controller/Bulb/Dimmer into Hubitat. I took the code today (December 28, 2019) from your GitHub depot.

Most commands work great. However, the "Set Color Temperature" command does not appear to work correctly and does not set the correct color temperature on the bulb.

Do you have any suggestions? Thanks very much

For group messaging this would be so that we can eliminate, at least mostly, the popcorn effect. This will still require an EXCELLENT wifi network as well as a FAST MQTT server. An RPi4 is more than fast enough.

Might also consider adding MQTT support for receiving updates? But why would we need this? It would make ti possible to run unmodified Tasmota builds, which I don't see a good reason to support really, but maybe...

Hi

I have over 20 NUE switches in our house and most seem fine. However I have about 7 single gang NUE Dimmers and 1 double gang NUE Dimmer which appear to fall of the Zigbee network regularly. I have tried the Hubitat driver and also your driver with presence. Your driver feels like it lasts longer, but, I have re-paired a few again today and see one now has "notPresentCounter" incrementing.

My environment: Hubitat C-7, all switches are NUE Zigbee (1,2,3 and 4 gang), some Tuya (I think) based zigbee temperature sensors, Aeotec Multi and Tri Sensors using Z-Wave, some Telstra Zigbee Plugs, and a few Alexa Echo Dots 3rd and 4th Gen)

One think I noticed is your driver has model: LXN56-DS27LX1.1 in while all my dimmers seem to be: LXN56-DS27LX1.3, I have tried (this week) to edit the drived and duplicate the device line and change model in the duplicated line). However since I've had to fix some today I do not think that has worked.

Currently all are using your "Zigbee - Generic Dimmer (with Presence)
endpointId: 01
application: 01
driver: v1.0.1.1123
softwareBuild: 00000001
model: LXN56-DS27LX1.3
firmwareMT: 117E-0101-00000001
isMultiEP: false
manufacturer: 3A Smart Home DE

I do have an in-wall or ceiling NUE Dimmer which is LXN56-DS27LX1.3 and does not drop off the Zigbee network
Using "Generic Zigbee Dimmer"
endpointId: 01
model: LXN56-DS27LX1.3
application: 00
isMultiEP: false
manufacturer: 3A Smart Home DE

So do you think adding this model to your deployment so I can use HPM to update would be worth it?
How to work why they are dropping off,

Nay assistance would be great.
Budjik

Unhandled Event PLEASE REPORT TO DEV - description:read attr - raw: A59101FCC082F700413D64100103282098390000000095398D2E0E40963900800945973900000000052104009A20100821160107270000000000000000092105060B20009B1001, dni: A591, endpoint: 01, cluster: FCC0, size: 82, attrId: 00F7, encoding: 41, command: 0A, value: 3D64100103282098390000000095398D2E0E40963900800945973900000000052104009A20100821160107270000000000000000092105060B20009B1001 | msgMap:[raw:A59101FCC082F700413D64100103282098390000000095398D2E0E40963900800945973900000000052104009A20100821160107270000000000000000092105060B20009B1001, dni:A591, endpoint:01, cluster:FCC0, size:82, attrId:00F7, encoding:41, command:0A, value:64100103282098390000000095398D2E0E40963900800945973900000000052104009A20100821160107270000000000000000092105060B20009B1001, clusterInt:64704, attrInt:247]

"Markus, I just tried out the AutoDiscover feature. It worked in that it found the 5 unassigned devices that I had. But I was surprised that after I had installed my first device that it did not lead me back to the other 4 devices in the AutoDiscover list. Meaning I would have to repeat the AutoDiscover process for each single device I installed.

If someone has been able to convert a device to Tasmota then they almost certainly know it's IP address. To me the primary advantage of AutoDiscover (I thought) would have been adding multiple devices in one run through."

Solution
I think in the screenshot to the right having two options.
Next Device and Quit AutoDiscovery or something like that.

This can be done, the results are not perfect, but not bad. Not a high priority right now though.

The listing of devices in Configure Devices screen shows the Tasmota version on each device. However it does not distinguish between the standard Tasmota and Tasmota for Hubitat versions. I see the screen being the easiest way to review the firmware version across devices and this is an important distinction that would make it easier to migrate from standard Tasmota to Tasmota for HE.

I have the Tuya Alarm/Siren in question and noticed that in hubitat it's not possible to "run custom command" against the siren with the driver because it's missing the "actuator" capability.

I did a quick test and adding the:
capability "Actuator"
and it did the trick.

Also, is it possible to add a list of all the sounds to the driver?
1: Doorbell 1
2: Fur Elise
3: Westminster
4: 4 Key Chime
5: William Tell
6: Mozart Piano
7: Space Alarm
8: Klaxon
9: meep meep
10: Wheep
11: Dogs
12: Alarm Siren
13: Doorbell 2
14: Old Phone
15: Police Siren
16: 4 beep 1 clang
17: 4 beep increasing volume
18: Psycho Siren

I just got my Hubitat yesterday and worked all day today trying to set it up. In Smartthings, I was able to use the Tasmota-connect (tasmota-hubitat-8.1.0.bin) on my wemos D1 mini boards. I used hongtat device drivers and app he made for smartthings and I was able to get smartthings to see both switches. In Hubitat, I can't figure out what driver and app I need for it to see two switches. For example, I have one switch that uses GPIO5 - relay 1, GPIO12-Relay2 and a couple of other pins for my buttons to manually turn on the lights. So My issue is when I find this in Habitat, it only sees the one switch (relay). What am I missing? I thought Hubitat was going to be easier than smartthings. I appreciate any help you can give me.

This is mostly done, there seems to be a bug in Tasmota preventing MQTT publish events when the needed Rules are applied. Still investigating.

• an effect that lets you set colors which it then fades between much like the random color fade only you get to pick the used colors. effect97(color1,color2,color3,...) color 1 would fade into 2 into 3 back into 1
• an effect that lets you pick a single color, fade direction and time over which to execute the fade. Effect98(color,+-time) where +10 would fade up from 0 to 100 over 10 seconds, and - would fade down.
• an effect that lets you pick a single color or string of colors, a time amount, and repeat option. which it then fades through the colors and levels in order from 0 to 100 and back to 0. effect99(color1,color2,15,0) would start color 1 at 0, fade up to 100, fade down to 0, over a total of 15 seconds then would change to color2 at 0 and fade up then back down again over 15 seconds. the light would stop and remain off. effect99(color1,color2,15,1) would repeat once then remain off, and effect99(color1,color2,15,#) would repeat until stopped by changing any light setting.

This is said to work with smartthings but the instructions is Hubitat specific. Are there instructions for the Smartthings hub?

Not sure if this would even be useable

fingerprint model:"LXN59-1S7LX1.0", manufacturer:"3A Smart Home DE", profileId:"0104", endpointId:"01", inClusters:"0000,0003,0004,0005,0006", outClusters:"", application:"01"

https://www.amazon.com/gp/product/B07X87XH9B

Should this be using switch or outlet driver the fingerprint needs to be added

Start with temperature and power, other sensor values probably don't make sense...

Hi. I'm using a bunch of your drivers for my aquara devices (water, temp/humid/press).

I just received my Xiaomi smoke detectors now and I'm using your driver for that as well and it works beautifully it seems.

However, I had to manually install it (as opposed to using the package manager) because it's not listed in your packageManifest.json. Would it be possible to add it there?

This is the one I'm talking about:
https://raw.githubusercontent.com/markus-li/Hubitat/release/drivers/expanded/zigbee-xiaomi-smoke-detector-expanded.groovy

Hi. I'm using a bunch of your drivers for my aquara devices (water, temp/humid/press).

I just received my Xiaomi vibration/tilt sensors now and I'm using your driver for that as well and it works beautifully it seems.

However, I had to manually install it (as opposed to using the package manager) because it's not listed in your packageManifest.json. Would it be possible to add it there?

This is the one I'm talking about:
https://raw.githubusercontent.com/markus-li/Hubitat/release/drivers/expanded/zigbee-aqara-vibration-sensor-expanded.groovy

This is related to issue #26

Specifically Im looking for how to

• set the Hubitat/Smarthings parameters, ip & port
• enable the Hubitat/Smarthings
• enable Hue Bridge emulation

Any chance you could whip up a driver for the KMC 4 Power Monitoring Plug?

https://templates.blakadder.com/kmc-4.html
{"NAME":"KMC 4 Outlet","GPIO":[0,56,0,0,133,132,0,0,130,22,23,21,17],"FLAG":0,"BASE":36}
https://www.amazon.com/dp/B0786B1LGM?tag=blakaddertemp-20

BTW this is amazing! Thank you so much for creating the modified firmware and drivers. My dad accidentally left two of these in the Amazon box he used to ship a care package for my kid... so I got a Christmas gift too!
I fired up Tuya-Convert on an old RPi and flashed regular Tasmota 7.2... then found this thread and was able to downgrade using the console commands posted on the Hubitat Community forums.

There was an issue with my account on the forums which is why I am sending a message on GitHub

need a driver for hubitat
{"NAME":"TL SS01S Swtch","GPIO":[0,0,0,0,52,158,0,0,21,17,0,0,0],"FLAG":0,"BASE":18}