PiDome Domotica/Home Automation

[John]

@tortoisedoc Yeah... that one is an oldie and can be discarded, that one was for example going to be used with for example arduino serial devices. Responding to the NID request with a driver id can load the driver specific for the software written on the arduino. this function is disabled in the api for mysensors.

Ok, i'm seeing the next:

2014-12-15 21:58:34,527 [Thread-29] TRACE org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Received from hardware driver: 0;0;3;0;14;Gateway startup complete.
2014-12-15 21:58:34,530 [Thread-29] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Handling internal: 0;0;INTERNAL;14;Gateway startup complete.
2014-12-15 21:58:34,533 [Thread-29] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Sending internal message to device: '0;0;3;0;2;Get Version'
2014-12-15 21:58:34,575 [pool-15-thread-1] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - sending: [B@13038e1

It is sended to the gateway, but there is no response. This routine has been working since implemented (almost the beginning when gateway ready was available).

@hek Am i missing something? Has the version info message been changed?

@tortoisedoc At moment of speaking i'm building a new test version on the build server (http://builder.pidome.org) which enables data when gateway ready arrives, but before it asks for a version. So you now should be able to send.

P.S. there now is a devices discovery page. devices with id appear here, devices without id (node id 255, so requesting one) still appear in the mysensors driver page. Also discovery is now enabled continuously. this is a quick build to get you going

[hek]

@John said:

Am i missing something? Has the version info message been changed?

Nope.

[Francois]

@John Hi my system was running fine till I what to add more sensor. Pidome do see the sensor but do not present the it in the "New nodes presentation" or the new "Discovered device". I can add the new nodes manually and that works. I am on version 508

here is info from the applog file:

[John]

@Francois Still busy with the centralized device discovery. The commit i did was to quickly have @tortoisedoc up and running to solve the issue he is having. it will be done today so devices will appear in the device discovery list.

Sorry for any inconvenience this commit has caused

[John]

@Francois Build server is busy with a quick fix for the MQTT gateway. Should be ready in a couple of minutes

[Francois]

@John download the ver509 and still doing the same thing.

[John]

@Francois Also not present in the discovery?

[Francois]

@John yes it is also not in discovery

[John]

@Francois Gimme half an hour

[EDIT] A bit longer, the devices proxy mapping (devices used in plugins) is misbehaving.[/EDIT]

[tortoisedoc]

@John thanks for the fix, will test it later today. Is the latest build still good to go?

[John]

@tortoisedoc Sending and receiving data is not influenced by the discovery utilities. It is possible new devices are not found (which have an ID assigned). But this should not be the case for nodes which are requesting an id (this is still handled by the driver).

The path to the hardware is now completely open after receiving of the gateway started message. I will in the meantime ask an other user if he has an issue with the request for the version number from the gateway

[John]

@Francois I have continued the normal development path of this feature. Otherwise i would be "hacking" the code and then remove this to be able to continue normally. I do have a quick build ready, could you check the latest build (510) if it is working for you?

[Francois]

@John This version (510) fix the issue and it did discovered the sensor. Thanks

[John]

@Francois Good!
@tortoisedoc Are you able to use the node assignment?

[Francois]

@John I must say that you product is getting better with every release. This new discovery process that you now add is making things ever easier to add sensors to the system Thanks for all the hard work that you are putting into this project. I real appreciate this. Keep up the good work. You product just work and I don't have to worries about it.

[John]

@Francois Thanks for your kind words! Too bad you didn't download the release on the builder this evening, you have fallen in a test sequence ;).

When the routine is completely implemented i will post a follow up on this feature.

[Francois]

@John I never skip an release the moment there is new release I installed.

[tortoisedoc]

@John said:

@tortoisedoc Are you able to use the node assignment?

Unfortunately not.

See here: appLog.txt
At this point, im starting to suspect about the PI. The miniterm shows correctly the gateway startup tho.

[ceburge]

Getting this error with the 510 build.

[John]

@tortoisedoc The only thing i see is a gateway ready message, i do not see any node presenting or asking for a node address. I suspect that this information is also not available in miniterm. If it is, you have to try again without miniterm cause this then is interfering.