search

WeeJeWel / net.weejewel.hyperion

Hyperion App for Homey
0 stars 4 forks source link

Error when selecting effect in flow #9

Closed Fire69 closed 6 years ago

Fire69 commented 6 years ago

Hi,

I just tried changing an Hyperion effect in a flow. This is what I got: image

When I check my Hyperion in Devices, everything is working OK. image

I tried creating a new device, same problem occurs.

Fire69 commented 6 years ago

Any chance this is getting an update? :(

WeeJeWel commented 6 years ago

I don't have a Hyperion installation anymore so probably not. If anyone wants to take ownership of the project i'd be more than happy!

Fire69 commented 6 years ago

No way you might be able to easily fix this with your programming superpowers if I send you a log? ;-) Since the device is working just fine the connection to Hyperion is working correctly (colors and effects can be selected), so it's a (small? :-) ) problem with the card in the flow probably.

WeeJeWel commented 6 years ago

Could you create a screenshot of the Inspector open when typing, then hit the Network tab, click the red request and show the 'response body' (Should be some JSON with an error message).

Fire69 commented 6 years ago

Thanks for taking the time :-) Not entirely sure it it's this you want? image The moment I select the card it shows the device-error in the card, I don't have to type anything.

WeeJeWel commented 6 years ago

Could you try to remove and add the card in the Flow again? Be sure to use the Homey Desktop App, I think there's a bug in the smartphone app preview when saving flows with devices.

Fire69 commented 6 years ago

Using the desktop app, I removed the card from the flow, deleted the device and then uninstalled the app. After that I started from zero => app, device, flow. Same error :(

WeeJeWel commented 6 years ago

Thank you! This is most likely a bug in Homey itself and I'm pretty sure it has been fixed in Homey v2.0

Fire69 commented 6 years ago

Not trying to be negative or anything here, but... 2.0? That's not going to be released for quite some time, right?

WeeJeWel commented 6 years ago

I understand your concern. It's close enough however to not fix issues like these in 1.x anymore.

Fire69 commented 6 years ago

Ok, I'll try to be positive then and wait it out ;-)