Topics created by mhkid

@mhkid here you go : https://arduino-esp8266.readthedocs.io/en/latest/esp8266wifi/station-class.html

Well I'm sorry you took it that way. By the time I happened along into the thread, you had already pronounced your diagnosis. I offered my thoughts into the thread, this way if your first diagnosis turns out not to be correct, you have other ideas to try. These issues can be complicated, and (I know from experience) some times what we think at first ends up not actually being the problem. As I said, I could be wrong anyway. @mhkid said in Node registration problem: And your comment was not based on any evidence it was just a feeling you had Each of us are chock full of thoughts, memories, things we learned which we are no longer consciously aware of. The sum total of all this "sub-conscious" thoughts and memories can manifest itself as a "gut feeling" but perhaps you are unaware of this. At any rate, it is not as if you need to be a "radio whisperer" or that this is some obscure subset of problems. Rather I would submit to you that these are the most common type of problems. @mhkid said in Node registration problem: you offered no solutions In fact I said "It sounded like radio propagation issues to me." No need for me to go into any further detail, if exchanging the gateway has solved the problem. However if you continue to experience problems, please share new information and we can continue from there.

@electrik Thank you

There doesn't seem to be a ton of interest in this but I wanted to provide an update. After writing the transport and using it for a bit I've decided to go another direction with the integration to SmartThings. I felt like the custom transport would require more maintenance and I wanted more of any option that was configuration rather than coding. Because there was C++ code on the MySensors side of things and then Groovy on the SmartThings side it just seemed like a brittle integration with the design and how I wrote the code. SmartThings is going to be moving in another development platform direction as well at some point. I'm working on an MQTT solution with Mosquitto and Node Red (on a Raspberry Pi) and it will also require some Groovy on SmartThings but a much simpler solution IMO. There will be more to come and I'll share here when it's complete but I do have a prototype/proof of concept working. The two way communication is much better/cleaner IMO than how I did it with the transport. If this is something that interests you let me know and I'd be happy to collaborate.

@alexsh1 Much the same principal as my 5v/3v solution for the 5v ultrasonic, only here I used a latching relay leaving the 3v Arduino on sleep power consumption. An interesting device however, with a low standby and effectively a timer function, it has many possibilities. Where this original project has been skewed is unfortunate, the selected devices compel the dual voltage solution, whereas an alternative strategy removes the need for it completely. Although pulses and switches can be regarded as "old" technology, they can still be highly effective for battery powered applications where energy conservation is critical..

@gohan I just tried that and answered my own question (it worked). Thanks for the pointer.

I hope you know some javascript, as it will be very handy with node-red

@vasarbob I have been able to make a rest call to the SmartThings API. I was using an esp8266 as the gateway but am in the middle of moving that to an Uno with Ethernet shield. The code is a little hacky right now and I am planning on refactoring and cleaning it up a bit. Would eventually like to write a transport layer but that's going to take some time. I also had to write the device handler code on SmartThings. That too is a little hacky and I need to refactor that as well. I'd be happy to share and collaborate if you want. I was trying to get a working prototype going and learn some things about MySensors as well as SmartThings and I think I understand it well enough now to be able to put it together.