Please put Tellstick core on next SDcard edition

[ChristianS]

The way it is today, I have to compile it to RazberryPi, and thats not the best way to do it. (after I've seen whats in the core, and how I can get control over the radio, I will be back with suggestions to how we at least can simplify population of the telldus.conf)

Another feature I think should be easy to add, would be to change from DHCP to Static IP in the Settings. No reason to have to go shelling out for that.

I see there is a couple of weather stations that is included as hardware; is there any description on how this interface works? In Norway, we have free weather services that uses better models.

[gizmocuz]

Sure the Norway system is much better compared to using wunderground (where also Norwegian people publish to, but ok...?)

I was actually thinking about NOT putting anything on the SD card except domoticz,
and then using scripts to install other things (or the wiki)
like NodeJs/NodeRed/....

This was we have a clean install

If you can make a wiki about getting the Tellstick up and running on a raspberry pi (or linux) that would be great

About DHCP/FixedIP, it is a good learning curve to get some SSH experience..

[ChristianS]

In a Linux sense of things, focusing on a clean install and designing the system as building blocks makes a lot of sense. There is also a point that people who wish to run this route, has the option to do it, and as far as I can tell, they do through the ordinary Linux distribution.

But there should be an embedded system approach too, and I think the SD image should cater to them. Ideally this should be something you just popped into your Raspberry Pi, and NEVER used SSH or even realized it had an OS. For people like me, who just wanted to upgrade their Popp Hub. (So far I've found 3 home automation system that is basically rebadged Raspberry Pi. And the software is usually shit.)

But I see a user experience issue , there you would have user interface options that only caters for a subset of platforms. So let me think more about the suggestion of setting up static IP.

I like the idea of rebuilding the structure to a "install what you need"- model. The downside is that if you do that, you really should have a binary repo with necessary configuration. As you do not have this for telldus core at the moment, I went with the baby steps idea of just getting telldus core into next version. If you go on with your idea, adding Telldus core in next version would actually be a great idea; anyway you think you would implement such solution, would start with a working image with the hardware driver present.

[ChristianS]

After investigating more, I really think making domoticz a core application, and keeping everything else as plugins and optional packages, would be a terrible way to do it. I see a lot of dependencies and lost opportunities. At least at the current development level.

I'm looking into getting Telldus.core into my RPI, and so far it has stopped on the most idiotic problems, (the deamon runs, the interface is there, the hardware is there, it still fails silently.) and the number of different implementation guides tells me there is a lot of undocumented dependencies. Its so bad, that I consider, making some small programs just to sanity test the installation.

The good news is as soon I have it on, my installation should stay stable, and we will have fairly good documentation, the bad news is that this still suboptimal, because for instance Node.RED has tellstick support as an option, and this should also be part of the package. And while node.RED gave the impression of being amazingly sexy, I wasn't really ready to investigate that too.

Just having it in the image already configured integrated and tested would be SOOOO much better.

But while I wait for next SD image, I will go back til z-wave on my pi, and build Domoticz on my linux server.

[gizmocuz]

What also would help.... buy an RFXCom RFXtrx433-e or RFLink ?

[ChristianS]

I'm considering it.

But I HAVE a tellstick, it works like a charm on it self, so I'm a bit miffed that it integrates so poorly, and I'm willing to spend a bit of time to get it working, simply because I'm a stubborn engineer .

I was going to go RFXCom, until I read that RFXCom looses more messages than Tellstick. Since I got a Tellstick for Christmas, I tought I could make it work, check out the quality and stability of send /receive, and then buy a RFXCom. If the problem is real, I would be able to document it and get a refund. If not, myth busted, and I could trash the tellstick.

[gizmocuz]

Yes, but the problem is someone has to keep supporting it.
If you can explain (send me a PM) how to compile and setup a 'new' raspbian sd card (with jessy) with tellstick support
then i can add it

[ChristianS]

OK. forget it for the moment ; I'm not there yet.

And I REALLY want the new image. The SD image is somewhat outdated Domoticz vise

Get Jessy the image out, and I will make the install documentation and we take it from there for the next version.

[gizmocuz]

Yes, until we will release a new 'stable' (the planning was this week),
then all will get a real stable

Since our last 'stable' a lot has been changed, automatic build systems etc...

the problem was that it was uploaded to sourceforge, and we did not want to have 100's of downloads
now this is in our own control, we can change this
(and this download page is just a day old bdw)

[gizmocuz]

OK. forget it for the moment ; I'm not there yet.

And I REALLY want the new image. The SD image is somewhat outdated Domoticz vise

Get Jessy the image out, and I will make the install documentation and we take it from there for the next version.

Me too !
But it will take some work...

- first release a new stable
- then make a new sd card image with all settings/tools we have now on the current

the issue i am facing at the moment is that the jessie image is very large!

Also your router/switch probably runs on an old linux firmware, nothing wrong with this as long as it can get updates

There are other projects (like kodi) that are kind of closed (in respect to the image)

... Did i forget to mention a new raspbian image just came out today (as expected?), would have been such a shame if all work had been put into the previous version
... could be that this was the reason the milestone of a new domoticz stable was set to 1-3?

[ChristianS]

Why not build your own project as a spin off? Building a full domoticz OS for RPi - to me - sounds like somewhat outside the project's goal. That said, the project could definitely do with better version management. Particularly in regards to what versions can be regarded as 'stable' or 'release'. Looking at the download page, it seems to me that the precompiled Windows versions are essentially beta. Correct?

I do not see this as building a full OS, only completing the hardware support under Domoticz and hardening the total software stack on current supported platform. From that perspective, RPi and other persistent hardware configurations like NAS'es, are reference designs for Domoticz.

For a home automation system, this is actually crucial. You could consider Domoticz as only the frontend and logic of a home automation system, and look forward to units like Tellstick Z-net Pro, that would give you a IP based interface to a Z-wave and rf433 radio, or Nexa bridge, that seem to do the same. But today, they actually support rf-link, a arduino based "build your own hardware" approach. So adding a simple c-interface should not represent an issue.

The reason I wish them to finnish the SDimage, is because someone has risen issues regarding Domoticz on Jessie. The latest Raspberry image is Jessie, so if I'm going to build domoticz with Z-wave and Tellstick support on raspberry from scratch and make/update the documentation for it, I wish to get away as many stupid problems as humanly possible. In the new Domoticz version, there is better support for Zwave (and i think the reason for my tellstick problems lays in a conflict with my current z-wave implementation,that has wider hardware support implications), some OS upgrade issues is fixed, and generally a lot of important issues has been solved. Starting documentation on the current Domotics/RPi level, will produce a lot of documentation on how to get around issues that is already solved at the time my documentation is finished.

Then I started out, I focused on Tellstick configuration on Linux, which in the documentation is considered more complex than on windows. This problem has more or less gone away. So that was my reasoning for making the Domoticz team add the hardware; they did the simple stuff and I would find a model and maybe build some code to get it to work. I got Tellstick onto my Linux box last night, and its the other way around : installing has a bit of complexity to it, actually configuring it, should be simple. I still want to hack the shit out of it though. There are no reason I have to settle with what telldus gives me. But thats personal

I gonna start flogging the Domoticz team about their future stable/beta/ roadmap/issuetracking as soon as the next stable is out, so I can start fixing the mess the Wiki is in now. Almost nothing of the documentation around this is correct at the moment and getting sourceforge out of the wrong parts of the Wiki is going to take some time.

But for now, we concentrate.

[gizmocuz]

Almost nothing of the documentation around this is correct at the moment and getting sourceforge out of the wrong parts of the Wiki is going to take some time.

Dont know what you are talking about ? The only reference of sourceforge is for people who compiled this a year ago

A new image has been released, if you can make a wiki for the tellstick that would be great, no need to touch the other wiki pages
Then we could include this in the next sdcard image as default

[ChristianS]

Almost nothing of the documentation around this is correct at the moment and getting sourceforge out of the wrong parts of the Wiki is going to take some time.

Dont know what you are talking about ? The only reference of sourceforge is for people who compiled this a year ago

A new image has been released, if you can make a wiki for the tellstick that would be great, no need to touch the other wiki pages
Then we could include this in the next sdcard image as default

I'm on it.

Is there anything wrong in the edits I made for the SD image install ?

[gizmocuz]

@gordon, that is what you get when you mix things.

Back to the OP question "Please put Tellstick core on next SDcard edition"

If this does not take space, if it is just a library or something we have to activate, then i see no problem with it.
@gordon, for example the raspberry supports 1-wire in the kernal, you can turn this on/off

Another option is to make a shell script that does all the magic to get the tellstick supported.
(downloading the libraries, compiling, installing etc...)

[ChristianS]

Back to the OP question "Please put Tellstick core on next SDcard edition"

If this does not take space, if it is just a library or something we have to activate, then i see no problem with it.

Another option is to make a shell script that does all the magic to get the tellstick supported.
(downloading the libraries, compiling, installing etc...)

I had a look at it. Since Telldus states that you should not use the beta version from Git in production I tried installing the stable release, which is troublesome. Make fails because two of the modules are not linked to pthread. There is a dependency trap if you run make with -j>1 and Make will fail again if you have doxygen installed because the control file for generating the HTML docs is in fact missing and needs to be fetched from Git. Telldus-core in fact turns out to be a service and I'm not sure if you really need it to be able to access Tellstick from Domoticz. One of the requirements is libftdi, so my guess is that it should be possible to go straight to the serial interface similar to the way RFXcom is handled. This would also eliminate the need for an additional screen to manage telldus-core.

My $ 0.02

And a very valuable $0.02 . I will try to cash in later. At the moment though, I will try to get the telldus-core in as is. Babysteps as I said.

I need to understand how the developers plan to develop Domoticz further and how they want the future structure to be. I tend to be lazy, and not jump in until I know where we are going. Personally I have several options available, including your suggestion, but I'm not one of the people that should decide.

And there is other factors, like the suggestion for telldus to include support for Tellstick.NET and Tellstick Zwave pro in telldus-core.

On the flip side, I expect to use the Git version. While I respect their comment on using other repos, there hasn't been changes on the code for 11 months and the last open issue is the problem with parallel compiling. And when the version is exactly the same, I go for the original source.

[asjmcguire]

@gordon - telldus-core is required for tdtool to work, this is the preferred method of controlling the tellstick, if you go down the route of talking to the tellstick directly - then you have to implement all the protocols yourself.

eg: tdtool --on 78 --on 67 --on 45 --off 2 to perform multiple switching commands or you can do them one by one if preferred.

telldus-core is also required for the c/c++ integration - http://developer.telldus.se/doxygen/