Zigbee flower and plant sensors for soil moisture + light + temperature + humidity?

reven · November 23, 2021, 5:38am

I’ve built one sensor (got pcbs made) and it binds to zha but only reports battery and temperature. I don’t want to switch to z2m, so I guess I’m stuck for now.

Hedda · November 23, 2021, 8:12am

Guessing from issue you posted to zha-device-handlers that you figured out will need new quirks for it:

https://github.com/zigpy/zha-device-handlers/issues/1171

github.com/zigpy/zha-device-handlers

[Device Support Request] EFEKTA Plant-Watering-Sensor-Zigbee

opened 06:05AM - 23 Nov 21 UTC

reven

Name: efektalab.ru EFEKTA_PWS. Custom DIY device. Pairs and appears in ZHA but …fails to report soil moisture. Reported temperature and battery level are incorrect. Info and source: https://github.com/smartboxchannel/Plant-Watering-Sensor-Zigbee **Device signature - this can be acquired by removing the device from ZHA and pairing it again from the add devices screen. Be sure to add the entire content of the log panel after pairing the device to a code block below this line.** ``` Sent 'mgmt_permit_joining_req' to 00:0d:6f:ff:fe:8e:7b:59: [<Status.SUCCESS: 0>] [0xe213] Delivery error for seq # 0x72, on endpoint id 0 cluster 0x0034: message send failure Sending 'zdo_leave_req' failed: [0xe213:0:0x0034]: Message send failure Device 0xe213 (00:12:4b:00:24:42:d3:d2) left the network Device 0xe213 (00:12:4b:00:24:42:d3:d2) left the network New device 0xbf06 (00:12:4b:00:24:42:d3:d2) joined the network [0xbf06] Scheduling initialization Tries remaining: 3 [0xbf06] Requesting 'Node Descriptor' Tries remaining: 2 [0xbf06] Extending timeout for 0x76 request Device 0xbf06 (00:12:4b:00:24:42:d3:d2) joined the network [0xbf06] Scheduling initialization [0xbf06] Canceling old initialize call Tries remaining: 3 [0xbf06] Requesting 'Node Descriptor' Tries remaining: 2 [0xbf06] Extending timeout for 0x78 request Device 0xbf06 (00:12:4b:00:24:42:d3:d2) joined the network [0xbf06] Scheduling initialization [0xbf06] Canceling old initialize call Received frame on uninitialized device <Device model=None manuf=None nwk=0xBF06 ieee=00:12:4b:00:24:42:d3:d2 is_initialized=False> from ep 0 to ep 0, cluster 19: b'\x00\x06\xbf\xd2\xd3B$\x00K\x12\x00\x80' [0xbf06:zdo] ZDO request ZDOCmd.Device_annce: [0xBF06, 00:12:4b:00:24:42:d3:d2, 128] Tries remaining: 3 [0xbf06] Requesting 'Node Descriptor' Tries remaining: 2 [0xbf06] Extending timeout for 0x7a request Received frame on uninitialized device <Device model=None manuf=None nwk=0xBF06 ieee=00:12:4b:00:24:42:d3:d2 is_initialized=False> from ep 0 to ep 0, cluster 54: b'\x02\xb4\x01' [0xbf06:zdo] ZDO request ZDOCmd.Mgmt_Permit_Joining_req: [180, <Bool.true: 1>] Received frame on uninitialized device <Device model=None manuf=None nwk=0xBF06 ieee=00:12:4b:00:24:42:d3:d2 is_initialized=False> from ep 1 to ep 255, cluster 3: b'\x11\x01\x01' [0xbf06] Received ZCL while uninitialized on endpoint id 1, cluster 0x0003 id, hdr: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=False disable_default_response=True> manufacturer=None tsn=1 command_id=1>, payload: b'' Received frame on uninitialized device <Device model=None manuf=None nwk=0xBF06 ieee=00:12:4b:00:24:42:d3:d2 is_initialized=False> from ep 0 to ep 0, cluster 32770: b'x\x00\x06\xbf\x02@\x80\x00\x00P\xa0\x00\x00\x00\xa0\x00\x00' [0xbf06:zdo] ZDO request ZDOCmd.Node_Desc_rsp: [<Status.SUCCESS: 0>, 0xBF06, NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=0, maximum_buffer_size=80, maximum_incoming_transfer_size=160, server_mask=0, maximum_outgoing_transfer_size=160, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)] [0xbf06:zdo] Unsupported ZDO request:ZDOCmd.Node_Desc_rsp Received frame on uninitialized device <Device model=None manuf=None nwk=0xBF06 ieee=00:12:4b:00:24:42:d3:d2 is_initialized=False> from ep 0 to ep 0, cluster 32770: b'z\x00\x06\xbf\x02@\x80\x00\x00P\xa0\x00\x00\x00\xa0\x00\x00' [0xbf06] Got Node Descriptor: NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=0, maximum_buffer_size=80, maximum_incoming_transfer_size=160, server_mask=0, maximum_outgoing_transfer_size=160, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False) [0xbf06] Discovering endpoints Tries remaining: 3 [0xbf06] Extending timeout for 0x7c request Received frame on uninitialized device <Device model=None manuf=None nwk=0xBF06 ieee=00:12:4b:00:24:42:d3:d2 is_initialized=False> from ep 0 to ep 0, cluster 32773: b'|\x00\x06\xbf\x01\x01' [0xbf06] Discovered endpoints: [1] [0xbf06] Initializing endpoints [<Endpoint id=1 in=[] out=[] status=<Status.NEW: 0>>] [0xbf06:1] Discovering endpoint information Tries remaining: 3 [0xbf06] Extending timeout for 0x7e request Received frame on uninitialized device <Device model=None manuf=None nwk=0xBF06 ieee=00:12:4b:00:24:42:d3:d2 is_initialized=False> from ep 0 to ep 0, cluster 32772: b'~\x00\x06\xbf\x10\x01\x04\x01\x0c\x00\x02\x04\x00\x00\x01\x00\x02\x04\x08\x04\x00' [0xe9c7:zdo] ZDO request ZDOCmd.NWK_addr_req: [00:0d:6f:00:15:44:ef:91, 0, 0] [0xbf06:1] Discovered endpoint information: SizePrefixedSimpleDescriptor(endpoint=1, profile=260, device_type=12, device_version=2, input_clusters=[0, 1, 1026, 1032], output_clusters=[]) Unknown cluster 1032 [0xbf06] Extending timeout for 0x81 request [0xbf06:1:0x0000] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=129 command_id=Command.Read_Attributes_rsp> [0xbf06] Read model 'EFEKTA_PWS' and manufacturer 'efektalab.ru' from <Endpoint id=1 in=[basic:0x0000, power:0x0001, temperature:0x0402, None:0x0408] out=[] status=<Status.ZDO_INIT: 1>> [0xbf06] Discovered basic device information for <Device model='EFEKTA_PWS' manuf='efektalab.ru' nwk=0xBF06 ieee=00:12:4b:00:24:42:d3:d2 is_initialized=True> Device is initialized <Device model='EFEKTA_PWS' manuf='efektalab.ru' nwk=0xBF06 ieee=00:12:4b:00:24:42:d3:d2 is_initialized=True> Checking quirks for efektalab.ru EFEKTA_PWS (00:12:4b:00:24:42:d3:d2) Considering <class 'zhaquirks.xbee.xbee_io.XBeeSensor'> Fail because endpoint list mismatch: {232, 230} {1} Considering <class 'zhaquirks.xbee.xbee3_io.XBee3Sensor'> Fail because endpoint list mismatch: {232, 230} {1} Considering <class 'zhaquirks.smartthings.tag_v4.SmartThingsTagV4'> Fail because input cluster mismatch on at least one endpoint Considering <class 'zhaquirks.smartthings.multi.SmartthingsMultiPurposeSensor'> Fail because device_type mismatch on at least one endpoint Considering <class 'zhaquirks.netvox.z308e3ed.Z308E3ED'> Fail because device_type mismatch on at least one endpoint Considering <class 'zhaquirks.gledopto.soposhgu10.SoposhGU10'> Fail because endpoint list mismatch: {11, 13} {1} Considering <class 'bellows.zigbee.application.EZSPCoordinator'> Fail because device_type mismatch on at least one endpoint device - 0xBF06:00:12:4b:00:24:42:d3:d2 entering async_device_initialized - is_new_join: True device - 0xBF06:00:12:4b:00:24:42:d3:d2 has joined the ZHA zigbee network [0xBF06](EFEKTA_PWS): started configuration [0xBF06:ZDO](EFEKTA_PWS): 'async_configure' stage succeeded Error handling '_save_attribute' event with (00:12:4b:00:24:42:d3:d2, 1, 0, 4, 'efektalab.ru') params: FOREIGN KEY constraint failed [0xbf06] Extending timeout for 0x83 request [0xbf06] Extending timeout for 0x85 request [0xBF06:1:0x0000]: finished channel configuration Error handling '_save_attribute' event with (00:12:4b:00:24:42:d3:d2, 1, 0, 5, 'EFEKTA_PWS') params: FOREIGN KEY constraint failed [0xBF06:1:0x0001]: bound 'power' cluster: Status.SUCCESS [0xbf06] Extending timeout for 0x87 request [0xBF06:1:0x0402]: bound 'temperature' cluster: Status.SUCCESS [0xbf06] Extending timeout for 0x89 request [0xbf06:1:0x0001] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=135 command_id=Command.Configure_Reporting_rsp> [0xBF06:1:0x0001]: Successfully configured reporting for '{'battery_voltage': (3600, 10800, 1), 'battery_percentage_remaining': (3600, 10800, 1)}' on 'power' cluster: [ConfigureReportingResponseRecord(status=0)] [0xBF06:1:0x0001]: finished channel configuration [0xbf06:1:0x0402] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=137 command_id=Command.Configure_Reporting_rsp> [0xBF06:1:0x0402]: Successfully configured reporting for '{'measured_value': (30, 900, 50)}' on 'temperature' cluster: [ConfigureReportingResponseRecord(status=0)] [0xBF06:1:0x0402]: finished channel configuration [0xBF06:1:0x0001]: 'async_configure' stage succeeded [0xBF06:1:0x0402]: 'async_configure' stage succeeded [0xBF06:1:0x0000]: 'async_configure' stage succeeded [0xBF06](EFEKTA_PWS): completed configuration [0xBF06](EFEKTA_PWS): stored in registry: ZhaDeviceEntry(name='efektalab.ru EFEKTA_PWS', ieee='00:12:4b:00:24:42:d3:d2', last_seen=1637646370.1822302) [0xBF06](EFEKTA_PWS): started initialization [0xBF06:ZDO](EFEKTA_PWS): 'async_initialize' stage succeeded [0xBF06:1:0x0001]: initializing channel: from_cache: False [0xbf06] Extending timeout for 0x8b request [0xBF06:1:0x0402]: initializing channel: from_cache: False [0xbf06] Extending timeout for 0x8d request [0xBF06:1:0x0000]: initializing channel: from_cache: False [0xBF06:1:0x0000]: finished channel initialization [0xbf06:1:0x0001] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=139 command_id=Command.Read_Attributes_rsp> [0xbf06] Extending timeout for 0x8f request [0xbf06:1:0x0402] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=141 command_id=Command.Read_Attributes_rsp> [0xBF06:1:0x0402]: finished channel initialization [0xbf06:1:0x0001] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=143 command_id=Command.Read_Attributes_rsp> [0xBF06:1:0x0001]: finished channel initialization [0xBF06:1:0x0001]: 'async_initialize' stage succeeded [0xBF06:1:0x0402]: 'async_initialize' stage succeeded [0xBF06:1:0x0000]: 'async_initialize' stage succeeded [0xBF06](EFEKTA_PWS): power source: Battery or Unknown [0xBF06](EFEKTA_PWS): completed initialization Ignoring message (b'110201') on cluster 3: unknown endpoint or cluster id: 'No cluster ID 0x0003 on (00:12:4b:00:24:42:d3:d2, 1)' [0x8012:1:0x0300] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=11 command_id=Command.Report_Attributes> [0x8012:1:0x0300] ZCL request 0x000a: [[Attribute(attrid=3, value=<TypeValue type=uint16_t, value=30138>), Attribute(attrid=4, value=<TypeValue type=uint16_t, value=26909>), Attribute(attrid=7, value=<TypeValue type=uint16_t, value=394>)]] [0x8012:1:0x0300] Attribute report received: current_x=30138, current_y=26909, color_temperature=394 [0xa0da:1:0x0006] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=82 command_id=Command.Report_Attributes> [0xa0da:1:0x0006] ZCL request 0x000a: [[Attribute(attrid=0, value=<TypeValue type=Bool, value=Bool.false>)]] [0xa0da:1:0x0006] Attribute report received: on_off=0 [0x8483:1:0x0006] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=111 command_id=Command.Report_Attributes> [0x8483:1:0x0006] ZCL request 0x000a: [[Attribute(attrid=0, value=<TypeValue type=Bool, value=Bool.false>)]] [0x8483:1:0x0006] Attribute report received: on_off=0 [0x8483:1:0x0008] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=112 command_id=Command.Report_Attributes> [0x8483:1:0x0008] ZCL request 0x000a: [[Attribute(attrid=0, value=<TypeValue type=uint8_t, value=254>)]] [0x8483:1:0x0008] Attribute report received: current_level=254 [0x8483:1:0x0008]: received attribute: 0 update with value: 254 Ignoring message (b'110301') on cluster 3: unknown endpoint or cluster id: 'No cluster ID 0x0003 on (00:12:4b:00:24:42:d3:d2, 1)' Ignoring message (b'110401') on cluster 3: unknown endpoint or cluster id: 'No cluster ID 0x0003 on (00:12:4b:00:24:42:d3:d2, 1)' Ignoring message (b'110501') on cluster 3: unknown endpoint or cluster id: 'No cluster ID 0x0003 on (00:12:4b:00:24:42:d3:d2, 1)' Ignoring message (b'110601') on cluster 3: unknown endpoint or cluster id: 'No cluster ID 0x0003 on (00:12:4b:00:24:42:d3:d2, 1)' Ignoring message (b'110701') on cluster 3: unknown endpoint or cluster id: 'No cluster ID 0x0003 on (00:12:4b:00:24:42:d3:d2, 1)' ``` **Additional context** ![image](https://user-images.githubusercontent.com/206993/142977706-33272d5b-7983-440f-8350-f4b5bea2a246.png)

Hedda · November 23, 2021, 8:31am

FYI, Water Content Measurement clusters for Zigbee Soil Moisture and Leaf Wetness sensors were just added by @majkrzak to ZHA integration component in Home Assistant core dev branch two weeks ago so has not made it into a HA release as of yet, see:

https://github.com/home-assistant/core/pull/59300

github.com/home-assistant/core

Add Water Content Measurement clusters

home-assistant:dev ← majkrzak:zha/add-water-content

opened 06:01PM - 07 Nov 21 UTC

majkrzak

+90 -0

## Proposed change Ads missing Water Content Measurement clusters: Soil Moisture and Leaf Wetness  ## Type of change  - [ ] Dependency upgrade - [ ] Bugfix (non-breaking change which fixes an issue) - [ ] New integration (thank you!) - [x] New feature (which adds functionality to an existing integration) - [ ] Breaking change (fix/feature causing existing functionality to break) - [ ] Code quality improvements to existing code or addition of tests ## Additional information  It requires https://github.com/zigpy/zigpy/pull/844 to be first pulled into the core. The Soil Moisture part was tested with https://github.com/smartboxchannel/Plant-Watering-Sensor-Zigbee, and seems to be working. Leaf Moisture was not tested, but according to the `zcl` specs it should behave in the very same way. I think that I have added new clusters in all the places they are supposed to be. Requires https://github.com/home-assistant/core/pull/59314 to be merged first. ## Checklist  - [x] The code change is tested and works locally. - [x] Local tests pass. **Your PR cannot be merged unless tests pass** - [x] There is no commented out code in this PR. - [x] I have followed the [development checklist][dev-checklist] - [x] The code has been formatted using Black (`black --fast homeassistant tests`) - [ ] Tests have been added to verify that the new code works. If user exposed functionality or configuration variables are added/changed: - [ ] Documentation added/updated for [www.home-assistant.io][docs-repository] If the code communicates with devices, web services, or third-party tools: - [ ] The [manifest file][manifest-docs] has all fields filled out correctly. Updated and included derived files by running: `python3 -m script.hassfest`. - [ ] New or updated dependencies have been added to `requirements_all.txt`. Updated by running `python3 -m script.gen_requirements_all`. - [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description. - [ ] Untested files have been added to `.coveragerc`. The integration reached or maintains the following [Integration Quality Scale][quality-scale]:  - [ ] No score or internal - [ ] 🥈 Silver - [ ] 🥇 Gold - [ ] 🏆 Platinum  To help with the load of incoming pull requests: - [ ] I have reviewed two other [open pull requests][prs] in this repository. [prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone  [dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html [manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html [quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html [docs-repository]: https://github.com/home-assistant/home-assistant.io

reven · November 24, 2021, 2:59am

That’s amazing news. I thought I would try to give the quirks a go myself, but it’s way above my level. I hadn’t even figured out that clusters needed to be implemented at the integration level.

Hedda · November 24, 2021, 12:36pm

To clarify so that there is no confustiuon; the above PR for “Add Water Content Measurement clusters” does not add any quirks for specific devices, it only adds support the missing device classes in ZHA. Once that is available in ZHA you may still sometimes need a custom quirk in “ZHA Device Handlers” for individual devices if they don’t follow the standard Zigbee Cluster Library specification, see https://www.home-assistant.io/integrations/zha/#zha-exception-and-deviation-handling

reven · November 24, 2021, 8:49pm

Yup, I understood that. My point was that I was trying to understand how quirk files worked when the support for that cluster wasn’t even there yet.

robertalexa · November 29, 2021, 3:04pm

I have built 20 of the DIYRUZ Flow for my wife. Based on the V3 including temperature sensor, 3D printed the frame case and added acrylic sheet to the front to protect the circuit from being touched. They are flashed with the most recent version at this time 2.1.0 and work perfectly fine with zigbee2mqtt

Unfortunately they have not passed the wife test (yeah… she prefers the 1 single miflora that she has, with terrible bluetooth range), so now I am kinda stuck with them. If anyone is interested in buying some pre-made ones, drop me a private message. I am based in the UK.

PS: just to clarify, i do not build them for profit, nor will I build any if asked. I just want to recoup some of the cost I had in building them. Of course if interested I can send pictures of them

PPS: I do not mean to spam anyone or commercialise or hijack this thread whatsoever. It is only that this thread was a big starting point for me when i looked for alternatives to the miflora, and I guess there might be others out there trying to achieve the same. I would hate to have these devices stuck in a drawer forever, or to throw them in the bin, if someone else can make use of them

LE: items are not available anymore

reinierh · December 3, 2021, 2:32pm

This sounds interesting. Can it be used outside? (is it fully waterproof?)
At the moment i use (old) gardena stuff. But i am busy changing this to a sonoff with a 24v valve. And need a few moisture sensors

robertalexa · December 3, 2021, 2:37pm

If the question was aimed at me, then no, my ones are not fully water proof. Splash resistant at best. In my use case they were meant for house plants (hence not passing the wife test haha). I would however say they would work in a greenhouse. I am not concerned about temperature, but rather the device getting wet.

AndrejDelany · December 3, 2021, 4:33pm

@horussjr I did send you a private message a few days ago, seems like you overlooked it. Please check

robertalexa · December 3, 2021, 6:01pm

The items are all gone. I hope they will do good in their new homes.

Thank you @AndrejDelany and @p71 and i hope you will enjoy them.

smartboxchannel · December 5, 2021, 4:43pm

PLZ try HEX Plant-Watering-Sensor-Zigbee/PROJECT SOURCE at main · smartboxchannel/Plant-Watering-Sensor-Zigbee · GitHub

smartboxchannel · December 5, 2021, 4:44pm

Efekta PWS/MiniPWS ZHA compatible

smartboxchannel · December 5, 2021, 4:48pm

Hedda · December 6, 2021, 10:24am

Update: Water Content Measurement clusters support for Soil Moisture (and Leaf Wetness) which was only available in HA Beta is set to come in Home Assistant 2021.12 to be released in less than a week:

https://rc.home-assistant.io/blog/2021/12/03/release-202112/

reven · December 19, 2021, 7:32am

@smartboxchannel Andrew, I’ve finally had a chance to test the new firmware. But unfortunately I still have the same issue: humidity and temperature reported varies wildly from one device to the next, so values seem quite unreliable.

smartboxchannel · December 20, 2021, 8:40am

Soil moisture values may differ on two sensors placed in the same flower pot, as soon as you stick them in the ground, wait a day until the soil around the sensors acquires the same structure. But as for the temperature data, there is a problem in measuring the internal temperature of the chip, the cc2530 has very conditional measurements of the internal temperature, I added this data simply because they could simply be obtained using a code. A new modification of the sensor with an external digital temperature and humidity sensor, as well as a digital light sensor, is already available.

smartboxchannel · December 20, 2021, 8:41am

photo_2021-12-12_21-28-331280×720 53.5 KB

Hedda · December 20, 2021, 8:49am

@smartboxchannel Any ideas about redesigning the board to make it physically smaller, i.e. less wide?

I believe it would raise the WAF (Wife Appeal Factor) a lot if could make “the head” of the board thinner.

As mentioned before, the Xiaomi Mi Flora is the major competition based solely on its slimmer design:

rindlerblabla · December 20, 2021, 4:27pm

There’s is also this mini version Mini Plant Watering Sensor EFEKTA (Zigbee) from Efektalab on Tindie. Don’t know about actual measurements though.