birdslikewires / hubitat Goto Github PK

Since installing the driver I've been getting these presence warnings every 10 minutes.

I also noticed a couple UNKNOWN DATA reports, so reporting to the Dev as requested.
Firmware on the shortcut button is as delivered when purchased.

dev:742021-10-21 09:00:28.028 pm warnShortcut Button : Presence : Waiting for first presence report.

dev:742021-10-21 08:50:36.214 pm warnShortcut Button : Received : cluster: null, clusterId: 0013, attrId: null, command: 00 with value: null and 12 bits of data: [84, F5, 6E, 47, D4, 0D, FE, FF, F9, E3, B4, 80]

dev:742021-10-21 08:50:36.212 pm warnShortcut Button : UNKNOWN DATA! Please report these messages to the developer.

dev:742021-10-21 08:50:28.036 pm warnShortcut Button : Presence : Waiting for first presence report.

dev:742021-10-21 08:40:28.046 pm warnShortcut Button : Presence : Waiting for first presence report.

Data window in Hubitat:

endpointId: 01
application: 46
driver: v1.10 (29th August 2023)
inClusters: 0000,0003,0004,0005,0006
manufacturer: _TZ3000_1obwwnmq
model: TS011F
outClusters: 0019,000A
profileId: 0104

Debug from Hubitat:

dev:7022023-10-13 14:58:34.207errorcom.hubitat.app.exception.UnknownDeviceTypeException: Device type 'Switch' in namespace 'hubitat' not found on line 782 (method parse)
dev:7022023-10-13 14:58:34.198errorcom.hubitat.app.exception.UnknownDeviceTypeException: Device type 'Switch' in namespace 'hubitat' not found on line 782 (method parse)
dev:7022023-10-13 14:58:34.189errorcom.hubitat.app.exception.UnknownDeviceTypeException: Device type 'Switch' in namespace 'hubitat' not found on line 782 (method parse)
dev:7022023-10-13 14:58:34.174errorcom.hubitat.app.exception.UnknownDeviceTypeException: Device type 'Switch' in namespace 'hubitat' not found on line 782 (method parse)
dev:7022023-10-13 14:58:29.750errorcom.hubitat.app.exception.UnknownDeviceTypeException: Device type 'Switch' in namespace 'hubitat' not found on line 782 (method parse)
dev:7022023-10-13 14:58:29.745errorcom.hubitat.app.exception.UnknownDeviceTypeException: Device type 'Switch' in namespace 'hubitat' not found on line 782 (method parse)
dev:7022023-10-13 14:58:29.742errorcom.hubitat.app.exception.UnknownDeviceTypeException: Device type 'Switch' in namespace 'hubitat' not found on line 782 (method parse)
dev:7022023-10-13 14:58:29.712errorcom.hubitat.app.exception.UnknownDeviceTypeException: Device type 'Switch' in namespace 'hubitat' not found on line 782 (method parse)
dev:7022023-10-13 14:56:21.050warnOutlet : Health Status : Last report received 8079 seconds ago.
dev:7022023-10-13 14:54:26.918errorcom.hubitat.app.exception.UnknownDeviceTypeException: Device type 'Switch' in namespace 'hubitat' not found on line 782 (method parse)
dev:7022023-10-13 14:52:21.029warnOutlet : Health Status : Last report received 7839 seconds ago.
dev:7022023-10-13 14:48:21.037warnOutlet : Health Status : Last report received 7599 seconds ago.
dev:7022023-10-13 14:44:21.755errorcom.hubitat.app.exception.UnknownDeviceTypeException: Device type 'Switch' in namespace 'hubitat' not found on line 782 (method parse)
dev:7022023-10-13 14:44:21.029warnOutlet : Health Status : Last report received 7359 seconds ago.
dev:7022023-10-13 14:40:21.032warnOutlet : Health Status : Last report received 7119 seconds ago.
dev:7022023-10-13 14:36:21.052warnOutlet : Health Status : Last report received 6879 seconds ago.
dev:7022023-10-13 14:34:16.638errorcom.hubitat.app.exception.UnknownDeviceTypeException: Device type 'Switch' in namespace 'hubitat' not found on line 782 (method parse)
dev:7022023-10-13 14:32:21.046warnOutlet : Health Status : Last report received 6639 seconds ago.
dev:7022023-10-13 14:28:21.044warnOutlet : Health Status : Last report received 6399 seconds ago.
dev:7022023-10-13 14:24:21.023warnOutlet : Health Status : Last report received 6159 seconds ago.
dev:7022023-10-13 14:24:11.448errorcom.hubitat.app.exception.UnknownDeviceTypeException: Device type 'Switch' in namespace 'hubitat' not found on line 782 (method parse)
dev:7022023-10-13 14:20:21.033warnOutlet : Health Status : Last report received 5919 seconds ago.
dev:7022023-10-13 14:16:21.046warnOutlet : Health Status : Last report received 5679 seconds ago.
dev:7022023-10-13 14:14:06.306errorcom.hubitat.app.exception.UnknownDeviceTypeException: Device type 'Switch' in namespace 'hubitat' not found on line 782 (method parse)
dev:7022023-10-13 14:12:21.027warnOutlet : Health Status : Last report received 5439 seconds ago.
dev:7022023-10-13 14:08:21.043warnOutlet : Health Status : Last report received 5199 seconds ago.
dev:7022023-10-13 14:04:21.025warnOutlet : Health Status : Last report received 4959 seconds ago.
dev:7022023-10-13 14:04:01.180errorcom.hubitat.app.exception.UnknownDeviceTypeException: Device type 'Switch' in namespace 'hubitat' not found on line 782 (method parse)

Hello, just wanted to report the failure on update on hubitat (pkg manager version 2.3.6.146). From the Logs i see this message:

groovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (java.lang.String) values: [https://raw.githubusercontent.com/birdslikewires/hubitat/master/general/libraries/library.zip]
Possible solutions: wait(), chars(), any(), wait(long), split(java.lang.String), any(groovy.lang.Closure) on line 2108 (method performUpdates)

Hello,

I have the Lidl smart extension HG06338 device.
Get this error when I try to install your driver.
library not found on line 14: #include BirdsLikeWires.library

Did a search for the BirdsLikeWires.library but ends up on a 404 page?
Any ideas what is wrong?

Keep up the good work :-)

This custom attribute jumps between values when trying to determine the correct mode, then sometimes gets it wrong.

Search in here for the word "interesting".

https://github.com/jamesleesaunders/PyAlertMe/blob/master/pyalertme/zbnode.py

There are 17 bytes which may contain something in the FE (CLUSTER_CMD_AM_VERSION_RESP) cluster message, but we don't know what they represent. Maybe something, maybe nothing.

Anyone who would like to dig, please do so! :)

As the title suggests, but it's too late early in the evening morning to do anything about it now.

Just for the fun of it, to be honest.

Im trying to send the state to the iris v1 keypad. Im running into trouble formatting the command
Using your code I have been able to decode and act on all the info it sends to Receive PINS and arm
What I need to figure out the chime and arm commands so the lights will work right.

Not sure if you have seen this source code links bellow.
It says to send the command on the same cluster as data is received which is 00C0
sendZigbeeCommands(["he raw ${device.deviceNetworkId} 0 ${device.endpointId} 0x00C0 02 {11 00 01 01 01} {0xC216}"])
sends Cluster:00C0 command:01 MAP:[01, 00, 86] back to me
{11 10 00 00 01} sends back Cluster:00C0 command:01 [00, 01, 00, 18, 00, 00, 01, 00, 18, 00]

Cluster:00C0 command:00 MAP:[20, 00] Gets resent over and over I suspect 20 is mode and 0 is off.

Can you offer any help on formatting the command to send to the pad. I noticed you dont have cluster 00C0 in any of your docs.

https://github.com/arcus-smart-home/arcusplatform/blob/a02ad0e9274896806b7d0108ee3644396f3780ad/platform/arcus-containers/driver-services/src/main/resources/ZB_AlertMe_KeyPad_2_4.driver

https://github.com/arcus-smart-home/arcusplatform/blob/a02ad0e9274896806b7d0108ee3644396f3780ad/agent/arcus-reflex-controller/src/main/java/com/iris/agent/reflex/drivers/AlertmeKeyPad.java

https://github.com/arcus-smart-home/arcusplatform/blob/a02ad0e9274896806b7d0108ee3644396f3780ad/common/arcus-protocol/src/main/irp/ame-general.irp

Needs investigating with a momentary switch and the three module types. Command "0A" should be received only when actuated locally, with command "0B" being the receipt of remote command message. Some SM308 and SM308-S modules send both, while I've not seen this behaviour on the SM308-2CH, yet.

Sorry to bother you. I have an issue with updateting the "Ikea symfonisk and tradfri driver". Getting this error when I try to update:

"An error occurred while installing the package: Failed to upgrade driver https://raw.githubusercontent.com/birdslikewires/hubitat/master/ikea/drivers/ikea_tradfri_shortcut_button_e1812.groovy."

If I remove the dot at the end I find the code copies it and put it in as drivercode.

Please advise

Regards
Kim

https://raw.githubusercontent.com/birdslikewires/hubitat/master/xiaomi/packageManifest.json has 4 drivers, missing the 5th.

If I install manually via https://raw.githubusercontent.com/birdslikewires/hubitat/master/xiaomi/drivers/xiaomi_aqara_cube_controller.groovy, I get:

The method public void push(java.lang.Object buttonId) { ... } duplicates another method of the same signature .
At [330:1] @ line 330 (library BirdsLikeWires.library, line 86), column 1. Repetitive method name/signature for method
'void push(java.lang.Object)' in class 'Script1'. @ line 78, column 1. Repetitive method name/signature for method
'void push(java.lang.Object)' in class 'Script1'. @ line 330 (library BirdsLikeWires.library, line 86), column 1.

HPM 1.8.8

Using most recent feb update, I can get clockwise start/continue/stop, ccw same.

I can never get (hubitat) status 'released' for button 1, and triple tap 'held' doesn't show up in the commands or state variables.

example of single, double, then triple tap.

no 'held' mode to speak of.

Thank you again for this awesome driver! I'm too nub to decipher where it could go wrong.

Total aside: They're not doing something dumb like sending the ascii of the battery level are they?

Have been getting this error for months now when trying to update. Thought it would get caught sooner but apparently I'm the only one using these devices lol.

Error Occurred During Installation
An error occurred while installing the package: Failed to upgrade driver https://raw.githubusercontent.com/birdslikewires/hubitat/master/xiaomi/drivers/xiaomi_aqara_temperature_humidity_sensor_wsdcgq11lm.groovy.

Sometimes, following battery replacement, security devices (Alarm, Contact and Motion) request IAS enrolment and utility devices (Button, Key Fob, Lamp, Power Clamp, SmartPlug) send match descriptor requests on cluster 0006. These drivers do not currently respond to these requests, which leaves the device in limbo, repeatedly sending requests that are never answered. It would appear that even the official Hubitat Iris V1 drivers skip messages on cluster 0006 at the moment.

As a result, a simple battery replacement can lead to non-functioning devices which require a reset and re-join (at minimum).

At the moment this is implemented in a deprecated way with a custom command, but it should use capability "Flash".

Could you add/develop drivers for the WS-USC02 switch?