Search
916 results for “0x0”
-
@[email protected] from what i've seen, most tagging software is mainly about rewriting file names or filling out all the fields of the track info
while djs will make use of these fields, a lot of them, me included, will want to give our music extra information that is tailored to their liking and there typically is no field for in the file's metadata. stuff like the time of the day to play it (warmup, prime time, afterhours,...), the setting (terrace, main floor, bar,...), the components you want to yoink from it when you loop it (vocals, bass, hihats,....), etc. every dj has their own needs and their own system for this
some will use playlists to categorize music like this, but some will want to write this sort of information into the comment field each file has, so you can search for it or have your dj software create smart playlists based on it.
i need some kind of software where i can go through a folder of music and listen to each track for a few seconds and then quickly select custom tags that apply to it and will be written into the file's comment field (e.g. #warmup #terrace #hihats).
ig this isnt dj specific because looking at the big dj software around non of these knuckledraggers care abt it, but if possible i also want the software to be responsive and have decent keyboard controls because that shit is infinitely faster than mouse stuff
https://onetagger.github.io/
this is the only thing ive found so far that does this, but its throwing me an error when i try to open the folder with my dj music collection, for some reason other folders work fine -
@telnet_cat set rzr 0x0fd225476bd5 #39c3 #telnet #hotwire
-
@telnet_cat set RZR 0x0fd225476bd5 #39c3 #telnet #hotwire
-
RE: https://infosec.exchange/@0x00string/116533684752244458
My commonplace book is the Tao Te Joan #TTJ. Even if I get hauled off to the camps, it should be available for my children to access from any computer able to access the internet.
-
RE: https://infosec.exchange/@0x00string/116533684752244458
My commonplace book is the Tao Te Joan #TTJ. Even if I get hauled off to the camps, it should be available for my children to access from any computer able to access the internet.
-
RE: https://infosec.exchange/@0x00string/116533684752244458
My commonplace book is the Tao Te Joan #TTJ. Even if I get hauled off to the camps, it should be available for my children to access from any computer able to access the internet.
-
RE: https://infosec.exchange/@0x00string/116533684752244458
My commonplace book is the Tao Te Joan #TTJ. Even if I get hauled off to the camps, it should be available for my children to access from any computer able to access the internet.
-
Check out this @BSidesNYC 0x03 interview by Preeti Ravindra with Mark Stamford from OccamSec, where he discussed why he has been supporting BSidesNYC since its inception and what it's like to found your own security company.
-
Check out this @BSidesNYC 0x03 interview by Preeti Ravindra with Mark Stamford from OccamSec, where he discussed why he has been supporting BSidesNYC since its inception and what it's like to found your own security company.
-
#? #радиация @rf @ua
https://0x0.st/oZUe.jpg
бля чёт местные стеклопакеты неоч фильтруют уф
чё нажать чтобы плёнка которая выжрет >95% УФ? -
Okay so. #AnimalCrossingNewHorizon shit! To recap, basically all on-screen text is stored in MSBT files. I think that's Message Studio Binary Tagged or sumth?
Basically, every line has an ID, is stored in UTF-16 (I think that's a header flag), and can contain tags. Tags are a 0x000E value followed by a function, sub-function, and argument count in bytes.
Got all that so far?
-
so there's this 90s warez cd series called "the legacy", a number of which are being dumped today
they're of the type of the "menu pretends to be something else if you don't run it with the correct password", so I took a look in IDA.
the config file is gzipped and memecrypted (custom algorithm with xor-sub-add) by the key (5 bytes initialised by xor/not/add/sub by the entered key, one of the bytes is always 0 as it's ANDed with itself and initialised to 0 lol)
the first (key+1) bytes of plaintext equals the null terminated key.
the actual archive files? they claim to be "FMV files" and actually are a 0xE byte header (first 4 bytes are magic number 4E 43 FF 10, u32 at 0x0A is number of files), followed by gzipped data
the uncompressed data is an array of structures: 93 byte header (32-bit length at 0x9, null-terminated path at 0xD), followed by [length] bytes of data
no memecrypto at all on the actual warez, just a custom archive format gzipped
lol
-
EIP-7702: прикручиваем код к EOA, где можно споткнуться?
EIP-7702 делает EOA похожим на смарт-контракт со всеми вытекающими. Что меняется в транзакциях, почему ломаются проверки msg.sender == tx.origin и address.code.length > 0 , как возникают коллизии хранилища при смене делегата, и что делать с приёмом ERC-721 и ETH. С примерами на Foundry и связкой с ERC-4337.
https://habr.com/ru/articles/1029386/
#EIP7702 #Smart_account #абстракция_аккаунта #account_abstraction #ethereum #authorization_list #transaction_type_0x04 #Solidity #Pectra #блокчейн
-
For anyone else capturing #USB on #macOS on Apple Silicon:
It does work, you just have to disable SIP entirely first (individual flags don't work, needcsrutil disable)
You need to manually set the correct interface up, e.g.sudo ifconfig XHC2 upFor identifying a specific device, the easiest way is to correlate with IORegistryExplorer.
For example:iPhone@02100000
^
XHC interfaceOnce you start the capture in Wireshark, you can filter to just that device using
usb.darwin.location_id == 0x02100000 -
For anyone else capturing #USB on #macOS on Apple Silicon:
It does work, you just have to disable SIP entirely first (individual flags don't work, needcsrutil disable)
You need to manually set the correct interface up, e.g.sudo ifconfig XHC2 upFor identifying a specific device, the easiest way is to correlate with IORegistryExplorer.
For example:iPhone@02100000
^
XHC interfaceOnce you start the capture in Wireshark, you can filter to just that device using
usb.darwin.location_id == 0x02100000 -
So I looked at the #datasheet (https://files.waveshare.com/upload/2/29/7.5inch_e-paper-b-Specification.pdf) to find what I had to do to display some red colour. It seems I have to send 0x04 for each red #pixel, 0x03 for black and 0x00 for white.
Checked the existing #driver and, sure enough, it sends 0x03 and 0x00! This seems to be the right way.
[continues] -
So I looked at the #datasheet (https://files.waveshare.com/upload/2/29/7.5inch_e-paper-b-Specification.pdf) to find what I had to do to display some red colour. It seems I have to send 0x04 for each red #pixel, 0x03 for black and 0x00 for white.
Checked the existing #driver and, sure enough, it sends 0x03 and 0x00! This seems to be the right way.
[continues] -
So I looked at the #datasheet (https://files.waveshare.com/upload/2/29/7.5inch_e-paper-b-Specification.pdf) to find what I had to do to display some red colour. It seems I have to send 0x04 for each red #pixel, 0x03 for black and 0x00 for white.
Checked the existing #driver and, sure enough, it sends 0x03 and 0x00! This seems to be the right way.
[continues] -
So I looked at the #datasheet (https://files.waveshare.com/upload/2/29/7.5inch_e-paper-b-Specification.pdf) to find what I had to do to display some red colour. It seems I have to send 0x04 for each red #pixel, 0x03 for black and 0x00 for white.
Checked the existing #driver and, sure enough, it sends 0x03 and 0x00! This seems to be the right way.
[continues] -
8 AI-Based Altcoins To Sell As Investors Rebalance Portfolios For 100X Potential - The cryptocurrency market is undergoing a notable shift, with AI-based altcoins becoming ... - https://coingape.com/markets/8-ai-based-altcoins-to-sell-as-investors-rebalance-portfolios-for-100x-potential/ #priceanalysis #render(rndr) #fetprice #0x0.ai. #grtusd #ocean #agix #arkm #tao
-
Weekend Reads
* Post-quantum RPKI framework
https://arxiv.org/abs/2603.06968
* DNSSEC negative trust anchors
https://quad9.net/news/blog/dnssec-ntas-no-good-compromises/
* AS112 deployment characteristics
https://0x03c0.com/files/pam26-as112-camera-ready-with-notice.pdf
* Geoff Huston on Internet timekeeping
https://www.potaroo.net/ispcol/2026-03/nts.html
* Measuring IX route servers prefix coverage
https://blog.benjojo.co.uk/post/how-far-can-you-get-with-ix-route-servers -
**Integrating Deye EV charger to Home Assistant**TL;DR
It works, somehow, via ha-solarman integration.
Charger type: Deye SUN-EVSE22K01-EU-AC
What works
I managed to integrate 2 entities for now:
- EV charger control power
- Max EV charging power
The process
I’ve started with David Rapan’s ha-solarman integration which works well with my Deye inverter (SUN-12K-SG04LP3-EU).
Then I edited config/custom_components/solarman/inverter_definitions/deye_p3.yaml and added:
#EV test - group: EV Charger items: - name: "EV Charge Control Power" l: 1 class: "power" state_class: "measurement" uom: "W" rule: 1 scale: 1 registers: [0x02C5] icon: "mdi:car-electric" - name: EV Max Charge power alt: EV Max Charge power platform: number class: "power" state_class: "measurement" uom: "W" scale: 1 rule: 1 registers: [0x0104] configurable: min: 0 max: 22000 range: min: 0 max: 22000Restarted HA and those 2 entities appeared in solarman device:
Both entities show the same data as Deye’s app. I can set EV Max Charging Power and it will reflect in the app and the inverter.
About “EV Charge Control Power” entity – Inverter tells the charger what is the max allowed charging power (for example, how much is the solar power excess).
Today it changed like this: (it was cloudy and I had ‘solar only’ enabled):
Don’t mind the initial spike, I wrongly set the scale factor (x10).
I call it partial success.
What doesn’t work (yet)
I still didn’t find modbus register for the most important entity: actual charging power. If exists at all. Maybe there is no mapping from EV charger to modbus registers. I’m communicating with Deye tech support, but I didn’t get the answer yet. Though, they sent me an updated modbus registers document.
I’m still working on EV charger configuration settings (Solar only, Grid off–>Charger Off, Free work, EV port Load/Grid). I found the register in Deye docs, but haven’t implemented yet (some bit manipulation needed):
AddrRegister meaningR/Wdata rangeunitnote259EV_charge_modeR/W[0x0，0xFFFF]
High 8 bits: Off grid SOC Low 8 bits: Bit0:solar energy only Bit1:free work Bit4:EV_charge device connet at Grid port Bit5:EV_charge device connect at LD portAnyone?
If anyone knows which register holds actual charging power value, consumption, charging schedules, please let me know.
https://blog.rozman.info/integrating-deye-ev-charger-to-home-assistant/ #deye #evcharger #homeassistant -
**Integrating Deye EV charger to Home Assistant**TL;DR
Integration of Deye EV charger to HA works (somehow) via ha-solarman integration (EV control power, Max. charging power) and parsing of EV charger local admin web page + Command line HA integration to get realtime charging power and energy.
Charger type: Deye SUN-EVSE22K01-EU-AC, connected to Deye’s inverter via LoRa and Wifi.
What works
I managed to integrate 2 entities via ha-solarman/modbus for now:
Via Solarman/modbus registers:
- EV charger control power
- Max EV charging power
And also (via scraping of EV charger admin web page + Command line HA integration):
- L1 Power
- L2 Power
- L3 Power
The process (reading modbus registers)
I’ve started with David Rapan’s ha-solarman integration which works well with my Deye inverter (SUN-12K-SG04LP3-EU).
Then I edited config/custom_components/solarman/inverter_definitions/deye_p3.yaml and added:
#EV test - group: EV Charger items: - name: "EV Charge Control Power" l: 1 class: "power" state_class: "measurement" uom: "W" rule: 1 scale: 1 registers: [0x02C5] icon: "mdi:car-electric" - name: EV Max Charge power alt: EV Max Charge power platform: number class: "power" state_class: "measurement" uom: "W" scale: 1 rule: 1 registers: [0x0104] configurable: min: 0 max: 22000 range: min: 0 max: 22000Restarted HA and those 2 entities appeared in solarman device:
Both entities show the same data as Deye’s app. I can set EV Max Charging Power and it will reflect in the app and the inverter.
About “EV Charge Control Power” entity – Inverter tells the charger what is the max allowed charging power (for example, how much is the solar power excess).
Today the control power swinged like this: (it was cloudy and I had ‘solar only’ enabled):
Don’t mind the initial spike, I wrongly set the scale factor (x10).
I call it partial success.
What doesn’t work (yet) via solarman/modbus
I still didn’t find modbus register for the most important entity: actual charging power. If exists at all. Maybe there is no mapping from EV charger to modbus registers. I’m communicating with Deye tech support, but I didn’t get the answer yet. Though, they sent me an updated modbus registers document.
I’m still working on EV charger configuration settings (Solar only, Grid off–>Charger Off, Free work, EV port Load/Grid). I found the register in Deye docs, but haven’t implemented yet (some bit manipulation needed):
AddrRegister meaningR/Wdata rangeunitnote259EV_charge_modeR/W[0x0，0xFFFF]
High 8 bits: Off grid SOC Low 8 bits: Bit0:solar energy only Bit1:free work Bit4:EV_charge device connet at Grid port Bit5:EV_charge device connect at LD portAnyone?
If anyone knows which modbus register holds actual charging power value, consumption, charging schedules, please let me know.
Workaround – getting data from EV charger via http / local web interface
Anyways, while waiting for Deye’s support to answer me which modbus registers contain actual charging power, I managed to get these numbers by parsing the EV charger’s web interface.
- I wrote a little curl script to get L1, L2 and L3 power from charger’s web interface. I found they’re hidden besides webdata_power1,2,3 variables:
get_EV_power.sh file:
#!/bin/sh DATA=$(curl -u user:pass -s http://EV_CHARGER_IP_ADDR/status.html) P1=$(echo "$DATA" | sed -n 's/.*webdata_power1[[:space:]]*=[[:space:]]*"\([0-9]\+\)".*/\1/p') P2=$(echo "$DATA" | sed -n 's/.*webdata_power2[[:space:]]*=[[:space:]]*"\([0-9]\+\)".*/\1/p') P3=$(echo "$DATA" | sed -n 's/.*webdata_power3[[:space:]]*=[[:space:]]*"\([0-9]\+\)".*/\1/p') echo "${P1:-0},${P2:-0},${P3:-0}"This script returns power of 3 phases in format X, Y, Z. The reason to put all three values together is to make only one http request instead of 3 (one for each phase).
2. Made it executable: chmod +x get_EV_power.sh
3. I put this script in Home Assistant’s directory /config/scripts/get_EV_power.sh
4. created new Command line sensor in my configuration yaml that executes the script above:
command_line: - sensor: name: EV Charger Raw command: "/config/scripts/get_EV_power2.sh" scan_interval: 10Then I added 3 sensors for each phase’s power and one combined sensor (summary charging power):
template: - sensor: - name: EV Power L1 state: "{{ states('sensor.ev_charger_raw').split(',')[0] | int }}" unit_of_measurement: "W" device_class: power state_class: measurement - name: EV Power L2 state: "{{ states('sensor.ev_charger_raw').split(',')[1] | int }}" unit_of_measurement: "W" device_class: power state_class: measurement - name: EV Power L3 state: "{{ states('sensor.ev_charger_raw').split(',')[2] | int }}" unit_of_measurement: "W" device_class: power state_class: measurement #summary charging power - name: EV Charger Power device_class: power state_class: measurement unit_of_measurement: "W" state: > {{ states('sensor.ev_power_l1') | int(0) + states('sensor.ev_power_l2') | int(0) + states('sensor.ev_power_l3') | int(0) }}5. Created a dashboard for tracking charging power:
6. Added my power sensor to Powercalc, to calculate the energy (using integration) needed for charging (kWh) and let it create some helpers: daily, weekly, monthly, yearly consumption.
7. Added power consumption to my power and energy dashboards:
Conclusion
Anyways, it works, now I can track the (almost realtime) power and consumption of the EV charger, which was the main goal.
The integration of Deye’s EV charger to HA could be easier, if Deye disclosed all inverter’s modbus registers OR provided a documented local API to the EV charger.
I wonder if companies that produce IoT aren’t aware that if they make the access to their devices easy for tinkerers like me, this is free marketing / recommendation for them. I would never recommend devices with closed local access to anyone.
Deye’s openness is so-so. It definitely could be improved. The local access is at least somehow possible, but not well documented and hacky.
https://blog.rozman.info/integrating-deye-ev-charger-to-home-assistant/ #deye #evcharger #homeassistant -
**Integrating Deye EV charger to Home Assistant**TL;DR
It works, somehow, via ha-solarman integration.
Charger type: Deye SUN-EVSE22K01-EU-AC
What works
I managed to integrate 2 entities for now:
- EV charger control power
- Max EV charging power
The process
I’ve started with David Rapan’s ha-solarman integration which works well with my Deye inverter (SUN-12K-SG04LP3-EU).
Then I edited config/custom_components/solarman/inverter_definitions/deye_p3.yaml and added:
#EV test - group: EV Charger items: - name: "EV Charge Control Power" l: 1 class: "power" state_class: "measurement" uom: "W" rule: 1 scale: 1 registers: [0x02C5] icon: "mdi:car-electric" - name: EV Max Charge power alt: EV Max Charge power platform: number class: "power" state_class: "measurement" uom: "W" scale: 1 rule: 1 registers: [0x0104] configurable: min: 0 max: 22000 range: min: 0 max: 22000Restarted HA and those 2 entities appeared in solarman device:
Both entities show the same data as Deye’s app. I can set EV Max Charging Power and it will reflect in the app and the inverter.
About “EV Charge Control Power” entity – Inverter tells the charger what is the max allowed charging power (for example, how much is the solar power excess).
Today it changed like this: (it was cloudy and I had ‘solar only’ enabled):
Don’t mind the initial spike, I wrongly set the scale factor (x10).
I call it partial success.
What doesn’t work (yet)
I still didn’t find modbus register for the most important entity: actual charging power. If exists at all. Maybe there is no mapping from EV charger to modbus registers. I’m communicating with Deye tech support, but I didn’t get the answer yet. Though, they sent me an updated modbus registers document.
I’m still working on EV charger configuration settings (Solar only, Grid off–>Charger Off, Free work, EV port Load/Grid). I found the register in Deye docs, but haven’t implemented yet (some bit manipulation needed):
AddrRegister meaningR/Wdata rangeunitnote259EV_charge_modeR/W[0x0，0xFFFF]
High 8 bits: Off grid SOC Low 8 bits: Bit0:solar energy only Bit1:free work Bit4:EV_charge device connet at Grid port Bit5:EV_charge device connect at LD portAnyone?
If anyone knows which register holds actual charging power value, consumption, charging schedules, please let me know.
https://blog.rozman.info/integrating-deye-ev-charger-to-home-assistant/ #deye #evcharger #homeassistant -
**Integrating Deye EV charger to Home Assistant**TL;DR
It works, somehow, via ha-solarman integration.
Charger type: Deye SUN-EVSE22K01-EU-AC
What works
I managed to integrate 2 entities for now:
- EV charger control power
- Max EV charging power
The process
I’ve started with David Rapan’s ha-solarman integration which works well with my Deye inverter (SUN-12K-SG04LP3-EU).
Then I edited config/custom_components/solarman/inverter_definitions/deye_p3.yaml and added:
#EV test - group: EV Charger items: - name: "EV Charge Control Power" l: 1 class: "power" state_class: "measurement" uom: "W" rule: 1 scale: 1 registers: [0x02C5] icon: "mdi:car-electric" - name: EV Max Charge power alt: EV Max Charge power platform: number class: "power" state_class: "measurement" uom: "W" scale: 1 rule: 1 registers: [0x0104] configurable: min: 0 max: 22000 range: min: 0 max: 22000Restarted HA and those 2 entities appeared in solarman device:
Both entities show the same data as Deye’s app. I can set EV Max Charging Power and it will reflect in the app and the inverter.
About “EV Charge Control Power” entity – Inverter tells the charger what is the max allowed charging power (for example, how much is the solar power excess).
Today it changed like this: (it was cloudy and I had ‘solar only’ enabled):
Don’t mind the initial spike, I wrongly set the scale factor (x10).
I call it partial success.
What doesn’t work (yet)
I still didn’t find modbus register for the most important entity: actual charging power. If exists at all. Maybe there is no mapping from EV charger to modbus registers. I’m communicating with Deye tech support, but I didn’t get the answer yet. Though, they sent me an updated modbus registers document.
I’m still working on EV charger configuration settings (Solar only, Grid off–>Charger Off, Free work, EV port Load/Grid). I found the register in Deye docs, but haven’t implemented yet (some bit manipulation needed):
AddrRegister meaningR/Wdata rangeunitnote259EV_charge_modeR/W[0x0，0xFFFF]
High 8 bits: Off grid SOC Low 8 bits: Bit0:solar energy only Bit1:free work Bit4:EV_charge device connet at Grid port Bit5:EV_charge device connect at LD portAnyone?
If anyone knows which register holds actual charging power value, consumption, charging schedules, please let me know.
https://blog.rozman.info/integrating-deye-ev-charger-to-home-assistant/ #deye #evcharger #homeassistant -
**Integrating Deye EV charger to Home Assistant**TL;DR
It works, somehow, via ha-solarman integration.
Charger type: Deye SUN-EVSE22K01-EU-AC
What works
I managed to integrate 2 entities for now:
- EV charger control power
- Max EV charging power
The process
I’ve started with David Rapan’s ha-solarman integration which works well with my Deye inverter (SUN-12K-SG04LP3-EU).
Then I edited config/custom_components/solarman/inverter_definitions/deye_p3.yaml and added:
#EV test - group: EV Charger items: - name: "EV Charge Control Power" l: 1 class: "power" state_class: "measurement" uom: "W" rule: 1 scale: 1 registers: [0x02C5] icon: "mdi:car-electric" - name: EV Max Charge power alt: EV Max Charge power platform: number class: "power" state_class: "measurement" uom: "W" scale: 1 rule: 1 registers: [0x0104] configurable: min: 0 max: 22000 range: min: 0 max: 22000Restarted HA and those 2 entities appeared in solarman device:
Both entities show the same data as Deye’s app. I can set EV Max Charging Power and it will reflect in the app and the inverter.
About “EV Charge Control Power” entity – Inverter tells the charger what is the max allowed charging power (for example, how much is the solar power excess).
Today it changed like this: (it was cloudy and I had ‘solar only’ enabled):
Don’t mind the initial spike, I wrongly set the scale factor (x10).
I call it partial success.
What doesn’t work (yet)
I still didn’t find modbus register for the most important entity: actual charging power. If exists at all. Maybe there is no mapping from EV charger to modbus registers. I’m communicating with Deye tech support, but I didn’t get the answer yet. Though, they sent me an updated modbus registers document.
I’m still working on EV charger configuration settings (Solar only, Grid off–>Charger Off, Free work, EV port Load/Grid). I found the register in Deye docs, but haven’t implemented yet (some bit manipulation needed):
AddrRegister meaningR/Wdata rangeunitnote259EV_charge_modeR/W[0x0，0xFFFF]
High 8 bits: Off grid SOC Low 8 bits: Bit0:solar energy only Bit1:free work Bit4:EV_charge device connet at Grid port Bit5:EV_charge device connect at LD portAnyone?
If anyone knows which register holds actual charging power value, consumption, charging schedules, please let me know.
https://blog.rozman.info/integrating-deye-ev-charger-to-home-assistant/ #deye #evcharger #homeassistant
