Posts made by roberts_lando

But why temperature sensors are automatically discovered and sedtronic sensor is not?

@tomas_hora Actually I'm reading 1wire devices using Linux FIlesystem like described here but I'm still not able to read your sedtronic 1wire sensor. I'm just able to read temperature sensors using this method. Any help please? I have also created a dashboard using node-red that displays all available 1wire devices with actual values in realtime

I have also found that /etc/owfs.conf is already present inside AXON even without the installation of OWFS. I have also checked evok source code and seems that evok uses OWFS to read 1wire sensors.
Is owfs already installed? I can't start it I have just found that file

At the end my question is: should I keep working with Linux Filesystem or Owfs for 1wire devices? Actually I'm stucked and I can't find a way to read the sedtronic sensors

@tomas_hora When will next release be ready? How can I upgrade the kernel?

@tomas_hora Thanks for the response! Does this patch also works for the Linux Filesystem method? What method does evok/mervis uses to read 1wire devices?

@Martin-Kudláček @tomas_hora any suggestions?

Hi, I'm working on a third-party software like codesys and mervis to support all axon features.

I'm trying to implement the 1wire devices read functions and I'm having some problems reading
sedtronic 1wire sensor. Actually I'm using owfs but I'm getting an error

[  473.375444] w1_master_driver w1_bus_master1: Attaching one wire slave 26.00000210d40b crc af
[  473.380035] w1_master_driver w1_bus_master1: Family 26 for 26.00000210d40b.af is not registered.

The 3 possibile ways to read one wire devices are:

1. Linux Filesystem
2. Use I2C converter DS2482-100 APIs
3. Use OWFS, the "one-wire file-system"

I would like to use the method 2 but in order to use it I would need the kernel toolchain of the unipi axon.

What do you suggest?

Thanks, Daniel

Hi, Is there a way to disable evok unipi-modbus-tools? Should I remove the apt package?

@tomasknot This is really nice! Thanks so much I will adopt this approach.

Oh I have missed that line, I was looking for "static" word in that file. Thanks :)

I can successfully set the static ip to 192.168.1.50 of eth0 interface but how can I choose another ip/netmask/gw/dns? I have checked the /etc/network/interfaces file and also /etc/dhcpcd.conf file but I can't find the static ip config.

@tomasknot is there a way to create a copy of the running image on axon? My problem is that I need to install other software and this operation takes time and would be much better and easy for me be able to make a copy to restore the same image in many devices.

Is there a way to write custom images on axon?

@martin-kudláček sorry for the late reply.

My node-Red interface is only used to send/receive the intensity to a specific address or group and create scenarios.

Once you have documented your documentation about dali I could check the files and try to make some changes and pull requests to the projects if needed.

Thanks

Hi Tomas, we are really interested of this support as we have developed a Dali interface in Node red to control lamps and create scenarios. Do you know how far is this support? About days, months or years? I would be glad to help if needed, we have bought one of your Dali S-605 to make some tests for now :) Where do I find the documentation to send those broadcast messages to the dali channel for example?

Is there any support for Dali in Evok? I can't find anything about Dali in Evok docs. If not, will it be supported in future?

Thanks

@Vesa-Kauppinen I think you have missed one or more step of the turorial. I suggest you to retry the tutorial and check if an instruction fails. Do you have switch on the GPRS module?

I always had compatibility problems when using Raspbian Stretch, try to use last Raspbian Jessie img and it should work

@unix I have tried that overlay and also I have tried pi3-miniuart-bt but it doesn't work with my Unipi Neuron S103-G. I have use this tutorial: https://spellfoundry.com/2016/05/29/configuring-gpio-serial-port-raspbian-jessie-including-pi-3/

I'm using Neuron with Raspbian Stretch image and I'm tring to work with serial 485 interface. I have enabled serial interface using raspi-config>Interfacing options>Enable Serial and than I have use those commands to disable console on interface

sudo systemctl stop serial-getty@ttyS0.service
sudo systemctl disable serial-getty@ttyS0.service

I have also removed the console from the cmdline.txt by removing the line: console=serial0,115200 :

sudo nano /boot/cmdline.txt

After reboot I can connect to the serial interface using node-red but when I try to read values I receive a timeout. What should I do to make it work?

Is there a slack workspace for evok? If not what about make one?