“no Zigbee2MQTT bridge found“ is triggered because the default topic is wrong.
In the input field it states “defaults to zigbee2mqtt” however I had to enter “zigbee2mqtt“ manually in order to connect.
my topic is all lowercase, maybe the code states MQTT with capitals?
For the Aqara FP300, do you think it would be possible to also expose Motion and Presence to Homey?
In Zigbee2MQTT, the device exposes “Presence” and “PIR Detection” separately:
However, in Homey we only get one value, which seems to be linked to “PIR Detection”:
Probably. See first post how you can help get devices/ capabilities supported: [APP][PRO] Zigbee2MQTT
I’d really love to and I have done so in the past before ordering a sensor for you. But somehow right now, I am to stupid to find your instructions in the first post which I need to get the info to you.
Will check again later today.
Is this what you are looking for? If you think you need physical access to the device let me know your local price, then we can come up with a deal, just like we did before 
{
“absence_delay_timer”: 30,
“ai_interference_source_selfidentification”: “ON”,
“ai_sensitivity_adaptive”: “ON”,
“battery”: 100,
“detection_range”: 16777215,
“detection_range_composite”: {
“detection_range_0”: true,
“detection_range_1”: true,
“detection_range_10”: true,
“detection_range_11”: true,
“detection_range_12”: true,
“detection_range_13”: true,
“detection_range_14”: true,
“detection_range_15”: true,
“detection_range_16”: true,
“detection_range_17”: true,
“detection_range_18”: true,
“detection_range_19”: true,
“detection_range_2”: true,
“detection_range_20”: true,
“detection_range_21”: true,
“detection_range_22”: true,
“detection_range_23”: true,
“detection_range_3”: true,
“detection_range_4”: true,
“detection_range_5”: true,
“detection_range_6”: true,
“detection_range_7”: true,
“detection_range_8”: true,
“detection_range_9”: true
},
“detection_range_prefix”: 768,
“humidity”: 50.9,
“humidity_report_mode”: “threshold and interval”,
“humidity_reporting_interval”: 3600,
“humidity_reporting_threshold”: 5,
“illuminance”: 19,
“led_disabled_night”: false,
“light_report_mode”: “threshold and interval”,
“light_reporting_interval”: 3600,
“light_reporting_threshold”: 15,
“light_sampling”: “low”,
“light_sampling_period”: 60,
“linkquality”: 168,
“motion_sensitivity”: “high”,
“pir_detection”: false,
“pir_detection_interval”: 30,
“power_outage_count”: 4,
“presence”: false,
“presence_detection_options”: “both”,
“schedule_end_time”: “09:00”,
“schedule_start_time”: “21:00”,
“schedule_time_raw”: 589845,
“target_distance”: 0,
“temp_&humidity_sampling": “low”,
"temp&_humidity_sampling_period”: 600,
“temp_reporting_interval”: 3600,
“temp_reporting_mode”: “threshold and interval”,
“temp_reporting_threshold”: 0.5,
“temperature”: 20.22,
“update”: {
“state”: “scheduled”
},
“voltage”: 3003
}
I need to use this via Zigbee2MQTT since I use Homey Self-Hosted.
@Gruijter Could you help me provide the info you need?
My bad. This is what happens when someone (me) jumps in without knowing anything about the conversation. Apparently, I could not even be bothered to read the title.
I am not at home right now, but from what I can check remotely it seems to work. I now see both values in the Homey App, and I see the two options in the advanced Flows:
Thank you so much!!! Will do the actual tests at home tonight and report back later this weekend.
1 Like
Hi Robin, thanks again for your great app.
Could you be so kind to add full support for the Aqara W100 thermostat in your app, too.
It is fully compatible in Z2M including the Aqara protocol and you can select devices and their modes, temperatures based on the buttons of the device. Additional there are sensors internal and external that can be used.
I want to use this thermostat for controlling my floor heating (change temperature) and my climate fan/ cooling. These devices are in homey already. Additional I’m using the internal sensors for temperature and humidity and based on homey groups the room temperatures and humidities as external sensors
Based on the middle button I want to change what homey device can be controlled.
Floor heating control and external sensors I have already implemented using mqtt workloads (based on the default z2m implementation) and flows
Thanks for your work
1 Like
v3.1.3 is ready for testing: Zigbee2MQTT | Homey
- Changed system_mode mapping to ENUM.
- Added fan_mode capability mapping and flows
- Added identify capability mapping and flows
- Added thermostat_mode capability mapping and flows
- Added temperature_external capability mapping and flows
- Added humidity_external capability mapping and flows
- Changed onoff uiComponent to button where applicable
@owuerker This should enable all useful capabilities for the W100 thermostat. Please test.
2 Likes
Got a flow alarm from the change.
Until now, the boolean onoff variable I had used. So this was a breaking change.
Bit of a reflowing had to be done. Now fixed and works with the “system_mode” attribute for thermostat.
1 Like
Ah yes, this is indeed a breaking change for people that use the changed onoff in their flows. Thx for testing @OH2TH
edit: mmh. Not so sure now I think about it a bit more. I only changed the UI behavior, not the flow behavior afaik.
Is it possible to dim or brighten the lights smoothly? When I dim the lights via a flow, the change happens abruptly. Ideally, I’d like the lights to transition to the new value over about one second, similar to how this works when adjusting the brightness via the Hue Bridge.
You need to do that somehow using a flow. I think there is an app for smooth transitioning.
Edit: try this one Transitions — Flexible time transitions
Hello @Gruijter thank you for creating this awesome app. I created a new bug on GitHub, could you please review when you have a chance ? I have about 15 covers at home and would love to have this capability exposed. Thanks a lot!
This is not a bug. The device is just not fully mapped in the Homey app. See first post in this thread why this is. You can donate (the funds) of a device, and I will try to implement the extra features.
New version 3.1.4 ready for test: Zigbee2MQTT | Homey
- Added tilt and state support for window coverings
Thx for your donation @cloudpulse_01 ! I added support for your shelly window coverings device. I think besides tilt the state was also not mapped correctly for your device. Both should be working now (without breaking existing State mapping I hope 
)
Please test and let me know 
Works good, thank you!
1 Like
