The simplest approach would be use something like Homeseer running on a Raspberry Pi as the central system, with a USB Zigbee device.
HomeSeer HS4-Pi Smart Home Software
HS4 is an advanced smart home automation software that's designed to work a wide range of smart home products and technologies. Use to remotely and automatically control smart home devices such as smart switches, thermostats, door locks, sensors & more. This edition is designed to run on...shop.homeseer.com
I do have some experience with Microsoft Azure which enables the cloud computing for IoT for the central server part but before I even go there, I need to access the devices' data. Seems like it's going to be quite a task.You need a central server to coordinate and collect data from the individual devices, and make it available.
Add one of the custom web page plugins, or write you own - all the device data can be read by accessing the appropriate homeseer URL
There are hundreds of other interface plugins available for that system.
That Maevi device seems very restrictive; you could access it indirectly via another web server on a separate device to collect and store data; nothing particularly fancy or powerful, any basic system that can run a LAMP stack for web interface should be OK to make requests, store data and access it - so again, a Pi or similar would work.
The hard part would be monitoring all the interactions between the Maevi unit and its own app, to reverse engineer the communications so you could read data from you own device.
You would need something like Wireshark running on the same LAN as the device and phone, to capture ethernet packets to and from each, then try and make sense of them.
Wireshark may need to run on the router to be able to monitor "third party" traffic, rather than in & out of the PC or device it's running on.
If your router can run DD-WRT or similar, you should be able to do it directly on that. More info here:
Otherwise, a linux machine with two ethernet ports could be used, with things set up so all data to be monitored passes through it.
A "man in the middle" setup, in other words.
no - that does not put the Pi in the signal path to the IoT device. The Pi will never see the data between the IoT device and the internet.So hypothetically does this look like the topology which I should be using?
no - that does not put the Pi in the signal path to the IoT device. The Pi will never see the data between the IoT device and the internet.
The Client mode AP would be used to connect a computer to the internet. With a Pi, that could be built-in Wifi or a USB WiFi device etc., whatever connect the Pi to the internet.
Then the second AP connected to the PC / Pi via Ethernet, with that providing the internet connection for the IoT device.
Set the Ethernet port up with a different LAN IP subnet and enable DHCP so things can connect to it and be allocated a suitable IP address for that subnet.
Then enable IP forwarding and routing so things on the second AP get internet access.
That allows programs on the Pi to directly tap in to all the data going through the connection from the second AP, so you can view or log it to work out what is happening.
Just hope it's not using HTTPS protocol, as that makes things more complex again. Same physical setup, but you would also have to emulate the IoT server on the Pi, to see decrypted data.
Yep, exactly.Ah I get it now. An AP instead of a "Raspi 2".
So basically what I'll need is basically a Pi (I guess Pi 4) and a wireless AP with an ethernet port. (Is the product linked sufficient?)
Can you set the monitoring machine as the "gateway", inspect the packet, and port-forward to the real gateway?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?