Back after a few days of testing: disappointed!

Off-Topic
21

Hi @Peter_Kawa, @Asterix,

Thanks indeed.

(I’ve never used the power supply that came with the Homey. I have a PoE adapter instead. I said ‘dongle’ because I was being lazy but that hasn’t quite worked out :grinning_face: )

I probably should have made clear - the ethernet connection was definitely fine when I first set up the Homey, months ago. I’ve had no reason to check whether the ethernet connection was still working. By surprise ethernet is now (and I have no idea since when), ‘Connected No’.

22

Hi Wigster,

When someone writes “my ethernet dongle doesn’t work” I automatically assume they just unpacked and connected it (with mixed cables). I know, Thy shallt not assume

I also did not hear about a working dongle quitting after x days yet (but all things can break, I know)
We both have things to improve :winking_face_with_tongue::wink:

On topic:
Did you replace the USB-C cable with a decent one? A number of questionable cables have been shipped with Homey.

And to determine if the dongle or the network might be the issue:
When it’s possible to connect a laptop/pc/rpi/… with the same network cable, is it able to T/R data, or doesn’t it?

23

After coming from a tinkering solution myself i can give two tips:

1: Stop thinking for the device. It works. The flow that does not work in your example, should have 2 cards. If A switches on, then switch on B. That works. If not, you can add timeline notifications. Write to timeline if A is switching on erc. Then you can ask yourself why the step is done (or not). Is the device reachable? Does it use a third party API (stay away from that type of device’s in general)

2 Buy decent quality products that are supported by Homey or have a good community support.

24

Thanks everyone for your kind messages and support! Since the conversation is going in many directions, I’ll go ahead and close this topic and post my questions in the right sections. Hope to see you there!

1 Like
25

1: Stop thinking for the device. It works. The flow that does not work in your example, should have 2 cards. [Of course] If A switches on, then switch on B. That works. [That works but only two or three times] If not, you can add timeline notifications. Write to timeline if A is switching on erc. Then you can ask yourself why the step is done (or not). Is the device reachable? Does it use a third party API (stay away from that type of device’s in general) [It’s Bosch Siemens Home Connect]

2 Buy decent quality products that are supported by Homey or have a good community support. [Dont’ know if you speak about Bosch-Siemens or Everspring. Everspring z-wave works since years with my jeedom box without any problem…]

26

Hi Peter,

I never used any USB cable supplied with the Homey. My cable to the PoE adapter, and onwards, are all fine. I bounced the Homey and it connected to ethernet again. It’s not a problem per se, it’s just odd.

Cheers!

1 Like
27

Well, that is a cloud service and my dryer stops reporting also (siemens).

So basically, if you have to create an account in an app or online , it might work but not as good as devices that are supported natively.

So start writing to the timeline in the flow so you can see if the flow is triggered and if so, you might have found the issue. Some API of some cloud service is unreliable. But hé, that is why Homey strives to be cloudless.

28

For me Bosch Home Connect in Homey works after a Homey Pull The Plug restart, once, then not again until Homey receives another PTP. I have been a Homey user for a few years and that particular app has never worked better than this for me. Your description rang a loud bell