Is Athom spending more time on writing blogs then fixing problems?

Menno · January 2017

Tried forum no reaction from athom
Tried github no reaction
And now I receive an email if I want to show of my non working zwave devices?

KoenMartens · January 2017

Yea I will guess the answer here is 'no'.

honey · January 2017

I believe the blog articles extremely valuable. They answer many in depth technical questions that (would) arise on the forum.

Regarding the no reaction part, you are right. They don`t even touch the serious issues (like voice recognition, zwave range issue), whether it is raised on the forum or on github.

mruiter · January 2017

There doing a massive fixing job in the dev-preview releases.
My load on Homey has never been this low , mem leaks are found.
Extra logging added and bugs are killed.
The blog was long promised and already 1 week late.
(That was last week that it got online)

There again mentioning this in this weeks mailing because peeps like you that missed it still get notified.

Just wait and you will see a awaysome firmware update published soon.

And please , dont drink that much. Even youre smiley is looking drunk

And last but not least, i welcome you on slack. They are online there sometimes.
But if the react to every one of your message they wont have time to write blogs anymore

bvdbos · January 2017

https://github.com/athombv/homey/issues/1030
Athom is working on zwave-issues:
https://forum.athom.com/discussion/comment/44307/#Comment_44307
Homey v1.1.3 is in our private Developer Preview channel, and we're tweaking some Z-Wave issues before releasing it to experimental. A next version will also include a visual map of your Z-Wave network, where unreachable devices can be identified and repaired.

So really don't know what you mean... Same with voice BTW @honey but not everything can be done at once...

mruiter · January 2017

For the records: We are already at 1.1.4rc4

honey · January 2017

Don`t want to make this a battlefield of Athom fanatics and complainers. But the voice is recognition issue is a year old and there were no steps taken to fix it. Yes z-wave is improving but not the range. When talking about the range than it means the max distance between homey and the first device. If it can`t reach the nearest device or not reliably than there is not much use of the visual map and other small fixes.

Menno · January 2017

ZperX · January 2017

I don`t think it will take Athom to fix it. If it is code related issue than they are good at those think. If it is signal processing issue (Voice, range, IR) than it is outside of their comfort zone. The voice recognition does not work since day one and that supposed to be the core feature, "Talk to your home". Two weeks you have mentioned is not that long, I would be positive about that.
I love the the blog articles they are truly informative.

bvdbos · January 2017

https://github.com/IcarusProject/me.zwave
That's not an Athom-app... And seeing your postings your device isn't supported yet?

Menno · January 2017

@BasVanDenBosch

Changelog: 0.0.10

Added support for the WALLC-S
Added 05433 as it seems to be a different device with the same identification information

0.0.9

Removed double device (05433 - manufacturerId: 100 productTypeId:4096 productId: 9)

0.0.8

Added support for the 054375
Added support for the 064394
Added support for the 064367
Added support for the 054336
Added support for the 05433
Changed wrong link to pictures of 054367Z

0.0.7

Updated to latest Z-Wave driver

0.0.6

Added support for the 05458

0.0.5

Added support for the 054313

0.0.4

Added basic support for the 054367Z

0.0.3

Added basic support for the 05461: Dual load switch

0.0.2

Replaced a couple of icons, fixed a slider issue and removed the tinycolor2 package (since it's not used)

0.0.1

First version

KoenMartens · January 2017

@Menno: Since one of your last posts was that you wanted to return to a version of the app in november, take a look at https://github.com/IcarusProject/me.zwave/commits/master.
For example at https://github.com/IcarusProject/me.zwave/tree/d33b6bb7fda4ef45a5794d91186c36e0000474b9 you could go back to v0.0.6 of the app (beginning of nov.).

bvdbos · January 2017

What I meant: You should ask the app-developers, in this case not Athom... They can also say if something is wrong in the zwave-driver (and make an issue for this). Or maybe something is wrong in your device?

Menno · January 2017

@KoenMartens Thanks @BasVanDenBosch also just told me how to do it. I was looking at the wrong place. Now downloading and hopefully I get it working again. BRB

mruiter · January 2017

Soooo. you will have the time now to write a blog post for the others with the looking in the wrong place problem....
Community is helping each other so do youre part

And again, youre welcome on slack. We could have helped you way sooner with that problem.

Menno · January 2017

@BasVanDenBosch like metioned earlier I have three time the same devices that have been working for two months without problems.

Menno · January 2017

@mruiter I am on slack but I don't want to chat about: Kut die naar Kibbeling ruikt en smaakt

mruiter · January 2017

We have a special timeslot to nag too ... (used it many times myself)
But if you asked for help we could have filled those slack bits that got burned with usefull information.
(guess youre mind drifted with al those nasty words like K&K)

Slow times are filled with nice things. For some thats K&K and other its PRON.
Some if waste is on blogs that got posted a week ago.
Everybody can choose for themselfs.

For the record and to make good to a promise i made.

The K&K inventor is my GOD. So he can say anything he wants and i will like it

Menno · January 2017

@mruiter now you are assuming that it's working I can tell you it's NOT. so I'm trying different versions different drivers but still it waiting for INTERVIEW_MULTI_CHANNEL but I will try more github versions.

So NO I don't have time to post a blog.

mruiter · January 2017

You could try copy-ing the the driver code into it yourself. If you take a look at the driver.js for zwave it really isn't that hard to get the hang of it.
There also a lot of examples in other zwave apps.

That maybee is the fastest way to get it to work and we would love to help if there are questions.
@Caseda is a real Wizard of Waves and we all will help

It would be fantastic if you add the working support to the app then with a git pull request.

And lets not forget, youre name will we in the ever lasting wall of fame in the app

Menno · January 2017

@mruiter @caseda is there a way to bypass the: INTERVIEW_MULTI_CHANNEL part?

caseda · January 2017

@Menno
there is no way to disable the interview part, unless you are very fancy and are able to flash the device's z-wave chip
or hack into the z-wave core code.

does it still happen if you disable ALL z-wave apps, PTP, don't restart any app after boot-up, but do try including the device, after having it reset with homey (homey's settings -> z-wave -> [remove device]).

while including have the z-wave settings page open with the stuff for geeks open as well. maybe something of an error is shown there.

Menno · January 2017

@caseda did like you are saying (just to be sure you mean ALL z-wave apps so also the z-wave.me app)

Did ptp removed all z-wave devices that are not working 3.
Still seems to hang at the interview multi channel what I see at State is:

{"zw_state":{"ver":5,"capabilities":{"api":"controller","timerSupported":false,"controllerType":"primary"},"nodes":[1,7,8,11,12,23,61],"chip_type":5,"chip_version":0,"homeId":4097722561,"nodeId":1,"nvr":[1,7,0,21,13,27,120,32,1,0,32,0,64,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,21,17,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,4,53],"CONTROLLER_IS_SECONDARY":false,"CONTROLLER_ON_OTHER_NETWORK":false,"CONTROLLER_NODEID_SERVER_PRESENT":true,"CONTROLLER_IS_REAL_PRIMARY":true,"CONTROLLER_IS_SUC":true,"NO_NODES_INCUDED":false,"sucId":1,"powerLevel":0,"version":"Z-Wave 3.99","networkKey":"8dbfa625246008ec8c03455637734d03","methodsAsync":["factoryReset","addNodeAbort","removeNodeAbort","replaceFailedNodeAbort","sendData","isFailedNode","getFailedNodes"]},"zw_ready":true}

Is Athom spending more time on writing blogs then fixing problems?

Comments