Optimize eWeLink CUBE interface on phone screens

Need a responsive interface of eWeLink CUBE, working with smaller displays like smart phones.

1 Like

I’m moving this feature request here @ociepa.ekotox

5 Likes

Why a bug is submitted to a vote as a “feature request”?

There is an update available and I need to turn on my laptop to click on “update”, because the button is hidden on the browser on my smartphone.

Only this issue should be more than enough to fix this bug asap

It is designed for PC browsers. It has a responsive design but is not for mobile platforms at the moment.

When you ask for a re-designed layout for mobile size/ratio, that’s a new feature.

Sorry, but we are in 2024.

Most people are on mobile devices and not on PC anymore.
If we need to turn-onn a PC just to make basic things on iHost, it’s a bug and not a feature to be implemented.

How many “votes” do you need to start looking at this? I sorted the posts by “number of votes” and the maximum votes we see in all “feature request” is 19 and the 2nd one has 8.

This one has 5

The problem is as old as ihost. From the very beginning, there was a need to optimize the IHOST interface for use on mobile devices.

1 Like

The vote is a major factor when we try to sort the priority of needs from users, but it won’t be decisive.

We know the mobile traffic is trending overall on the internet but that could be different for CUBE. We will reconsider the priority once we have more data from the newly opened User Experience Program on eWeLink CUBE.

What does it means?

If it will collect the statistics of the browser used to access iHost, I’m pretty sure the amount of Mobile Browsers were be minimum, because we are forced to use PC Browsers. If I use the mobile browser, I don’t have access to basic things.

In the case of mobile login to ihost cube you will not receive any data, because such login currently does not make sense. The cube interface is displayed incorrectly.

1 Like

@renatoyamane @ociepa.ekotox

Thanks for the insights. We will consider this factor too.

Having got used to Cast I don’t mind having to rarely use the big screen interface but there are some missing features, so you could just have a simplified interface and no need to make the whole interface mobile friendly:
From memory

  1. battery levels
  2. reboot
  3. firmware update

My internet provider router has an interface you can’t navigate from a phone, but I can reset it and firmware updates are automatic. There is no equivalent of battery levels for them to sort. I’ve resorted to a node red push notification if they get low, but it doesn’t work if things go suddenly from High to Zero without a Low measurement on the way, but I use rechargeable batteries so I think their Voltage/Energy curve tricks the voltage sensors. It would be nice to be able to tell them the battery chemistry but I’m guessing that is a hardware thing?

1 Like

I have a device where the readings are displayed on iHost devices list, but not on Cast :roll_eyes:

This is an example of why we should have the iHost perfectly accessible on smartphone browsers

I don’t see this as an example of why there should be a layout for use on smartphones.

I understand that iHost is a device bridge.

That’s the idea behind it!

This could easily be controlled by placing all devices paired via Matter on Google Home or Alexa.

That’s if these devices work on these platforms.

I believe that iHost should have a better layout for different types of screens. Because not everyone has a PC with large screens or even has a PC. Sometimes the user has a tablet and uses it as if it were a PC because it works for everyday use, etc.

That’s why I think it’s important for everyone to vote on this item, since it seems to be very important to many people.

I believe that the layout and backup features are the ones that people talk about the most, but they’re the ones that don’t get many votes.

I believe that if the number of votes is significant, they will speed up its development.

Does that data appear anywhere on the Node Red Device. When I got a TRV the cast dashboard did not work for their temperature measurement so I ended up creating a node Red dashboard for them. Looked dead ugly because I put no effort into the design but it was okay while the cast was catching up it did the job.

Very wise words. :+1:
But it is true that fewer and fewer people are taking an active part in the discussion.:thinking:

One thing I noticed is that people are reading less.

I believe that Cube has a great chance to evolve and improve a lot!

I believe that with the launch of the NS Painel Pro 120
The forum should see an increase in activity.

In the coming months, there should also be an increase in the number of people appearing on the forum due to the HUB and the new launches.

I believe that Sonoff, together with eWelink, are trying to build a strong and solid ecosystem.

However, some things are still lacking.

For example, a mobile interface could be easily implemented via the eWelink APP. However, I don’t know what the limitations are, etc.

I understand that iHost is completely OFF-Line, no servers, etc.

However, there should be a way to access iHost through the eWelink app, even if it is limited at first. For example, just to view the status of things, etc.

However, as I said, I don’t know the technical limitations for this.

Every day that passes, more and more users want things that are easier to use.
They don’t want complicated things, for example, they don’t want to have to use node-red or other things for simple automation, etc.

Today we have simpler HUBS from other companies that work entirely locally and are viewed via their app.

Well, I don’t know what the best solution would be.

However, I believe that with more speeches and users voting more for this functionality, they would be forced to think about this solution soon and with that it would be implemented more quickly.