Posts made by diamantmatch

i have tried making the MPR talk to arduino, but i could not find the right library for your code.. what lib are you using? the adafruit one just spews out errors..

yes there is indeed something in the source code there.. but it is only the setpoint almost like a thermostat.

in my code i presented three values. two of these values where not recognised as could be seen in the last post. but the last value was indeed a temperature setting and was recognised as a thermostat.

i guess i will post this to domoticz and hopefully it will be implemented

Thanks you guys for the help!

i will post back here if i find anything usefull or when it is working just so others can find it.

@mfalkvidd thanks for the tip! i got the following result in domoticz.

16-08-29 11:22:34.763 (mysensor) Temp (Baro Temp)
2016-08-29 11:22:34.772 (mysensor) General/Barometer (Baro)
2016-08-29 11:22:35.059 MySensors: Node: 12, Sketch Version: 1.0
2016-08-29 11:22:35.099 Error: MySensors: Unhandled sensor (sub-type=22), please report with log!
2016-08-29 11:22:35.108 Error: MySensors: Unhandled sensor (sub-type=21), please report with log!
2016-08-29 11:22:35.115 (mysensor) Thermostat (Setpoint Heat)
2016-08-29 11:22:35.298 (mysensor) Temp (Baro Temp)

this is what i get when presenting 3 values back to domoticz.
i guess this means that V_HVAC_FLOW_STATE and V_HVAC_SPEED are not implemented in domoticz yet?
is there a way for me to work around this?

is there anyone that has the switch for HVAC working in domoticz?

i have tried several times to create a HVAC switch by presenting my node with " present(CHILD_ID_HVAC, S_HVAC);"
but when i look in domoticz there is no node to be found in the devices or in the hardware( under setup), only in the log i can see that the node has presented itself correctly.

is it possible that S_HVAC is not supported by domoticz? is there a workaround for this?

thanks for the help anyway!

count me in!
i'll be happy putting in some effort to help MYSController!

arduino pro mini + nRF24L01+ @ 3.5v

you can search for MYScontroller on the forum, you'll find this post regarding OTA updates with MYScontroller.

it involves flashing a new bootloader, but it is totally worth it once you upload new code to a node embedded in a wall or something.

@tekka
Awesome! everything now works like a charm! many thanks for your help!

i tried using the OTA FW update by following your guide a few posts up and i must say i like it a lot!
i just cant figure out how to upload FW from the software. every time it starts uploading FW by responding on FW requests my gateway seems to freeze, i use a usb ttl converter and arduino pro mini with radio as gw. i also uploaded the log. by the time the server responds to the FW req i have assigned FW to the node. then the GW just stops recieving and transmitting for no apearent reason so there is no communication back and forth, then when i reset the GW ( by pushing the reset button on the GW the comm is back up.. when the GW is frosen the led (pin 13, clock) is also completely off.. and yes, i also tried a radio with capacitor.
MySensors_20150318-202006.log

ahw, I realy like the ui of EasyIoT.
isn't there any other way I can feed it serial data? it doesn't necessarily have to be so easy, but if I could just get it to accept my data I would be verrrry happy

I can imagine there is a function requesting data from some sort of library that handles communication with the RF24 through the GPIO ports. but can I not feed the serial data directly to the requesting function? sure, I like it a lot that the GPIO pins get used for the radio, but unafortunatly I do not own a raspberry.

@EasyIoT In the description of EasyIoT it says that it also works on the windows platform.
I can get the server running on a windows machine but i can not seem to get it connected to my serial gateway. i have a usb interface with arduino nano and a rf24 module but i can not find the setting in EasyIoT to use COM14.

is there anyone with the same problem?

@Dirk_H
I use LiFe batteries in my battery sensors. they are a bit oversized, but they work just fine.
And because of the lower operating voltage I don´t need any type of voltage regulation

@epierre
as a battery operated solution I use li-fe battery's they have a lower voltage per cell then lion and lipo so there is no need for any type of voltage regulation witch makes it simple. I just need to watch out not to over discharge the battery, but with 3Ah on a temp/hum sensor that will not be much of a problem

OT:
seems like a very interesting board with lots of function and usefull stuff. But for $25 I would mutch rather throw my own hardware on a breadboard or protoboard or something.

@tbowmo
The relays are 12VDC so the arduino can not be wired directly to the relay. the arduino should power a shift register, transistor, FET, or other semiconductor (and not pulling any more than 40mA.) and therefore indirectly controlling the 12v flow to the relay.

I think it is wise to use optocouplers if you would want to protect the 5v circuitry against the 12v rail, but everyone should chose for themselves since the extra cost and hassle for optoisolators may not weigh up to the cost of the 5v circuit.
all that happens when you accidentally apply 12v to your arduino is that it may smell a bit and it will never work again, witch is a quick fix with a new nano. Opto-isolation is more effective when working with 110 - 220v and when working in humid environments i.e. shower or bathroom.

if you are going to be on the cheap side and use relays without a breakout board and/or set up your own relayboard then please pay attention to the flyback diode you should have across the coil of your relay. it prevents flyback voltage from building up and damaging your fet/transistor/shiftregister. ( even though it might not fail on the first time you try it without flyback, it will eventually and finding the problem is quite a pain)

wow, this is something!
would really love to set this up at home!
i also can't wait for your link to appear, really exited !

Never had a roomba, but i have obtained remote control of my automatic LG vacuum
I just copied the IR remote commands and transmit them on command from a sensor node.
There is no feedback, but i don't think i need feedback, when the battery is empty it drives back to the docking station. All i can say is that just pushing start remotely and getting home to a clean house is nice

bump

I also wonder what the S, T, PT & L values stand for..
i see them coming and going but never understood what they are here for

happy new year!

@daulagari

i installed DomotiGa with a git command as described on the installation page. so i guess i have th latest version.

Eventhough i did execute the command sucessfully and the response was that i am already a member of the group i think something must have gone wrong is this step. i wouldnt know how to check or redo/undo whatever this step.
"
$ sudo addgroup domo dialout
"

thanks!

hello @hek ,

i have installed the domotiga server on my ubuntu machine but i can not seem to get the usb connection working
when i start domotiga i can configure the mysensors interface according to the installation guide, but i can not open the serial connection ..

this is all i got .. what am i doing wrong?
2014/11/20 23:03:12 [Plugin] MySensors, Instance #1 enabled.
2014/11/20 23:03:12 [MySensors] ERROR: MySensors serial interface FAILED to connect to port /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A800eFAw-if00-port0
2014/11/20 23:03:12 [MySensors] ERROR: Cannot open serial port (#5)
2014/11/20 23:03:12 [MySensors] Relay disabled.

hey,

i really feel like i'm just nagging about things here.. sorry about that.
i can not seem to get the sensor to listen to the serial output from the plugin..
i suspect the plugin from not transmitting a newline, every string transmitted should end with \n

thanks

Thanks @tbowmo !
I uploaded two standard sketches to the node and the gateway so i never noticed before.
It seems quite logical to define the child-sensor-ID in the sketches on the sensor node itself.
will do that next time i upload a new sketch!

hi,

Awesome that you want to implement the support for the AUTO assigning of unique ID's!

yes, as far as i got it now it starts out with the sensor presenting itself by shouting 255;255;3;0;3; across the network.
Decoded this means the following:
node-id: "255;" this means the node has no ID
child-sensor-id: "255;" this means the node has no child sensor ID's assigned to any sensors attached ( i do not know if this would also be automatically assigned aswell.. but i hope @hek could give us some clarification on this? )
message-type: "3;" the message type defines the type of message and basicaly why the message is send. the number 3 means that it is an internal message (propably for configuration)
ack: "0;" no ack needed
sub-type: "3;" this is where the magic happens. since in the message type it was defined this is an internal message we can state what type of internal message it is in this parameter. the 3 means "I_ID_REQUEST" wich means internal ID request. The node is requesting an ID.
payload: "(NULL, nothing, empty)" there is no payload, the request is simply enough.

the controller recieves this request and defines what ID's are already in use. the controller picks a unique number between 1 and 254 and assignes it to the node using the same message-type but a different sub-message-type ( sub-message-type 4 means "Id response back to sensor. Payload contains sensor id" .
The assigned ID will be transmitted in the payload section.

example:
The node boots and looks in his EEPROM memory if it already has a node-ID. if it doesnt it wil broadcast a request for the ID with: 255;255;3;0;3;

The controller then looks in his table of vended ID's and sends back the first number available (in this example i have only one sensor so number 1 would be vended) and transmits the assigned ID to the node with: 255;255;3;0;4;1

The node then owns the number 1.
when something would be transmitted to the node it will listen to this number.

i dont yet know how the child-sensor-id's work.. sorry for that

thanks for the help !
i hope i made it a bit more clear what is needed to vend a node ID.

vincent,

hey @freedomotic

The AUTO-id feature @hek explains is exactly what i mean.
The node in my network doesnt know what ID to listen to and requests a unique ID from the controller.

I like the plugin for freedomotics a lot! and i hope the AUTO-id feature can be functional with my setup anytime soon.

thanks!

hey all,

I have installed freedomotic on my pc and up and running with the mysensors plugin.
there is a serial gateway(arduino duemilanove) connected via USB. i also have one sensor in the field with a relay switch.

The serial connection of the gateway to the mysensors plugin is open. I verified this through the log view plugin where i saw the gateway presenting itself and telling the gateway startup is complete.

The problem however is that when the sensor presents itsself asking for a node-ID, the controller never responds with anything. The node just keeps asking for a node ID by presenting as ID 255.
Is there some kind of option in freedomotic or the mysensors plugin where i have to enable the vending of node ID's ? Or am i doing something wrong here..

Thanks in advance,

vincent

i have the exact same problem.
i use freedomotics as my controller with mysensors plugin and when my sensor asks for a unique ID the controller never responds. how come the controller never responds?

bump