CliveS wrote:siclark wrote:Yes I have to flash the old controller devices with router firmware.
Have you bought another zigazigah stick?
No, I am waiting for the zzz-p to be released, hopefully with router firmware.
UPDATE 1 Feb 2021
Just received an email about new Firmware and now includes a router firmware for the CC2652R1.17.1
@Koenkk Koenkk released this 5 hours ago
Notes
New firmwares are available for:
Texas Instruments CC2530/CC2531: 20201127 (default) and 20201128 (default) (changelog).
Texas Instruments CC2652R, CC2652RB, CC1352P-2
Coordinator: 20210120 (changelog)
Router: 20210128 (changelog)
The report feature (report: true) is now deprecated. This feature was mostly used for getting state changes of bound devices. With this release Zigbee2MQTT will automatically setup reporting when binding devices. It is also possible to configure reporting per device via zigbee2mqtt/bridge/request/device/configure_reporting or via the frontend. To migrate away from this feature remove report: true from your configuration.yaml and rebind your bound devices. Alternatively it's fine to keep report: true until this feature is fully removed, even after removal of the report feature the reportings will stay configured.
siclark wrote:autolog wrote:I am currently experimenting using a Hubitat Elevation (HE) as a Zigbee Controller at the moment. I have two Zigbee networks running: My cc2531 (Zigbee2MQTT) and HE.
The experience I had when the CC2531 went pear-shaped over Christmas and a level of complexity involved with setting up Zigbee2MQTT is what made me interested in Hubitat as it seems easier (even if more expensive).
As mentioned, the setup in HE seems easier but you do have to install some 3rd party specific Zigbee Device drivers. I have got MQTT to work and the HE devices are reflected in Indigo via Joe’s MQTT Shims plugin.
More work to do on HE but it looks promising.
£135 for the HE is a lot for what we need as a controller USB. We would be buying a home automation system to operate as a controller for zigbee? I would be more tempted to use the zig-a-zig-ah in Home Assitant and use the plugin for that than pay for HE.
I dont see the point in HE if we still need Shims. With the new zigbee stick it should be a one time setup and then using the node red interface for zigbee2mqtt it takes 30 seconds to rename a new device.
Ideally we would have indigo auto create the device, but once we have the proper Shims templates setup, it would be no longer to create the indigo device than for a zwave device.
siclark wrote:Thanks Jon. Why do you have 2? .
autolog wrote:I have now got my Hubitat Elevation C7 connected to Indigo via MQTT using a purpose built plugin that I decided to develop. I have been developing and running this "Hubitat" plugin on my development system and have now promoted it to my production system and am now commencing the migration of my Zigbee devices from zigbee2mqtt to my Hubitat Elevation C7.
FlyingDiver wrote:... If you are using the Connector plugin, any feedback on ease of use or missing features?
siclark wrote:Thanks Jon. Why do you have 2?
I’ve now got my zigazigah stick working and I’m impressed. Other than a dodgy aqara temp sensor the zinger mesh is very robust, all devices are talking to each other and lots of direct routes back to the controller.
siclark wrote:I think the issue is with the aqara temperature sensors rather than the protocol or the usb stick. In fact there are a lot of complaints about getting them to work in the hubitat site
I think I’ll try the sonoff one in the same location I’m having trouble with and see if that is better.
On that basis I don’t know what advantage there is to buying an expensive hub.
CliveS wrote:... Now considering the Hubitat C7 if Jon is going to make his plugin available, so many question to ask about that if he does.
Users browsing this forum: No registered users and 12 guests