No one any idea how to get my iCasa remote to work?
(see my post just above this one)
@Gruijter perhaps? 
I looked into it, but this button is not following normal reporting. Therefore not possible to map. Sorry 
No need to say sorry. Very thankfull that you looked into it! 
My thoughts were such, because I checked at the “supported devices” pages of Zigbee2mqtt, I see a lot of devices using “action_group”.
Isn’t it possible to read "action_group_ from mqtt as well and make it avalable as a variable?
I guess i could do that. Your flows would be complex though, since you need to combine info from 2 variables that are not triggered simultaneous.
I don’t know anything about the Homey app, so just ignore me if I’m talking nonsense, but wouldn’t this work:
WHEN device is turned on
AND action group equals …
THEN
So add a condition card for action_group (or at least a token containing the group the action was sent to, so you can use a regular Logic card to test equality).
1 Like
That would be great…
Is that possible, @Gruijter?
maybe. but lot on my plate now. Hope I dont forget… (or you could create a pull request 
)
I’d be happy to create an issue on Github if that is convenient for you?
I am just no programmer (and not much familiar with Github as well) unfortunately…
v2.8.3 ready for testing: Zigbee2MQTT | Homey
- Added Air Quality sensor icon.
- Added sending payload to groups.
- Added bridge reset button.
- Added action_group.
Thx @daniel3 for your code contributions!
@Henk_Renting please test action group.
2 Likes
I had recently a situation where my SLZB-06 coordinator started having buffer full issues resulting in that it didn’t report anything to Zigbee2MQTT server.
Now I didn’t check, if there is any MQTT messages, but was wondering if the bridge card ’Msgs/minute became less than’ could have been used to trigger on such event?
This would help in triggering a power cycle the coordinator (restart was not enough).
Just try. You can see in Insights what msgs/minute was doing during the issue.
1 Like
Thanks for the hint on insights. Msgs/minute 123 at the time of event. Which looks like a floor value for the past week anyway. Will need to do some monitoring on that.
There is a zigbee dev firmware update for SLZB to address the buffer full problem, but that version may require to re-pair all 84 devices. Need to wait for a stable version for that.
1 Like
That is a lot of messages by the way. What is your log level set at. Level ‘Info’ should give the best results.
Have log level at info.
Looks like the Moes thermostats are spamming quite a bit.
1 Like
Added debounce to the thermostats and msgs/minute is down to ~75.
1 Like
Any chance to get Z2M scene support in a further release.
Some background why I am looking forward to it.
I moved all my Hue Lamps to Z2M and use Biforst as Hue Emulator GitHub - chrivers/bifrost: Hue Bridge Emulator
The Hue App is still my primary frontend. With Bifrost as Hue emulator I have support for all original features (including effects, entertainment area in testing, just Dynamic Scenes need to be implemented) without a hue bridge in background. Everything is done through Biforst and Z2M
Creating a Group/ Room scene in the Hue App (including the originals of the app) they are written in z2m scenes of the group/room. This makes the original Hue scenes universally available through z2m
So it would be great if the Hue Scenes can be used in Homey, too via Z2M Scenes. This will eliminate the need of the Homey Hue (API) App but will include all features of it within the flows
Since the last update you’re able to set payloads in groups. That way you can also store and recall scenes using the following payload:
{“scene_recall”: 100}
{“scene_store”: 100}
The number e.g. 100 in this case is the number of the scene you want to either store or recall. If you want to store a scene with a number that doesn’t exists, it creates a scene with that number.
I hope this helps 
2 Likes
Thanks. Great
1 Like
