iHostis not for HA, it was not designed for it, the hardware is expensive, the access is blocked and the zigbee is very limited.
So much so that it makes no sense to spend time and money on programmers to make something that already exists and is free.
If you still find that your ihost is in the same location as your Raspberry PI or other HA host, ihost cannot connect and control the device but HA can, please contact us and we will see if there is a hardware problem with your device.
Because the signal strength displayed by HA and the LQI displayed by ihost, please do not simply see the display information, HA is full of cells and ihost has only one cell, and simply think that the signal of ihost is not good.
Next, we will purchase a skyconnect and do a comparison test. We will send the results here to compare and see where the differences are. Since EFR32MG21 is also used on ihost, theoretically there should be no difference between them.
In addition, we also hope that you can synchronize your test results to us, and want to know what data you are judging by: please do not simply compare the signal strength display icon displayed on the two systems - because they do not show the same parameter
From the pictures provided, we can not see the corresponding signal strength or communication quality information of the equipment. If you are referring to the comparison that the eWeLink cube currently supports fewer device types and product models than Zigbee2Mqtt or ZHA, then we admit that it does. Currently, eWeLink Cube recognizes and supports far fewer device types and product models than open source projects such as Zgbee2mqtt.
In addition, according to the users we contacted after selling ihost, 80% of the users are non-technical people who do not understand technology at all, and they do not want to learn how to install and config a opensource sysetem, so they cannot use HA smoothly - they just want to use ihost directly out of box. Our current product development direction is to serve these users well - so in order to ensure the security of equipment data, We will not open zigbee chips to any third party applications.
If you are a technical user or developer who knows HA, then you also want to install and run HA on eWeLink Cube, we have also opened the USB port for Docker, you can plug in skyconnect into USB port and install HA , they can work together.
Please understand that we cannot support all device types and models. We can only ensure 100% support for SONOFF brand and eWeLink support products. For other brand products, we can only say that we will try our best to support them, but we cannot guarantee 100%.
The example you mentioned is because the eWeLink cube does not currently support the socket type with power meter capability, there is not any UI card to show this type of deveice, so it cannot be supported. We will continue to add various types of devices in the future - there are many types that we do not support at present , and we need to add them one by one, if you read the monthly upgrade record, you will find that we are constantly adding new supported device types - but this job which will take time, we will continue to add support for various categories.
For many devices, we can not support all their functional configurations, because each brand supports a variety of Settings are different, the protocol is not standard uniform, need to be compatible with one by one - some Settings are not public need to crack. So we currently only promise to support the standard capabilities of each type of device - the default power-on state you mentioned is not a standard capability, but a private instruction made by tuya itself, so we cannot support it - just like you connect SONOFF devices to tuya gateway, there are many configurations that cannot be displayed and used.
In the end, we can only promise full functional support for the SONOFF brand and eWeLink support products, the rest we can only say - we will do our best, but can not guarantee full compatibility support.
For supported product types and product models, as well as supported capabilities, we update the Zigbee Compatibility list - and we continue to update this list. If your device is not on this list, or is on this list but is not supported, you are welcome to contact us - we will try to see what to do, but will not give you any promises about when it will be supported.
Regarding your inquiry, ZBBridge-P will be supported in the new version of eWeLink smart home addon, which will be released around September 15th. Please be sure to upgrade your ZBBrdige-P to the latest firmware version to support LAN mode, so that ihost can find it in the local area and synchronize the device.
I understand @Alexie , and that is why I am still using iHost and trying to help.
Sonoff does not have a lot of devices, for example doesnt has a Switch with 4 channels like this. This device is even smaller than the Sonoff ZBmini and has a better zigbee signal.
The iHost is sold with the promise that it will be compatible with other brands.
The problem is a lot of people that bought the iHost with this promise will become iHost haters, as we can see in this forum.
I have also got some Zigbee Moes Thermostatic Radiator Valves. Bought them ages ago, well before Sonoff had TRV, but I think you are soon adding the device type to the iHost? Is it worth seeing if these Moes TRV work with iHost in a future iHost update or should I not bother? They work in home assistant. Thanks, Eerke
Not really the same, as PCs running XP and Windows 7 would still continue working once MS stopped supporting the platforms, A place I worked last year still had several standalone PCs running XP as the devices they controlled had no drivers for Windows 7 or 10.
yes lots of 3rd party servers are available, but one day how ever long it was ago, i thought.... hey i fancy a game of UT only to find that the official server had been turned off. yes, some googling later a alternative & a patch were found, but it did not say , on the packaging, the outside of the packaging, prior to purchase of a physical media game, that the internet was required or that it would turn off at some point and take all your achievements with it.
I am not so sure, this is consumer tech and the cut-off dates are 3 years away. Bluntly, most people will have got bored of it or replaced it long before then. If they stop selling them then fine but people ditch all sorts of other tech products, often in a shorter timeframe without a second thought.
I am clearly a lone voice on this but I don't understand why there is an expectation that it would turn out any other way. It is consumer electronics dressed up with tech and Apps as a security system.
These things should be classed as appliances with an expected life measured in decades, not the sort of stuff that gets relegated to the attic or tip when something a slightly different colour is released...
I'd like some other home automation stuff that works with either of these, excluding stuff that can spy on us or gather more detailed information than how hot we keep our house. But they all seem to have proprietary software that means you have to use their hub, even if it's supposedly Hive compatible (like the fancy light bulbs). And they're also bloody expensive for what they are.Keeping users trapped in their walled patio means they can charge what they like.
Actual chime, wire and transformer are up to you (and the wiring code in your jurisdiction), but at least once you install it you'll be secure in the knowledge that it'll last your lifetime, and possibly through your grandkid's, too.
I agree with your comments on IoT, solely in relation to the Cloud. However, I don't think smart building tech is a flash in the pan. I also don't think that the timescale you mention is reasonable. Several of my clients are still using smart tech ten or more years after I installed it.
I use, and install, lots of IoT devices. But, I have an immutable rule that I don't install anything that relies on ongoing Cloud services provided by third parties. So, every installation has a local server (usually a NUC. Sometimes a Raspberry Pi), that works locally whether or not there is an Internet connection. Some can even be controlled by SMS.
One of the systems that several of my clients use, and love, is the Logitech Media Server (Squeezeboxes, essentially). Whilst originally there was a Cloud option, there has always been a locally installable server (originally SlimServer). Logitech killed LMS years ago. There was a sharp intake of breath amongst their users, but they open-sourced the server code, and it is still going strong. Hopefully Hive do similar.
Conventional wisdom with these type of IOT devices is that you pay a premium and go with a brand leader so they will receive security updates and the backend functionality won't get prematurely turned off. As is often the case, ignoring conventional wisdom saves a lot of money.
I tried to buy a camera for viewing my front door a few years ago. It was just for letting me see who was at the door making a delivery, when I was at home, in the garden out the back. Would be going on a closed circuit wifi or wired network.
Gave the sales bloke my requirements, told him there obviously couldn't be any cloud element and I didn't really need recording. If he'd got nothing that fit the bill please would he tell me now and save me some valuable time.
He then proceeded to show me a Ring doorbell which when queried if they'd released an update to allow offline working admitted they hadn't. I then saw Nest, Hive and I think something else, all of which needed an internet/cloud connection.
When I said no to all of them he informed me that I was obviously going to need the internet or how could I view the camera when away from home? I asked if he'd listened to my requirements when I first spoke to him and he rather bizarrely said yes.
Didn't stop them with me. I ordered a fridge freezer from them but they cancelled my order due to supply issues. A few weeks later came a letter offering me extended warranty for the none existent appliance.
3a8082e126