Ive had a hildebrand stick for a while and didn't know i could get this connected to hubitat.
I have it connected ok using my sticks MAC address and input the correct user and password but on checking the logs its comes back with:
Hildebrand glow : Configuration complete
Hilderbrand glow: Presence:Waiting for first presence report
It doesn't seem to be receiving any data at the child devices?
Have i set this up correctly? You mention above cloud access is required which im not sure i have do i just request this though the hildebrand support?
Cloud access isn't required, in fact local access to the feed from a broker is preferable, but the cloud MQTT feed is there as an option so that folk don't have to go to the hassle of setting it up in the first instance.
I'd suggest dropping them a line, as cloud MQTT is a "by request" feature and it may be their servers can do the work of generating the feed on your GlowStick's behalf.
The method public void updated() { ... } duplicates another method of the same signature . At [461:1] @ line 461 (library BirdsLikeWires.library, line 29), column 1. Repetitive method name/signature for method 'void updated()' in class 'Script1'. @ line 119, column 1. Repetitive method name/signature for method 'void updated()' in class 'Script1'. @ line 461 (library BirdsLikeWires.library, line 29), column 1.
It looks like some sort of clash with the Library.
New to this so wondering if anyone had any ideas to solve the issue and get the Hildebrand drivers working?
Just tried to install your latest update.
Now it errors again with code below. any ideas? Hope its not because of my request to support the export as well
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: user_driver_BirdsLikeWires_Hildebrand_Glow_970.groovy: 419: The method public void installed() { ... } duplicates another method of the same signature . At [419:1] @ line 419, column 1. void installed() { // library marker BirdsLikeWires.library, line 29 ^ user_driver_BirdsLikeWires_Hildebrand_Glow_970.groovy: 60: Repetitive method name/signature for method 'void installed()' in class 'user_driver_BirdsLikeWires_Hildebrand_Glow_970'. @ line 60, column 1. void installed() { ^ user_driver_BirdsLikeWires_Hildebrand_Glow_970.groovy: 346: Repetitive method name/signature for method 'void mqttConnect()' in class 'user_driver_BirdsLikeWires_Hildebrand_Glow_970'. @ line 346, column 1. void mqttConnect() { ^ user_driver_BirdsLikeWires_Hildebrand_Glow_970.groovy: 376: Repetitive method name/signature for method 'void mqttClientStatus(java.lang.String)' in class 'user_driver_BirdsLikeWires_Hildebrand_Glow_970'. @ line 376, column 1. void mqttClientStatus(String status) { ^ user_driver_BirdsLikeWires_Hildebrand_Glow_970.groovy: 419: Repetitive method name/signature for method 'void installed()' in class 'user_driver_BirdsLikeWires_Hildebrand_Glow_970'. @ line 419, column 1. void installed() { // library marker BirdsLikeWires.library, line 29 ^ user_driver_BirdsLikeWires_Hildebrand_Glow_970.groovy: 1083: Repetitive method name/signature for method 'void mqttConnect()' in class 'user_driver_BirdsLikeWires_Hildebrand_Glow_970'. @ line 1083, column 1. void mqttConnect() { // library marker BirdsLikeWires.library, line 693 ^ user_driver_BirdsLikeWires_Hildebrand_Glow_970.groovy: 1114: Repetitive method name/signature for method 'void mqttClientStatus(java.lang.String)' in class 'user_driver_BirdsLikeWires_Hildebrand_Glow_970'. @ line 1114, column 1. void mqttClientStatus(String status) { // library marker BirdsLikeWires.library, line 724 ^ 7 errors (method mqttConnect)
No, this is because I've been updating some of my older drivers, but a combined library of code is a double-edged sword. Let me take a peek, I've basically just left in a method in both the library and the specific driver, or for some reason both parts haven't updated at the same time.
UPDATE: All fixed, it was option one. I've just updated my own system through HPM, so it should be fine now. If the update won't complete (it should) then run HPM's driver repair option and it'll reinstall.
BONUS: Cumulative export has been added to the electricity meter in v1.10. Strictly speaking it's also there in the gas meter too, but I doubt any of us are going to start exporting gas any time soon.
I noticed that the export data doesn't seem to be in the cloud feed. It looks like it's just in the local feed, unless I'm just overlooking something obvious. In all honesty the Zigbee Smart Energy Profile Specification isn't what I fancy reading of an evening, but I'll happily add (or accept a pull request!) from anybody who's prepared to figure out the cluster spec and spell it out to me in words of one syllable.
Always assuming that your meter is reporting correctly and mine isn't. When I had everything on smartlife I compared my usage with the meter and they were 10-11% over actual, the clue was my electric bill going up when extra insulation was fitted.
DON'T trust any meter or bill until you absolutely know its accurate, look up Clive on YouTube on smartmeters as to why.
Oh, and my advice if you're in arrears is to put the account on a standing order, not direct debit, because they will try to steal money out of your account. I was in the middle of 1st stage chemotherapy and got an email telling me they were going to take £2100 out of my account without permission just using the direct debit. THE NEXT DAY. While in dispute about them overcharging me. In this case Shell Energy but other companies are apparently playing the same games.
Great, always like to hear that things are working! Especially for the cloud service, as I don’t use that every day, so it’s always possible for something to break and me not be aware.
This driver now supports the healthStatus custom attribute, so will no longer misuse presence as a means of reporting connectivity to your MQTT broker.
