I have issue with i4DC. I can not use it with simple push buttons, while I use several i4 (AC version) with “okay” experience. (of course type of input is configured well) Simpy Action events (single, double, long, etc) do not trigger the flows.
Btw. “Okay” experience with AC version is because Action event flow cards do work, while there is no any change in GUI at “State of input” 1-2-3-4 for 6 months, but I use it daily.
When a channel is configured as button the input will not change as buttons do not have an on or off state. The input should actually be removed automatically from the device in Homey. If they there is either something wrong with polling the device from Homey due to networking issues, you are using an outdated version of the app or it’s a bug (which I dont think so as I would have heard of it before).
The i4AC and i4DC use the exact same code. When you say type of input is configured well on the i4DC I assume you mean you have it set as button if you want to use the action events. If that does not trigger the flow it’s probably due to networking issues as well.
All my shelly devices, about 15, lost connection to my Homey Pro a couple of days ago. It could perhaps be du to my Unifi Dream Machine having updated to the lates OS, as it is check for updates at 3am and the CPU usage of the Shelly app in Homey droped at exactly that time. They all work through the Shelly cloud thing and the wifi connection seems fine. All settings seem ok to me and the router as well as the Homey has been rebooted a few times. Is anyone else experiencing this issue?
Hi all, is it possible to rename temperature sensors from Shelly Add-on connected to Shelly 2PM? I can rename them direct in shelly, but sensor names are not shown in Homey…
Not possible at the moment. I looked into this but the name is not available under the status endpoint. That means I’d have to implement a complete separate logic just to sync names of external temp sensors. Next to that, having update the names conflicts with other logic on how capability options (like the generic names of the current external sensors) are implemented. That means I’d have to refactor that as well. A whole lot of work for something that already works.
A work around to get your own name in Homey is to use virtual devices and sync the temp sensor with a virtual device having your own name.
I checked the Zwave network, device responds to test messages sent from developer web surface quite fast what means the connection is reliable and good. I understand that AC and DC version share the same code, but have you tested the DC version personally, is there anyone here who has experiece with it?
I disabled cloud on my Shelly HT devices and checked the websocket port as well. I’ve tried both wireless and LAN IP from my Homey Pro and it works fine for a day and it stops. I set the threshold for humidity at 1% to make sure it’s reporting several times a day but it just stops and last report shows two days ago.
Perhaps this device isn’t suitable for Homey and I’m wondering if there are people out there who got it permanently working?
Would they be addable to Homey just like any other wifi device, using the “Any Shelly WiFi device”? Is there anything I need to consider in comparison to the “normal” Shelly devices (that are not intended to be embedded).
They should be compatible but this hasnt been tested extensively. Since there are so many use cases and configurations for this device there might be still something that isnt working. Just report it when you run into this.