# Problems with snzb-6p and ihost 1.13.0 **URL:** \ **Category:** eWeLink CUBE\ **Created:** [January 28, 2024, 2:04pm UTC](https://forum.ewelink.cc/t/problems-with-snzb-6p-and-ihost-1-13-0/27749 "2024-01-28T14:04:32Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![sintoxx](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/sintoxx/32/3644_2.png) [@sintoxx](https://forum.ewelink.cc/u/sintoxx)\ **Post date:** [January 28, 2024, 2:04pm UTC](https://forum.ewelink.cc/t/problems-with-snzb-6p-and-ihost-1-13-0/27749/1 "2024-01-28T14:04:32Z")
Since the last ihost update, the snzb-6p sensor with firmware 1.0.6 detects it incorrectly. It takes 15 minutes to indicate that there is no presence, has anyone else noticed a similar problem. ---
**Author:** ![ociepa.ekotox](https://avatars.discourse-cdn.com/v4/letter/o/c68b51/32.png) [@ociepa.ekotox](https://forum.ewelink.cc/u/ociepa.ekotox)\ **Post date:** [January 28, 2024, 2:21pm UTC](https://forum.ewelink.cc/t/problems-with-snzb-6p-and-ihost-1-13-0/27749/2 "2024-01-28T14:21:02Z")
Check the sensor settings to see if the no-motion reporting time has changed. ---
**Author:** ![sintoxx](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/sintoxx/32/3644_2.png) [@sintoxx](https://forum.ewelink.cc/u/sintoxx)\ **Post date:** [January 28, 2024, 2:37pm UTC](https://forum.ewelink.cc/t/problems-with-snzb-6p-and-ihost-1-13-0/27749/3 "2024-01-28T14:37:16Z")
> [@ociepa.ekotox](#): > > Check the sensor settings to see if the no-motion reporting time has changed. It is at 15sg and low detection level ---
**Author:** ![ociepa.ekotox](https://avatars.discourse-cdn.com/v4/letter/o/c68b51/32.png) [@ociepa.ekotox](https://forum.ewelink.cc/u/ociepa.ekotox)\ **Post date:** [January 28, 2024, 2:42pm UTC](https://forum.ewelink.cc/t/problems-with-snzb-6p-and-ihost-1-13-0/27749/4 "2024-01-28T14:42:41Z")
Ihost doesn’t support 15 seconds yet. The smallest value you can select is 1 minute. ![20240128_154311](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/6/6fb6272ee74508834d7760e01ef4eb4fca8047ac.jpeg) ---
**Author:** ![ociepa.ekotox](https://avatars.discourse-cdn.com/v4/letter/o/c68b51/32.png) [@ociepa.ekotox](https://forum.ewelink.cc/u/ociepa.ekotox)\ **Post date:** [January 28, 2024, 2:47pm UTC](https://forum.ewelink.cc/t/problems-with-snzb-6p-and-ihost-1-13-0/27749/5 "2024-01-28T14:47:52Z")
For now, the time for the SNZB-06P sensor is 15 seconds, it can only be set in nspanel pro. ---
**Author:** ![sintoxx](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/sintoxx/32/3644_2.png) [@sintoxx](https://forum.ewelink.cc/u/sintoxx)\ **Post date:** [January 28, 2024, 4:06pm UTC](https://forum.ewelink.cc/t/problems-with-snzb-6p-and-ihost-1-13-0/27749/6 "2024-01-28T16:06:52Z")
I have set it to 1min and I still have the same problem, I don’t know what’s wrong with the device or the ihost. ---
**Author:** ![ociepa.ekotox](https://avatars.discourse-cdn.com/v4/letter/o/c68b51/32.png) [@ociepa.ekotox](https://forum.ewelink.cc/u/ociepa.ekotox)\ **Post date:** [January 28, 2024, 4:19pm UTC](https://forum.ewelink.cc/t/problems-with-snzb-6p-and-ihost-1-13-0/27749/7 "2024-01-28T16:19:57Z")
it worked well for you before? turn off the current sensor for a minute and turn it on again. Maybe this will help ---
**Author:** ![ociepa.ekotox](https://avatars.discourse-cdn.com/v4/letter/o/c68b51/32.png) [@ociepa.ekotox](https://forum.ewelink.cc/u/ociepa.ekotox)\ **Post date:** [January 28, 2024, 4:27pm UTC](https://forum.ewelink.cc/t/problems-with-snzb-6p-and-ihost-1-13-0/27749/8 "2024-01-28T16:27:02Z")
If that doesn’t help. Remove the sensor from ihost and pair it again ---
**Author:** ![sintoxx](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/sintoxx/32/3644_2.png) [@sintoxx](https://forum.ewelink.cc/u/sintoxx)\ **Post date:** [January 28, 2024, 4:37pm UTC](https://forum.ewelink.cc/t/problems-with-snzb-6p-and-ihost-1-13-0/27749/9 "2024-01-28T16:37:34Z")
> [@ociepa.ekotox](#): > > If that doesn’t help. Remove the sensor from ihost and pair it again I had already disconnected them and I have also unlinked them several times. I’m going to leave it disconnected for longer to see if there’s any luck. ---
**Author:** ![Teki](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/teki/32/1161_2.png) [@Teki](https://forum.ewelink.cc/u/Teki)\ **Post date:** [January 29, 2024, 7:04am UTC](https://forum.ewelink.cc/t/problems-with-snzb-6p-and-ihost-1-13-0/27749/10 "2024-01-29T07:04:04Z")
Hi, it is suggested to submit feedback with system logs on iHost Settings page. We’ll look into your issue. and btw is your iHost on Version 1.13.2? if not please update first by checking the firmware version on Settings page. ---
**Author:** ![sintoxx](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/sintoxx/32/3644_2.png) [@sintoxx](https://forum.ewelink.cc/u/sintoxx)\ **Post date:** [January 29, 2024, 9:09pm UTC](https://forum.ewelink.cc/t/problems-with-snzb-6p-and-ihost-1-13-0/27749/11 "2024-01-29T21:09:20Z")
> [@Teki](#): > > Hi, it is suggested to submit feedback with system logs on iHost Settings page. > We’ll look into your issue. > and btw is your iHost on Version 1.13.2? if not please update first by checking the firmware version on Settings page. Sorry if it was a mistake, the version is 1.13.2 [Nueva imagen de mapa de bits (2).bmp](https://forum.ewelink.cc/uploads/short-url/utdq0htnw7fPPi718qWxfF9QPUc.bmp) (5.9 MB) [Nueva imagen de mapa de bits.bmp](https://forum.ewelink.cc/uploads/short-url/rwj5HyLH0Wgfb3v1k2YIXZTBi6u.bmp) (5.9 MB) ---
**Author:** ![sintoxx](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/sintoxx/32/3644_2.png) [@sintoxx](https://forum.ewelink.cc/u/sintoxx)\ **Post date:** [January 29, 2024, 10:01pm UTC](https://forum.ewelink.cc/t/problems-with-snzb-6p-and-ihost-1-13-0/27749/12 "2024-01-29T22:01:03Z")
I have a sonoff bridge pro and I have linked the snzb-06p and it works perfectly, with the ihost there is no way for it to work, it keeps detecting infinity. I have removed the custom translation in case it may affect, I have restarted several times, I also deleted it and I have re-paired the device and the results are the same. I do not really know what to do. ---
**Author:** ![port4u](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/port4u/32/5117_2.png) [@port4u](https://forum.ewelink.cc/u/port4u)\ **Post date:** [January 30, 2024, 2:21am UTC](https://forum.ewelink.cc/t/problems-with-snzb-6p-and-ihost-1-13-0/27749/13 "2024-01-30T02:21:24Z")
Hi, The UI for 06P’s detection interval is not clear enough on iHost. I assume you may have set it to 1 hour rather than 1 minute. ---
**Author:** ![sintoxx](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/sintoxx/32/3644_2.png) [@sintoxx](https://forum.ewelink.cc/u/sintoxx)\ **Post date:** [January 30, 2024, 10:39am UTC](https://forum.ewelink.cc/t/problems-with-snzb-6p-and-ihost-1-13-0/27749/14 "2024-01-30T10:39:11Z")
I set that interval of 1 hour, because setting 1 min didn’t work, it was for testing. As you can see in the image with the interval of 1h it could be 2 hours or more without changes in the state. After restarting the ihost, unlinking devices, deleting the ihost translation, etc… it started working, the reasons why? unknown, but it has caused me a lot of headaches. ---
**Author:** ![Jemma](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jemma/32/8657_2.png) [@Jemma](https://forum.ewelink.cc/u/Jemma)\ **Post date:** [January 30, 2024, 12:56pm UTC](https://forum.ewelink.cc/t/problems-with-snzb-6p-and-ihost-1-13-0/27749/15 "2024-01-30T12:56:21Z")
Please submit iHost system logs