Releases: armzilla/amazon-echo-ha-bridge
added support for more than 25 devices
so good it skipped a version!
change log:
- require --upnp.config.address= to be specified during startup
- support more than 25 emulated devices currently set to 75, can be increased at 25 device increments by specifying --emulator.portcount= default is 3 thus 3*25 = 75 total devices. Works by taking emulator.baseport and opening n number of ports sequentially from baseport to baseport+portcount
- relaxed http response codes to anything in the 200 to less than 300 http response codes to support misbehaving resources
other notes:
Ive seen some folks able to run this but not able to discover devices. I would recommend checking for duplicated devices names as i have seen this to cause the echo to reject all devices. The lazy way would be to delete the /data directory and start over.
now with post/put support
v0.2.1 add request body, content type, and verb in creation
configurator and harmony support
Experimental dimming support
try dimming adding a device with an on url of something like:
http://192.168.1.201:3480/data_request?id=action&output_format=json&serviceId=urn:upnp-org:serviceId:Dimming1&action=SetLoadLevelTarget&DeviceNum=<deviceid>&newLoadlevelTarget=${intensity.percent}
dont forget to replace deviceid, clear devices, and rediscover
Now with Cors..lite?
fixed the following from various contributors (thanks!)
*fixed REALLY connected home with more than 10 devices.
*auto discovery of interfaces, skipping ipv6 so no need to specify ipv4 only flag anymore
*added cors header filter from springboot to allow really permissive usage for now. (no worse than the vera api)
fixed issue #2
moved to httpcomponents instead of resttemplate, will not merge downstream as codebase is going to be vastly different in 0.2.x
56dcba6deced078f6e3ecbb73ab9665e2be59450 amazon-echo-bridge-0.1.1.jar