Thank you for your feedback. Regarding the request for CUBE OS to support a virtual thermostat, I will confirm the details and get back to you as soon as possible. We appreciate your patience.
Thank you for your detailed feedback. We have successfully reproduced the issue and will investigate it further. We will keep you informed of any progress.
Hello,
We have confirmed that CUBE OS currently does not support syncing virtual thermostats. Thank you for your valuable request ā we have duly noted it. We will periodically review all feature requests and keep you informed as soon as any progress is made.
But we want a thermostat in CubeOS that allows us to conveniently set the target temperature without having to do it via scenes.
Hi @Miao
After updating to IHOST v2.13.2, I cannot log in to the built-in function (Add eWeLink-linked Devices). I get a login error.
feedback 277556
Hi @ociepa.ekotox
Thank you for your feedback. We have received the log files. We will investigate the issue as soon as possible and keep you updated on any progress. We appreciate your understanding and support.
Hello,
Thank you for your feedback. Could you please clarify whether your Cube OS is running in a virtual machine or a Docker environment? Additionally, have you connected a Zigbee Dongle to your Cube OS?
None of my devices work through the Matter Bridge anymore. All of the devices that are failing are connected to my SONOFF iHost.
When I open the Matter configuration page, the system shows that all of my devices are not compatible with Matter. This is incorrect, as these exact same devices worked perfectly through the Matter Bridge until the latest update.
Gateway Information
-
Model: SONOFF iHost
-
eWeLink CUBE Version: 2.13.2
-
Device ID: 10021792bd
The last time I experienced this issue, your team pushed a special firmware version directly to my Device ID, which resolved the problem completely. I would appreciate it if you could do the same again.
Thank you in advance for your support. Regards
Hello,
Thank you for your feedback. We apologize for any inconvenience this may have caused.
To help us locate the issue more quickly, please provide your iHost logs following the instructions below. Instructions on how to obtain the logs are provided in the attached guide. If the log file is too large to upload successfully, we recommend uploading it to Google Drive and sharing a link that does not require access approval, as shown in the attached image.
We appreciate your understanding and support.
Itās running as a VM on Proxmox. Iāve never connected my Zigbee Dongle-M directly to CubeOS, because itās already configured in Home Assistant over Ethernet.
My understanding is that if the dongle is already paired and in use with an existing Zigbee setup, it shouldnāt be discoverable by other systems, to avoid accidentally taking over or disrupting the existing Zigbee network.
At the very least, it would be useful to have an option to enable or disable network discovery for the dongle, or to have an option at cubeos to ignore it and never offer it again .