This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Closed
Homey v0.10.1
JeroenVollenbrock
Member
Homey v0.10.1 has been released to the experimental channel.
Changelog:
Changelog:
- Added button to remove notifications
- Increased app resource usage warning threshold to 30 seconds
- Devices without a running app are now displayed as unavailable instead of hidden
- Update Node.JS to 4.6.0 to resolve security issues
- Bugfixes
This discussion has been closed.
Comments
Not al GIT 0.10.1 issues are staged for release, are these not in the update?
Or are all issues with milestone 0.10.1 in this release but not yet closed due to the community has to test this?
For me it now shows a Multisensor, but it's for sure a rogue device. Will it be possible to delete such a device in a future version?
Positives:
- Dutch built in commands work again!
- Screensaver app (Ledring) works again.
Unsure:
- IR still doesn't seem to work, but there are no crashes like before with 0.10.0.
- IR also adding more then 1 IR devices doesn't give any errors when using them in a flow.
Negatives:
- Variables are still not being saved after reboot. (workaraound: by first switching the app off and then on again and then creating new variables, they will stay after reboot)
- Still it's pretty difficult to move flows to a map
- IR doesn't emmit any IR signal. Tested this with a Samsung TV and a AXA Remote (window opener). Tested by pointing my camera at the Homey and then testing the flow but no IR is picked up by my camera. But when I use the original remote the IR is seen by my camera.
But all in all so far so good! Nice work Athom and pretty fast as well!
https://github.com/athombv/homey/issues/890#issuecomment-249662873
Athom fixed it for me remote and knows the (probable) cause.
Contact Athom / @jeroenvollenbrock on Slack or via support@athom.com
if you have auto updating enabled (and experimental) maybe you can wait until Homey updates by itself...
otherwise you will have to ask help from Athom support.
Tried every trick but no success with 0.10.1
It's a 2 min job, no biggy.
Also, have to mention this, app Buienrader suddenly works!
i just found out that a lot of things in the flows when you use the test button gives errors
i had it with a logic blok that reads the co2 level used the tag and i get a red triangle with a ! in it
but when i save the flow the flow does work as my ventilation just turned on and homey says the co2 level
also for the brightness control of hue lights
same errors but flows work
is there somebody else that can test my findings
I think I know wat you mean, but a little more info and a screenshot would maybe have helped understand you.
For what I Read....
Not everything in a test produces what you expect.
Tokens from triggers are filled with a example value that . is defined by the developer.
for example https://forum.athom.com/discussion/comment/22446/#Comment_22446
- Every test with someone came home results in the user John Do ... (And John doesn't live here...)
- Every test with sunset and sunrise and maybe other time related trigger cards result in 21:23 any time of the day...
The Tokens are filled with the correct values when the trigger is fired.for example the flow in the picture in https://github.com/athombv/homey/issues/924
would only produce two green checks on the Time after and Time before cards if the current time is between the two defined times.
(Testing after 22u55 would always result with a red Cross as in the picture, only this was the bug in 0.10.0 the submitter described, should be fixed in 0.10.1 )
But the Lux token has no defined default/example value so the test card always crashes with a red exclamation mark.
Would the developer of the App define a default test value of 123 it would always test with the third card as a red Cross as 123 is never less than 35.
When you encounter that and want to test the execution, you can easily check the invert checkbox (Upper Right NOT checkbox) on all condition cards that are not true when testing (NOT + Not True = True)
Test the execution of the flow, and when finished remove all extra invert check-boxes you have set end SAVE.
Happy Testing !!
I have bumped into an issue: Homey does not stop listening. It is 5 minutes now and it is still continuously listening. It`s not that the LED ring is frozen in orange colour because it is pulsing as I speak. @Athom are you spying on me?
I guess I need to reboot.
Both custom IR device (training the buttons) and Samsung TV built in IR doesn't seem to be sending an IR signal. I've added these devices separately (so not one directly after the other) and also tested them separately.
I've checked to see if any IR signal was being send by using a camera (you should see a purple-ish light pulsing), but Homey doesn't seem to be sending out any IR signal...
https://github.com/athombv/homey/issues/937
I have checked that last night in pitch dark. I set up a flow to send predefined IR signals every 5 sec. It was really interesting experience (I might post it on youtube). I could see the IR LED`s lit up and also the chips not located at the openings, blocked by the casing. So they do lit up. But before 0.10.1 I had the same issue as you. Might worth to raise this issue on Github.
I have done the experiment with the default Philips remote. You could try it with the Philips remote first. It might be that something is wrong with the Samsung virtual remote.
see : https://github.com/athombv/homey/issues/937
Also tried that one. But unfortunately no positive result...