Hub Firmware Beta 45.6

No, that just means the code has been accepted into the main repository. It next needs to be pulled across to the beta repository and deployed into the beta channel from there, and there is a similar process for production. When I was waiting for fixes for the Sonoff button a couple of times it was taking up to two weeks from initial acceptance to hitting the beta channel.

2 Likes

I hoped to have solved the disconnection problems, instead I see from IDE a disconnected switch while from App still not, but I’m sure it will happen soon in fact it does not work from App.

I looked at the hub messages and noticed these multiple Trani error messages. Can anyone help me understand what they are?


I do not know if the problem is related to this firmware

Ps after 2 hours: The lamp came back online without ever going offline from the App (only to the ide) , so it was only a temporary problem, but I still have doubts about what the hub was doing.

The IKEA dimmer buttons are registering button pressed again after removing and re-adding. Now if the IKEA motion sensors would register motion I’d be all set. Thanks for the guidance!

This pull request may resolve the issue of IKEA motion sensors not reporting motion.

1 Like

Thank you for the update and sorry, I’m not a developer so I’m just guessing here but github says Review required, 2 of 8 tests failed, Merging is blocked which means this hasn’t been implemented yet?
If correct, will you let us know when the fix is pushed out so I don’t have to keep deleting and re-adding the device please?

2 Likes

Once a PR gets merged, it goes to the beta channel on the Tuesday following the merge. Then it will go to production on the Tuesday after that. So Nov 1st is probably the earliest it will get released.

1 Like

When will 45.X Lua libraries be released?

1 Like

Hi, @philh30!
I already mentioned this to the team, we’ll keep you updated. Just as a reference, the update to v45 just finished last Friday for all users.

@philh30, the libraries for v45 are now live:

6 Likes

It seems that with the 45.x libraries now can already create EDGE child devices and there are libraries to handle them.
They have also published in the smartthings beta channel the drivers for zooz-zen-30-dimmer-relay, zwave-dual-switch (fibaro Walli double switch) and qubino-flush-2-relay with child devices

4 Likes

Firmware 0.45.11 is rolling out now. Here are the release notes:

  • Fixed a bug where ZigBee is stuck in an offline state until the hub is rebooted
  • Resolved a known issue where customers with Sonos devices were experiencing frequent Hub reboots
  • Set the default reportable change for Zigbee Power Meter devices to 5 instead of 1 to reduce event noise
6 Likes

Is there an integration with Sonos that will still function once Groovy is shutdown?

They are moving Sonos to an Edge driver

Reposting this here for your reference:

1 Like

@nayelyz
Thanks for the information.
The only way to see if they work well is to use them for debugging.
They will surely be polished and modified.

What I have seen both in these EDGE child devices and in the LAN child devices that I have used in my drivers, is that the child devices do not appear in the Hub as connected devices.
Does this mean that they only count as 1 device as they depend on another existing parent device?

Do you mean they don’t appear in the Hub’s detail page of the app?
They should count as separate devices even though they depend on another one but let me check with the team, but we need more reference about where you checked the “connected devices”

Yes, in App Hub detail view

I wouldn’t expect them to appear in the detail view of the hub as they aren’t the hub’s children.

Indeed, they are grandchildren of the Hub according to the API
Normally, for grandparents, grandchildren are the most important thing in the family. :grinning:

The child devices have the physical device as their parent device.
Child device has the Hub.id defined

    "deviceId": "4d311824-5fd6-4eb0-a52a-89b1ef5fecd6", ### Child device

    "parentDeviceId": "688e24be-a9cc-4d9f-a7ea-8ce05ecf701b", ### Parent device
    "profile": {
        "id": "53e0732a-e02e-3ac5-89a0-"
    },
    "lan": {
        "networkId": "switch31663695626",
        "driverId": "540ae948-6fcc-4137-809c-875c3e186071",
        "executingLocally": true,
        "hubId": "d6c3122b-1c8bxxxxxxxxxxx", ### HUB
        "provisioningState": "DRIVER_SWITCH"
    },
    "type": "LAN",

Physical devices have the Hub as parent device. This may be the difference so that they are displayed in the Hub
From the parent device hang all the child devices

   "deviceId": "688e24be-a9cc-4d9f-a7ea-8ce05ecf701b", ### Parent device

    "parentDeviceId": "d6c3122b-1c8b-xxxxxxxxxxxx", ### HUB
    "childDevices": [
        {
            "deviceId": "2811cb2c-ae76-49b6-88b8-f327bce81ac4",
            "profile": {},
            "allowed": []
        },
        {
            "deviceId": "4d311824-5fd6-4eb0-a52a-89b1ef5fecd6", ### Child device
            "profile": {},
            "allowed": []
        },
        {
            "deviceId": "8e680471-fa6f-4cc5-81d9-c835f4974429",
            "profile": {},
            "allowed": []
        }
    ],
    "profile": {
        "id": "8e481832-11ad-3c14-bce2-c19e8e7aba61"
    },
    "zigbee": {
        "eui": "EC1BBDFFFEA87FAC",
        "networkId": "3C41",
        "driverId": "540ae948-6fcc-4137-809c-875c3e186071",
        "executingLocally": true,
        "hubId": "d6c3122b-1c8b-xxxxxxxxxxxx", ### HUB
        "provisioningState": "DRIVER_SWITCH"
    },
    "type": "ZIGBEE",

With the child devices developed in the stock drivers, if they count as one more device, it is a bad deal for some, since the parent device now only shows the main component and therefore from having 1 multiple device now have two by obligation, just like if make a virtual devices.

If they had made it optional, whoever does not need child devices would only have 1 multiple device.

But we can not have everything!

1 Like

I’d rather they had just fixed the problem which to me was in the UI and in the connector apps. There is no fundamental reason for there to only be one dashboard tile for a device, and no reason for third party integrations to ignore components.

3 Likes