Skip to content
Snippets Groups Projects
Select Git revision
  • congestioncontrol
  • merge-v-data-collection-spammer-0.8.2
  • WIP-merge-v-data-collection-spammer-0.8.2
  • merge-v-data-collection-spammer-0.7.7
  • tmp
  • test-masterpow-fixing
  • test-masterpow
  • test-echo
  • v-data-collection
  • v-data-collection-spammer
  • tmp-dump-spam-info
  • dump-msg-info-0.3.1
  • test-dump-message-info
  • spammer-exprandom
  • develop default protected
  • extra/tutorial
  • without_tipselection
  • hacking-docker-network
  • hacking-docker-network-0.2.3
  • master
  • v0.2.3
21 results
Compare
user avatar
Feat: Refactor and cleanup some code (#301)
Hans Moog authored 
* Feat: refactored the address

* Feat: started adding solidification of transferOutputs

* Feat: cleaned up checker code

* Feat: going to bed - good night world

* Feat: refactored transferoutput package

* Fix: fixed a bug from refactoring

* Refactor: removed old transferoutputmetadata package

* Refactor: started refactoring transfer package

* Refactor: refactored transfer/id package

* Refactor: moved transfer struct to new package

* Refactor: fixed issues after refactor

* Refactor: fixed sth

* Refactor: continued to move files

* Refactor: commit before migration of last refactored files

* Refactor: another refactor before move

* Refactor: refactor test

* Fix: fixed some bugs connected to refactor

* Refactor: continued refactor

* Refactor: fixed some bugs

* Refactor: does it work now?

* Feat: added a method to generate a random transferid

* Feat: rename transfer to transaction

* Refactor: refactor according to new names

* Refactor: continued to refactor transaction package

* Refactor: moved payload id to payload package

* Refactor: moved signatures to transaction package

* Refactor: moved signature to transaction

* Fix: fixed bug due to refactor

* Fix: fixed bugs due to refactor

* Refactor: fixed some bugs after refactor

* Fix: fixed additional bugs

* Fix: bug fix

* Refactor: moved signature to signaturescheme package

* Fix: fixed signatures test

* Fix: fixed bug in tangle

* Fix: fixed payloadmetadata test

* Fix: fixed payload test

* Refactor: moved payloadmetadata to payload package

* Fix: fixed some refactor bugs

* Fix: fixed a bug due to refactor

* Fix: fixed broken test

* Refactor: moved approver to payload package

* Refactor: moved missingpayload to payload package

* Refactor: refactored coloredbalance package

* Fix: fixed bug due to refactor

* Refactor: moved address signaturescheme to address package

* Fix: fixed refactor bug

* Feat: added missing outputs to tangle

* Fix: fixed issues due to refactor

* Refactor: started moving tangle classes to tangle package

* Refactor: moved payloadmetadata to tangle

* Fix: fixed bugs due to refactor

* Refactor: moved TransactionMetadata to tangle package

* Refactor: moved some files to tangle

* Fix: fixed bug due to refactor

* Feat: added TransactionMetadata storage

* Fix: fixed some issues

* Fix: fixed some issues

* Fix: fixed missing release
490f10e3
History
user avatar 490f10e3
History
Name Last commit Last update
docker
docs
.gitignore
README.md
config.go
devices.go
gateway.go
go.mod
main.go
utils.go
xaal.go
z2m.go
README.md

xAAL Gateway for Z2M

The main goal of this project is to provide a xAAL Gateway for Zigbee devices. After severals tests with ZHA, we decided to switch to Zigbee2MQTT.

The main reasons are:

  • ZHA provides a great API, but a lot of devices are not supported.
  • Z2M supports a lot of devices and provides a nice web interface to fine tune devices.
  • Z2M is written in NodeJS and we don't support JS right now.
  • Z2M is a standalone application, so we can run it in a container.

This gateway simply forwards Z2M events to xAAL bus and vice versa through MQTT. You can now use Z2M without messing with MQTT. Simply run this gateway, Z2M and a broker in a docker container. And you can use your Zigbee devices with xAAL. A docker-compose file is provided to run all services.

Installation

TBD

FAQ

  • Why are you using this gateway instead of Z2M MQTT throught HomeAssistant ? xAAL supports HomeAssistant out of the box. And I don't want to really on MQTT (spof, bad security).
  • Why are you using Go instead of NodeJS or Python ? We don't have a native JS implementation of the xAAL stack right now. And I mainly want to test the Go implementation.