OpenHAB 2 with Souliss Binding

[Di Maio, Dario]

Have someone used Souliss over openHAB 2? Please share your tips.

Dario.

From Mobile.

[Juan Pinto]

I have OH2 on my computer and the last time I opened it worked ok with Souliss.

 

Regards.

[Di Maio, Dario]

Thanks.

--
You received this message because you are subscribed to the Google Groups "souliss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to souliss+u...@googlegroups.com.
To post to this group, send email to sou...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/souliss/7cc67b48-7afb-4b0a-904a-d878ded9cea0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Marko S]

Did you try OH2 also with the esp8266 nodes? Would be nice to know if it works? Btw is the webinterface different for OH2 vs OH1? (because the stock one has that strong ios apperance hehe )

Dne ponedeljek, 13. julij 2015 18.05.23 UTC+2 je oseba Juan Pinto napisala:

[Di Maio, Dario]

Of it works, it will with all supported devices.

Yes the new web interface is html5 and looks different.

Dario.

From Mobile.

--

You received this message because you are subscribed to the Google Groups "souliss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to souliss+u...@googlegroups.com.
To post to this group, send email to sou...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/souliss/9783c010-1b45-4e68-916b-8e2261942a93%40googlegroups.com.

[Juan Pinto]

On OH2 you've a "classic UI" too.

 

Regards

--
You received this message because you are subscribed to a topic in the Google Groups "souliss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/souliss/g6YQ4FroR7k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to souliss+u...@googlegroups.com.

To post to this group, send email to sou...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/souliss/CAKGhMPKUKApHTn%3DADnqiwcMio8ZAsjD1HGYeNPg6zw9k%2B_ApMA%40mail.gmail.com.

[Marko S]

Juan or Dario, so do Souliss nodes or sensors, get autodetected with OpenHAB 2, I've read that now they implemented some sort of auto-detection.

Dne torek, 21. julij 2015 15.55.55 UTC+2 je oseba Juan Pinto napisala:

[Di Maio, Dario]

The openHAB binding is not for openHAB2 and hasn't yet this feature.

Dario.

From Mobile.

To view this discussion on the web visit https://groups.google.com/d/msgid/souliss/85ce4aa8-3d2d-459c-b4be-203aff05b67d%40googlegroups.com.

[Marko S]

Is binding for OH2 planned and if so when?

Dne četrtek, 06. avgust 2015 23.20.30 UTC+2 je oseba Dario Di Maio napisala:

[Antonino Fazio]

Yes, it is planned but we haven't yet started the development.
We hope to start it next month.

[Juan Pinto]

Good to know Antonino :)  We need autodetection on OH :P 

 

If I can help you just tell me :P

 

Regards

[Antonino Fazio]

Hi Juan,
are there some change to do to sintax of items and sitemap?

[Juan Pinto]

Im not sure, but I used the same .items file and works. (I tested some time ago)

 

Regards

 

PD. Praying on autodiscovery function... :P ;)

2015-08-27 8:51 GMT+02:00 Antonino Fazio <faz...@gmail.com>:

Hi Juan,
are there some change to do to sintax of items and sitemap?

--
You received this message because you are subscribed to a topic in the Google Groups "souliss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/souliss/g6YQ4FroR7k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to souliss+u...@googlegroups.com.
To post to this group, send email to sou...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/souliss/14f68f4c-cd2e-4c42-8711-16e03d8fdbba%40googlegroups.com.

[Frederik Vanhollebeke]

Hi

What is the status of the Souliss binding? I am trying it on OH2, but keep getting nullPointerExceptions...
I'm currenlty using: org.openhab.binding.souliss:1.9.0.b5

The error I'm receiving:

2016-12-29 14:15:04.204 [WARN ] [org.apache.karaf.services.eventadmin] - EventAdmin: Exception during event dispatch [org.osgi.service.event.Event [topic=openhab/command/shutter_kitchen1] {bridgemarker=true, item=shutter_kitchen1, command=STOP} | {org.osgi.service.event.EventHandler, org.osgi.service.cm.ManagedService}={event.topics=openhab/*, service.pid=org.openhab.souliss, component.name=org.openhab.binding.souliss, component.id=163, service.id=284, service.bundleid=184, service.scope=bundle} | Bundle(org.openhab.binding.souliss_1.9.0.b5 [184])]
java.lang.NullPointerException
        at org.openhab.binding.souliss.internal.SoulissBinding.receiveCommand(SoulissBinding.java:135)[184:org.openhab.binding.souliss:1.9.0.b5]
        at org.openhab.core.events.AbstractEventSubscriber.handleEvent(AbstractEventSubscriber.java:42)[180:org.openhab.core.compat1x:2.0.0.b5]
        at org.apache.felix.eventadmin.impl.handler.EventHandlerProxy.sendEvent(EventHandlerProxy.java:415)[6:org.apache.karaf.services.eventadmin:4.0.8]
        at org.apache.felix.eventadmin.impl.tasks.HandlerTask.run(HandlerTask.java:90)[6:org.apache.karaf.services.eventadmin:4.0.8]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_77]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_77]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_77]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_77]
        at java.lang.Thread.run(Thread.java:745)[:1.8.0_77]


Thanks for any hints!

Best regards
Fred.



Op donderdag 27 augustus 2015 15:46:29 UTC+2 schreef Juan Pinto:

[Di Maio, Dario]

Hi,

You can use it with OH2 in compatibility, several users are using it in that way.

Regards,
Dario.

From Mobile.

You received this message because you are subscribed to the Google Groups "souliss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to souliss+unsubscribe@googlegroups.com.

To post to this group, send email to sou...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/souliss/7a786dc0-d36d-492d-ab9e-4c71d3842f68%40googlegroups.com.

[Artūrs Stīpnieks]

Hi. Some time has gone since the latest update here, but I think this will be the correct place to discuss a problem I have with Openhab2. 

The issue is that sometimes I got an error from Souliss binding even if I do not directly interact with Souliss. That is, I have dynamic charts with rrd4j and if I change chart period I get this error. The same was when I use weather binding I got that error. And With Mysensors I get this error. Interesting is that Binding seems to work fine, all my nodes works and chart period works as well. For mysensors openhab needs to be restarted to get error disappear.

I did a quick google search and I'm not the only one as it seems. It is interesting that error appears sometimes for people that even do not use Souliss.

https://community.openhab.org/t/yamahareceiver-binding-has-issue-with-zone-2/19731

https://community.openhab.org/t/issue-with-souliss-binding-after-update/20246

I will add error as a picture because I have not it copied. 

EDIT:

It seems that someone has already reported the issue

https://groups.google.com/forum/#!topic/souliss/7eu8E_qJMGc

[Holger Lösken]

Hi Artürs,

the one who reported the issue was me.
Good to see that I am not alone with this problem, but it looks like there is at the moment no progress to develop the souliss binding to Openhab2.

[Artūrs Stīpnieks]

Hi Holger, that's then makes two of us :D 

Are you seen any other problems beside this error itself? 

What other bindings you use?

Maybe it is better to add issue in openhab binding issue tracker, not really sure. 

Is no one else havs problem with this? I guess I have more questions than answers.

It would be nice to see Antonio (If I remember correctly) and Dario opinion about this.

--
You received this message because you are subscribed to a topic in the Google Groups "souliss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/souliss/g6YQ4FroR7k/unsubscribe.

To unsubscribe from this group and all its topics, send an email to souliss+unsubscribe@googlegroups.com.

To post to this group, send email to sou...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/souliss/bd7cc559-e61d-44a8-9255-25293f7030d1%40googlegroups.com.

[Lorenzo Giordano]

Hi guys, we are three...I reported similar error and random delay in the feedback.
I know Tonino promise to review the binding with OH2 on spare time...
There are still the T3x binding to correct since almoust one year.
We need some smart guy who can help Tonino
Ciao
Lorenzo

[Artūrs Stīpnieks]

Sadly I am no help, I can only complain :(

I have no knovlage sadly.

--
You received this message because you are subscribed to a topic in the Google Groups "souliss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/souliss/g6YQ4FroR7k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to souliss+unsubscribe@googlegroups.com.
To post to this group, send email to sou...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/souliss/f1f722f5-85b1-4000-b468-9febeb3506d9%40googlegroups.com.

[Holger Lösken]

Hi,

I posted the issue first in the Openhab community, then I was pointed to this Google Group.
At the moment I am more or less still in the Openhab testphase.
My master souliss nodes works good. My slave node has sometimes very slow reponse, and sometimes stops totally to react.
Restarting Openhab then helps to get everything on track.
Controlling over the Android Souliss App is always ok. So it is an issue wiith the OH-binding.
Well I hope Tonino finds some time to fix this issue.
I am also no big help, besides to run some testing and report the results.

Holger

[Artūrs Stīpnieks]

Interesting, I have newer noticed any slowness on my souliss nodes or gateway. 

To say true I have only one gateway (operational more than a year) and two nodes all included gateway the same (svitch, dht21, relay) all running on ESP-12 based boards.

[Holger Lösken]

After restarting Openhab everything runs fine. Then after about 12h the slave node is no longer working propperly. What I see in OH is that the health status is going down from 255 -> 243 -> 231 and sometimes further down. I pull also the update time from the nodes, it is sometimes 5min behind.
I also saw someone posting in the OH community, that he is looking for a possibility to restart the Souliss binding via timer daily. So there seems to be a common problem.

Holger

[Jammoyano]

I'm using Souliss binding and no problem found yet .. (gtw+3peers)
Have you had a look on OH logs? Could you post the logs to compare?

[Holger Lösken]

Normal execution looks like this in the log:  (I switch the LEDs for 10s on, and for 1s off, just as life signal for the nodes.)

2017-03-17 18:07:18.867 [INFO ] [ding.souliss.internal.SoulissBinding] - receiveCommand - Node0LED = OFF - Typical: 0x11
2017-03-17 18:07:18.873 [INFO ] [ding.souliss.internal.SoulissBinding] - receiveCommand - Node1LED = OFF - Typical: 0x11
2017-03-17 18:07:21.906 [INFO ] [ding.souliss.internal.SoulissBinding] - receiveCommand - Node0LED = ON - Typical: 0x11
2017-03-17 18:07:21.912 [INFO ] [ding.souliss.internal.SoulissBinding] - receiveCommand - Node1LED = ON - Typical: 0x11
2017-03-17 18:07:26.500 [INFO ] [.internal.network.udp.SendDispatcher] - Packet Execution timeout - Requeued
2017-03-17 18:07:26.614 [INFO ] [.internal.network.udp.SendDispatcher] - Packet Execution timeout - Requeued
2017-03-17 18:07:28.119 [INFO ] [.internal.network.udp.SendDispatcher] - Packet Execution timeout - Requeued
2017-03-17 18:07:29.661 [INFO ] [.internal.network.udp.SendDispatcher] - Packet Execution timeout - Requeued
2017-03-17 18:07:31.180 [INFO ] [.internal.network.udp.SendDispatcher] - Packet Execution timeout - Requeued
2017-03-17 18:07:31.921 [INFO ] [ding.souliss.internal.SoulissBinding] - receiveCommand - Node0LED = OFF - Typical: 0x11
2017-03-17 18:07:31.926 [INFO ] [ding.souliss.internal.SoulissBinding] - receiveCommand - Node1LED = OFF - Typical: 0x11

I always get some of the Packet execution timeouts always.... but everything works

Then later  I get:

2017-03-18 00:28:13.248 [WARN ] [org.apache.karaf.services.eventadmin] - EventAdmin: Blacklisting ServiceReference [{org.osgi.service.event.EventHandler, org.osgi.service.cm.ManagedService}={event.topics=openhab/*, service.pid=org.openhab.souliss, component.name=org.openhab.binding.souliss, component.id=155, service.id=290, service.bundleid=184, service.scope=bundle} | Bundle(org.openhab.binding.souliss_1.9.0 [184])] due to timeout!

and after that I see no more Logs from Souliss!

[Lorenzo Giordano]

The situations seems working better with the latest OH2 build ... It is 2 days I did not receive any souliss binding exception error and the T18 feedback seems working better...

By the way if someone can update the binding 1.9 correcting the T31 I will be glad since I just complete a crono weekly Termostat in OH2/HAPPANEL and I would like to test it ...

Tonino...can you at least correct the binding and send to the OH team to update the actual 1.9?

Regards

Lorenzo

[Tejo W. Effendi]

Hello, I have a problem to connect souliss with openhab2. I have an esp12-e as a souliss gateway with latest library, but unable to send command from OH. Android app is working normally.

I see from wireshark that OH server and souliss gateway are communicating every second, but no command is received. Health and timestamp is blank too.

I'm completely new with both souliss and OH, but able to bind network, weather, and create some rules in OH. what information should I give to get help from you guys? I'm thinking about my souliss sketch, souliss.cfg, souliss.items, souliss.sitemap, OH log.

Thank you for your help.

[Tejo W. Effendi]

Hello, here is my files, with hope to get some help.
helloworld.ino

/**************************************************************************

    Souliss - Hello World for Expressif ESP8266

    

    This is the basic example, create a software push-button on Android

    using SoulissApp (get it from Play Store).  

    

    Load this code on ESP8266 board using the porting of the Arduino core

    for this platform.

        

***************************************************************************/

// Let the IDE point to the Souliss framework

#include "SoulissFramework.h"

// Configure the framework

#include "bconf/MCU_ESP8266.h"              // Load the code directly on the ESP8266

#include "conf/Gateway.h"                   // The main node is the Gateway, we have just one node

#include "conf/IPBroadcast.h"

// **** Define the WiFi name and password ****

#define WIFICONF_INSKETCH

#define WiFi_SSID               "wifi"

#define WiFi_Password           "password"    

// Include framework code and libraries

#include <ESP8266WiFi.h>

#include <EEPROM.h>

#include <OneWire.h>

#include <DallasTemperature.h>

/*** All configuration includes should be above this line ***/ 

#include "Souliss.h"

// for debugging

//#define SERIALPORT_INSKETCH

//#define LOG    Serial

// This identify the number of the LED logic

#define MYLEDLOGIC1          0               

#define MYLEDLOGIC2          1               

#define MYLEDLOGIC3          2   

#define MYLEDLOGIC4          3               

// **** Define here the right pin for your ESP module **** 

#define OUTPUTPIN1 D1

#define  OUTPUTPIN2     D2

#define  OUTPUTPIN3     D3

#define  OUTPUTPIN4     D4

#define PRESSURE0             10               // Leave 2 slots for T58

//#define TEMP0                 12               // Leave 2 slots for T52

#define Dallas_1                 4           // This is the memory slot used for the execution of the logic in network_address1

#define DEADBAND            0.01        // Deadband value 1%

#define One_Wire_Bus_Pin  D5

OneWire oneWire(One_Wire_Bus_Pin);

DallasTemperature sensors(&oneWire);

DeviceAddress Temperatura_exterioara =

{0x28, 0x8C, 0x39, 0x26, 0x00, 0x00, 0x80, 0x0B};

void setup()

{   

    Initialize();

    sensors.begin();

    Serial.begin(9600);

    // Connect to the WiFi network and get an address from DHCP

    GetIPAddress();                           

    SetAsGateway(myvNet_dhcp);       // Set this node as gateway for SoulissApp  

    // This is the vNet address for this node, used to communicate with other

// nodes in your Souliss network

    SetAddress(0xAB01, 0xFF00, 0x0000);

    //SetAsPeerNode(0xAB02, 1);

    //SetAsPeerNode(0xAB03, 2);

    //SetAsPeerNode(0xAB04, 3);

   

    Set_SimpleLight(MYLEDLOGIC1);        // Define a simple LED light logic

    Set_SimpleLight(MYLEDLOGIC2);        // Define a simple LED light logic

    Set_SimpleLight(MYLEDLOGIC3);        // Define a simple LED light logic

    Set_SimpleLight(MYLEDLOGIC4);        // Define a simple LED light logic

    pinMode(OUTPUTPIN1, OUTPUT);         // Use pin as output 

    pinMode(OUTPUTPIN2, OUTPUT);         // Use pin as output 

    pinMode(OUTPUTPIN3, OUTPUT);         // Use pin as output

    pinMode(OUTPUTPIN4, OUTPUT);         // Use pin as output

    Set_Pressure(PRESSURE0);

      // Set the typical to use:

  Set_Temperature(Dallas_1);

  sensors.setResolution(Temperatura_exterioara, 10);

}

void loop()

{ 

    // Here we start to play

    

    

    EXECUTEFAST() {                     

        UPDATEFAST();   

        

        FAST_50ms() {   // We process the logic and relevant input and output every 50 milliseconds

            Logic_SimpleLight(MYLEDLOGIC1);

            LowDigOut(OUTPUTPIN1, Souliss_T1n_Coil,MYLEDLOGIC1);

            Logic_SimpleLight(MYLEDLOGIC2);

            LowDigOut(OUTPUTPIN2, Souliss_T1n_Coil,MYLEDLOGIC2);

            Logic_SimpleLight(MYLEDLOGIC3);

            LowDigOut(OUTPUTPIN3, Souliss_T1n_Coil,MYLEDLOGIC3);

            Logic_SimpleLight(MYLEDLOGIC4);

            LowDigOut(OUTPUTPIN4, Souliss_T1n_Coil,MYLEDLOGIC4);

        } 

              FAST_910ms()

    {

      // Aquire temperature from the ADC.

      sensors.requestTemperatures();

      float dallas = sensors.getTempC(Temperatura_exterioara);

      Serial.println(dallas);

      Souliss_ImportAnalog(memory_map, Dallas_1, &dallas);

    }

    FAST_2110ms()

    {

      Logic_Temperature(Dallas_1);

    }

        // Here we handle here the communication with Android

        FAST_GatewayComms();                 

    }

    EXECUTESLOW()

    {   

        UPDATESLOW();

        SLOW_10s()  {

            Logic_Pressure(PRESSURE0);

            

                     

        }

        

        SLOW_50s()  {

          float pressure = 1000;

          

          ImportAnalog(PRESSURE0, &pressure);

          

        }   

    }

    

       

} 

souliss.cfg (souliss gateway get IP 192.168.1.90)

# For ITEM defination in file .item

#{souliss=<Typical>:<nodeID>:<slot>:[<bit>]}

IP_LAN=192.168.1.90

USER_INDEX=79

NODE_INDEX=79

#SERVERPORT - Leave empty for casual port

SERVERPORT=

# time in mills

REFRESH_DBSTRUCT_TIME=600000

REFRESH_SUBSCRIPTION_TIME=120000

REFRESH_HEALTY_TIME=60000

REFRESH_MONITOR_TIME=500

SEND_DELAY=1500

SEND_MIN_DELAY=100

SECURE_SEND_TIMEOUT_TO_REQUEUE=5000

SECURE_SEND_TIMEOUT_TO_REMOVE_PACKET=30000

souliss.items

Group All

Group grp1              (All)

Group Diagnostic        (All)

Group TechnicView_Node0 (All)

Switch SimpleLight1 "SimpleLight5" (grp1, TechnicView_Node0) {souliss="T11:0:0", autoupdate=“true”}

Switch SimpleLight2 "SimpleLight6" (grp1, TechnicView_Node0) {souliss="T11:0:1", autoupdate=“true”}

Switch SimpleLight3 "SimpleLight7" (grp1, TechnicView_Node0) {souliss="T11:0:2", autoupdate=“true”}

Switch SimpleLight4 "SimpleLight8" (grp1, TechnicView_Node0) {souliss="T11:0:3", autoupdate=“true”}

Number HEALTHNodo0 "Health Node 0 [%1d]” <keyring> (Diagnostic, TechnicView_Node0, Health) {souliss="D98:0:998"}

String TIMESTAMP_Nodo0 "Update Node 0 [%1$td.%1$tm.%1$tY %1$tk:%1$tM:%1$tS]" <keyring> (Diagnostic, TechnicView_Node0) {souliss="D99:0:999"}

souliss.sitemap

sitemap souliss1 label="Main Menu"

{

Frame label="Souliss - Hello World" {

Switch item=SimpleLight1 mappings=[ON="ON", OFF="OFF"]

Switch item=SimpleLight2 mappings=[ON="ON", OFF="OFF"]

Switch item=SimpleLight3 mappings=[ON="ON", OFF="OFF"]

Switch item=SimpleLight4 mappings=[ON="ON", OFF="OFF"]

Text item=HEALTHNodo0 icon="icon16x16"

Text item=TIMESTAMP_Nodo0 icon="icon16x16"

}

}

I also attached a screenshot of wireshark that is sniffing OH - souliss communication

[Lorenzo Giordano]

A stupid question... 

did you install the Souliss binding in paper ui? 

did you enable the 1x former binding in OH2 setting?

The attached seems ok...

Regards

Lorenzo

[sat...@gmail.com]

[sat...@gmail.com]

 Hi  Dario

Openhab2 on RPI3 and Souliss binding (OH2_binding_beta-20170924T13104Z-001)  following  log on openhab 

       please guide 

      Regards

      Satek

2017-09-25 21:03:22.826 [INFO ] [thome.io.rest.core.item.ItemResource] - Received HTTP POST request at 'items/LEDLT3' for the unknown item 'LEDLT3'.
2017-09-25 21:04:56.869 [ThingRemovedEvent         ] - Thing 'souliss:gateway:159' has been removed.
2017-09-25 21:05:55.399 [WARN ] [el.core.internal.ModelRepositoryImpl] - Configuration model 'souliss.items' has errors, therefore ignoring it: [7,82]: mismatched input '“' expecting RULE_STRING
2017-09-25 21:06:19.559 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'souliss.sitemap'
2017-09-25 21:06:21.200 [ThingAddedEvent           ] - Thing 'souliss:gateway:159' has been added.
2017-09-25 21:06:32.747 [INFO ] [otocol.SoulissBindingUDPServerThread] - Starting UDP Server Thread - Server on port 56527
2017-09-25 21:06:52.662 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occurred while calling thing handler factory 'org.openhab.binding.souliss.internal.SoulissHandlerFactory@18e5d74': Value out of range. Value:"159" Radix:10
	at org.openhab.binding.souliss.internal.SoulissHandlerFactory.createHandler(SoulissHandlerFactory.java:71)[231:org.openhab.binding.souliss:2.1.0.201709181958]
2017-09-25 21:06:52.701 [hingStatusInfoChangedEvent] - 'souliss:gateway:159' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_REGISTERING_ERROR): Value out of range. Value:"159" Radix:10
2017-09-25 21:19:11.298 [INFO ] [thome.io.rest.core.item.ItemResource] - Received HTTP POST request at 'items/LEDLT4' for the unknown item 'LEDLT4'.

[Luciano Bono]

Hello, I'm testing the latest version of the binding,

  excellent work! (org.openhab.binding.souliss_2.1.0.201710160124 (OH2 current) .jar) taken from here: https://drive.google.com/drive/folders/0BzYvfLL0ppGAalRxLVhjZ1hXVW8

I have 2 problems, the T13 are updated correctly in the log, but the stateOnOff parameter is not reflected in the sitemap, is it necessary to do some mapping?

On the other hand, and most serious, is that the cpu of my Rpi2 goes to 100% when I use the binding.

Is there a repository in Github for further development?

Regards.-

El domingo, 12 de julio de 2015, 5:56:56 (UTC-3), Dario Di Maio escribió:

Have someone used Souliss over openHAB 2? Please share your tips.

Dario.

From Mobile.

[Tonino Fazio]

Have you oh log when CPU ho 100?

T13. It woek in PaperUI?

--

You received this message because you are subscribed to a topic in the Google Groups "souliss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/souliss/g6YQ4FroR7k/unsubscribe.

To unsubscribe from this group and all its topics, send an email to souliss+u...@googlegroups.com.

To post to this group, send email to sou...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/souliss/c679c1df-4e4b-42f4-ba80-b39a5f87dc34%40googlegroups.com.

[Luciano Bono]

Here is the log:

2017-10-19 23:58:09.505 [INFO ] [otocol.SoulissBindingUDPServerThread] - Starting UDP Server Thread - Server on port 52910
2017-10-19 23:58:45.947 [INFO ] [otocol.SoulissBindingUDPServerThread] - Starting UDP Server Thread - Server on port 230
2017-10-19 23:58:46.371 [ItemStateEvent            ] - souliss_t13_0_9_lastStatusStored updated to 2017-10-19T23:58:46.220-0300
2017-10-19 23:58:46.387 [ItemStateEvent            ] - souliss_t13_0_9_stateOnOff updated to ON
2017-10-19 23:58:46.450 [ItemStateEvent            ] - souliss_t13_0_16_lastStatusStored updated to 2017-10-19T23:58:46.432-0300
2017-10-19 23:58:46.463 [ItemStateEvent            ] - souliss_t13_0_16_stateOnOff updated to ON
2017-10-19 23:58:46.537 [ItemStateEvent            ] - souliss_t13_0_7_lastStatusStored updated to 2017-10-19T23:58:46.520-0300
2017-10-19 23:58:46.543 [ItemStateEvent            ] - souliss_t13_0_7_stateOnOff updated to ON
2017-10-19 23:58:46.590 [ItemStateEvent            ] - souliss_t13_0_8_lastStatusStored updated to 2017-10-19T23:58:46.572-0300
2017-10-19 23:58:46.596 [ItemStateEvent            ] - souliss_t13_0_8_stateOnOff updated to ON
2017-10-19 23:58:46.626 [ItemStateEvent            ] - souliss_t11_1_0_onoff updated to OFF
2017-10-19 23:58:46.683 [ItemStateEvent            ] - souliss_t13_0_5_lastStatusStored updated to 2017-10-19T23:58:46.660-0300
2017-10-19 23:58:46.695 [ItemStateEvent            ] - souliss_t13_0_6_lastStatusStored updated to 2017-10-19T23:58:46.674-0300
2017-10-19 23:58:46.711 [ItemStateEvent            ] - souliss_t13_0_3_lastStatusStored updated to 2017-10-19T23:58:46.684-0300
2017-10-19 23:58:46.727 [ItemStateEvent            ] - souliss_t13_0_3_stateOnOff updated to ON
2017-10-19 23:58:46.848 [ItemStateEvent            ] - souliss_t13_0_4_lastStatusStored updated to 2017-10-19T23:58:46.832-0300
2017-10-19 23:58:46.866 [ItemStateEvent            ] - souliss_t13_0_5_healty updated to 255
2017-10-19 23:58:46.880 [ItemStateEvent            ] - souliss_t13_0_6_healty updated to 255
2017-10-19 23:58:46.891 [ItemStateEvent            ] - souliss_t13_0_4_healty updated to 255
2017-10-19 23:58:46.900 [ItemStateEvent            ] - souliss_t52_0_12_healty updated to 255
2017-10-19 23:58:46.907 [ItemStateEvent            ] - souliss_t13_0_1_healty updated to 255
2017-10-19 23:58:46.915 [ItemStateEvent            ] - souliss_t13_0_2_healty updated to 255
2017-10-19 23:58:46.927 [ItemStateEvent            ] - souliss_t13_0_9_healty updated to 255
2017-10-19 23:58:46.940 [ItemStateEvent            ] - souliss_t53_0_14_healty updated to 255
2017-10-19 23:58:46.952 [ItemStateEvent            ] - souliss_t13_0_16_healty updated to 255
2017-10-19 23:58:46.965 [ItemStateEvent            ] - souliss_t13_0_7_healty updated to 255
2017-10-19 23:58:46.978 [ItemStateEvent            ] - souliss_t41_0_0_healty updated to 255
2017-10-19 23:58:46.987 [ItemStateEvent            ] - souliss_t13_0_8_healty updated to 255
2017-10-19 23:58:46.997 [ItemStateEvent            ] - souliss_t13_0_3_healty updated to 255
2017-10-19 23:58:51.114 [ItemStateEvent            ] - souliss_t11_1_0_lastStatusStored updated to 2017-10-19T23:58:50.936-0300
2017-10-19 23:58:51.137 [ItemStateEvent            ] - souliss_t11_1_0_sleep updated to OFF
2017-10-19 23:59:16.942 [ItemStateEvent            ] - souliss_t13_0_5_lastStatusStored updated to 2017-10-19T23:59:16.903-0300
2017-10-19 23:59:16.954 [ItemStateEvent            ] - souliss_t13_0_6_lastStatusStored updated to 2017-10-19T23:59:16.911-0300
2017-10-19 23:59:16.975 [ItemStateEvent            ] - souliss_t13_0_4_lastStatusStored updated to 2017-10-19T23:59:16.928-0300
2017-10-19 23:59:16.985 [ItemStateEvent            ] - souliss_t52_0_12_lastStatusStored updated to 2017-10-19T23:59:16.938-0300
2017-10-19 23:59:16.998 [ItemStateEvent            ] - souliss_t52_0_12_value updated to 22.0
2017-10-19 23:59:17.014 [ItemStateEvent            ] - souliss_t13_0_1_lastStatusStored updated to 2017-10-19T23:59:16.951-0300
2017-10-19 23:59:17.025 [ItemStateEvent            ] - souliss_t13_0_2_lastStatusStored updated to 2017-10-19T23:59:16.963-0300
2017-10-19 23:59:17.044 [ItemStateEvent            ] - souliss_t13_0_9_lastStatusStored updated to 2017-10-19T23:59:16.968-0300
2017-10-19 23:59:17.078 [ItemStateEvent            ] - souliss_t53_0_14_lastStatusStored updated to 2017-10-19T23:59:16.977-0300
2017-10-19 23:59:17.090 [ItemStateEvent            ] - souliss_t53_0_14_value updated to 36.0
2017-10-19 23:59:17.109 [ItemStateEvent            ] - souliss_t13_0_16_lastStatusStored updated to 2017-10-19T23:59:16.994-0300
2017-10-19 23:59:17.122 [ItemStateEvent            ] - souliss_t13_0_7_lastStatusStored updated to 2017-10-19T23:59:17.002-0300
2017-10-19 23:59:17.129 [ItemStateEvent            ] - souliss_t41_0_0_onOffAlarm updated to OFF
2017-10-19 23:59:17.137 [ItemStateEvent            ] - souliss_t41_0_0_rearmAlarm updated to OFF
2017-10-19 23:59:17.160 [ItemStateEvent            ] - souliss_t41_0_0_lastStatusStored updated to 2017-10-19T23:59:17.014-0300
2017-10-19 23:59:17.169 [ItemStateEvent            ] - souliss_t41_0_0_rearmAlarm updated to OFF
2017-10-19 23:59:17.185 [ItemStateEvent            ] - souliss_t41_0_0_lastStatusStored updated to 2017-10-19T23:59:17.063-0300
2017-10-19 23:59:17.199 [ItemStateEvent            ] - souliss_t13_0_8_lastStatusStored updated to 2017-10-19T23:59:17.099-0300
2017-10-19 23:59:17.214 [ItemStateEvent            ] - souliss_t13_0_3_lastStatusStored updated to 2017-10-19T23:59:17.105-0300
2017-10-19 23:59:20.909 [ItemStateEvent            ] - souliss_t13_0_5_lastStatusStored updated to 2017-10-19T23:59:20.894-0300
2017-10-19 23:59:20.919 [ItemStateEvent            ] - souliss_t13_0_5_stateOnOff updated to ON
2017-10-19 23:59:20.934 [ItemStateEvent            ] - souliss_t13_0_6_lastStatusStored updated to 2017-10-19T23:59:20.917-0300
2017-10-19 23:59:20.948 [ItemStateEvent            ] - souliss_t13_0_4_lastStatusStored updated to 2017-10-19T23:59:20.924-0300
2017-10-19 23:59:20.960 [ItemStateEvent            ] - souliss_t52_0_12_lastStatusStored updated to 2017-10-19T23:59:20.936-0300
2017-10-19 23:59:20.966 [ItemStateEvent            ] - souliss_t52_0_12_value updated to 22.0
2017-10-19 23:59:20.978 [ItemStateEvent            ] - souliss_t13_0_1_lastStatusStored updated to 2017-10-19T23:59:20.952-0300
2017-10-19 23:59:20.998 [ItemStateEvent            ] - souliss_t13_0_2_lastStatusStored updated to 2017-10-19T23:59:20.965-0300
2017-10-19 23:59:21.014 [ItemStateEvent            ] - souliss_t13_0_9_lastStatusStored updated to 2017-10-19T23:59:20.971-0300
2017-10-19 23:59:21.030 [ItemStateEvent            ] - souliss_t53_0_14_lastStatusStored updated to 2017-10-19T23:59:20.981-0300
2017-10-19 23:59:21.038 [ItemStateEvent            ] - souliss_t53_0_14_value updated to 36.0
2017-10-19 23:59:21.051 [ItemStateEvent            ] - souliss_t13_0_16_lastStatusStored updated to 2017-10-19T23:59:20.988-0300
2017-10-19 23:59:21.070 [ItemStateEvent            ] - souliss_t13_0_7_lastStatusStored updated to 2017-10-19T23:59:20.993-0300
2017-10-19 23:59:21.085 [ItemStateEvent            ] - souliss_t13_0_8_lastStatusStored updated to 2017-10-19T23:59:21.002-0300
2017-10-19 23:59:21.101 [ItemStateEvent            ] - souliss_t13_0_3_lastStatusStored updated to 2017-10-19T23:59:21.008-0300
2017-10-19 23:59:21.110 [ItemStateEvent            ] - souliss_t41_0_0_onOffAlarm updated to OFF

...And continue like this.

With TOP, Souliss Binding running:

top - 00:18:04 up 3 days,  5:14,  2 users,  load average: 1.58, 1.59, 1.17
Tasks: 128 total,   1 running, 127 sleeping,   0 stopped,   0 zombie
%Cpu(s): 12.8 us, 19.1 sy,  0.0 ni, 68.0 id,  0.0 wa,  0.0 hi,  0.1 si,  0.0 st
KiB Mem:    994236 total,   622900 used,   371336 free,    55568 buffers
KiB Swap:   102396 total,        0 used,   102396 free.   324024 cached Mem


  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
30173 openhab   20   0  454416 174480  12636 S 123.3 17.5  22:37.99 java
  722 openhab   20   0  124504  34632  17604 S   2.0  3.5   1:51.76 node
30019 openhab+  20   0    6804   2420   2012 R   1.0  0.2   0:09.27 top
  941 openhab   20   0    5128   1444   1352 S   0.3  0.1   0:09.85 tail
29161 root      20   0       0      0      0 S   0.3  0.0   0:00.31 kworker/1:1
31065 root      20   0       0      0      0 S   0.3  0.0   0:00.05 kworker/u8:1
    1 root      20   0    5476   3900   2732 S   0.0  0.4   0:23.77 systemd
    2 root      20   0       0      0      0 S   0.0  0.0   0:00.37 kthreadd
    3 root      20   0       0      0      0 S   0.0  0.0   0:08.07 ksoftirqd/0
    5 root       0 -20       0      0      0 S   0.0  0.0   0:00.00 kworker/0:0H
    7 root      20   0       0      0      0 S   0.0  0.0   1:17.85 rcu_sched
    8 root      20   0       0      0      0 S   0.0  0.0   0:00.00 rcu_bh
    9 root      rt   0       0      0      0 S   0.0  0.0   0:00.53 migration/0
   10 root       0 -20       0      0      0 S   0.0  0.0   0:00.00 lru-add-drain
   11 root      20   0       0      0      0 S   0.0  0.0   0:00.00 cpuhp/0
   12 root      20   0       0      0      0 S   0.0  0.0   0:00.00 cpuhp/1
   13 root      rt   0       0      0      0 S   0.0  0.0   0:00.69 migration/1
   14 root      20   0       0      0      0 S   0.0  0.0   0:00.41 ksoftirqd/1
   16 root       0 -20       0      0      0 S   0.0  0.0   0:00.00 kworker/1:0H
   17 root      20   0       0      0      0 S   0.0  0.0   0:00.00 cpuhp/2
   18 root      rt   0       0      0      0 S   0.0  0.0   0:00.49 migration/2
   19 root      20   0       0      0      0 S   0.0  0.0   0:07.20 ksoftirqd/2
   21 root       0 -20       0      0      0 S   0.0  0.0   0:00.00 kworker/2:0H

When Souliss stoped, with bundle:stop in Karaf console:

top - 00:25:42 up 3 days,  5:21,  2 users,  load average: 0.09, 0.68, 0.93
Tasks: 131 total,   1 running, 130 sleeping,   0 stopped,   0 zombie
%Cpu(s):  2.5 us,  0.8 sy,  0.0 ni, 96.7 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem:    994236 total,   625124 used,   369112 free,    55568 buffers
KiB Swap:   102396 total,        0 used,   102396 free.   324104 cached Mem


  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
31675 root      20   0    9204   4316   3864 S   4.6  0.4   0:00.14 sshd
30173 openhab   20   0  454436 175936  12828 S   3.3 17.7  26:54.41 java
31678 sshd      20   0    9204   1868   1416 S   2.3  0.2   0:00.07 sshd
30019 openhab+  20   0    6804   2420   2012 R   0.7  0.2   0:13.24 top
  398 root      20   0       0      0      0 S   0.3  0.0   2:19.05 RTW_CMD_THREAD
31339 root      20   0       0      0      0 S   0.3  0.0   0:00.21 kworker/0:1
    1 root      20   0    5476   3900   2732 S   0.0  0.4   0:23.80 systemd
    2 root      20   0       0      0      0 S   0.0  0.0   0:00.37 kthreadd
    3 root      20   0       0      0      0 S   0.0  0.0   0:08.10 ksoftirqd/0
    5 root       0 -20       0      0      0 S   0.0  0.0   0:00.00 kworker/0:0H
    7 root      20   0       0      0      0 S   0.0  0.0   1:18.11 rcu_sched
    8 root      20   0       0      0      0 S   0.0  0.0   0:00.00 rcu_bh
    9 root      rt   0       0      0      0 S   0.0  0.0   0:00.53 migration/0
   10 root       0 -20       0      0      0 S   0.0  0.0   0:00.00 lru-add-drain
   11 root      20   0       0      0      0 S   0.0  0.0   0:00.00 cpuhp/0
   12 root      20   0       0      0      0 S   0.0  0.0   0:00.00 cpuhp/1
   13 root      rt   0       0      0      0 S   0.0  0.0   0:00.69 migration/1
   14 root      20   0       0      0      0 S   0.0  0.0   0:00.41 ksoftirqd/1
   16 root       0 -20       0      0      0 S   0.0  0.0   0:00.00 kworker/1:0H
   17 root      20   0       0      0      0 S   0.0  0.0   0:00.00 cpuhp/2

I added the gateway and nodes from the Paper UI autodiscovery, and then I got the auto-created names (simple mode enabled) for items from the BD JSON, so is my .items:

Group All Group Alarma "Alarma" (All) Group Sensores "Sensores" (All) Group Estados "Estado de los nodos" (All) Group Luces "Luces" (All) // El nombre de los items sale del autodiscovery de Paper UI // Gateway // Entradas Alarma Contact souliss_t13_0_1_stateOnOff (Alarma) {souliss="T13:0:1", autoupdate="true"} Contact souliss_t13_0_2_stateOnOff (Alarma) {souliss="T13:0:2", autoupdate="true"} Contact souliss_t13_0_3_stateOnOff (Alarma) {souliss="T13:0:3", autoupdate="true"} Contact souliss_t13_0_4_stateOnOff (Alarma) {souliss="T13:0:4", autoupdate="true"} Contact souliss_t13_0_5_stateOnOff (Alarma) {souliss="T13:0:5", autoupdate="true"} Contact souliss_t13_0_6_stateOnOff (Alarma) {souliss="T13:0:6", autoupdate="true"} Contact souliss_t13_0_7_stateOnOff (Alarma) {souliss="T13:0:7", autoupdate="true"} Contact souliss_t13_0_8_stateOnOff (Alarma) {souliss="T13:0:8", autoupdate="true"} // Sensor DHT11 en el Gateway Number souliss_t52_0_12_value "[%.1f °C]" (Sensores) {souliss="T52:0:12"} // souliss=" typical : ID nodo : slot " Number souliss_t53_0_14_value "[%.1f %%]" (Sensores) {souliss="T53:0:14"} // Nodo Cochera Switch souliss_t11_1_0_onoff "Luz Cochera" <light> (Luces) {souliss="T11:1:0"}

And my sitemap:

sitemap Souliss label="Red Souliss"

{

Frame label="Alarma"{

Text item=souliss_t13_0_1_stateOnOff label="Entrada 1" 

Text    item=souliss_t13_0_1_stateOnOff label="Entrada 2" 

Text    item=souliss_t13_0_1_stateOnOff label="Entrada 3"

    Text    item=souliss_t13_0_1_stateOnOff label="Entrada 4"

Text    item=souliss_t13_0_1_stateOnOff label="Entrada 5"

Text    item=souliss_t13_0_1_stateOnOff label="Entrada 6"

Text    item=souliss_t13_0_1_stateOnOff label="Entrada 7"

    Text    item=souliss_t13_0_1_stateOnOff label="Entrada 8"

}

Frame label="Sensores"{

Text item=souliss_t52_0_12_value icon="temperature" label="Temperatura Fuera"

Text item=souliss_t53_0_14_value icon="humidity"    label="Humedad Fuera"

}

Frame label="Luces"{

Switch item=souliss_t11_1_0_onoff icon="light"       label="Luz Cochera"

}

}

Regards.-

[Luciano Bono]

With Souliss stopped from bundle:stop in the Karaf console:

top - 00:33:53 up 3 days,  5:30,  2 users,  load average: 0.13, 0.24, 0.59
Tasks: 130 total,   1 running, 129 sleeping,   0 stopped,   0 zombie
%Cpu(s):  2.2 us,  0.4 sy,  0.0 ni, 97.4 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem:    994236 total,   628060 used,   366176 free,    55568 buffers
KiB Swap:   102396 total,        0 used,   102396 free.   324132 cached Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND

32261 root      20   0    9204   4324   3872 S   4.6  0.4   0:00.14 sshd
32262 sshd      20   0    9204   1828   1376 S   2.6  0.2   0:00.08 sshd
30173 openhab   20   0  454436 178708  12828 S   2.0 18.0  27:08.75 java
30019 openhab+  20   0    6804   2420   2012 R   1.0  0.2   0:18.33 top
29161 root      20   0       0      0      0 S   0.3  0.0   0:00.45 kworker/1:1
    1 root      20   0    5476   3900   2732 S   0.0  0.4   0:23.83 systemd
    2 root      20   0       0      0      0 S   0.0  0.0   0:00.37 kthreadd
    3 root      20   0       0      0      0 S   0.0  0.0   0:08.13 ksoftirqd/0

    5 root       0 -20       0      0      0 S   0.0  0.0   0:00.00 kworker/0:0H

    7 root      20   0       0      0      0 S   0.0  0.0   1:18.36 rcu_sched
    8 root      20   0       0      0      0 S   0.0  0.0   0:00.00 rcu_bh
    9 root      rt   0       0      0      0 S   0.0  0.0   0:00.53 migration/0

   10 root       0 -20       0      0      0 S   0.0  0.0   0:00.00 lru-add-drain
   11 root      20   0       0      0      0 S   0.0  0.0   0:00.00 cpuhp/0
   12 root      20   0       0      0      0 S   0.0  0.0   0:00.00 cpuhp/1
   13 root      rt   0       0      0      0 S   0.0  0.0   0:00.69 migration/1

   14 root      20   0       0      0      0 S   0.0  0.0   0:00.42 ksoftirqd/1

   16 root       0 -20       0      0      0 S   0.0  0.0   0:00.00 kworker/1:0H
   17 root      20   0       0      0      0 S   0.0  0.0   0:00.00 cpuhp/2
   18 root      rt   0       0      0      0 S   0.0  0.0   0:00.49 migration/2

   19 root      20   0       0      0      0 S   0.0  0.0   0:07.23 ksoftirqd/2

   21 root       0 -20       0      0      0 S   0.0  0.0   0:00.00 kworker/2:0H

   22 root      20   0       0      0      0 S   0.0  0.0   0:00.00 cpuhp/3
   23 root      rt   0       0      0      0 S   0.0  0.0   0:00.56 migration/3
   24 root      20   0       0      0      0 S   0.0  0.0   0:00.36 ksoftirqd/3

I added the gateway and nodes from the Paper UI autodiscovery, and then I got the auto-created names (simple mode enabled) for items from the BD JSON, so is my .items:

Group All Group Alarma "Alarma" (All) Group Sensores "Sensores" (All) Group Estados "Estado de los nodos" (All) Group Luces "Luces" (All) // El nombre de los items sale del autodiscovery de Paper UI // Gateway // Entradas Alarma Contact souliss_t13_0_1_stateOnOff (Alarma) {souliss="T13:0:1", autoupdate="true"} Contact souliss_t13_0_2_stateOnOff (Alarma) {souliss="T13:0:2", autoupdate="true"} Contact souliss_t13_0_3_stateOnOff (Alarma) {souliss="T13:0:3", autoupdate="true"} Contact souliss_t13_0_4_stateOnOff (Alarma) {souliss="T13:0:4", autoupdate="true"} Contact souliss_t13_0_5_stateOnOff (Alarma) {souliss="T13:0:5", autoupdate="true"} Contact souliss_t13_0_6_stateOnOff (Alarma) {souliss="T13:0:6", autoupdate="true"} Contact souliss_t13_0_7_stateOnOff (Alarma) {souliss="T13:0:7", autoupdate="true"} Contact souliss_t13_0_8_stateOnOff (Alarma) {souliss="T13:0:8", autoupdate="true"} // Sensor DHT11 en el Gateway Number souliss_t52_0_12_value "[%.1f °C]" (Sensores) {souliss="T52:0:12"} // souliss=" typical : ID nodo : slot " Number souliss_t53_0_14_value "[%.1f %%]" (Sensores) {souliss="T53:0:14"} // Nodo Cochera Switch souliss_t11_1_0_onoff "Luz Cochera" <light> (Luces) {souliss="T11:1:0"}

And my Sitemap:

sitemap Souliss label="Red Souliss"

{

Frame label="Alarma"{

Text item=souliss_t13_0_1_stateOnOff label="Entrada 1" 

Text    item=souliss_t13_0_1_stateOnOff label="Entrada 2" 

Text    item=souliss_t13_0_1_stateOnOff label="Entrada 3"

    Text    item=souliss_t13_0_1_stateOnOff label="Entrada 4"

Text    item=souliss_t13_0_1_stateOnOff label="Entrada 5"

Text    item=souliss_t13_0_1_stateOnOff label="Entrada 6"

Text    item=souliss_t13_0_1_stateOnOff label="Entrada 7"

    Text    item=souliss_t13_0_1_stateOnOff label="Entrada 8"

}

Frame label="Sensores"{

Text item=souliss_t52_0_12_value icon="temperature" label="Temperatura Fuera"

Text item=souliss_t53_0_14_value icon="humidity"    label="Humedad Fuera"

}

Frame label="Luces"{

Switch item=souliss_t11_1_0_onoff icon="light"       label="Luz Cochera"

}

}

t13s work fine from paper ui, but are not updated in Basic UI.

Regards.-

[Luciano Bono]

I added the gateway and nodes from the Paper UI autodiscovery, and then I got the auto-created names (simple mode enabled) for items from the BD JSON, so is my .items:

Group All Group Alarma "Alarma" (All) Group Sensores "Sensores" (All) Group Estados "Estado de los nodos" (All) Group Luces "Luces" (All) // El nombre de los items sale del autodiscovery de Paper UI // Gateway // Entradas Alarma Contact souliss_t13_0_1_stateOnOff (Alarma) {souliss="T13:0:1", autoupdate="true"} Contact souliss_t13_0_2_stateOnOff (Alarma) {souliss="T13:0:2", autoupdate="true"} Contact souliss_t13_0_3_stateOnOff (Alarma) {souliss="T13:0:3", autoupdate="true"} Contact souliss_t13_0_4_stateOnOff (Alarma) {souliss="T13:0:4", autoupdate="true"} Contact souliss_t13_0_5_stateOnOff (Alarma) {souliss="T13:0:5", autoupdate="true"} Contact souliss_t13_0_6_stateOnOff (Alarma) {souliss="T13:0:6", autoupdate="true"} Contact souliss_t13_0_7_stateOnOff (Alarma) {souliss="T13:0:7", autoupdate="true"} Contact souliss_t13_0_8_stateOnOff (Alarma) {souliss="T13:0:8", autoupdate="true"} // Sensor DHT11 en el Gateway Number souliss_t52_0_12_value "[%.1f °C]" (Sensores) {souliss="T52:0:12"} // souliss=" typical : ID nodo : slot " Number souliss_t53_0_14_value "[%.1f %%]" (Sensores) {souliss="T53:0:14"} // Nodo Cochera Switch souliss_t11_1_0_onoff "Luz Cochera" <light> (Luces) {souliss="T11:1:0"}

And my Sitemap:

sitemap Souliss label="Red Souliss"

{

Frame label="Alarma"{

Text item=souliss_t13_0_1_stateOnOff label="Entrada 1" 

Text    item=souliss_t13_0_1_stateOnOff label="Entrada 2" 

Text    item=souliss_t13_0_1_stateOnOff label="Entrada 3"

    Text    item=souliss_t13_0_1_stateOnOff label="Entrada 4"

Text    item=souliss_t13_0_1_stateOnOff label="Entrada 5"

Text    item=souliss_t13_0_1_stateOnOff label="Entrada 6"

Text    item=souliss_t13_0_1_stateOnOff label="Entrada 7"

    Text    item=souliss_t13_0_1_stateOnOff label="Entrada 8"

}

Frame label="Sensores"{

Text item=souliss_t52_0_12_value icon="temperature" label="Temperatura Fuera"

Text item=souliss_t53_0_14_value icon="humidity"    label="Humedad Fuera"

}

Frame label="Luces"{

Switch item=souliss_t11_1_0_onoff icon="light"       label="Luz Cochera"

}

}

t13s work fine from paper ui, but are not updated in Basic UI.

Regards.-

   21 root       0 -20       0<span style="color

[Antonino Fazio]

No. Wrong sintax.
Look at https://groups.google.com/forum/m/#!topic/souliss-it/ZXLwCXw6-f8
At paragraph "Sintassi"

You must declare items with this:
{channel="souliss:Txx:node-slot:channelName}

Example:
Switch SwitchPortoncino "Portoncino" (G_Soggiorno) { channel="souliss:T11:1-6:value", autoupdate="false" }

Tonino

[Luciano Bono]

Thanks for the reply.

I have corrected the syntax of the items, yet the T13s do not work, and the CPU of the Pi is still 100%. Any other suggestions?

Group All

Group Alarma "Alarma" (All)

Group Sensores "Sensores" (All)

Group Estados "Estado de los nodos" (All)

Group Luces    "Luces" (All)

// El nombre de los items sale del autodiscovery de Paper UI

// Gateway

// Entradas Alarma

Contact  Entrada1 (Alarma) {channel="souliss:t13:0-1:stateOnOff", autoupdate="true"}

Contact  Entrada2 (Alarma) {channel="souliss:T13:0-2:stateOnOff", autoupdate="true"}

Contact  Entrada3 (Alarma) {channel="souliss:T13:0-3:stateOnOff", autoupdate="true"}

Contact  Entrada4 (Alarma) {channel="souliss:T13:0-4:stateOnOff", autoupdate="true"}

Contact  Entrada5 (Alarma) {channel="souliss:T13:0-5:stateOnOff", autoupdate="true"}

Contact  Entrada6 (Alarma) {channel="souliss:T13:0-6:stateOnOff", autoupdate="true"}

Contact  Entrada7 (Alarma) {channel="souliss:T13:0-7:stateOnOff", autoupdate="true"}

Contact  Entrada8 (Alarma) {channel="souliss:T13:0-8:stateOnOff", autoupdate="true"}

// Sensor DHT11 en el Gateway

Number TemperaturaFuera "[%.1f °C]" (Sensores) {channel="souliss:t52:0-12:value"} 

Number HumedadFuera "[%.1f %%]" (Sensores) {channel="souliss:T53:0-14:value"}

// Nodo Cochera

Switch LuzCochera (Luces) {channel="souliss:t11:1-0:onoff", autoupdate="false"}

[Juan Pinto]

Hi, I have a problem with T54, here is a log:
https://pastebin.com/FPPcnwcv

Other T5x works well.

Thanks

[Tonino Fazio]

Fixed.

Try latest version...

Tonino Fazio

[Luciano Bono]

Hi Juan, do you check the cpu usage?

It's going to 100% on mi Pi when I use Souliss binding.

[stef mertens]

Hi Everybody,

I have installed Openhab 2.1 on a windows PC. For testing purposes i have a simple gateway on an ESP8266 with one T19 dimmable light.

After installing the openhab souliss binding, Openhab discovered my 'thing' very well. - i did not have to write config files or anything. 
I also installed the Philips Hue binding, since i have a HUE gateway and some rgb bulbs. the control fine.

The thing is: my T19 and gateway are discovered well, but when I try to control it, none of the brightness sliders work. The T19 is presented as a few parts: a rollershutter and a dimmer. The up/down buttons of the rollershutter do control my ledwall, but none of the sliders work. 

Does anybody have an idea on where to check configuration files to sort this out? The automatic discovery feature doesn't seem to write any files in the 'conf' folder.

Thanks in advance,

Stef

Op zondag 12 juli 2015 10:56:56 UTC+2 schreef Dario Di Maio:

[Luciano Bono]

This is happening with the latest version:

openhab> Exception in thread "Thread-32" java.lang.NullPointerException

        at org.openhab.binding.souliss.internal.protocol.SoulissBindingUDPDecoder.decodeHealthyRequest(SoulissBindingUDPDecoder.java:357)

        at org.openhab.binding.souliss.internal.protocol.SoulissBindingUDPDecoder.decodeMacaco(SoulissBindingUDPDecoder.java:130)

        at org.openhab.binding.souliss.internal.protocol.SoulissBindingUDPDecoder.decodeVNetDatagram(SoulissBindingUDPDecoder.java:85)

        at org.openhab.binding.souliss.internal.protocol.SoulissBindingUDPServerThread.run(SoulissBindingUDPServerThread.java:77)

Exception in thread "Thread-50" java.lang.NullPointerException

        at org.openhab.binding.souliss.handler.SoulissGatewayHandler.pingSent(SoulissGatewayHandler.java:250)

        at org.openhab.binding.souliss.handler.SoulissGatewayThread.run(SoulissGatewayThread.java:58)

The CPU of mi Rpi is still above 100% when activating the binding.

[Jose Luis Sánchez Muñoz]

Hello!

I have a problem with the last binding of souliss in openhab 2.2.0.

When restarting the server, everything works perfect, but at 24 / 48h the Gateway fails to ping with the server and disconnects. And from there it is never updated again with the server.

Can you help me??

==> /var/log/openhab2/events.log <==

2017-12-25 18:18:51.005 [hingStatusInfoChangedEvent] - 'souliss:gateway:78' changed from OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:78 do not respond to 16 ping to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:78 do not respond to 17 ping

2017-12-25 18:19:21.055 [hingStatusInfoChangedEvent] - 'souliss:gateway:78' changed from OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:78 do not respond to 17 ping to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:78 do not respond to 18 ping

2017-12-25 18:19:51.073 [hingStatusInfoChangedEvent] - 'souliss:gateway:78' changed from OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:78 do not respond to 18 ping to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:78 do not respond to 19 ping

2017-12-25 18:20:21.092 [hingStatusInfoChangedEvent] - 'souliss:gateway:78' changed from OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:78 do not respond to 19 ping to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:78 do not respond to 20 ping

2017-12-25 18:20:35.389 [me.event.ThingUpdatedEvent] - Thing 'souliss:gateway:78' has been updated.

Regards, Jose Luis.

[Gabriele Ribichini]

Same problem here,

Tonino please tell us how to help in debugging..

[Antonino Fazio]

I discovered a bug in T31 when run on OH2.2.

Do you have a T31?

[Antonino Fazio]

Fixed.... can be.

Try latest version please and let me know:

https://drive.google.com/open?id=0BzYvfLL0ppGAalRxLVhjZ1hXVW8

Il giorno martedì 26 dicembre 2017 17:23:22 UTC+1, Jose Luis Sánchez Muñoz ha scritto:

[Jose Luis Sánchez Muñoz]

Thank you! Now back to the online Gateway, tomorrow I'll try again and comment.

Another thing the T21 does not recognize me as rollershutter, but if it recognizes well T22, but if not already change me in the Arduino.

A greeting and thanks again

Jose Luis

[Antonino Fazio]

Pay attention. 

Due to new bugfix last version is "org.openhab.binding.souliss_2.1.0.201801072303"

Tonino

[Luciano Bono]

Hi, I'm using the latest version. Everything works correctly until I add a T13 of the discovered in the Inbox, after adding it, the gateway stops responding.

Here I copy the log:

openhab> log:tail
12:02:35.708 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'souliss:gateway:50' changed from OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 14 ping to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 15 ping
12:03:05.723 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'souliss:gateway:50' changed from OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 15 ping to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 16 ping
12:03:35.749 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'souliss:gateway:50' changed from OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 16 ping to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 17 ping
12:04:05.764 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'souliss:gateway:50' changed from OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 17 ping to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 18 ping
12:04:35.769 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'souliss:gateway:50' changed from OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 18 ping to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 19 ping
12:05:05.781 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'souliss:gateway:50' changed from OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 19 ping to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 20 ping
12:05:35.783 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'souliss:gateway:50' changed from OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 20 ping to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 21 ping
12:06:05.801 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'souliss:gateway:50' changed from OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 21 ping to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 22 ping
12:06:35.832 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'souliss:gateway:50' changed from OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 22 ping to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 23 ping
12:07:05.827 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'souliss:gateway:50' changed from OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 23 ping to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 24 ping
12:07:35.841 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'souliss:gateway:50' changed from OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 24 ping to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 25 ping
12:08:05.847 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'souliss:gateway:50' changed from OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 25 ping to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 26 ping
12:08:35.864 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'souliss:gateway:50' changed from OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 26 ping to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 27 ping
12:09:05.875 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'souliss:gateway:50' changed from OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 27 ping to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:50 do not respond to 28 ping

[Tonino Fazio]

Are you sure that you running lastest version? 




From console:

ssh -p 8101 openhab@localhost




default pwd is habopen

commands from openhab console:

bundle:list | grep Souliss

If you see only last Souliss binding it is ok!

Tonino Fazio

--

You received this message because you are subscribed to a topic in the Google Groups "souliss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/souliss/g6YQ4FroR7k/unsubscribe.

To unsubscribe from this group and all its topics, send an email to souliss+unsubscribe@googlegroups.com.

To post to this group, send email to sou...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/souliss/cf1eab56-2ae2-4bbb-bf1a-f9631cafaff0%40googlegroups.com.

[Luciano Bono]

Yes, I'm using latest version:

openhab> bundle:list | grep Souliss
242 │ Active   │  80 │ 2.1.0.201801072303     │ Souliss - Arduino based SmartHome Binding
openhab>

When I remove T13's from paper UI everything goes fine.

Regards.-

Tonino Fazio

To unsubscribe from this group and all its topics, send an email to souliss+u...@googlegroups.com.

To post to this group, send email to sou...@googlegroups.com.

[Antonino Fazio]

Ok.
I going to test T13

[Jose Luis Sánchez Muñoz]

Hello again, I've been testing these days. I have no T31 and T13. I have:

T11, T16, T22, T53, T52.

I usually get disconnected in a couple of hours from the Gateway, even sometimes in 1 minute. Always at 5 ping not answered, if I try from CMD in Windows, none fails with spare in < = 1ms

My Gateway is a Mega Arduino with ethW5100, fixed IP if it helps... with Openhab 1.8.3 works all right

Greetings and I hope your help

 

2018-01-23 18:50:24.430 [vent.ItemStateChangedEvent] - Temperatura_C_comedor changed from NULL to 23.0

2018-01-23 18:50:24.433 [GroupItemStateChangedEvent] - Temperatura changed from 20.0 to 21.5 through Temperatura_C_comedor

2018-01-23 18:50:24.453 [vent.ItemStateChangedEvent] - Humedad_C_comedor changed from NULL to 18.0

2018-01-23 18:50:54.669 [ome.event.ItemCommandEvent] - Item 'setpoint_ac_jose_calor' received command 24.0

2018-01-23 18:50:54.687 [vent.ItemStateChangedEvent] - setpoint_ac_jose_calor changed from 22 to 24.0

2018-01-23 18:51:27.644 [ome.event.ItemCommandEvent] - Item 'activar_ac_jose_calor' received command ON

2018-01-23 18:51:27.651 [vent.ItemStateChangedEvent] - activar_ac_jose_calor changed from NULL to ON

==> /var/log/openhab2/events.log <==

2018-01-23 18:51:32.520 [ome.event.ItemCommandEvent] - Item 'setpoint_ac_jose_calor' received command 23.5

2018-01-23 18:51:32.665 [vent.ItemStateChangedEvent] - setpoint_ac_jose_calor changed from 24.0 to 23.5

2018-01-23 18:51:33.424 [ome.event.ItemCommandEvent] - Item 'setpoint_ac_jose_calor' received command 23.5

2018-01-23 18:52:23.567 [hingStatusInfoChangedEvent] - 'souliss:gateway:11b8181c' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:11b8181c do not respond to 4 ping

2018-01-23 18:52:23.572 [hingStatusInfoChangedEvent] - 'souliss:t52:0-4' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)

2018-01-23 18:52:23.580 [hingStatusInfoChangedEvent] - 'souliss:t52:4-4' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)

2018-01-23 18:52:23.583 [hingStatusInfoChangedEvent] - 'souliss:t22:1-0' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)

[Antonino Fazio]

It is incredibile.
Are young sure that you are using latest binding?

Can you look into general log for some exception before 2018-01-23 18:52:23.572 minus 4*GW ping time?

[Antonino Fazio]

Ops...
Lastest is 28/01/2018.
Try it please.

[Jose Luis Sánchez Muñoz]

Hello! I'm testing the last binding and currently with 36 hours online, not disconnected from the Gateway.

I also deleted a T21, which I think is what gave error. Just by switching to online that T21, the Gateway was disconnected. That does not concern me, because I will change for a T22 that works better with Openhab.

I'll keep trying and anything that happens warns you.

Greetings and thanks for your work!

[Judy van der Woning]

Hi,

I have the same issue. Everything works much better since the 1.x version, except for the dimmable lights, they don't work at all. I'm forces to used the old version now.

Do you know how I can solve this issue?

Regards,

Robert

Op dinsdag 24 oktober 2017 15:13:43 UTC+2 schreef stef mertens:

[Enric G.]

Hello good afternoon. Excuse my English, but I have a problem and I do not know how to fix it.

After a week with OH in operation, yesterday I added a T13 and the openhab was disconnected, today I mentioned this T13 in Arduino, I restarted everything and I still have the same problem, I connected the error that occurs in the REGISTER. Thank you very much, but I do not know what else to restart, delete or try. From the souliss app, everything works fine, since OH does not show values, but I can turn the lights on and off and control the blinds, but the temperatures and humidity do not appear in habpanel or paperui.

2018-11-21 20:13:35.197 [ERROR] [io.openhabcloud.internal.CloudClient] - Socket.IO error: {}
io.socket.engineio.client.EngineIOException: xhr post error
 at io.socket.engineio.client.Transport.onError(Transport.java:71) [226:org.openhab.io.openhabcloud:2.3.0]
       at io.socket.engineio.client.transports.PollingXHR.access$000(PollingXHR.java:19) [226:org.openhab.io.openhabcloud:2.3.0]
       at io.socket.engineio.client.transports.PollingXHR$4$1.run(PollingXHR.java:88) [226:org.openhab.io.openhabcloud:2.3.0]
  at io.socket.thread.EventThread$2.run(EventThread.java:80) [226:org.openhab.io.openhabcloud:2.3.0]
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
        at java.lang.Thread.run(Thread.java:748) [?:?]
Caused by: java.io.IOException: 400
       at io.socket.engineio.client.transports.PollingXHR$Request$1.run(PollingXHR.java:218) ~[?:?]
    ... 1 more
2018-11-21 20:13:35.224 [INFO ] [io.openhabcloud.internal.CloudClient] - Disconnected from the openHAB Cloud service

2 minutes later... THE PROBLEM

2018-11-21 20:15:33.687 [hingStatusInfoChangedEvent] - 'souliss:gateway:77' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:77 do not respond to 4 ping
2018-11-21 20:15:33.715 [hingStatusInfoChangedEvent] - 'souliss:t11:77:7-6' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.720 [hingStatusInfoChangedEvent] - 'souliss:t22:1-8' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.724 [hingStatusInfoChangedEvent] - 'souliss:t11:77:3-7' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.740 [hingStatusInfoChangedEvent] - 'souliss:t11:77:3-8' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.743 [hingStatusInfoChangedEvent] - 'souliss:t52:6-4' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.745 [hingStatusInfoChangedEvent] - 'souliss:t11:77:5-7' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.748 [hingStatusInfoChangedEvent] - 'souliss:t12:1-6' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.750 [hingStatusInfoChangedEvent] - 'souliss:t12:1-9' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.753 [hingStatusInfoChangedEvent] - 'souliss:t52:2-4' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.755 [hingStatusInfoChangedEvent] - 'souliss:t53:1-2' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.758 [hingStatusInfoChangedEvent] - 'souliss:t53:5-2' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.761 [hingStatusInfoChangedEvent] - 'souliss:t11:77:1-7' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.763 [hingStatusInfoChangedEvent] - 'souliss:t12:3-6' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.765 [hingStatusInfoChangedEvent] - 'souliss:t11:77:8-9' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.767 [hingStatusInfoChangedEvent] - 'souliss:t12:5-6' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.769 [hingStatusInfoChangedEvent] - 'souliss:t53:3-2' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.771 [hingStatusInfoChangedEvent] - 'souliss:t52:7-4' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.773 [hingStatusInfoChangedEvent] - 'souliss:t11:77:8-7' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.775 [hingStatusInfoChangedEvent] - 'souliss:t53:7-2' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.777 [hingStatusInfoChangedEvent] - 'souliss:t12:8-6' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.781 [hingStatusInfoChangedEvent] - 'souliss:t11:77:8-8' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.783 [hingStatusInfoChangedEvent] - 'souliss:t11:77:2-7' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.785 [hingStatusInfoChangedEvent] - 'souliss:t11:77:6-6' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.787 [hingStatusInfoChangedEvent] - 'souliss:t52:5-4' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.789 [hingStatusInfoChangedEvent] - 'souliss:t22:4-3' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.791 [hingStatusInfoChangedEvent] - 'souliss:t52:3-4' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.793 [hingStatusInfoChangedEvent] - 'souliss:t11:77:2-8' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.795 [hingStatusInfoChangedEvent] - 'souliss:t12:2-6' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.799 [hingStatusInfoChangedEvent] - 'souliss:t12:4-4' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.802 [hingStatusInfoChangedEvent] - 'souliss:t12:6-7' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.805 [hingStatusInfoChangedEvent] - 'souliss:t52:1-4' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.808 [hingStatusInfoChangedEvent] - 'souliss:t53:2-2' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.810 [hingStatusInfoChangedEvent] - 'souliss:t22:4-2' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.811 [hingStatusInfoChangedEvent] - 'souliss:t41:0-0' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.814 [hingStatusInfoChangedEvent] - 'souliss:t53:6-2' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:15:33.816 [hingStatusInfoChangedEvent] - 'souliss:t54:7-11' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2018-11-21 20:16:03.704 [hingStatusInfoChangedEvent] - 'souliss:gateway:77' changed from OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:77 do not respond to 4 ping to OFFLINE (BRIDGE_OFFLINE): Gateway souliss:gateway:77 do not respond to 5 ping

[Enric G.]

Does anyone know how to do it?

Enric

[Antonino Fazio]

Have you problem only with T13 anf T5x or also with other tipicals?

[Enric G.]

Doesn't works nothig, the gateway is offline.

Enric

[Antonino Fazio]

Can you try lastest OH and binding?
Lastest OH vers 2.4
Download binding bere: https://github.com/souliss/bindingopenhab2/releases

Keep an eye on it because in the next days I will upload new version.

[Enric G.]

ok I will try it! thanks a lot!!

Enric 

[Enric G.]

Great, thank you very much, it works perfectly, now I have everything online. Although the scan takes a long time and does not stop detecting all the slots.

Enric

[stef mertens]

Hi Antonio,

I have strange issues with a clean, fresh install.

Running OH2.4 on a windows 2012 server. Zulu as JDK and the latest binding downloaded from Github. Mysql persistence activated.

openhab console:

openhab> Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driv
er class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered v
ia the SPI and manual loading of the driver class is generally unnecessary.
bundle:list | grep Souliss
204 | Active | 80 | 2.4.0.201812300050 | Souliss - Arduino based SmartH
openhab>

and this is in the openhab log:

2019-01-25 15:38:21.976 [INFO ] [al.discovery.SoulissGatewayDiscovery] - Starting org.openhab.binding.souliss - Version: 2019 01 25 15:29:00
2019-01-25 15:38:21.976 [INFO ] [al.discovery.SoulissGatewayDiscovery] - Starting Servers
2019-01-25 15:38:21.976 [INFO ] [.protocol.SoulissBindingUDPServerJob] - Starting UDP Server Job - Server on port 60288
2019-01-25 15:38:32.945 [INFO ] [al.discovery.SoulissGatewayDiscovery] - Starting org.openhab.binding.souliss - Version: 2019 01 25 15:29:00
2019-01-25 15:38:32.961 [INFO ] [al.discovery.SoulissGatewayDiscovery] - Starting Servers
2019-01-25 15:38:32.961 [INFO ] [.protocol.SoulissBindingUDPServerJob] - Starting UDP Server Job - Server on port 60289

It doesn't start a server job on UDP 230, as i would expect it.

The binding shows up in OH, but it discovers nothing (as i would expect) maybe something wrong in my souliss.cfg? :

################################ Souliss Binding ##########################################
#
# Souliss
#
# For ITEM defination in file .item
#{souliss#<Typical>:<nodeID>:<slot>:[<bit>|<useOfSlot>]}

souliss:IP_LAN=192.168.80.180
souliss:USER_INDEX=71
souliss:NODE_INDEX=134
#SERVERPORT - Leave empty for casual port
souliss:SERVERPORT=230

#time in mills - min 50
souliss:REFRESH_DBSTRUCT_TIME=600000
souliss:REFRESH_SUBSCRIPTION_TIME=120000
souliss:REFRESH_HEALTY_TIME=60000
souliss:REFRESH_MONITOR_TIME=500
souliss:SEND_DELAY=1500
souliss:SEND_MIN_DELAY=100
souliss:SECURE_SEND_TIMEOUT_TO_REQUEUE=5000
souliss:SECURE_SEND_TIMEOUT_TO_REMOVE_PACKET=30000
###########################################################################################

I had a completely working system before, on OH 2.2, but wanted an upgrade. That didn't work out well, so i had to start from scratch.

Any idea what could be the problem?

Thanks,

Stef

[stef mertens]

Hi ,

Following my previous post i have tried a couple of things.

Clean setup of OH24, with the previous binding (org.openhab.binding.souliss_2.1.0.201805302105)... At first it looked like working: things were discovered, but when i controlled any of them it didn't work - it looked like Openhab simply did not send the commands. (firewall is OFF on this machine)  - it DOES read changes, though. If i use Soulissapp to set the temperature of my T31, the OH interface follows. But not the other way around.

So i tried it again, start from scratch (OH24 and binding org.openhab.binding.souliss_2.1.0.201805302105), and had the same issues as i have now: no communication at all.

I downloaded the latest binding from github (org.openhab.binding.souliss_2.4.0.201812300050) and still no luck. It seems like any combination i try, the binding doesn't start a thread on udp 230.

I grabbed my old install from the crashed virtual windows10 machine (OH22) and started it on the windows 2012 server, and that works as well as it used to do (with some minor issues like my T31 not reporting status - so i cannot see if the heating is running or not)

Anybody?

Thanks in advance,

Stef

Op vrijdag 25 januari 2019 17:39:42 UTC+1 schreef stef mertens:

[stef mertens]

Owkay, so i got it up and running. Clean install of OH2.4, manually put the latest binding in /addons,.. Then in the paperui  just add the gateway manually. everything shows up after that.

Only thing: after 9 hours of working great, this error starts showing up in the logfile:

2019-01-27 09:54:29.890 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception: 

java.lang.ClassCastException: org.openhab.binding.souliss.handler.SoulissGatewayHandler cannot be cast to org.openhab.binding.souliss.handler.SoulissGatewayHandler

at org.openhab.binding.souliss.internal.protocol.SoulissBindingUDPDecoder.decodePing(SoulissBindingUDPDecoder.java:174) ~[?:?]

at org.openhab.binding.souliss.internal.protocol.SoulissBindingUDPDecoder.decodeMacaco(SoulissBindingUDPDecoder.java:104) ~[?:?]

at org.openhab.binding.souliss.internal.protocol.SoulissBindingUDPDecoder.decodeVNetDatagram(SoulissBindingUDPDecoder.java:88) ~[?:?]

at org.openhab.binding.souliss.internal.protocol.SoulissBindingUDPServerJob.run(SoulissBindingUDPServerJob.java:63) ~[?:?]

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:?]

at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) ~[?:?]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) ~[?:?]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) ~[?:?]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]

at java.lang.Thread.run(Thread.java:748) [?:?]

and after that, every minute this error shows up:

2019-01-27 16:05:11.603 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler SoulissGatewayHandler tried updating the thing status although the handler was already disposed.

Everything seems to be be working, though.

Does anyone have any suggestions on how to fix this?

Thanks in advance,

Stef

Op zaterdag 26 januari 2019 13:52:36 UTC+1 schreef stef mertens:

[Артем ТИхонович]

I have the same problem on OH 2.5  Have you resolve this problem?

воскресенье, 27 января 2019 г., 18:13:07 UTC+3 пользователь stef mertens написал:

[Sander Lagrand]

I experienced the same problem.

After adding the following parameters to the definition of my gateway in the .things file, it all seems to work:

TIMEOUT_TO_REQUEUE=5000, TIMEOUT_TO_REMOVE_PACKET=20000]

Gateway stays online as do all my other things.

The schedule error stays.

Op dinsdag 14 januari 2020 14:36:13 UTC+1 schreef Артем ТИхонович: